MUR Software
On this page
How to set up and use the team's software outside the autonomous stack, starting with wireless telemetry and the mur-voir dashboard.
This section covers software the whole MUR team uses, not only Autonomous. So far that’s wireless telemetry, which gets data off the car while it drives, and mur-voir, the dashboard you watch it in.
How wireless telemetry works
Section titled “How wireless telemetry works”A Raspberry Pi on the car reads both CAN buses and the BMS. It does three things with that data:
- It records everything to its SD card as MF4 files, one file per minute. Recording carries on when the network drops.
- It sends a selection of signals live over the car’s cellular modem to a backend server in Azure. Anyone on the MUR tailnet can watch them in mur-voir.
- It uploads each finished MF4 file to the backend, which archives it in Azure Blob storage.
Car CAN buses ──┐ ┌── everything ─────── SD card (MF4 files) ├── Raspberry Pi ──┤BMS ────────────┘ ├── live selection ─── cellular ── backend ── mur-voir └── finished MF4s ──── cellular ── backend ── Azure archiveAn older pair of XBee radios can also send a smaller selection straight to a laptop at the track. That link doesn’t need internet access.
Which page you need
Section titled “Which page you need”| You want to | Read |
|---|---|
| Watch live data, or open a recorded log | mur-voir dashboard |
| Set up the Pi, run it on the car, or get its logs | Telemetry Pi |
| Receive data over the XBee radios, or stream it to Marple | Radio link |
Source code
Section titled “Source code”- mur-voir is the dashboard, a fork of AdvantageScope. It’s public.
- Wireless-telem holds everything that runs on the Pi, the radio base station and the Azure backend.
- mur-msgs holds the DBC files that define every CAN signal, and the live telemetry API.
Wireless-telem and mur-msgs are private. You need to be in the Melbourne-University-Motorsports GitHub organisation to open them.