100 Series NAV Delete – True Standalone HVAC Solution (OEM+)

Enthusiast Level vs. OEM Level

  • Enthusiast

    Votes: 21 21.0%
  • OEM

    Votes: 79 79.0%

  • Total voters
    100
  • Poll closed .

This site may earn a commission from merchant affiliate
links, including eBay, Amazon, Skimlinks, and others.

And which one of those includes the removing of the theft screen upper unit at the top of the bezel? It'd be like triple din hole.
 
Last edited:
I’m sincerely interested in this as the climate controls/screen/stereo are the one aspect of my ‘06 LX that truly makes it seem like a 20 year old vehicle. I also truly appreciate all of the effort being put in here and very much hope that this will be brought to fruition.

That being said, I have some questions. Starting with the flanking PWR and TUNE knobs - will those be rendered useless, or will the PWR knob just basically activate the antenna? Secondly, will the LCD temp display bar still be active and correspond with the new HVAC controls? And the biggest question- what happens with the entire upper area? I haven’t seen a good option for nesting any aftermarket double din head units in that location.

Overall, again, I seriously appreciate the work being put in here, but I just don’t want to end up with a slew of non-functional buttons and knobs or create a lot of further problems to solve.

At this point I’ve actually begun listening to music on cassette tapes again to try to embrace the antiquated factory audio setup…
 
And which one of those includes the removing of the theft screen upper unit at the top of the bezel? It'd be like triple din hole.
If only there were folks on this forum capable of capturing, modeling, and reproducing complex geometry with a variety of manufacturing methods!

😉

20260419_163823.webp


At this point we've got the cassette bay scanned, and the cassette module itself scanned & parametrically modeled. I owe @Anarchy some files and drawings so he can provide them to an industrial designer, but I'll play around with some control layouts as well!

Whenever I get time that is... Between a new baby, the day job, Lumberjack Engineering, and now this quest to modernize the HVAC controls & radio unit, it's busy around here!
 
If only there were folks on this forum capable of capturing, modeling, and reproducing complex geometry with a variety of manufacturing methods!

😉

View attachment 4130771

At this point we've got the cassette bay scanned, and the cassette module itself scanned & parametrically modeled. I owe @Anarchy some files and drawings so he can provide them to an industrial designer, but I'll play around with some control layouts as well!

Whenever I get time that is... Between a new baby, the day job, Lumberjack Engineering, and now this quest to modernize the HVAC controls & radio unit, it's busy around here!
What timeframe do you realistically expect to have a unit I can buy? Again, I’d be happy to be a test pilot. My system is almost dead and I do t have many options on having a functioning stereo. Let me know if I can do anything to help. I’ve bought a good amount of Lumberjack Engineering products so I l kw your good at what you do!
 
Something like this has been on my todo list for a few years, as a 100 series specific extension to my existing sensor data acquisition node (analog temps, pressures, EGT etc) I use in my 80, but I've had other priorities while my 100's were down. I have a Teyes unit in one 100 and it uses CAN bus to communicate with the HVAC successfully. The implication being that CAN bus communication with the HVAC is proven possible and is robust and the message ID's, format and behaviour are already known. That 100 will be back in use within weeks and I'll be looking into that and what other lost information is available because I'd really like to recover the security light as a minimum but the fuel usage and other interesting information must also be available.

Not trying to hijack, just a heads up that there's a good source of information on using CAN bus messages to communicate with the HVAC already. My interest is purely technical / personal usage.
 
There are a few different approaches out there that make things work, but they’re typically doing it by sitting in the middle and translating or approximating behavior. The direction here has been to keep the original control logic intact and interact with the system in a way that preserves how it actually operates.

That same principle carries across the rest of the network as well. The intent is to avoid removing or disrupting anything the vehicle expects to see, and instead work alongside it so other systems continue to behave normally without side effects.

On the project side, the system architecture is now defined, MCU and I/O are locked, and the PCB schematic has gone through a full pass and revision cycle. The majority of review items have been implemented, including updates to MPX handling, pin assignments, signal naming, and debug access.

Progress is steady and it’s now in a much more concrete, build-ready phase than it was even a couple weeks ago.
 
I have this uncomfortable feeling that I'm the only one not fully grasping the end-game.

This? Retaining the OE HVAC buttons (now dead) and keeping the OE inside temp (dead?), outside temp and clock?

Screenshot 2026-05-01 at 1.53.50 PM.webp


Is the expectation that a new head unit and bezel/surround will eliminate the remaining HVAC buttons?
What happens to the vertical stack of buttons - Map, Dest, Menu, etc., in that scenario?

Side note: does it make sense to have a "companion" thread for this thread - for bezels, head units, etc. - to keep this thread clean?
 
Last edited:
I have this uncomfortable feeling that I'm the only one not fully grasping the end-game.

This? Retaining the OE HVAC buttons (now dead) and keeping the OE inside temp (dead?), outside temp and clock?

