eZ Navi Delete Project
 

I have been working on a way to delete the factory Navi in my ‘09 370Z while still retaining AC control that did not involve replacing the CAN based AC Amp, modifying existing wiring harnesses, or running new wires to the ECU and fuze box. My proof of concept is shown here. It is a plug-n-play solution to custom navi delete installations using the existing wiring harness. Just last week, the prototype went out for fabrication. I hope to start initial testing early next month. The cartoon below illustrates the current capabilities.

https://i.imgur.com/rU71Tnv.png

The above attempts to show the full capability of the interface, not a specific use case. Typically, only a subset of the functionality would be utilized in a custom Navi Delete installation depending on the type of installation being done, but any or all combinations could be used (with the exception of multiple AC controllers). There is a port for the base model dial AC control module, steering wheel control signals, user out, a Bluetooth module, and two connectors to interface with the wire harness via the connectors that went to the stock HU and control panel.

• Dial Control Connector- Base model AC control module interface
• Steering Wheel Control Connector- Steering wheel control signals from resistive switch network
• User Out Connector - Breaks out potentially useful signals from the wiring harness to be used in custom stereo installs and custom expandability
• Bluetooth - Wireless data interface with apps running on custom HU or Tablet installs

Installations using the base model AC dial controls can be implemented by purchasing a used (or new if you hate money…) dial control module (~$45 on eBay) and making the wiring adapter that connects the dial control module to the interface board (~$5 in parts).

Installations using app based AC control can be implemented using the Cardroid app developed by Fred as seen in this video and the project can be found here. Fred is currently working on a new version of his app that allows for customized control and status layouts and sounds like the perfect solution to these types of custom builds. We have been in contact and are maintaining commonality in our projects so that his app will be compatible with this hardware.

Can you make something that retrains the stock Nav -AC controls and Stereo?

I'm building a Ipad Mini kit to cover the stock screen and keypad controls with the ability to slide out to get to access the stock screen when i need to. The only purpose it will serve me is just to see the HVAC condition and see the volume indicator. If i can get those AC controls/Volume indicator on the ipad then i wouldn't need to have access to it at all.

Perhaps I am missing something because it sounds like if you wouldn't need to access the the stock Navi screen anymore, there is no point to keeping the stock system, right? Why not just remove it and install a modern aftermarket solution? You could install an aftermarket HU with the base model controls and have a tablet mount where the stock screen used to be similarly to other implementations.

What you are proposing with the stock Navi control panel can be done, but would take significant effort as the Infotainment CAN protocol would have to be reverse engineered and the interface would have to be redesigned, and this wouldn't really buy you anything other than using the stock Navi controls to get status on an app.

The eZ Navi Delete system has a data packet format (compatible with Cardroid) it is outputting over the Bluetooth with a type that describes the AC state and the updated Cardroid app would allow for this information to be displayed on the device. Running on an Apple device might complicate things as the Cardroid app is Android based.

i think you are right. I've been trying to work around the stock stereo for so long that the tablet is the last missing piece for me.

How much do you plan to sell?

Subscribed. Can't wait for this. I have been itching to remove my 09 stock navigation unit for a while. Let me know if I can do anything to help out with your progress.

I haven't really figured out how I would make this available to those interested yet. I was always planning on making the firmware and design files available on GitHub for anyone to implement on their own after I confirmed a fully working revision. I realize that soldering this thing could be intimidating. There would have to be significant interest to make the cost feasible to have a low volume assembly done (manual assembly is a bit tedious), but perhaps I could manage...


Just got my PCB's yesterday. Planning on assembling and initial testing this weekend! Hopefully, I will have results after Easter.

https://i.imgur.com/3jxQxZc.jpg

More to come...

Hardware is assembled and working (for the most part). A few hardware tweaks are being considered for the next iteration. The current firmware also has untested code that will need to be refined, but works! I wanted to get more testing done this weekend, but blanked on the fact that it's Easter (Happy Easter everyone!) and the Sharks game 6 tonight.... So I may be unable to focus on useful testing... ::insert drinking emoji here::

https://i.imgur.com/RQGgPpM.jpg

Sweet! I love canbus integration. I don't have factory navi, but may try to add it

Ok, i don't know if i'm missing something but we have been able to delete OEM navi for a long time now, without a need for anything custom...

Hi
as my english is not 100% accurate, tell me if I correctly understood : this PCB allows you to remove the OEM navi (display, buttons, radio) but to keep the AC amplifier. Then just have to add the 3 buttons AC controller to be able to continue to use the AC.
This allows you to display AC functions on an android device.

I'm correct ?

You are half correct.

Yes - there is a way to delete the OEM Navi which was accomplished by swapping out the CAN based AC Amp and replacing it with a base model AC Amp. (which I know you know about because I am familiar with the work you and others have contributed to and done in this area :tup: )

No - the because the above method requires you to add pin connections to existing harnesses to make the connections needed for the base model AC Amp, splice into existing wiring harnesses, and run new wire to the ECU and fuse box.

This solution is designed to be a plug-n-play adapter to the stock wiring harnesses of a Navi based car, maintain CAN Bus AC status and control, and open options for AC control/status on custom apps. A base model AC dial control module can connect directly to this interface, or control can be received from an app in "Tesla" style conversions that remove all physical controls. I am trying to make it as universal as possible and expandable to support future custom build ideas that are linked to the CAN Bus.

In fact, I was planning on pairing this with the Joying 9.7" Android HU, which I see someone is attempting right now!!!! EXCELLENT!

http://www.the370z.com/diy-section-d...ure-heavy.html

Really interested to see how their install ends up! I was thinking of going with the horizontal version (better UI IMO) but I really like to see how it actually fits.

:tup:
Yes, that is one possible configuration. The intent is that you can also control the AC without the physical button through an app on a "tesla" style install if that is the build you are attempting. So, you can control through 3 dial module from base model Z, or through an app. There would be a specific firmware for the desired configuration, but the hardware platform would support it all. Either configuration would also allow for AC status on the app.

It was a while ago that i did this but all i had to do was add a pin to the connector, no splicing into harness

From the current Navi Delete thread I posted that involved swapping the CAN AC Amp and running new wire:

These are things I wanted to avoid in addition to running new wire to the ECU and fuse block. A big part was also wanting to provide a way to integrate status/control into custom apps.

Update - HW Test
 

New PWA and current firmware are working (for the most part). I have a few bugs to work out with the timing and proper interpretation of the Mode form the CAN bus. Also, I have more work to do on the Bluetooth interface. There are things that need to be done on the app side as well that are being examined to complete that feature.

*please ignore all the blue test/debug wires headders... :shakes head:
https://i.imgur.com/jooUb7r.jpg

Illumination in action:


Operation in action: (I dont have my debug screen available, but the changes in airflow can be heard)


:usa::usa::usa: