Ini Failed skyline r33 gtst z32 (EU) ecu nistune "solved"

Discussions related to Nissan DataScan I software (NDSI) for Android
Post Reply
R.J. Bijsterbosch
Posts: 13
Joined: 07 Jun 2013, 16:28

Ini Failed skyline r33 gtst z32 (EU) ecu nistune "solved"

Post by R.J. Bijsterbosch »

Hello,

I have a Nissan skyline r33 gtst with a Z32 ECU and nistune. I have bought the OBD1 Nissan consult BT 14 PIN DDL Diagnostic Interface From OBD Innovations as mentioned on the NDS Page. I'm trying to connect the adapter with the OBD 1 & 2 Lite Android app but it's not working.
[attachment=1]20160928_192817.jpg[/attachment]


I have tried the NDS1 lite app and after connecting it says ini failed (see screenshot) Also there is no possibility to scroll through the tabs. Screen is frozen.
[attachment=2]Screenshot_2016-09-28-17-00-20.jpg[/attachment]

I have tried the NDS2 lite app and there is a connection but the screen is also frozen and there is no possibility to scroll the tabs.
[attachment=0]Screenshot_2016-09-28-17-00-01.jpg[/attachment]

Am i doing something wrong. Can somebody help me out?
Attachments
NSD2 lite
NSD2 lite
Screenshot_2016-09-28-17-00-01.jpg (32.77 KiB) Viewed 3549 times
Adapter
Adapter
20160928_192817.jpg (44.83 KiB) Viewed 3549 times
NSDI lite
NSDI lite
Screenshot_2016-09-28-17-00-20.jpg (33.52 KiB) Viewed 3549 times
Last edited by R.J. Bijsterbosch on 28 Oct 2016, 06:02, edited 2 times in total.
R.J. Bijsterbosch
Posts: 13
Joined: 07 Jun 2013, 16:28

Re: Nissan skyline r33 gtst z32 (EU) ecu nistune

Post by R.J. Bijsterbosch »

I have done some research and found out the following.
[attachment=0]Connections checked.jpg[/attachment]


I have checked the cables from the ECU to the OBD connector in my car. See Attached picture. These look ok.
[attachment=1]OBD1 connector car.jpg[/attachment]


Pin 1 = (-) black/silver ECU channel 60
Pin 2 = (CLK) yellow/red/silver ECU channel 31
Pin 3 = Yellow/green/silver
Pin 4 = Pink silver
Pin 5 = N/A
Pin 6 = N/A
Pin 7 = N/A
Pin 8 = (RX) Brown/yellow/silver ECU channel 21
Pin 9 = (TX) yellow silver ECU channel 22
Pin 10 = N/A
Pin 11 = N/A
Pin 12 = N/A
Pin 13 = (CHK) yellow/purple/silver ECU channel 47
Pin 14 = (IGN) blue/white/silver ECU channel 45

I have cheched the pins on the adapter and the wiring inside the adapter. See Attached picture.
What stands out is that pin 13 and 14 are not connected and pin 7 is not connected @ the ECU. Is this correct or not.
[attachment=2]Adapter-connectorboard.jpg[/attachment]

Pin 1 = (-) black ECU channel 60
Pin 2 = (CLK) Brown ECU channel 31
Pin 3 = N/A
Pin 4 = N/A
Pin 5 = N/A
Pin 6 = N/A
Pin 7 = red N/A @ ECU ???????
Pin 8 = (RX) orange ECU channel 21
Pin 9 = (TX) yellow ECU channel 22
Pin 10 = N/A
Pin 11 = N/A
Pin 12 = N/A
Pin 13 = N/A ??????? ECU channel 47
Pin 14 = N/A ??????? ECU channel 45

Please Advise,

Best regards,

R.J. Bijsterbosch
Attachments
Connections checked.jpg
Connections checked.jpg (86.53 KiB) Viewed 3542 times
OBD1 connector car.jpg
OBD1 connector car.jpg (25.18 KiB) Viewed 3542 times
Adapter-connectorboard.jpg
Adapter-connectorboard.jpg (38.47 KiB) Viewed 3542 times
Tom
Site Admin
Posts: 647
Joined: 09 Dec 2011, 19:17

Re: Nissan skyline r33 gtst z32 (EU) ecu nistune

Post by Tom »

It sounds like exactly the same problem you are having with the USB adapter and the Windows software. Since you have changed the ECU and you are having problems with both adapters maybe there are issues with your wiring. It could be something simple like the HICAS wiring shorting out the communication lines.

I would suggest bypassing the the car wiring and connecting directly to the pins on the engine ECU.
R.J. Bijsterbosch
Posts: 13
Joined: 07 Jun 2013, 16:28

