Dashboard
—Data chain
Sensor placement
Units
Errors (last 24 h) Full log in Transfers →
Bridge FTP
The bridge relay is not enabled on this installation.
Only data measured inside the daily windows leaves the bridge on its own. Everything else stays there until the bridge retention deletes it — fetch it here when you need it.
| Range (local) | Kind | Status | Files | Size | Note |
|---|
Transfers
what came off the bridge and what was delivered to CAEmateWindows — last 14 days
Each cell is one window of one unit: fetched % / delivered %, coloured by delivered. The day column holds the unit's total for that day; the bottom row all units together.
Transferred files per day
Events
Recent transfers (hour files)
| Time (UTC) | File | Src files | Rows | Size | Dataset | Took | Status |
|---|
Daily coverage per sensor
Number of source files per device and day (a full day of continuous measurement = 1440 files). Click a day cell to see the hourly detail.
Hourly detail · —
Source files per device and hour (UTC; a fully measured hour = 60 files).
Devices
unit health, measurement control and data retention| Unit | State | Rate | Marker | Samples | Last data / report | Power | Storage | Firmware | Control |
|---|---|---|---|---|---|---|---|---|---|
| loading… | |||||||||
Files and delivery per unit
| Serial | Device name | Status | Last data (UTC) | Age | Files today | Hours sent | Backlog (h) | Errors |
|---|---|---|---|---|---|---|---|---|
| loading… | ||||||||
Data retention
Retention deletes files. The per-hour statistics — min/max/mean and RMS per axis, temperature, coverage and the natural frequencies — are never deleted, so the long-term record of how the bridge behaves outlives the data it came from.
Recent commands
| Time (UTC) | Unit | Action | Result | Detail |
|---|
Measures
hourly acceleration data — statistics, natural frequencies & interactive waveformSelect a device, a day and one of its measured hours.
| Device | Axis | Min [g] | Max [g] | Mean [g] | RMS (AC) [g] | Peak-to-peak [g] |
|---|
Natural frequencies
Strongest spectral peaks of the hour per axis (Welch average of 20 s segments, 0.3–30 Hz). The axis carrying gravity is the vertical one, where the deck's bending modes appear. Q is the peak's sharpness — a high, stable Q is a structural mode; a broad peak is traffic or wind.
| Device | Axis | f₁ [Hz] | Q₁ | f₂ [Hz] | Q₂ | f₃ [Hz] | Q₃ | Segments |
|---|
Vibration events in this hour
Stretches where a 5-second swing exceeded the detection rule (see Vibrations). Their source files are kept out of retention. Click an event to zoom the waveform to it.
| Device | Time (UTC) | Duration | Axis | Peak-to-peak [g] | Hour median [g] | Ratio |
|---|
Offsets shift the curves so a sensor's resting reading sits at zero. Whether they also apply to the data exported to the SFTP is set in Settings. Red bands mark vibration events.
Trend of the selected devices
Hour by hour: the dominant natural frequency on the vertical axis, the vibration level (RMS) and the temperature. A frequency that drifts with temperature is normal; a lasting drop at the same temperature is a loss of stiffness.
Vibrations
detected vibration events — the moments worth keeping in fullEvery built hour is scanned in 5-second windows. A window whose peak-to-peak swing exceeds both an absolute floor and a multiple of the hour's own median is an event; adjacent windows merge. The minute files around each event are exempt from retention, so the raw data behind an impact, a heavy vehicle or a sudden shift survives after the quiet hours have been reduced to statistics.
Events per day
Events
| Time (UTC) | Device | Duration | Axis | Peak-to-peak [g] | Hour median [g] | Ratio | |
|---|---|---|---|---|---|---|---|
| loading… | |||||||
Detection rule
A 5-second window is an event when its peak-to-peak swing reaches the absolute floor and is at least the given multiple of the hour's median swing. The floor stops a still sensor from flagging its own noise (about 4 mg on this installation); the ratio keeps a busy hour from flagging its own traffic. New thresholds apply to hours built from now on — “Re-scan” applies them to the hours already built and updates which files are kept.
FTP explorer
source — raw sensor data ·SFTP explorer
target — transformed data for CAEmate ·Settings
Device names (SN ↔ devname)
The name is written as devname into every newly transferred file. Devices without
a name use their serial number. Already transferred files are not rewritten — switching the dataset re-transfers
everything with current names.
| Serial | Last data (UTC) | Device name | Position | Offset x [g] | Offset y [g] | Offset z [g] |
|---|
Retention of measurement files
How long the full measurement files are kept. This deletes files; the per-hour statistics — min/max/mean and RMS per axis, temperature, coverage and the natural frequencies — are never deleted, so the long-term record of how the bridge behaves outlives the data it was computed from. Minute files around detected vibration events are kept regardless. Takes effect on the next cycle; no restart needed.
Bridge FTP — windows and retention
Data measured inside these daily windows (whole hours, local time) is fetched from the bridge after each window ends and delivered as usual. The rest stays on the bridge for the retention period and can be fetched on demand from the Dashboard. Deletions stay off until you switch them on: then relayed files and files older than the retention are deleted on the bridge.
Exported data
By default every row is exported exactly as the device recorded it. Turning this on applies each device's offsets to the exported accelerations as well, so the partner receives data already corrected for how the sensor sits. It affects hours built from now on; files already delivered are not rewritten, so a dataset can end up mixing both. Offsets are set per device in the table above.
Exchange format
| # | Source | Header | Unit / decimals / value |
|---|
Vibration detection
The thresholds that decide which stretches count as vibration events — and therefore which minute files retention keeps — are set on the Vibrations tab, next to the events they produce.
Language
The language of this dashboard. It is remembered in this browser; exported files and log entries stay in English.
Sync configuration
Read-only. Change values in .env and restart the container
(docker compose up -d).