ERBESSD / 485848008 · sensor attached · replace sensor · analysis runs
high
(score 19.94, higher is worse),
calculated 2026-09-07 23:44:25+0000 by analysis
87a84329ff09861e6f6f00e6846f5eba.
| Level | Score | Calculated | Analysis |
|---|---|---|---|
| high | 19.94 | 2026-09-07 23:44:25+0000 | 87a84329ff09861e6f6f00e6846f5eba |
| high | 13.38 | 2026-09-07 23:43:32+0000 | e01855475496e087fd93e1cfc747f0ef |
| high | 13.00 | 2026-09-07 23:42:29+0000 | 39bdfc20516b93bff76265714431803a |
90 measurements; latest 2026-09-06 17:40.
| KPI | Latest value | Points in trend |
|---|---|---|
| rms | 3.1877620990758286 | 90 |
| velocity_rms_10_1000hz | 39.277501025223756 | 90 |
| velocity_rms_2_1000hz | 39.285220548516946 | 90 |
| velocity_rms_2_max | 39.31174850431057 | 90 |
| velocity_rms_10_max | 39.30403419125065 | 90 |
| peak | 24.404633872950797 | 90 |
| peak2peak | 26.339404263855577 | 90 |
| crest_factor | 7.655726216214817 | 90 |
| kurtosis | 29.98977239238569 | 90 |
| envelope_rms | 33.80363836103721 | 90 |
| envelope_peak_score | 39.20696604688396 | 90 |
| Symptom | Active | Detections | Possible faults |
|---|---|---|---|
| symptomDominant1x | yes | 30 active of 30 | unbalance (50%), structuralLooseness (30%), resonance (20%) |
| symptomImpacting | yes | 30 active of 30 | outerRaceBearingDamage (50%), mechanicalLooseness (30%), processRelatedImpacting (20%) |
| symptomDominant2xLineFrequency | yes | 30 active of 30 | vfdElectricalNoise (60%), softFoot (30%), looseConnections (10%) |
| Active change | Type | At |
|---|---|---|
| Emerging Mode | emergingMode | 2026-09-05 16:40 |
| Emerging Mode | emergingMode | 2026-09-04 10:40 |
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.
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).