MACHINESAVER / Machine 01 (GW-01) · sensor attached · replace sensor · analysis runs
low
(score 2.96, higher is worse),
calculated 2026-10-06 02:34:17+0000 by analysis
49e94f0e8c9ead81a4b1ae5463073588.
| Level | Score | Calculated | Analysis |
|---|---|---|---|
| low | 2.96 | 2026-10-06 02:34:17+0000 | 49e94f0e8c9ead81a4b1ae5463073588 |
| low | 2.96 | 2026-09-16 16:24:08+0000 | 0a286d5a9c651c4b44909176ce595aeb |
78 measurements; latest 2026-09-07 23:36.
| KPI | Latest value | Points in trend |
|---|---|---|
| rms | 0.31476599421892554 | 78 |
| velocity_rms_10_1000hz | 0.6336010888113903 | 78 |
| velocity_rms_2_1000hz | 0.7837456721424039 | 78 |
| velocity_rms_2_max | 0.7976527925684667 | 78 |
| velocity_rms_10_max | 0.6507250099952393 | 78 |
| peak | 1.0648295898437499 | 78 |
| peak2peak | 2.098 | 78 |
| crest_factor | 3.382924488034566 | 78 |
| kurtosis | 3.0550389389341763 | 78 |
| envelope_rms | 0.21010900134940286 | 78 |
| envelope_peak_score | 0.0 | 78 |
No symptoms reported by the latest analysis.
| Active change | Type | At |
|---|---|---|
| Emerging Mode | emergingMode | 2026-09-07 22:02 |
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.
| Slot | Scalar | Latest | Trend |
|---|---|---|---|
| axis X | acceleration_rms__X (rms) | 0.014 g | |
| axis Y | acceleration_rms__Y (rms) | 0.005 g | |
| axis Z | acceleration_rms__Z (rms) | 0.006 g | |
| axis X | velocity_rms__X (velocity_rms) | 0.61 inch_s | |
| axis Y | velocity_rms__Y (velocity_rms) | 0.356 inch_s | |
| axis Z | velocity_rms__Z (velocity_rms) | 0.406 inch_s |
| Sensor-level | Latest | Trend |
|---|---|---|
| RSSI (untyped) | -35 dBm | |
| battery (battery) | 100 % | |
| temperature (temperature) | 22 C |
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).