View attachment 4132854

Is the expectation that a new head unit and bezel/surround will eliminate the remaining HVAC buttons?
What happens to the vertical stack of buttons - Map, Dest, Menu, etc., in that scenario?

Side note: does it make sense to have a "companion" thread for this thread - for bezels, head units, etc. - to keep this thread clean?

I believe the intent is to be able to remove everything above the Security/Temp display, allowin for the use of aftermarket trim kits that will fill the gap left and affix a new head unit.
 
Quick update.

The PCB schematic is now in final review before layout.

Core architecture is locked. MCU pinout has been checked against the prototype setup. LED strategy is confirmed. Temp/fan encoder plan is set.

The last open item is the factory dimmer signal. The physical rheostat is already on the way for bench verification. Once that input is confirmed, the schematic gets locked and the board moves into layout.

We are very close to turning this into real hardware.

One clean feature made it in too: the temp knob push function will handle Fahrenheit/Celsius selection, so there is no need for another button.

The deeper this project gets, the more obvious it becomes why nobody has released a clean solution yet.
The truck does not need another android screen pretending to be Toyota, it needs the missing factory control behavior restored at the protocol level.
 
Quick update.

The PCB schematic is now in final review before layout.

Core architecture is locked. MCU pinout has been checked against the prototype setup. LED strategy is confirmed. Temp/fan encoder plan is set.

The last open item is the factory dimmer signal. The physical rheostat is already on the way for bench verification. Once that input is confirmed, the schematic gets locked and the board moves into layout.

We are very close to turning this into real hardware.

One clean feature made it in too: the temp knob push function will handle Fahrenheit/Celsius selection, so there is no need for another button.

The deeper this project gets, the more obvious it becomes why nobody has released a clean solution yet.
The truck does not need another android screen pretending to be Toyota, it needs the missing factory control behavior restored at the protocol level.
This is gonna be a game changer. Cant wait to see the final product! Thanks for all the hard work thats been put into this.
 
Quick update.

The PCB schematic is now in final review before layout.

Core architecture is locked. MCU pinout has been checked against the prototype setup. LED strategy is confirmed. Temp/fan encoder plan is set.

The last open item is the factory dimmer signal. The physical rheostat is already on the way for bench verification. Once that input is confirmed, the schematic gets locked and the board moves into layout.

We are very close to turning this into real hardware.

One clean feature made it in too: the temp knob push function will handle Fahrenheit/Celsius selection, so there is no need for another button.

The deeper this project gets, the more obvious it becomes why nobody has released a clean solution yet.
The truck does not need another android screen pretending to be Toyota, it needs the missing factory control behavior restored at the protocol level.
Great news! Thanks for sorting the temp C/F option!
 
Very cool - we do a ton of OEM non-Navi conversions (instagram: LandCruiserSociety).

Would be happy to provide the oem parts to see if you can mirror and 3d print replacements for the upper din section so that you can leverage this new control unit with OEM like goodies.

OEM used kits are getting harder to find and now cost almost $1500 usd for just the parts. 🤪

AR500096.webp


AR508723.webp
 
I'm thinking a custom bezel (similar to the above) with some provisions for accessory mounting (RAM mounts, switch panel mounts, etc) above would be snazzy...
 
Very cool - we do a ton of OEM non-Navi conversions (instagram: LandCruiserSociety).

Would be happy to provide the oem parts to see if you can mirror and 3d print replacements for the upper din section so that you can leverage this new control unit with OEM like goodies.

OEM used kits are getting harder to find and now cost almost $1500 usd for just the parts. 🤪

View attachment 4135713

View attachment 4135714

Question about this… the security strip is different in the nav/non nav version… so I assume we will need to source the non nav version.
Will that part simply plug in and work?
Or is there a facia adapter that can utilise the nav security strip without the need buy a different one?

The one above is the only style I’ve found when searching.

Of course someone with the skills could 3d scan and turn it in to a cad design then there’s the option to adjust it to fit double din or larger screens (Kenwood 8-10inch displays) then simply use a 3d printer. I realise there’s a lot of work doing this…just starting to learn this myself.
 
Quick update.

The PCB schematic is now in final review before layout.

Core architecture is locked. MCU pinout has been checked against the prototype setup. LED strategy is confirmed. Temp/fan encoder plan is set.

The last open item is the factory dimmer signal. The physical rheostat is already on the way for bench verification. Once that input is confirmed, the schematic gets locked and the board moves into layout.

We are very close to turning this into real hardware.

One clean feature made it in too: the temp knob push function will handle Fahrenheit/Celsius selection, so there is no need for another button.

The deeper this project gets, the more obvious it becomes why nobody has released a clean solution yet.
The truck does not need another android screen pretending to be Toyota, it needs the missing factory control behavior restored at the protocol level.

Are you willing to share any technical details of which connections you're using, data protocol and packet formats?
 
Back
Top Bottom