Consult 1 Port acting weird on my R32 GTR

[qthegaijin]

Hope someone may have an answer who browses here. Before going the full on Link ECU route or sending the car off to UP Garage here in the states, I wanted to do some checks on my 94 R32 GTR using the consult port.

TLDR: Consult Port not connecting to ECU no matter what I tried, even splicing direct into the cable and hardwiring the USB adapters.

I currently have cable wise:

- 1x PLMS Consult Cable

- 1x Ebay Consult Cable

- Nisscan/ECUTalk/Nistune/Conzult Software

Before my tests:

- Made sure all software and drivers were correct

- Made sure that the Power and RX lights were showing that they were functioning from the correct Windows COM port (for both cables)

- Read all of the Nistune connection error docs

- Made sure there was continuity between the ECU and the Consult Port on ECU Pins:

--Pin 21: RX (Yellow/Green Stripe)

--Pin 22: TX (Yellow)

--Pin 31: Clock (Yellow/Red Stripe)

--Pin 45: Ignition (Black/Red)

--Pin 50: Ground (Black)

- My ECU is STOCK as far as I am aware, with the Nissan stickers still sealed around it.

- Checked that the Clock is at the specified 153Khz rate on both adapters

-Baud rate of 9600

Tests done with Both cables

Test 1:

- Plugged in Consult Cable to Port in Fuse Box, Plugged into laptop, open up ECUtalk, select COM port for the device (usually 3 or 4 for my system)

- Hit connect, the RX light blinks, then nothing.

Test 2:

- Plugged in Consult Cables etc etc, Opened up Nissan Datascan, selected the correct COM Port, and then hit FIND ECU.

- Nothing is registered when it does the scan, nor when I select connect.

Test 3:

- Got fed up trying all the different methods and driver reinstalls/trying different COM ports so I decided to chop the TX/RX/CLK wires right by the ECU and add quick connects. (with Ignition and Ground coming from a separate spot that one of my gauges is hooked up to)

- Even when Plugged directly into the harness right next to the ECU, the ECU does not respond or send out a TX signal to the adapter.

At this point I don't know what else do to try and get the ECU to respond to my adapters. Any ideas? Anyone else had any luck with Datascan and their Consult Port?

[joshuaho96]

My stock R33 just works with Nissan Datascan. Does it blink out error codes if you use the jumper wire method?

[GTSBoy]

It's a better than even chance that someone has hamfisted it in the past and burnt tracks in the ECU. Open the ECU and look closely (magnifying glass) at whatever tracks you can see that run from the Consult related connector pins. There might be something visible. Of course, there might not. There's pull up resistors and other doohickies involved in those connections that can get trashed without showing much in the way of burn.

The Consult related tracks could also conceivably have been damaged in an unrelated incident. It's not unknown for injector or ignition drivers to get destroyed, taking out tracks. It might have been repaired - but only repairing the things needed to make it run the engine. There's a million scenarios like that.

[qthegaijin]

Cool. I will take a look at the ECU after trying out the Jumper method to see if the dash lights blink out the codes.

[GTSBoy]

On 3/14/2022 at 11:56 AM, qthegaijin said:

trying out the Jumper method to see if the dash lights blink out the codes

R32 ECUs have a switch/potentiometer accessible through a small hole in the side of the case that is used to trigger fault code display. How to use it is covered in the workshop manual. You basically have to just turn it all the way one way then all the way back, or something equally simple (and long forgotten, in my case, having replaced the whole thing with an R34 ECU).