issue with 1996 OBD 2 g20 .adr file

[enohand]

when i load this on my type 4 board, i cannot connect, it tells me it cant find the USB drivers, the consult button also says "usb consult"


i am using a Blatz serial cable with a serial to usb converter.

If i use a different adr file (94-95 g20) all works OK, but i get a error that says something about a mismatch, & supply's a recommendation on a file, i accept & all seems to work,

but i don't know if using the older adr file will cause any issues, i have not done any tuning yet due to this issue....



also a completely unrelated question, is there any application i can install on my laptop, that will "interface" with the nistune board & give me a whp, or bhp reading?? or even a estimate?

[enohand]

Bump~

anyone else running a OBD2 file? i think its the 200sx one.....its looking for USB drivers, i run a serial cable....setting the com to 1 doesnt help either

[Matt]

i think it shouldnt be requesting that address file but need to check it

[enohand]

any info?


why does it try to load usb drivers only using the odb2 file?

its weird

[Matt]

What is the part number on your board, or reported by Nistune (ECU ID 23710-xxxxx). Once I have that I can check what its trying to load instead

[enohand]

hmmm...wont be able to get you that untill thursday, im on the road for work....

ANdy from autovaughn might know, since they litereally JUST did the ecu

[enohand]

ok got some screen shots for you matt..

ok i connect & select the adr file,



then i select my bin



then i hit consult & get this error



then the consult button turns to "usb consult" (im using the blatz serial cable, not usb)






So in order to get it to work i select this adr



then i pick my bin



but then i get this error



i hit ok, & all seems well

[enohand]

bump any info?

[Matt]

will look at it tonight. in my inbox

[enohand]

ok kool, just let me know....


also im thinking it just maay be some code in the adr file, since it changes to look for the usb drivers....

i also noticed that there is no bin file for a MT for the 1996 g20....how can i dump my bin from my ecu & have nistune use that?

[Matt]

Thanks for the pics

Your ECU reports 23710-0J202 as the part number

You should be selecting the entry 'G20 Infiniti P10 SR20DE 0J2XX, 0J6XX' as the address file

The matching file you should be selecting is G20_P10_SR20DE_0J202_MT_1995.bin

Don't use the OBD2 address file/BIN file for this one. That is for 1996+ ECUs which I'm working on with an upgraded Type 4 board

[enohand]

im using a 1996 g20 tho....the ecu i sent the guys at autovaughn was a 1996 g20- ecu.
are you saying that the board i have installed isnt yet fully finished? will i have to send it back? i was told that the type 4's were all done, thus the reason i bought it, if i would have known there was going to be a revision, i would have waited..

[Matt]

okay yours an early 1996 ECU. Just had this discussion with someone the other day. As stated before use the 1995 address file and it will work.

The later model OBD-II 1996 ECUs which have dual ROMs use the newer 1996 address file. The board you have is correct for your ECU and runs. Its the later ones which arent finished (and dont work at all)

[enohand]

ok no problem..



so in the event of a NEW FW for my ecu (say a FW with launch control, & MAYBE the possibility to MASK/Delete MIL codes from the ECU (only code i want to do this to is the code for running the 109tooth fw in my car...) in 1994, the G20 was equipped with the Crank position sensor. It sits in hte front of the bell housing & "monitors" the FW. the sensor is a HAL sensor, so there's a magnetic field, that gets altered by the teeth on the FW, being that i am running the 109 tooth (109 originally came from 1991-93.4, is meant for ODBI cars, but will work in any SR, but throws a CEL on ODBII cars) the 108 tooth FW works in ANY sr20, without throwing a MIL

So being that i am running the wrong one...is there a way to extract that code from the ECU?

[Matt]

I think there is but I havent been able to find the filter yet. Most earlier ECUs have a series of memory addresses which are used to filter out DTC codes. Havent found it on this one yet for disabling some of them