A dash screen for the R53 bridge, and an SD log that never stops

The R53 K-line and CAN bridge now drives a touchscreen off its USB-C: live gauges, a 20-second graph, the SD log with New log and Mark buttons, and DME read presets. Underneath, it logs every CAN f...

Build 381

A dash screen for the R53 bridge

The K-line and CAN bridge now drives a touchscreen off its own USB-C, the way the methanol controller drives its round screen: live gauges, a 20-second graph, the SD log with a New log and a Mark button, and presets for what it reads off the DME. Under it, the bridge now logs everything it hears to the SD card, all the time.

5pages, swiped
20 Hzlive values
4screens it runs on
Alwayslogging to SD

Every screen image on this page is rendered from the screen firmware's own page code with simulated data, a third-gear pull at 5,940 rpm and 10.8 psi. They are not photos of the hardware: the new screens haven't arrived yet.

The pages

Swipe left and right. The line at the top says whether the bridge is there and whether the card is recording; the dots at the bottom say which page you're on. Shown on the 2.8″ round LCD.

Round dash screen showing 5940 rpm on an amber arc, AFR 12.3, boost 10.8 psi, coolant 92, timing 20.0 in red
Gauges. RPM large, with an arc that goes amber at 5,800 and red at 6,800. AFR, boost, coolant and timing under it. Timing turns red while the DME is pulling knock retard.
Round dash screen with three traces: RPM, AFR and MAP over twenty seconds through a pull
Graph. Three channels over the last 20 seconds, each on its own scale. Tap it for the next set: RPM, AFR and MAP; RPM, timing and knock retard; AFR and both fuel trims; coolant, intake and battery.
Round dash screen: Logging, file 0042_003.r53raw, 18.3 MB, 14:07, 20.9 GB free, New log and Mark buttons
Log. What the bridge's SD card is doing: the file, its size and time, the space left. New log starts fresh files; Mark drops a numbered mark into the log, so "that pull at the third cone" is easy to find later.
Round dash screen listing four presets, Fuelling outlined in green as the one running, 5 blocks, 23 reads a second
Presets. Which DME blocks the bridge reads over the K-line. The running one is outlined in green, with how many reads a second it's getting.
Round dash screen with a brightness slider at 80 percent, a boost in psi switch, and the bridge's build number
Display. Brightness, boost in psi or MAP in kPa, and the link's health.
Round dash screen before the bridge is connected: every gauge reads two grey dashes, No bridge at the top
No bridge. Before the cable is in, or if the bridge stops talking: every value goes to grey dashes. Nothing on the screen is ever a frozen number from a second ago.

Three screens, one firmware

The same pages run on four Waveshare ESP32-S3 boards. I ordered the three new ones to see which reads best in the car; the 2.1″ is the methanol controller's screen, which I already have.

Gauges page on the 2.8 inch round LCD
2.8″ round LCD. The biggest face, and the easiest port: the 2.1″'s wiring with a different panel and touch chip.
Gauges page on the 1.75 inch round AMOLED
1.75″ round AMOLED. Fits a 52 mm gauge pod, and the methanol screen ran on it before, so its code came back out of git.
Gauges page on the 2.41 inch AMOLED in portrait, RPM bar across the top
2.41″ AMOLED. The brightest of the lot. Portrait for now; landscape once I've seen the real panel.
ScreenPanelBrightnessFits
2.1″ round LCD480 × 480 IPSnot published52 mm pod
2.8″ round LCD480 × 480 IPSnot published60 mm pod or a printed bezel
1.75″ round AMOLED466 × 466700 nits52 mm pod
2.41″ AMOLED450 × 600800 nitsdash top or centre stack

The AMOLEDs have real blacks, so a dark gauge face holds its contrast in daylight far better than a backlit LCD at the same rating. They can burn in a fixed layout, so the whole picture drifts a few pixels every three minutes, the same care the methanol screen's AMOLED build had.

It logs everything, all the time

The bridge has had a microSD slot since the rev C board. Until now it only logged when the app switched it on, and only the channels it decodes. Now it logs whenever a card is in, and keeps all of it.

  • Every CAN frame off the bus, before any filter: the DME, the ABS, the AEM wideband, everything.
  • Every K-line request and reply, whoever asked: the bridge's own rotation, and anything the R53 Logger app asks for (coding reads, fault reads, the lot).
  • The decoded log as before, in TrackEncoder or RaceCapture format, beside the raw file.
  • When the card fills, the oldest logs go. Under 256 MB free, the oldest of the bridge's own logs are deleted until 512 MB is free. It never touches any other file on the card, so a card full of something else stops the logging instead of losing your files.

The raw files are about 25 MB an hour of driving and close every 64 MB, so a 32 GB card holds weeks of it and trims an hour at a time.

Presets

The K-line is slow: every block the bridge reads costs time on the wire. A preset picks which DME blocks get that time. Fewer blocks, each read more often. The CAN bus and the raw SD log record everything whatever the preset.

PresetWhat you seeDME blocks
EverythingEvery block the bridge decodes. The default.18131416191727
FuellingAFR, fuel trims, injector pulse, MAF, MAP.1813171916
Timing & knockIgnition and knock, the knock block read twice as often.18141314
BoostMAP, throttle and RPM, as fast as it goes.1813

A preset is the same kind of block list the app already sets, and goes through the same checks: block reads only, nothing that writes to the car. The bridge keeps it across a restart, and the app can set its own at any time.

Hooking it up

One USB-C cable from the bridge to the screen. The bridge is the USB host and powers the screen, exactly as the methanol controller does with its screen. That means the bridge needs its screen build of the firmware, and in that build its USB-C is the screen's, so the serial console moves to the spare header (D4 and D5). The normal build is unchanged for anyone without a screen.

Both go on from Chrome or Edge with the R53 flasher, build 11 on:

  • The bridge. Plug in the XIAO, press Connect, tick This board drives a dash screen and flash. Update keeps your K-line polling and shift light settings. From then on the USB-C is the screen's, so to flash the bridge again, hold BOOT on the XIAO while you plug it into the computer.
  • The screen. Flash it on its own, not plugged into the bridge. All four have the same chip, so the first time the flasher asks which one it is; after that it knows from the firmware. Not sure whether a 2.41″ is the V1 or V2 board: flash the V2 build, and if it stays dark, the V1.

Where it's at

The firmware builds for the bridge and for all four screens, the link between them is checked by tests on a PC, every page renders as you see above, and it's all on the flasher as build 11 (bridge firmware 381, screen firmware 0.1.0). None of it has run on a screen in the car yet, so keep build 10 on a bridge you rely on until it has. The 2.1″ goes on first, since its panel and touch code are already proven on the methanol controller; the three new screens follow when they land.