485848003__Z (waveform)

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

Priority

high (score 13.00, higher is worse), calculated 2026-09-07 23:43:24+0000 by analysis 791ff206d0cf7b123e12e7140a9e3a0d.

LevelScoreCalculatedAnalysis
high 13.00 2026-09-07 23:43:24+0000 791ff206d0cf7b123e12e7140a9e3a0d
high 13.00 2026-09-07 23:42:23+0000 7db46217983ffda262769fa68bc33379

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

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

KPILatest valuePoints in trend
rms3.53946958368711430
velocity_rms_10_1000hz56.08836363453132630
velocity_rms_2_1000hz56.08836785229955530
velocity_rms_2_max56.08836785229955530
velocity_rms_10_max56.08836363453132630
peak5.19650590367452930
peak2peak10.35749755317907330
crest_factor1.468159502662333330
kurtosis1.5053725979394330
envelope_rms0.00545426244418953130
envelope_peak_score0.00445901095095455130

Diagnostic findings (GET /sva/791ff206d0cf7b123e12e7140a9e3a0d/symptoms and /changes/active)

SymptomActiveDetectionsPossible faults
symptomDominant2xLineFrequency yes 30 active of 30 vfdElectricalNoise (60%), softFoot (30%), looseConnections (10%)

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).