Can we get the Map trace feature fixed too for the Maxima?? Could then more easily compare our ECU's

[QUOTED FROM NISSAN DATASCANSITE
10. Map trace

A real time trace of a position on the map. This function is only available for z32 300zx cars at the moment. If the real time TP value address is known the function can be set up to work on any Consult I Nissan car. ]

 

my advice to you sir, would be to email the gent or call him. you have the convienence of actually living in the same city as the programers of NDS, so i'd recommend you to them to help us all out with some direct testing. have you sucessfully connected your 95 ecu to NDS with a blazt cable?

 

ME?? Are you sure, the address on the nissan datascan site - nissandatascan@curl.com.AU(Australia) .. I live in Auckland, New Zealand... I'm mad keen if hes in NZ but I think hes not.

I have the PLMS cable (http://www.plmsdevelopments.com/consult_if.shtml) running with datascan on a 1994 (A32) Cefiro.. local car club having a meeting so will run it on different years. All cables are essentially the same just sending serial converted to consult protocol.. its detecting the ECU type thats the issue.

 

My bad mate, I mixed up the companies. It's blazt that is based in Auckland.

"Blazt was founded by Jason Dear and Mike Thompson in Oct 2004 and is located in Auckland, New Zealand."

 

We're pretty much stuck at nothing at this point. I guess I'll go back to checking fuses etc. The thing that gets me is the fact that Iansw's serial based Nprobe and Nprobe software worked fine on my car.

 

will be a hard task unless you can get serial port functionality (then u can just use the ecutalk pocket pc software with a serial consult interface). do you have a serial port on ur laptop? should have got the serial interface if you did, since the usb one involves virtual com ports and other signal conversions, although most people have no issues. usb consult is also useless to hook up to pda (unless it has host usb support and the usb chip has drivers for win ce).

as to your main problems, whats the serial number on ur ecu? (23710-xxxxx) does the ecu look like its been tampered with at all? remapped? its possible they could have messed up the consult code perhaps (although unlikely).

does your ecu support odb2? i didnt think many ecu's support both consult and obd2 - the reason the consult port is there is due to other control units (a/t, air con, hicas, etc) using it. when they hooked up to consult at nissan, was it consult 1 or 2? which port did they hook it up to (consult or obd?) did they say it was connecting to the ecu, or was it connecting to other control units?

do you always get the same 3 init things responding with obdscantech each time you try it? (this might rule out serial data issues where FF FF EF is being read as FF FF E7 - ie, 7 instead of F is a single bit that has been misread

Peter

 

If he has a 95 it will be Consult I protocol. Consult II started in 2000. The Consult port is not just for the other control units, it is certianly used for the ECU (probably the most important, generally).

Also, most of the 95's, to my knowledge are OBD2 compliant as well.

 

All 4th gens are OBDII


Any news Kenji?