| Sensor | Status | Latest Reading | Severity | Last Seen | Admin |
|---|---|---|---|---|---|
| No sensors have sent data yet. Check that sensors are powered on and connected. | |||||
- X
- --
- Y
- --
- Z
- --
- Magnitude
- --
- X
- --
- Y
- --
- Z
- --
- Magnitude
- --
- X
- --
- Y
- --
- Z
- --
- Magnitude
- --
- Sensor Type
- --
- Location
- --
- Vendor
- --
- Model
- --
- Available Metrics
- --
- Frequency Source
- --
- Frequency Validation
- --
- Temperature
- --
- Last Update
- --
Data checks
--
| Axis | Latest | Average | Change | Quality |
|---|---|---|---|---|
| X | — | — | — | — |
| Y | — | — | — | — |
| Z | — | — | — | — |
- Latest overall RMS
- --
- Latest X
- --
- Latest Y
- --
- Latest Z
- --
- Mean overall RMS
- --
- Maximum overall RMS
- --
- Standard deviation
- --
- Peak-to-mean ratio
- --
- Sample count
- --
- Last data time
- --
Raw shows each received reading as a point. 1 minute and coarser show the reading distribution as a box plot. Use the range and zoom controls, or drag, scroll, and pinch the chart to explore the data.
What am I looking at?
- Maximum
- Highest reading in the interval.
- Q3
- 75% of readings are at or below this value.
- Median
- Middle reading in the interval.
- Q1
- 25% of readings are at or below this value.
- Minimum
- Lowest reading in the interval.
One box per interval. Taller box = more variation.
Pick up to 4. The first is used for sorting.
CSV save interval only.
- Active recordings
- 0 / 10
- Time recorded
- 0s
- Rows saved
- 0
- File size
- 0 B
- File
- --
Recording details and CSV help
- Live data connection
- --
- Save interval
- --
- Readings not saved between intervals
- 0
- Estimated 30-day file
- --
- All recordings: 30-day estimate
- --
- Delayed file writes
- 0
- Sensors being recorded
- None
- Saved on
- This computer — choose a location when recording starts
server_receive_time_utc_iso8601 is the time this IVSS server received the reading.
sensor_timestamp_raw is the sensor's original timestamp. sensor_timestamp_meaning explains how to interpret it.
Units use spreadsheet-safe text: um, degC, and m/s^2.
- Sensor Messages
- --
- Live Stream
- --
- Selected Sensor
- --
- Sensor State
- --
- Data Quality
- --
- Readings per Second
- --
- Readings on Screen
- --
- Readings Thinned Out
- --
- Waiting to Process
- --
- Bad Readings Received
- --
- Last Reading Time
- --
- Recorder
- --
Pattern Recognizer
Live vibration vs. your taught patterns.
Nothing taught yet.
Patterns are outdated. Learn them again.
An administrator sets this up in Pattern Setup.
- Match
- --
- Confirmed by
- --recent checks
- Next check
- ----
How close is each recorded pattern?
How the result was decided
- Match
- How closely the live vibration fits a recorded pattern. It looks at the vibration level and at how it changes over time.
- Confirmed by
- The shown result only changes after several checks in a row agree, so one noisy reading cannot flip it.
- Unknown pattern
- The vibration does not resemble anything recorded. That can mean a new fault, or a normal condition nobody has recorded yet.
- Ambiguous
- Two recorded patterns fit almost equally well, so the system will not pick one.
What is a “pattern”?
Abnormal / unrecognised pattern is automatic - never add it as a label. Pattern recogniser training requires at least 1 label and 20 samples per label.
How do I record a good example?
Why does this matter?
What happens?
Signals Used For Learning
Which signals should I pick?
Changing signals clears examples.
Matching
What do these settings do?
Sensitivity changes need re-learning.
Settings version: -- | Last saved: -- | Sync: offline