P11 Infiniti G20
Moderator: Matt
Re: P11 Infiniti G20
I'll look at it tonight
-
- Posts: 367
- Joined: Wed Jun 04, 2008 3:48 am
- Location: USA Socal
Re: P11 Infiniti G20
Here is the 1993/4 B13 SE-R bin downloaded using the 93 B13 address file
- Attachments
-
- Victor 23710-94Y00 07-1993 B13 dwnlded with B13 93 address.bin
- (32 KiB) Downloaded 198 times
-
- Posts: 367
- Joined: Wed Jun 04, 2008 3:48 am
- Location: USA Socal
Re: P11 Infiniti G20
Ok Matt I noticed you added
however it still shows up like this when you select 97 B14 address
Besides all that everything else is all jibberish
however it still shows up like this when you select 97 B14 address
Besides all that everything else is all jibberish
Re: P11 Infiniti G20
thats the OBD-II B14 file I have... different to what you have. Use an earlier selection for your file
Seems the years dont line up exactly as I would like
Maybe this is even later than 97 (99??)
Seems the years dont line up exactly as I would like
Maybe this is even later than 97 (99??)
There is no part number for that one. What is the part # of your 97 ECU?B14 SR20DE 200SX ?? USDM ????? N A U OBD2 " JA18-B89 B49"
- Attachments
-
- B14_SR20DE_xxxxx.BIN
- (64 KiB) Downloaded 193 times
-
- Posts: 367
- Joined: Wed Jun 04, 2008 3:48 am
- Location: USA Socal
Re: P11 Infiniti G20
Well either JWT ECU ID list is wrong or Nistune is reading someting wrong but how else would Nistune read this part numberMatt wrote:thats the OBD-II B14 file I have... different to what you have. Use an earlier selection for your file
Seems the years dont line up exactly as I would like
Maybe this is even later than 97 (99??)There is no part number for that one. What is the part # of your 97 ECU?B14 SR20DE 200SX ?? USDM ????? N A U OBD2 " JA18-B89 B49"
NISSAN FASTUNISA JECS wrote:I'd also like to add that its not showing the DTC code description when there is a check engine light but it will reset teh light. Sorry dont have a screen shot of that though.
Heres a screen shot showing the ECU part number for the (0896-0897) JA18-H69 BP2
Last edited by UNISA JECS on Sat Aug 21, 2010 2:42 am, edited 2 times in total.
-
- Posts: 367
- Joined: Wed Jun 04, 2008 3:48 am
- Location: USA Socal
Re: P11 Infiniti G20
So lets see break it down:
Nistune B14_SR20DE_512_E_95.adr reads my JA18-H69 BP2 as part number 23710-1M871
I guess since I have a 0896-0897 it works with the B14_SR20DE_512_E_95.adr
Ok if thats the case thats cool but I do still have issue's
(1) Not displaying the trouble codes
(2) Fuel Maps "select flag" flags cover entire fuel map
(3) Knock Flags "selecte flag" it highlights no flags at all on the map
(4) Injection Multiplier looks very small is this correct?
Screen Shot:
Nistune B14_SR20DE_512_E_95.adr reads my JA18-H69 BP2 as part number 23710-1M871
I guess since I have a 0896-0897 it works with the B14_SR20DE_512_E_95.adr
Ok if thats the case thats cool but I do still have issue's
(1) Not displaying the trouble codes
(2) Fuel Maps "select flag" flags cover entire fuel map
(3) Knock Flags "selecte flag" it highlights no flags at all on the map
(4) Injection Multiplier looks very small is this correct?
Screen Shot:
Re: P11 Infiniti G20
B14_SR20DE_512_E_95.adr should be used for all B14 SR20DE apart from the ECUs which look like your 1999 P11 one
JWT doesnt have a part number for that particular ECU and Nissan ECU ID does not display anything (I checked the disassembly and there is no part# stored in there)
1. Not sure with trouble codes. Have you tried triggering say coolant temp sender disconnected?
2. Fuel maps for any ECU with VE maps will have O2 selected over entire map. Leave it as such. Nissan did it this way but not sure the exact reasons behind it
3. Knock flags only work in a particular window where the ECU can reliably (as best as it can) detect knock. This is normal
4. K values by ECU, so numbers will not necessary match different ECUs. Its a magic number. If you adjust it and injection pulsewidth changes then it is correct
JWT doesnt have a part number for that particular ECU and Nissan ECU ID does not display anything (I checked the disassembly and there is no part# stored in there)
1. Not sure with trouble codes. Have you tried triggering say coolant temp sender disconnected?
2. Fuel maps for any ECU with VE maps will have O2 selected over entire map. Leave it as such. Nissan did it this way but not sure the exact reasons behind it
3. Knock flags only work in a particular window where the ECU can reliably (as best as it can) detect knock. This is normal
4. K values by ECU, so numbers will not necessary match different ECUs. Its a magic number. If you adjust it and injection pulsewidth changes then it is correct
-
- Posts: 367
- Joined: Wed Jun 04, 2008 3:48 am
- Location: USA Socal
Re: P11 Infiniti G20
Matt wrote:B14_SR20DE_512_E_95.adr should be used for all B14 SR20DE apart from the ECUs which look like your 1999 P11 one
JWT doesnt have a part number for that particular ECU and Nissan ECU ID does not display anything (I checked the disassembly and there is no part# stored in there)
1. Not sure with trouble codes. Have you tried triggering say coolant temp sender disconnected?
2. Fuel maps for any ECU with VE maps will have O2 selected over entire map. Leave it as such. Nissan did it this way but not sure the exact reasons behind it
3. Knock flags only work in a particular window where the ECU can reliably (as best as it can) detect knock. This is normal
4. K values by ECU, so numbers will not necessary match different ECUs. Its a magic number. If you adjust it and injection pulsewidth changes then it is correct
Ok Matt i'll see if I can try that today with the Coolant Temp Sensor.
Im just trying to get things in order before I take the ECU's in today to get the Nistune boards installed and I have one more ECU that concerns me because although all the maps and everythings seems to be correct this OBDI 0793 B13 SR20DE ECU consult gauges all appear to be maxed out and are not correct looking at all, I also noted that the injection multiplier number is a small number just like my OBDII B14 97 ECU.
Can you have a look at this 0793 B13 SR20DE 23710-94Y00 ECU .bin and tell me if somehting is wrong, thank you.
Heres a screen shot showing the funky readings
However if I use the P10_SR20DE_512_E_94-95 ADR File with the B13 23710-94Y00 BIN File everything appears to read correctly can you confirm this and if so add a title change/addition to reflect this.
How is it that a 512 ADR work on a 256 BIN, this B13 ECU has a blue OBDI connector.
- Attachments
-
- Victor 23710-94Y00 B13 0793 downloaded using P10 94 ADR File.bin
- (64 KiB) Downloaded 221 times
-
- Victor 23710-94Y00 07-1993 B13 dwnlded with B13 93 address.bin
- OBDI 0793 B13 SR20DE 23710-94Y00
- (32 KiB) Downloaded 211 times
Last edited by UNISA JECS on Tue Aug 24, 2010 3:23 am, edited 1 time in total.
-
- Posts: 367
- Joined: Wed Jun 04, 2008 3:48 am
- Location: USA Socal
Re: P11 Infiniti G20
I feel like im just clutterying up this thread but I wanna put all the stock base images I downloaded into one post so here they are these are the ones im sending out with my ECU's to:
DC Performance Inc.
3370 South Livonia Ave.
Los Angeles, CA 90034
Contact Chris on 310-841-6996
DC Performance: Proven Performance
Attached are the BIN Files
DC Performance Inc.
3370 South Livonia Ave.
Los Angeles, CA 90034
Contact Chris on 310-841-6996
DC Performance: Proven Performance
Attached are the BIN Files
- Attachments
-
- Lil Rick 23710-54F00 S13 KA24DE 0790-0291 MT.bin
- Title self explanatory
- (32 KiB) Downloaded 196 times
-
- Charlie 23710-1M871 B14 SR20DE 0896-0897 MT.bin
- Title self explanatory
- (64 KiB) Downloaded 196 times
-
- Big Rick 23710-54F00 S13 KA24DE 0790-0291 MT.bin
- Title self explanatory
- (32 KiB) Downloaded 200 times
-
- Posts: 367
- Joined: Wed Jun 04, 2008 3:48 am
- Location: USA Socal
Re: P11 Infiniti G20
And one more...........
- Attachments
-
- Victor 23710-94Y00 B13 SR20DE 0793 MT.bin
- Title self explanatory
- (32 KiB) Downloaded 187 times
Re: P11 Infiniti G20
done. email me for the ENT files (cant attach them on this forum)
Re: P11 Infiniti G20
with the 1994 B13 SR20DE file I dont have a definition for that one yet
I'm in the middle of adding it but have noticed after looking at the disassembly it is a 64KB ROM image
eg.
Use the P10 SR20DE 512 address file to download a 64KB image and email that through. It may be we just use that address file to create the image (does consult display correctly with that one? consult table may be in the same memory location then if so)
I'm in the middle of adding it but have noticed after looking at the disassembly it is a 64KB ROM image
eg.
falls outside the regular 0x8000-0xFFFF 32KB rangejsr 0x6598
Use the P10 SR20DE 512 address file to download a 64KB image and email that through. It may be we just use that address file to create the image (does consult display correctly with that one? consult table may be in the same memory location then if so)
Re: P11 Infiniti G20
Update on B13 SR20DE (1994) yes you are right exactly the same as P10 1994 SR20DE. 64KB file, consult table same location, TP same memory address. I've created a new address file and entry for this. You can use the P10 one in the meantime. Found the 64KB file you posted on the previous page too. Chris has been emailed those files tonight also
So these are doable OBD-II ECUs
S14 KA24DE (1996 23710-70Fxx)
B14 SR20DE (1996-1997 23710-0M7xx, 1M8xx, 2M0xx)
P11 SR20DE (1996-1997 23710-3J8xx, 3J4xx, 3J5xx, 3J8xx), G20 P10 SR20DE (23710-0J2xx, 0J6xx)
just confirming on the OBD-II stuff several things too which need the Type 4 OBD-II board (2nd prototype in testing)
A32 VQ30DE (1996 ECU)
Addresses 4000-FFFF in main 64KB ROM
OBDII code second processor 0x044000 in second OBD-II ROM (have this ROM)
Addresses 4000-FFFF in main 64KB ROM
OBDII code second processor 0x044000 in second OBD-II ROM (have this ROM)
Addresses 4000-FFFF in main 64KB ROM
OBDII code second processor 0x044000 in second OBD-II ROM (have access to this ROM)
B14 SR20DE (1998/99? ECU)
Code addresses 3400-FFFF (maps 1000-33FF) in main 64KB ROM. Uses the same installation as ER34 (two jumpers) but adaptor B connector. Internal addresses are the same but appears no access to extra ROM within code. Not sure on these ones
* What I have tried here is downloading the ROM, putting it on a board but wont run. I think it still uses the adaptor B pin configuration (even though the ECU is same hardware as ER34/WC34) but the memory mapping is 1000-FFFF like with ER34. That doesnt seem to want to work and might need some more investigation/tweaking
Does not appear to require second OBD-II ROM like what we are doing on the updated Type 4 boards, so could potentially run with the current Type 4 board if I can figure it out. We have no boards (Techtom/JWT) to look at for clues with these ECUs so that makes it more difficult. The OBD-II boards are fairly simple since they just read address 0x40xxxx from another ROM chip on the board
I have no idea how Techtom/JWT got the OBD-II ROM out of the Nissan ECU. Consult cannot access outside 0x0000 - 0xFFFF addresses. I suspect they may have used Nissan OBD-II read commands to get that part. Something I'm still trying to figure out in spare time
So these are doable OBD-II ECUs
S14 KA24DE (1996 23710-70Fxx)
B14 SR20DE (1996-1997 23710-0M7xx, 1M8xx, 2M0xx)
P11 SR20DE (1996-1997 23710-3J8xx, 3J4xx, 3J5xx, 3J8xx), G20 P10 SR20DE (23710-0J2xx, 0J6xx)
just confirming on the OBD-II stuff several things too which need the Type 4 OBD-II board (2nd prototype in testing)
A32 VQ30DE (1996 ECU)
Addresses 4000-FFFF in main 64KB ROM
OBDII code second processor 0x044000 in second OBD-II ROM (have this ROM)
S14 KA24DE (1996+ ECU 23710-72Fxx)0x46A1: 5C 68 47 04 jmp 0x044768
Addresses 4000-FFFF in main 64KB ROM
OBDII code second processor 0x044000 in second OBD-II ROM (have this ROM)
Z32 VG30DETT (1996 ECU)0x48B2: 5C 9D 45 04 jmp 0x04459d
Addresses 4000-FFFF in main 64KB ROM
OBDII code second processor 0x044000 in second OBD-II ROM (have access to this ROM)
P11 SR20DE (1999 ECU) and0x54EA: 5C 00 40 04 jmp 0x044000
B14 SR20DE (1998/99? ECU)
Code addresses 3400-FFFF (maps 1000-33FF) in main 64KB ROM. Uses the same installation as ER34 (two jumpers) but adaptor B connector. Internal addresses are the same but appears no access to extra ROM within code. Not sure on these ones
* What I have tried here is downloading the ROM, putting it on a board but wont run. I think it still uses the adaptor B pin configuration (even though the ECU is same hardware as ER34/WC34) but the memory mapping is 1000-FFFF like with ER34. That doesnt seem to want to work and might need some more investigation/tweaking
Does not appear to require second OBD-II ROM like what we are doing on the updated Type 4 boards, so could potentially run with the current Type 4 board if I can figure it out. We have no boards (Techtom/JWT) to look at for clues with these ECUs so that makes it more difficult. The OBD-II boards are fairly simple since they just read address 0x40xxxx from another ROM chip on the board
I have no idea how Techtom/JWT got the OBD-II ROM out of the Nissan ECU. Consult cannot access outside 0x0000 - 0xFFFF addresses. I suspect they may have used Nissan OBD-II read commands to get that part. Something I'm still trying to figure out in spare time
-
- Posts: 367
- Joined: Wed Jun 04, 2008 3:48 am
- Location: USA Socal
Re: P11 Infiniti G20
Thanks Matt I emailed you at enquiries@nistune.com for ENT Files.
Thanks
Charlie
P.S. Do you have a 99 USDM Infiniti G20 SR20DE ECU for testing? cause if not I have one. This is really the ECU I wanted to NIstune but if maybe in the furture you get it working I'll buy another one again from you?
Thanks
Charlie
P.S. Do you have a 99 USDM Infiniti G20 SR20DE ECU for testing? cause if not I have one. This is really the ECU I wanted to NIstune but if maybe in the furture you get it working I'll buy another one again from you?
Re: P11 Infiniti G20
if you want to send it here I can give it a shot. I would really like to get that one and my B14 one working but must be something I've missed