I'm so excited for this project. I want to be the very first buyer for my '07 LX!
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
This site may earn a commission from merchant affiliate
links, including eBay, Amazon, Skimlinks, and others.
I would buy a standard double din radio and put that in. The touch screen feedback with OEM screen is still laggySuccessful command injection with the HVAC command set mapped and confirmed under controlled testing.
Now validating full standalone operation without the OEM NAV/MFD connected, including startup behavior and power-cycle stability.
The goal remains:
OEM-style physical controls
No screen
Plug-and-play
Curious to hear from those following the development:
- If you could completely remove the factory NAV screen, run any head unit you want, and relocate HVAC to OEM-style physical controls in the lower dash - would you choose that over current Teyes/Grom/Android options?
- And honestly, what would make you NOT buy something like this?
Appreciate the feedback. This community has been a big part of shaping the direction.
Will someone 3D print the appropriate buttons to fit the HVAC controls in place of the cassette deck and head unit?Update 3/29/2026:
Out of the “prove it can talk” phase and into the “prove it’s stable and repeatable” phase.
Over the last stretch, did a full pass on state behavior so we understand what the system expects over time (not just a single button press), and built a replay/regression harness so we can run changes against known-good captures and catch regressions early. This is the unsexy part, but it’s separates a real solution from something that only works on a bench.
Power-interface testing/startup behavior is also being treated as a hard requirement (clean wake, clean power-cycle, no boot delays that leave you without HVAC for 30 seconds, etc).
Where this is headed next:
- tighten state tracking (fan/mode/recirc/defrost interactions)
- bind that into the physical control strategy
- keep validating OEM “feel” items (defrost logic, compressor behavior, fault/indicator behavior)
AI Generated for visualization:
View attachment 4111663
Watching your progress with a high level of optimism!Successful command injection with the HVAC command set mapped and confirmed under controlled testing.
Now validating full standalone operation without the OEM NAV/MFD connected, including startup behavior and power-cycle stability.
The goal remains:
OEM-style physical controls
No screen
Plug-and-play
Curious to hear from those following the development:
- If you could completely remove the factory NAV screen, run any head unit you want, and relocate HVAC to OEM-style physical controls in the lower dash - would you choose that over current Teyes/Grom/Android options?
- And honestly, what would make you NOT buy something like this?
Appreciate the feedback. This community has been a big part of shaping the direction.
I just put a Sony XAV-AX6000 in my daily and I love it. A little on the pricey side, but works really well and has the ability to turn the screen completely off with a push of a physical button which is a must for me.Watching your progress with a high level of optimism!
Bought an '03 LX470 in Dec with 105k miles on it, and have been baselining since.
Getting to acceptable separate entertainment and HVAC suites has cost me hours at Google U, with nothing but
disappointment in the current offerings.
Was thinking Grom or T'Eyes, but if I could purchase a solid NAV delete, I would go Kenwood or Sony, Alpine for the head unit in a heartbeat!
The only things that come to mind to prevent a purchase, of course cost (at some dollar point I accept what is there or inferior alternatives)
and maybe uncertain supply/support.
So I think cost is gonna be a big factor here. When I think OEM quality I think thousands of dollars on par with purchasing the nav delete hardware. I’ve got a Teyes unit right now that’s inelegant for AC control but I’m not sure it’s $1000 inelegant. But if a better solution were in the range of $200-$400 then I’d be more tempted.Update 4/1/2026:
I know there’s a lot of questions but I'm going to avoid those for now.
The focus has moved into making the system behave correctly, consistently, and predictably across all operating conditions.
Current work is centered around:
Validating full HVAC state behavior across the network
Implementing command retry logic and queuing for stability
Transitioning from raw protocol work into defined hardware architecture
We’re moving from software -> hardware design.
That means locking in:
MCU selection
Pin mapping
Interfaces (MPX, power, IO, etc.)
Also separating critical functions properly:
Dedicated UART (runtime comms / logging)
Dedicated JTAG/SWD (debug / programming)
Architecture decisions are now being locked in... this is where mistakes get expensive later, so it’s being done carefully.
There’s also a decision being made on what this ultimately becomes:
OPTION A - Enthusiast Product
Small batch
Slight imperfections acceptable
Faster to market
Lower cost
OPTION B — OEM-Level Product (direction this is heading)
High polish
Bulletproof reliability
Clean hardware architecture
The path forward is:
1. PCB Design + Prototyping
Schematic → PCB layout
First prototype boards
Iteration / revisions
2. Hardware Validation
Real vehicle testing
Electrical noise, voltage spikes, edge cases
3. Enclosure + Physical Controls
Buttons, knobs, fitment
Achieving OEM-level feel
4. Manufacturing Strategy
Low volume vs mass production
Assembly decisions
Supply chain
This is the part of the project that’s less visible, but far more important than the earlier stages.
I added a poll; Curious how many people would actually choose OEM-level over fast-to-market.
More to come.
It is good to see this type of planning. One you cross the Chasm it moves to becoming an industry standard solution.Update 4/1/2026:
I know there’s a lot of questions but I'm going to avoid those for now.
The focus has moved into making the system behave correctly, consistently, and predictably across all operating conditions.
Current work is centered around:
Validating full HVAC state behavior across the network
Implementing command retry logic and queuing for stability
Transitioning from raw protocol work into defined hardware architecture
We’re moving from software -> hardware design.
That means locking in:
MCU selection
Pin mapping
Interfaces (MPX, power, IO, etc.)
Also separating critical functions properly:
Dedicated UART (runtime comms / logging)
Dedicated JTAG/SWD (debug / programming)
Architecture decisions are now being locked in... this is where mistakes get expensive later, so it’s being done carefully.
There’s also a decision being made on what this ultimately becomes:
OPTION A - Enthusiast Product
Small batch
Slight imperfections acceptable
Faster to market
Lower cost
OPTION B — OEM-Level Product (direction this is heading)
High polish
Bulletproof reliability
Clean hardware architecture
The path forward is:
1. PCB Design + Prototyping
Schematic → PCB layout
First prototype boards
Iteration / revisions
2. Hardware Validation
Real vehicle testing
Electrical noise, voltage spikes, edge cases
3. Enclosure + Physical Controls
Buttons, knobs, fitment
Achieving OEM-level feel
4. Manufacturing Strategy
Low volume vs mass production
Assembly decisions
Supply chain
This is the part of the project that’s less visible, but far more important than the earlier stages.
I added a poll; Curious how many people would actually choose OEM-level over fast-to-market.
More to come.
Voted for OEM-level! Imagining both the price and speed to market being no more than 2x the enthusiest level.Update 4/1/2026:
I know there’s a lot of questions but I'm going to avoid those for now.
The focus has moved into making the system behave correctly, consistently, and predictably across all operating conditions.
Current work is centered around:
Validating full HVAC state behavior across the network
Implementing command retry logic and queuing for stability
Transitioning from raw protocol work into defined hardware architecture
We’re moving from software -> hardware design.
That means locking in:
MCU selection
Pin mapping
Interfaces (MPX, power, IO, etc.)
Also separating critical functions properly:
Dedicated UART (runtime comms / logging)
Dedicated JTAG/SWD (debug / programming)
Architecture decisions are now being locked in... this is where mistakes get expensive later, so it’s being done carefully.
There’s also a decision being made on what this ultimately becomes:
OPTION A - Enthusiast Product
Small batch
Slight imperfections acceptable
Faster to market
Lower cost
OPTION B — OEM-Level Product (direction this is heading)
High polish
Bulletproof reliability
Clean hardware architecture
The path forward is:
1. PCB Design + Prototyping
Schematic → PCB layout
First prototype boards
Iteration / revisions
2. Hardware Validation
Real vehicle testing
Electrical noise, voltage spikes, edge cases
3. Enclosure + Physical Controls
Buttons, knobs, fitment
Achieving OEM-level feel
4. Manufacturing Strategy
Low volume vs mass production
Assembly decisions
Supply chain
This is the part of the project that’s less visible, but far more important than the earlier stages.
I added a poll; Curious how many people would actually choose OEM-level over fast-to-market.
More to come.