An end-suction centrifugal pump and its motor, generated from a layout table.
Live readings float beside the parts they belong to; pull it apart; give one bearing a
bad day and watch which card notices.
A newer build is ready.
Checking WebXR…
Close any other tab using the camera. A second camera page silently
stops ARCore ever finding a surface — no error, just nothing.
How long it stands
Detail
What it shows
Running — shaft, coupling, impeller and fan turn; the whole set shakes by an
amount taken from the vibration reading; fluid runs suction → impeller → volute
→ discharge.
Six cards on the drive-end and non-drive-end bearings, the motor, the suction, the
discharge and the seal. They ride their part when it moves.
Inspect pulls it apart, outside first: guard and cowl, then casing and motor, then
cover and impeller, then the bearings out of a split frame. Tap any part for its name.
Alert gives the drive-end bearing a fault. Its ring, its card and the lamp go red.
Nothing else changes — that is the point of a card per part.
Replay the shift runs a whole twelve-hour night past you in under a minute, or
lets you drag through it. The bearing degrades, the discharge is throttled back at
22:00, and at 07:00 a handover note appears — written from what the shift
recorded, not typed in. Jump between events with the ◀◀ and
▶▶ buttons; the ticks on the bar are where something happened.
Two things move during that shift and only one of them is the fault. The
throttling changes flow and head and leaves vibration alone — which is the only
reason “which change mattered?” has an answer. Both had to be captured for it to.
Crossing times are found by scanning the readings, never written down in advance;
node tools/check_history.mjs asserts that on the bench.
Vibration zones follow ISO 10816-3 Group 2 boundaries as illustrative numbers
(2.8 warn, 4.5 alarm mm/s). Readings are simulated; the seam to a
real feed is one function. Tag P-2104-A is fictional.