DE - Comp B
Low Not assessed Motor on Cooling / CL-COMP-B
Not in alert.
Likely faults
| Fault | Likelihood | Seen on |
|---|---|---|
| VFD electrical noise | 60% | stream a22b841c |
| Soft foot | 30% | stream a22b841c |
| Loose connections | 10% | stream a22b841c |
Each axis is analysed on its own; a fault seen on several shows the highest likelihood any of them reports, never a sum.
What changed
No active changes.
Trends
Measurement time 2026-09-27 11:05 to 2026-10-27 13:40 (UTC). ▏went into alert · ▏back to low, cleared or as the evidence faded — from Multiviz's priority history.
Vibration level
How strongly the machine vibrates at this point. A rise here is what usually lies behind an alert: compare it with the alert marks.
Reported by the sensor itself, about every 5 min. MultiViz also computes it from each waveform (about every 1 h); the sensor's value is shown because it comes more often. The two may differ: each uses its own frequency range.
Impacting
Short, sharp impacts, as from a damaged bearing, raise crest factor and kurtosis — often before the overall level moves.
Reported by the sensor itself, about every 5 min. MultiViz also computes it from each waveform (about every 1 h); the sensor's value is shown because it comes more often. The two may differ: each uses its own frequency range.
Computed by MultiViz from each vibration measurement (waveform), about every 1 h.
Computed by MultiViz from each vibration measurement (waveform), about every 1 h.
Operating conditions
What the machine was doing. A change in speed or temperature explains many changes in vibration.
Reported by the sensor itself, about every 5 min.
Nothing recorded for this measuring point yet.
Sensor health
About the sensor, not the machine: a flat battery or a weak signal shows up as gaps in the data.
Reported by the sensor itself, about every 5 min.
Reported by the sensor itself, about every 5 min.
Record a status
Your verdict, recorded here and sent to Multiviz as a clear of the point: its priority drops to low and rises again only on what is detected after now. It counts once Multiviz has accepted the clear.
Axes
| Axis | Priority | Latest measurement | |
|---|---|---|---|
| Stream 8cf5fada | Low | 2026-10-27 11:00 | Analysis and trends → |
| Stream a22b841c | Low | 2026-10-27 11:00 | Analysis and trends → |
| Stream e2e0abd1 | Low | 2026-10-27 11:00 | Analysis and trends → |
History
Priority
Each time the point's level changed, from Multiviz's priority history (bounded by the deployment). A fall to low says how the alert ended: a clear, or the evidence faded.
| Data as of | Priority | What happened | Because of |
|---|---|---|---|
| 2026-10-27 11:00 | Low | — | an analysis |
Clears
Never cleared.