Privacy settings

We use Microsoft Clarity to understand how CALC is used — only if you agree. Necessary cookies keep the app working (sign-in, security, free-quota enforcement) and are always active.

Dlubal CALCDocumentation

Search documentation…

Search titles, headings and page text

Open Dlubal CALC

Reading results

Reading a result is where a wrong number is easiest to produce and hardest to notice, so this page is mostly about being specific.

Always name the load case

Warning

A result request without a load case can return values across every calculated loading at once. The number that comes back is then a maximum over cases you may not have meant to combine, and it looks exactly like the answer you wanted.

Say which one:

Give me the maximum bending moment in member 3 for load case 2 only.
Try in Dlubal CALC
For load case 1, list the support reactions at every support, and say which support
carries the largest vertical force.

Ask for the location, not just the value

A moment without a position is hard to check against a hand calculation. Ask for both:

Maximum moment in the rafter with the x-position where it occurs, load case 2.

Cross-check one value by hand

The habit worth keeping: pick one result you can verify with a formula and check it before you trust the rest.

Example: a single span of 6 m under a uniform 12 kN/m should give roughly qL²/8 = 54 kNm at midspan. If RFEM says 54, the model is behaving. If it says 27 or 108, the load or the system is not what you think it is.

Sign conventions

Signs follow the axis orientation the model runs with, and the assistant states that orientation after it creates or changes geometry. If a reaction comes back with an unexpected sign, check that line before you go looking for a modelling error: Working with RFEM covers it.

Where to go next