Zexel Consult

ahto42 · Post by **ahto42** » Sat Mar 21, 2009 4:55 pm

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.

Matt · Post by **Matt** » Sun Mar 22, 2009 10:31 am

We dont support that particular engine (Primera CD20T) and have only done Patrols with Zexel Disel ECUs

You will need to enable debug logging and then retry the connection. But wont be able to do that in trial mode since you only get one shot...

ahto42 · Post by **ahto42** » Sun Mar 22, 2009 8:04 pm

It is a littlebit pointless to buy the software only for logging

ill try on

ahto42 · Post by **ahto42** » Sun Mar 22, 2009 11:42 pm

I searched local tuningforum, and found some one, ho knows someone ho have nistune, and he logged for me

Matt · Post by **Matt** » Mon Mar 23, 2009 1:01 am

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?

ahto42 · Post by **ahto42** » Mon Mar 23, 2009 1:30 am

Com 4 is consult, and it manually set in settings. others are bluetooth etc

nissan datascan found E7 and DC are active, but no connection

I know that with handheld consult(in Nissan service) can communicate with my car.

Matt · Post by **Matt** » Mon Mar 23, 2009 9:31 am

update your address file and try firstly adding

INIT_BYTE=&H00E7

then reload address file and try connecting. See if that works

If not then change to

INIT_BYTE=&H00DC

and see if that works

Might be just the different init string

So datascan does init string detection now?

ahto42 · Post by **ahto42** » Mon Mar 23, 2009 10:03 pm

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

Matt · Post by **Matt** » Tue Mar 24, 2009 6:15 am

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

ahto42 · Post by **ahto42** » Tue Mar 24, 2009 7:21 am

Matt wrote: Perhaps try it again from a cold start (ECU off)
we know it

How to do that?

Matt · Post by **Matt** » Tue Mar 24, 2009 9:19 am

when you tried the second attempt, the ECU had already received something from the first attempt and responded differently to that init string

so just power off the ECU, wait 10 seconds and then power back up and retry the second init string again

ahto42 · Post by **ahto42** » Tue Mar 24, 2009 7:41 pm

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.

ahto42 · Post by **ahto42** » Fri Mar 27, 2009 1:35 am

I know that http://www.etas.com/en/products/1273.php worked on my car

Matt · Post by **Matt** » Fri Mar 27, 2009 10:07 am

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