I initiate my project when I wish to monitor the engine live data on a handy manner three month ago. I trust that Arduino is a fit to my objective. I currently monitor namely, vss, rpm, coolant temp, battery, btdc, inj. time, throttle, O2, AAC, MAF, A/F, A/Fself, DTC up to 13 data due to 20x4 LCD size restriction. I have also developed two separate Arduino programs designated to the idle adjustment (in which the AAC valve enables to be off by Consult. It is cool rather than the manner to take the connector off physically) as well as the fault code.
The project is done.
My main system is to utilize Arduino with LCD as the following system diagram.
Consult 14 pin connector <-> Inhouse I/F adapter (like the commercial product Nissan-14) <-> Arduino with LCD. An alternative one is Consult 14 pin connector <-> Inhouse I/F adapter <-> USB-TTL adapter(CH340) <-> free software like ecuTalk or Conzult in Windows10. I use Python partially to check status of serial data transmission (Tx,Rx), which is much easier to deal with than Arduino. I have no plan to develop a system based on Python. While Pyhton does not matter os, I use Ubuntu mainly.
The other day I browse the R32 service manual, I come across the Hicas diagnostic test. I wish to simulate the test conducted by Consult so as to watch the rear wheel turning actually.
This is a present stage to struggle the initialization.
I agree with you as well that both ECU need to be initialized. Because the Hicas ECU (wire #5? in trunk) connects to the engine ECU (passenger side) and it finally goes to Consult 14 pin outlet. The engine ECU is initialized first and then followed by the Hicas ECU. I think that both ECU should be on a standby condition concurrently.
Once the Hicas ECU is initialized, no any other significant issues on the following events would remain.
No. I have no idea on Nistune, etc at all.
That's all. How comes in this morning trial?