mur-voir dashboard
On this page
Install mur-voir, connect it to the car's live telemetry, and open recorded logs.
mur-voir is the team’s telemetry dashboard. It shows live data from the car and opens recorded logs. It’s a fork of AdvantageScope, the FRC log viewer.
Install
Section titled “Install”Download the installer for your computer from the latest release:
| Computer | File |
|---|---|
| Mac with Apple silicon | mur-voir-<version>-mac-arm64.dmg |
| Mac with Intel | mur-voir-<version>-mac-x64.dmg |
| Windows | mur-voir-<version>-win-x64.exe, or win-arm64 on ARM laptops |
| Linux | mur-voir-<version>-linux-x86_64.AppImage, or linux-arm64 |
The apps aren’t signed, so your computer warns you the first time you open one. On a Mac, drag mur-voir into Applications. If macOS refuses to open it, run this and try again:
xattr -cr /Applications/mur-voir.appOn Windows, if SmartScreen blocks the installer, choose More info, then Run anyway.
You can also skip the install and use the browser version.
Join the MUR tailnet
Section titled “Join the MUR tailnet”The live data is only reachable from inside the MUR tailnet. That’s a private network run on Headscale, an open-source server for Tailscale clients. You join it with the normal Tailscale app, logged in to MUR’s server at https://vpn.melbourneuniracing.com instead of Tailscale’s own.
- Install Tailscale from tailscale.com/download.
- Log in to MUR’s server:
- Mac: hold Option and click the Tailscale icon in the menu bar. Go to Debug → Custom Login Server → Add Account…, enter
https://vpn.melbourneuniracing.com, and click Add Account. - Windows: in PowerShell, run
tailscale login --login-server https://vpn.melbourneuniracing.com. - Linux: run
sudo tailscale up --login-server https://vpn.melbourneuniracing.com. - iPhone or iPad: tap the account icon, then Log in…. Open the options menu at the top right, choose Use custom coordination server, and enter
https://vpn.melbourneuniracing.com.
- Mac: hold Option and click the Tailscale icon in the menu bar. Go to Debug → Custom Login Server → Add Account…, enter
- Your browser opens a page with a command for registering your device. Send it to the MUR Headscale admin, who runs it to let you in.
- Keep Tailscale’s DNS setting turned on, which is the default. The dashboard addresses only work through it.
To check you’re in, open http://mur-base.tailnet.internal:8080/healthz. It should load rather than time out.
The Headscale setup is written up in Headscale’s client guides.
Connect to live telemetry
Section titled “Connect to live telemetry”- Join the tailnet.
- In mur-voir, open File → Connect, or press Cmd/Ctrl+K.
- Choose MUR Telemetry and enter
http://mur-base.tailnet.internal:8080. - Expand the signal tree and drag a signal onto a Line Graph axis. The graph loads up to five minutes of history, then follows the live data.
The window title shows the connection state:
| Title | Meaning |
|---|---|
address (Searching) | mur-voir is connecting. |
address | Connected and receiving data from the car. |
address (No car data) | Connected to the backend, but the car isn’t sending. Check the Pi. |
address (Error) | The connection failed. See troubleshooting. |
If the connection drops, mur-voir reconnects by itself and fills in whatever history the backend still has. Anything the car couldn’t send stays a gap.
Reading signal names
Section titled “Reading signal names”Live signals are named vehicles/<car>/<bus>/<message>/<signal>, all in lower case. For example, motor speed is vehicles/mur27/can0/inv_motorposition/inv_motorspeedrpm. BMS values are under vehicles/mur27/bms/.
can0 is bus 0, the Control bus, and can1 is bus 1, the Telemetry bus. These are bus numbers, not the Pi’s interface names, which are swapped: the Pi reads the Control bus on its can1 interface.
Live values arrive in SI units. Motor speed is in rad/s rather than rpm, temperatures are in kelvin, speeds are in m/s, voltages are in volts and pressures are in pascals. Recorded logs use the DBC’s units instead. BMS values have no units attached.
Use the browser version
Section titled “Use the browser version”There’s a hosted copy at voir.melbourneuniracing.com, so you don’t need to install anything.
- Join the tailnet.
- Open
https://voir.melbourneuniracing.com/. - Connect with MUR Telemetry and the address
https://voir.melbourneuniracing.com. This is the default.
The page loads without the tailnet, but live data doesn’t. If it won’t connect after you join, reconnect Tailscale and restart your browser so it picks up the tailnet’s DNS. Trackside and Video only work in the desktop app.
Open recorded logs
Section titled “Open recorded logs”Open logs with File → Open Log(s). mur-voir reads MF4, candump .log, CSV, JSONL and WPILOG files, and you can select several at once.
The Pi writes one MF4 file per minute of running. Telemetry Pi covers how to get them and merge them into longer files. They hold raw CAN frames, which mur-voir decodes with the DBC files bundled from mur-msgs. To use other DBCs, choose a DBC folder in Preferences.
| Tab | Use it for |
|---|---|
| Line Graph | Signals over time. It has its own time axis, and can plot against lap time or distance instead (both experimental). |
| Trackside | Big readouts for the pit wall, an optional graph of the last 30 seconds, and alarm limits. Always shows the latest data. Desktop only. |
| Track and laps | The GPS track, lap times and lap comparisons, in Map, Laps and Split views. |
| Driver Inputs | Steering, throttle and front and rear brake pressure as bars. |
| Car Dynamics | Front wheel angles and speeds, yaw, acceleration and damper positions on a drawing of the car. |
| Points | A plain 2D plot of one signal against another. |
| Table, Statistics, Console, Video, Metadata | Inherited from AdvantageScope. Video is desktop only. |
Every tab except Line Graph and Trackside shares one timeline. Driver Inputs and Car Dynamics draw the car at the timeline cursor, which follows your mouse.
Set up a layout
Section titled “Set up a layout”A layout is your set of tabs and the signals in them. Save it with File → Export Layout to reuse it. Layouts match signals by their DBC name, so a layout built on live data also works on a recorded MF4.
- Trackside. Drag signals into Tiles. Click a tile’s graph icon to plot it. Click its type icon to set a critical minimum or maximum, and leave it blank for no limit. Active DBC faults show above every tab, even without a tile.
- Track and laps. Assign the lap setup signals, choose the event, and set the start/finish line if needed.
- Driver Inputs and Car Dynamics. These start empty. Drag signals into Sources, then right-click a source to choose what it is. Set the scales for the car: Steering Ratio (default 3.827:1), Wheel Radius (0.203 m), Brake Full Scale (1000 psi), Damper Range (50 mm), Wheelbase, Track and Max Speed.
The SBG IMU is mounted with +X pointing right and +Y pointing back, so three signals need flipping in Car Dynamics. Right-click each source and choose Inverted:
| Car Dynamics source | SBG signal | Setting |
|---|---|---|
| Longitudinal Accel | AccelY | Inverted |
| Lateral Accel | AccelX | Inverted |
| Yaw Rate | GyroZ | Inverted |
mur-voir only asks the backend for signals that are on screen, which keeps the dashboard’s traffic down. It doesn’t change how much the car sends over cellular.
Try it without the car
Section titled “Try it without the car”mur-voir comes with a mock backend that sends made-up car data. You need Node.js 22.18 or newer.
git clone https://github.com/Melbourne-University-Motorsports/mur-voir.gitcd mur-voirnpm cinpm run compilenpm run mock-backend -- --lap-counter --speed 1Then connect mur-voir to http://localhost:8090. Keep --speed 1 if you want laps: at higher speeds every lap is marked invalid.
To run mur-voir from this checkout instead of the installed app, open a second terminal and run:
unset ELECTRON_RUN_AS_NODEnpm startTroubleshooting
Section titled “Troubleshooting”| Problem | What to check |
|---|---|
| Stuck on Searching, or Error | That you’re on the tailnet, that the address is right, and that the backend is running. |
| No car data | The dashboard reached the backend, so the problem is on the car. Check the Pi’s services and its cellular connection. |
| Empty graph | That a signal is on an axis, and that it’s available. A signal can be listed while the car isn’t sending it. |
| No recent history | The backend may have restarted, which clears its history. Live data still shows. |
| A signal in a saved layout stays missing | The signal needs the same DBC name. Signals you’ve derived yourself need assigning again. |
| Browser version won’t connect | Reconnect Tailscale, then restart the browser. |
Report bugs and feature requests on the mur-voir issues page.
More detail
Section titled “More detail”- Cellular telemetry guide: the full connection and layout reference.
- DEVELOPING.md: building mur-voir, its tests, and releases.
- Pi-to-dashboard runbook: how the backend and live API work (private).