How a bearing is selected and checked

How a bearing is selected and checked

How a bearing is chosen for the required loads and, when enabled, checked against EN 1992-1-1 §10.9.5 or DAfStb Heft 600. Left: deformation bearings; right: sliding bearings. Green: requirement met; red: not met. The tool tries bearing lengths and thicknesses until one passes every check. Product checks show their source on a second line; EC2 checks show the condition only. Generated from the calculation code. Pick a unit-test case in the Trace panel to replay its path.

Legend

accepted — meets requirement
rejected — does not meet requirement
a check / decision
start / end
green arrow: check passed
red arrow: check failed
dashed arrow: retry loop
visited by the traced path (badge = visit count)
current step (dashed outline)
heavy arrow: traversed by the path
dimmed: not on the path

The tool automatically tries different sizes until one passes every check (the loop).

Click a check in the diagram to see its clause, meaning and failure reason.

Keyboard

+ / − zoom
0 100%
F fit to screen
↑↓←→ pan
Esc close panels

When focus is in the trace panel:

Space play / pause
← / → previous / next step
PgUp / PgDn forward / back 10 steps
Home / End first / last step

Trace

Pick a case to trace its path.

Values

Quantity	Value	Check	Expected

No values recorded at this step

meets requirement does not meet decision start / end

Rendering diagram…

100%

0 / 0

Node details

Import trace

Paste a trace JSON, choose a file, or drop it anywhere on the page.

To trace a case from the CISTA app: change any field in the studio, open the browser console (Cmd+Option+J on macOS, Ctrl+Shift+J on Windows), run copy(window.__CISTA_TRACE__) and paste the result here.

Trace JSON

Drop trace JSON