Fleet
Devices online
last 2 hoursFrames per minute
Server
Host CPU and memory
last 2 hoursGateway network
in and out, per secondCommand outcomes last hour
Attention
| Status | IMEI | Silent for | Last event | Position | Speed | ACC | Battery | GSM | Frames |
|---|
Engine and power
Notes
Send command
Replies typically take about 6 seconds and can exceed a minute. Sending again repeats the action on the vehicle.
Recent commands
Recent frames newest first
Location
Timeline events, commands and connections together
Alarms newest first
Driver cards card reads, newest first
Live map
Route history
Map tiles load from OpenStreetMap, which means your browser tells them the area being viewed. The positions themselves stay on this gateway.
Command history
| Sent | IMEI | Command | Status | Latency | Reply | Source |
|---|
Multi-device command
Sends one command to every device you select. The same button that asks for a firmware version can reboot a fleet, so pick the devices deliberately and read the report afterwards.
Devices
Command
Report
Previous runs
Forwarder
Forward data to another platform
Pushes decoded data to an external system in the same format the vendor's dispatcher uses. Changes take effect immediately and survive a restart. Turning this on starts sending this fleet's data somewhere else.
Send command results back
When a device answers a command — or fails to — the result is
posted to /pushInstructResponse on the platform's command
service. That is a different service from the one above, on its own port
and with its own token, so it is configured separately here.
Forwarding activity
Live
Each line is one batch. The size column opens the exact JSON sent, for accounts that can manage forwarding.
Failed batches kept on disk so nothing is lost while the platform is down
Users and permissions
Accounts
Add an account
Your password
Anyone can change their own without an administrator.
Recorded video
Find a device
Full-resolution main stream from the SD card, for evidence rather than a quick look. The device caps one request at 60 seconds, so the range is split into one clip per minute per camera — each a separate command, sent a few at a time.
Pick a recording on the right to play it here.
Historical logs
Decoded events, one file per device per day. Finished days are stored gzipped and are decompressed here for reading; the archive is never modified. Card-swipe events carry driver identity, so treat what you see here as personal data.