485848004__Y (waveform)

ERBESSD / 485848004 · sensor attached · replace sensor · analysis runs

Priority

low (score 0.00, higher is worse), calculated 2026-09-07 23:43:25+0000 by analysis 3a3ba0c9ce9aeffe979411d0cdf3d501.

LevelScoreCalculatedAnalysis
low 0.00 2026-09-07 23:43:25+0000 3a3ba0c9ce9aeffe979411d0cdf3d501
low 0.00 2026-09-07 23:42:24+0000 000a4a253a4dab3c1773ef882e7b0534

Latest KPI values (GET /mpoints-streams/{id}/kpi)

30 measurements; latest 2026-09-04 05:40.

KPILatest valuePoints in trend
rms6.33798075099634830
velocity_rms_10_1000hz7.019115686220315530
velocity_rms_2_1000hz7.0191156868310830
velocity_rms_2_max7.84476500071860930
velocity_rms_10_max7.84476500017212730
peak21.2039026847542730
peak2peak41.56563903285578530
crest_factor3.345529675428717430
kurtosis2.84405435712559130
envelope_rms75.9012196561618730
envelope_peak_score0.030

Diagnostic findings (GET /sva/3a3ba0c9ce9aeffe979411d0cdf3d501/symptoms and /changes/active)

SymptomActiveDetectionsPossible faults
symptomHaystack yes 30 active of 30 lubricationIssue (60%), processRelatedLoading (40%)

Trend scalars at this measuring point (GET /scalars/?sensor_id=…)

Scalars are keyed by sensor, not by stream — the link to this measuring point is derived: this point's streams name their active sources, the sources name their sensors, and the sensors' scalars are what you see here. The scalars page draws the whole chain.

The sensors at this measuring point report no trend scalars.

rpm: outside 600–3600 RPM an rpm scalar is required — without it, bearing analysis silently returns nothing.

Embedded analysis view

This iframe is the one thing the browser loads straight from the deployment. Its URL carries only the stream id — no credential — and this page's own Content-Security-Policy: frame-src header is what allows the frame (the deployment sets no framing restriction of its own).