AustinSupra
Member
- First Name
- Bryan
- Joined
- Oct 16, 2025
- Threads
- 1
- Messages
- 6
- Reaction score
- 6
- Location
- Austin texas
- Car(s)
- 2026 Supra
- Thread starter
- #1
Thread title: Factory Supra HUD tachometer project — working V1, progress and next milestones
Hey everyone—wanted to share a project I’ve been working on: adding a live tachometer and shift lights to the Supra’s factory windshield HUD.
My car is a 2026 GR Supra 3.0 Premium, six-speed manual, running NBT Evo NBTevo_T24081I. The idea is an S2000-inspired RPM display that uses the existing HUD hardware and makes room for factory navigation and radio functions.
We now have a working V1 installed on my car.
What’s working
What we’ve actually verified
The current November 18 baseline survived an iDrive restart, and I completed a drive with no visible tachometer loss. The post-drive checks matched the installed files and configuration, recorded six clean handoffs to factory functions, and showed no new permanent application fault records.
That doesn’t mean the app ran as one uninterrupted process: it deliberately stops and resumes drawing around factory activity. The goal is for that behavior to feel seamless while preserving factory priority.
Earlier live testing also helped resolve unwanted symbols, flashing, color mapping, and graphics cleanup.
The difficult part
Drawing a tachometer was only part of the challenge. Making it coexist with the car’s own display behavior has required much more work.
This uses a shared factory guidance path, so it isn’t a completely independent HUD layer. We’ve had unsuccessful startup-integration attempts and head-unit restarts during development, followed by factory recovery. Those results shaped the current startup, cleanup, fault logging, and rollback approach.
I’ve been using ChatGPT Work to assist with research, code, test analysis, and documentation, alongside actual vehicle testing. Passing software tests is useful, but I’m keeping that separate from what has really been demonstrated in the car.
Next milestones
The source and compiled V1 components are on GitHub, but this is not a universal, plug-and-play installer.
So far, the verified installation is one car on one firmware version. The public download still requires a verified vehicle drawing profile, the target car’s own startup configurations, and compatibility checks. Another owner’s factory configuration should never be copied blindly.
There is a documented rollback path, and the original factory executables were not replaced. Firmware flashing or downgrading is not being proposed as a way to make other cars compatible.
The shift-light thresholds are display settings, not validated engine limits. Extended reliability and every possible factory warning interaction remain open testing items.
Project links
I’ll use this thread to share progress, actual HUD photos/video, problems we encounter, and milestone results. If you have experience with NBT Evo, QNX, or the factory HUD’s navigation/radio behavior, I’d be interested in comparing notes.
Hey everyone—wanted to share a project I’ve been working on: adding a live tachometer and shift lights to the Supra’s factory windshield HUD.
My car is a 2026 GR Supra 3.0 Premium, six-speed manual, running NBT Evo NBTevo_T24081I. The idea is an S2000-inspired RPM display that uses the existing HUD hardware and makes room for factory navigation and radio functions.
We now have a working V1 installed on my car.
What’s working
- Live engine RPM from the factory engine-speed feed.
- Large RPM digits, a 24-segment tachometer bar, and five orange/red shift lights.
- Native operation on the head unit—no connected Mac or laptop needed during normal operation.
- Automatic startup, with a settling period and checks that navigation and radio are idle before drawing.
- Removal of the custom graphics when factory navigation or the radio selector needs the display, followed by automatic return once those functions release it.
What we’ve actually verified
The current November 18 baseline survived an iDrive restart, and I completed a drive with no visible tachometer loss. The post-drive checks matched the installed files and configuration, recorded six clean handoffs to factory functions, and showed no new permanent application fault records.
That doesn’t mean the app ran as one uninterrupted process: it deliberately stops and resumes drawing around factory activity. The goal is for that behavior to feel seamless while preserving factory priority.
Earlier live testing also helped resolve unwanted symbols, flashing, color mapping, and graphics cleanup.
The difficult part
Drawing a tachometer was only part of the challenge. Making it coexist with the car’s own display behavior has required much more work.
This uses a shared factory guidance path, so it isn’t a completely independent HUD layer. We’ve had unsuccessful startup-integration attempts and head-unit restarts during development, followed by factory recovery. Those results shaped the current startup, cleanup, fault logging, and rollback approach.
I’ve been using ChatGPT Work to assist with research, code, test analysis, and documentation, alongside actual vehicle testing. Passing software tests is useful, but I’m keeping that separate from what has really been demonstrated in the car.
Next milestones
- Repeated startup testing: overnight sleep/wake and repeated cold starts on this exact final build.
- Longer endurance testing: more runtime and more navigation/radio transitions.
- Broader factory-function checks: warning and assistance-display interactions that haven’t yet been covered.
- Better documentation: clearer setup, compatibility checks, troubleshooting, and restoration instructions.
- Future features: explore configurable display settings and additional data such as boost, after the V1 baseline has more validation. Those features are not currently implemented.
The source and compiled V1 components are on GitHub, but this is not a universal, plug-and-play installer.
So far, the verified installation is one car on one firmware version. The public download still requires a verified vehicle drawing profile, the target car’s own startup configurations, and compatibility checks. Another owner’s factory configuration should never be copied blindly.
There is a documented rollback path, and the original factory executables were not replaced. Firmware flashing or downgrading is not being proposed as a way to make other cars compatible.
The shift-light thresholds are display settings, not validated engine limits. Extended reliability and every possible factory warning interaction remain open testing items.
Project links
- Source, overview, and software preview
- Current verified status
- Exact November 18 V1 baseline and limitations
I’ll use this thread to share progress, actual HUD photos/video, problems we encounter, and milestone results. If you have experience with NBT Evo, QNX, or the factory HUD’s navigation/radio behavior, I’d be interested in comparing notes.
Sponsored