Yeah 8-12 would be fine (I know how it is working nights) but since I have my daughter I would prefer if you came out to my place in Milwaukie. I'll PM you my number.

 

Okay so D-Bo and I met up, and we did some cancelling out. Here's the results:

First I tested out the BlaZt cable on D-bo's 97. nothing from datascan or odbscantech, which I had tried to reconfigure (might explain it) but I ran EcuTalk and it worked perfectly. None of the 3 programs work on my car.

So next, we measured the ohm resistance of D-Bo's Port and Mine. D-Bo's top left read 37, mine was something like 9? same result with the other 3 pins that had a reading. So I've figured out now that my car's consult port is not giving same readings as D-Bo's, which works with ECUtalk. What would be my next coarse of action for diagnosing the problem, and attempting to solve it. Is the consult port fused?

D-Bo suggested I try going into Nissan and kindly asking them to try out their consult on my car (to see if they'll just give it a whirl) Then to their suprise if it doesn't work, they can reveal to me what needs to be done to fix it.

We took D-Bo's generic OBDII scanner and tested it out on my car. We pulled the maf to throw a code and sure enough it worked.

 

Those readings were in ohms too right Kenji? The ECUTalk was pretty cool to watch but I wish we could have come up with a more definitive answer for you.

 

Went to Beaverton Nissan this morning, hooked up to their consult. They said it read fine. Now I'm even more stumped. I'm wondering if maybe the consult two uses different pins?

 

WTF???? Now I'm really confused...

 

He said the different resistance could be as simple as Nissan using a different gauge wire between 95 and your 97.

 

I suppose everyone stopped reading this thread but the two of us D-Bo.. either that or noone knows what's wrong.

 

So the readings aren't telling us anything then...I wonder if the difference could be between 95-96 & 97-99? Need to test on another 95-96 and see what comes up. Although Jime is a 95 too, I wonder if what the variables are between you two?





Anybody else have thoughts/opinions?

 

I can't figure this one out. I believe you have the BlazT and I have the PLMS one but I do know other guys have the BlazT and it works fine.

 

I still haven't ruled out the consult port as being faulty. Not until someone can verify that the Nissan Consult II uses the same pins or that it can read around it. The blazt cable and the other consult I cable's I've seen only utilize 3 pins on the entire port. Where's SR20DEN?

 

Kenji. Did you get your consult stuff to work on any of the NW maximas/nissans??

 

Kenji they are using the Consult I on your car, not Consult II. The nomenclature is just the communication protocol, the hardware tool they use is the same.

Jime: you think the OBDScanTech (Nissan) works better than DataScan? I can't use the DataScan on my 98, that's one of the features I liked about ScanTech, the ability to read the ECU and change the initialization hex numbers so that it would talk to different years.

 

It worked great on Cliff Clavins 92se, (VTC control, timing advance/retard hell Kenji killed his car by clicking the fuel pump off button) limited functionality on a few other 97-99 but didn't work at all on Nozamas 95...IIRC

 

Indeed. It worked on every other model year I tried, from 92 VE to 98 VQ, with the exception of both 95 model year VQ's I tryed it on.

Mine, prod date 12/94 didn't work at all, but IanSW got his Nprobe / Nprobe software to work fine on it.
Nozama? prod date 6/94 didn't work at all, but IanSW got his Nprobe / Nprobe software to work fine on it.

So I now know that all cars work except for 95's to my knowledge.

 

I want to see if the blazt serial cable would work. That would mean that something to do with the different resistance between 95 and others would make it harder for a usb interface to read the port than it would for a serial.

 

Dandy, how exactly did you get the obdscantech to work on your 98? I tryed playing around with those hex numbers to no avail.

 

okay when i run obdscantech's ecu finder on com port 4 this is what comes up:


FOUND: FF FF DA
FOUND: FF FF DC
FOUND: FF FF E7

 

Hmm playing around with device manager I was able to change it to com1. Going to test it again. Also found this screen that says transmit and recieve speeds (all set to highest) It says you can lower them if you are having problems. I'll try that too.

 

I just did the ECU scan. THe various hex codes are for the modules available. THe engine code for 96's for example is EF and for the 98 is ED.

 

Nothing nada failed connect

 

Let's kick it up a notch, BAM! I got an email back from Tom at Nissan Data Scan. He sent me a program to diagnose it. I'm gonna go check it out. Here's the email.

Hi Kevin,

What are the symptomps? When you press the "Connect"
does the progress bar move at all? Do you get a the
ECU number?

Can you try the attached software? This should tell us
if the ECU responds at all.

1. Open the attached "HEX terminal" application
2. Select the correct Com Port number in Settings
3. Under File click on Connect
4. Under Action click on Send Initialization String
5. Under Action click on Send HEX String, type in d0
f0 and click OK
Now you should be receiving a continues string of
data, you can stop it by sending 30.
6. Also try Discover Live Registers and send me the
results

Regards,
Tom

 

Cool. I'll maybe email him too about getting it programmed for a 98 too.. it's not a whole lot different than the other years, just different init strings and a few different registers if I'm not mistaken.

 

No result that I can see from the program. Guess I'll wait to hear back from him. Off to bed.

 

Back to the drawing board huh? Well at least it sounds like you're getting some good manufacturer's support.

 

We are making progress. With the time difference to NZ, it's really a 24 hour email tag though. I will update again when we find something significant. He's going to try to crack the 95 ecu which apparently is different than 97. I told him 98 was an issue as well. We'll see how that goes. Once support is better, nissan data scan should be the premier program to use, with all of the options. Especially if integrated in a carputer where you could pretty much drive around wherever with 'tests' applied full time.

 

I will be going the carputer route once I choose a suitable VIA or AMD Geode or possibly AMD64 platform. Gotta decide between using Center console or glovebox. I will definately try and integrate this as well as MP3, DVD, GPS, and possible EU in the future.

 

Good to hear, keep us updated please.

I do like DataScan but I'm not sure it's the premier.. once you get ScanTEch Nissan working it is as good if not better in some ways.

 

btw no intel suggestions I boycott

 

I suppose that's true. But I already paid for NDS!!! I suppose it's not too much to pay for OBDST as well.

 

Is it still under development? I know NDS is still work in progress.

 

Hi,

It doesn't look like any of those 2 UCEs is an engine
ECU. Without finding the right command to initiate
comms with the ECU I can not do much. Would anyone on
your forum know it?
I don't have access to any Maximas so can't do much
myself.

Regards,
Tom


--- Kevin Hoy <> wrote:

> ff ff dc: Finished. 101 Registers Scanned. 0
> Detected as alive. See log file ... for details,
> log enclosed.
> ff ff e7: scans and runs a little then stops. I let
> it wait for a while to see if it did anything,
> probably 1-2 minutes. Nothing happened. Here are
> the log files.
> No my ECU is a stock 12/94 production date 1995
> nissan maxima ECU that came with the car and is not
> chipped etc. I am guessing that if you can figure
> out how to make it work for my car it will work for
> all of the other 95's that it doesn't work on as
> well? There is also a problem with 98's up. So
> realistically, it has only really worked on 96-97
> (up to 98.5)

 

If Nissan DataScan doesn't work for you try OBDScan Tech as this worked when initially Nissan Datascan didn't.

Just to add to the mix..

My JDM Cefiro VQ30DE 1994 works with both Nissan Datascan and OBDScan Scantech .. using cable from www.plmsdevelopments

 

Kenji please tell Tom that for the 98's the engine code is FF FF ED.

Thanks.

PS the code for 96 is FF FF EF... very similar...

You can also try to find the code on a 95 by using ScanTech Nissan's ECU finder.

 

Okay, does anyone have a working setup, USB, serial, or whatever with a 12/94 prod date maxima, a 6/94, anything in between or anything else? If you would like that info included in the next release of nissan data scan, or if you would like to help out my cause and anyone else who can't currently scan their car, please follow this:

Is it a PC software? You could log the serial
communication strings, which would have the info we
need. I could then implement it in the new release.
Free HHD Serial Monitor is good for it:
http://www.hhdsoftware.com/Products/...itor-lite.html

Regards,
Tom

The quicker someone can do this, the better. The more info he can get, the more he can do. I think he needs more than just the data that OBDST ecu finder gives, that's why he sent me the hex terminal. It spits out a huge log of info for each string.

 

So is he planning to get it working on 98's then for the new release? Or just 95's? I'd love to have 98 working too...

 

Do any programs work with your cable? if so, run the program and do your usual routine with it although this time use the program i linked in the background to log it. then send it to him: nissandatascan (at) yahoo (dot) com

 

please if anyone is reading that has ANY consult utility working on their 95, do the same for me. I'd really appreciate it.

 

Ok thanks will do.. sorry somehow I missed the link above.

 

Hi Kevin,

Thanks for the info. FF FF EF is commonly used on most
Nissans.

Let me just try to summarise what you have found so
far.
1. You have ran the ScanTech Nissan ECU finder and
found 3 ECUs:
FF FF DA
FF FF DC
FF FF E7
2. You have interrogated the last 2 but they turned
out not to be the engine ECUs.
3. The first one (FF FF DA) did not respond to the
initiation string which is strange.

Any chance you can try the first one again? Otherwise
I would have to write a small application to do the
lot.

1. Open the "HEX terminal" application
2. Select the correct Com Port number in Settings
3. Under File click on Connect
4. Under Action click on Send HEX String, type in ff
ff da and click OK
5. Under Action select Discover Live Registers

Thanks,
Tom

 

The DA DC and E7 codes are for other on-vehicle modules, if I'm not mistaken, not the engine. I think I got the auto tranny to connect on a friend's 98 auto IIRC.. can't remember which one it was.

But for example a lot of these programs were developed initially specifically for the Z32, and they'd have the auto tranny, HICAS (active 4 wheel steering) and Climate control (A/C etc) modules in addition to the engine.