Dashboard
—Sensor placement
Waldschlößchenbrücke — plan view (Buchholz side on the left). Assign devices to positions in Settings; click a sensor to open its measurements.
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).
Transferred files per day
Events
Devices
| Serial | Device name | Status | Last data (UTC) | Age | Files today | Hours sent | Backlog (h) | Errors |
|---|
Recent transfers (hour files)
| Time (UTC) | File | Src files | Rows | Size | Dataset | Took | Status |
|---|
Devices
unit health, measurement control and data retention| Unit | State | Rate | Marker | Samples | Last data / report | Power | Storage | Firmware | Control |
|---|---|---|---|---|---|---|---|---|---|
| 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 & 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] |
|---|
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.
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. Takes effect on the next cycle; no restart needed.
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.
Sync configuration
Read-only. Change values in .env and restart the container
(docker compose up -d).