Re: Nissan skyline r33 gtst z32 (EU) ecu nistune

Post by R.J. Bijsterbosch »

Ok Tom, i will try that.

I will also measure the MHZ signal on pin 2 from the adapter, because i thought that the signal came from the ecu.

I followed the cables from the obd connector in my car to the ecu and there is nothing connected inbetween.

Hicas is not in the car anymore and is controled by a seperate ecu i think. I will sort this out.

What is reminding me wright now is that the HKS speedlimit defenser is still wired in the ecu wiring. It was used when i had the OEM r33 ECU. Me and my tuner let it in because it was not causing any problems with the Z32 nistune ecu. Its not needed anymore because there is a speedlimit defenser in the nistune software. I will remove the HKS speedlimit defensor to get the wiring in it's original state. Maybe this device is causing interference.

I also still have the OEM r33 ECU, i can try to install this one and than look what happens. When idling this can't be a problem. If the problem is solved then it's the Z32 ecu that's causing the problem. If the problem still exists than i have to look further and uninstall the HKS speedlimit defenser.
R.J. Bijsterbosch
Posts: 13
Joined: 07 Jun 2013, 16:28

Re: Nissan skyline r33 gtst z32 (EU) ecu nistune

Post by R.J. Bijsterbosch »

Can you tell me which of the following signals are needed to let the adapter/nissan datascan work.

CLK
RX
TX
CHK
IGN
Ground (-)
Tom
Site Admin
Posts: 647
Joined: 09 Dec 2011, 19:17

Re: Nissan skyline r33 gtst z32 (EU) ecu nistune

Post by Tom »

You need the following:
CLK
RX
TX
IGN
Ground (-)
R.J. Bijsterbosch
Posts: 13
Joined: 07 Jun 2013, 16:28

Re: Nissan skyline r33 gtst z32 (EU) ecu nistune

Post by R.J. Bijsterbosch »

OK thanks,

I have the "Nissan Consult Bluetooth adaptor with optional OBDII interface. Available from www.obdinnovations.com." as mentioned on the NDS site. I've checked the pins on the adapter and cable connector who connects with the circuitboard inside the adapter. As mentioned in my earlier post.

There are 14 pins and 5 wires as you can see in the photo.

Pin 1 = (-) blackwire goes to ECU channel 60 (-)
Pin 2 = (CLK) Brown wire goes to ECU channel 31
Pin 3 = Not connected
Pin 4 = Not connected
Pin 5 = Not connected
Pin 6 = Not connected
Pin 7 = red wire goes nowhere because the pin on the carconnector is not wired. ???????
Pin 8 = (RX) orangewire goes to ECU channel 21
Pin 9 = (TX) yellow wire goes to ECU channel 22
Pin 10 = N/A
Pin 11 = N/A
Pin 12 = N/A
Pin 13 = Not connected ??????? ECU channel 47
Pin 14 = Not connected ??????? ECU channel 45

So Pin 14 the IGN connection needs to be wired inside the adapter but there is no wire/connection. Could this be the problem.

I also checked if there is a jumper between pin 7 and 14 but there is no jumper
I placed some pictures of the board inside the adapter so that you can see if this is ok.

I also found a topic on the NDS forum about a white wire that needs to be soldered in. This wire is not in my adapter. See link below.
viewtopic.php?f=12&t=340&sid=a181a5a83d ... a5f1c17563
Attachments
20161006_204235.jpg
20161006_204235.jpg (60.35 KiB) Viewed 3526 times
20161006_204211.jpg
20161006_204211.jpg (71.4 KiB) Viewed 3526 times
Adapter-connectorboard.jpg
Adapter-connectorboard.jpg (38.47 KiB) Viewed 3528 times
Tom
Site Admin
Posts: 647
Joined: 09 Dec 2011, 19:17

Re: Nissan skyline r33 gtst z32 (EU) ecu nistune

Post by Tom »

Do the lights come up on the adapter? If they do then the power is getting to the adapter and IGN pin doesn't need to be wired.

The "white wire" fix was only required for the first version adapters. This was fixed by the manufacture in the later versions. You can test this by checking the CLK pin for the clock signal.
R.J. Bijsterbosch
Posts: 13
Joined: 07 Jun 2013, 16:28

Re: Nissan skyline r33 gtst z32 (EU) ecu nistune

Post by R.J. Bijsterbosch »

Problem is solved. Both the adapter and NDSI app are working.

I got a faulty adapter and had to do the white wire fix.

The problem was that there was no CLK signal on Pin 9 communicating with the ECU.

With the wire fix there is communication with the ECU now.

I want to thank tom for his technical support on this.
Post Reply