Zexel Consult
Moderator: Matt
Zexel Consult
Hi
I have a Nissan Primera with diesel engine(CD20T) with zexel ECU(23710-2J610) and 14 pin gray connector.
When i try to connect its says "Consult not connected". The com port is correct.
I have Nissan consult interface
and a serial to USB adaptor, I can read petrol engines, no problems, but i cant connect to my car with any software.
I have a Nissan Primera with diesel engine(CD20T) with zexel ECU(23710-2J610) and 14 pin gray connector.
When i try to connect its says "Consult not connected". The com port is correct.
I have Nissan consult interface
and a serial to USB adaptor, I can read petrol engines, no problems, but i cant connect to my car with any software.
I searched local tuningforum, and found some one, ho knows someone ho have nistune, and he logged for me
- Attachments
-
- nistune.log
- (10.5 KiB) Downloaded 212 times
how many COM ports do you have...
12:34:59.421 COM3 found
12:34:59.734 COM4 found
12:34:59.734 COM5 found
12:34:59.734 COM6 found
12:35:02.468 COM7 found
It only attempted connection to COM4 so you must have it in manual COM port selection? Is that the one for your consult port?
It didnt get a response to that port after sending FF FF EF initialisation tring with 200ms delay between each character
Unless that string needs to be slower for your ECU?
12:34:59.421 COM3 found
12:34:59.734 COM4 found
12:34:59.734 COM5 found
12:34:59.734 COM6 found
12:35:02.468 COM7 found
It only attempted connection to COM4 so you must have it in manual COM port selection? Is that the one for your consult port?
It didnt get a response to that port after sending FF FF EF initialisation tring with 200ms delay between each character
Unless that string needs to be slower for your ECU?
Yes
Datascan ecu finder bombs the ecu with ff ff xx and found DC and E7
With DC nistune found standart consult, but nothing else
Datascan ecu finder bombs the ecu with ff ff xx and found DC and E7
With DC nistune found standart consult, but nothing else
- Attachments
-
- nistune DC.log
- (116.09 KiB) Downloaded 159 times
-
- nistune E7.log
- (9.11 KiB) Downloaded 174 times
DC was the correct init byte to use
Perhaps try it again from a cold start (ECU off)
But what I see so far...
- All read register attempts responded with no valid registers found
- ECU Identification command did not stream out an ID
Not too sure what this ECU is doing but doesn't look like consult the way we know it
Perhaps try it again from a cold start (ECU off)
But what I see so far...
- All read register attempts responded with no valid registers found
- ECU Identification command did not stream out an ID
Not too sure what this ECU is doing but doesn't look like consult the way we know it
I tryed to turn ignition key to LOCK, wait for 10 sec and then tryed again. Same result. A blank consult registers screen poped up and thats all.
- Attachments
-
- nistune DC.log
- (297.24 KiB) Downloaded 237 times
I know that http://www.etas.com/en/products/1273.php worked on my car
whats happening is that the READ REGISTER command is not getting any valid displayable registers back from the ECU
it may be using a different CONSULT-II command we dont know about to retrieve the registers
not much i can do unless you get the original CONSULT-II terminal, and put a serial port sniffer between the ECU and terminal and then log all the traffic both ways unfortunately
it may be using a different CONSULT-II command we dont know about to retrieve the registers
not much i can do unless you get the original CONSULT-II terminal, and put a serial port sniffer between the ECU and terminal and then log all the traffic both ways unfortunately