new problem:o2 readings

Nistune topics specific to the 6802 cpu

Moderator: Matt

Matt
Site Admin
 

Posts: 8961
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: Dies when insert burnt ROM with TPS plugged, OK with nis

Post by Matt »

I've fixed a few things in the tune file. Put the TP cut tables to normal

With EPROM make sure sync tune into 26P00 BIN file and burn that to ROM. I cannot really help you with why it works in the board, but not with the EPROM

What parts of log did you want me to look at (it is half an hour log file!). For just changing injectors you should not need to change the warmup, decel timing or enrichment tables normally.

Rest of file looks okay, but normally with larger injectors (K is almost half) you would need to flatten the fuel map accordingly
Attachments
Z31_VG30ET_1988_26P00_midian_updated.bin
(16 KiB) Downloaded 148 times
midian
 

Posts: 43
Joined: Wed Jan 14, 2015 10:16 am

Re: Dies when insert burnt ROM with TPS plugged, OK with nis

Post by midian »

thanks, Matt. will check this evening, if all be o.k., probably logs wouldn't be necessary yet.
on logs-a thout you're need at least (!)3-5 minutes long.
midian
 

Posts: 43
Joined: Wed Jan 14, 2015 10:16 am

Re: Dies when insert burnt ROM with TPS plugged, OK with nis

Post by midian »

morning, Matt, just tested. MUCH BETTER with almost minor changes in bin.
but, I still have one question:
before I blow engine 2 years ago, after installing new nistune version I'd lost "O2 voltage". I thought sensor is out. Replaced today with new one-no changes.
started overall check, found it sends signal tu ECU.
also found ECU "flashes with green diode over 10 times per 5seconds if rpm 2000 and higher", so ECU founds it, nistune's "consult" don't have "33 error" (came only with blown or unplugged sensor), feedback switch "on", but still no readings.
any suggestion? or it operating, but was removed in post 0.12 revisions (currently I use last)
midian
 

Posts: 43
Joined: Wed Jan 14, 2015 10:16 am

Re: Dies when insert burnt ROM with TPS plugged, OK with nis

Post by midian »

I done overall test according to fsm, including testing continuity and voltage (0.114 to 0.45 usually, over 1 occasionally) on 24pin.
probably it operates if vehicle moves? (speed over 0). I don't think ecu is toasted, cause it flashes as fsm tells, but still.
p. s. currently with daughterboards, cause ALL eproms need to be erased.
p.p.s. close to this issue viewtopic.php?f=2&t=1935&p=14672&hilit= ... age#p14672
midian
 

Posts: 43
Joined: Wed Jan 14, 2015 10:16 am

Re: new problem:o2 readings

Post by midian »

btw, just my thoughts - could it be cause by socket soldering fail?
Matt
Site Admin
 

Posts: 8961
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: new problem:o2 readings

Post by Matt »

If nistune connects then the ECU program should be running okay. Doubt soldering socket issue otherwise no gauge items will display

O2 sensor input voltage comes from memory address 0005 in 1987 ECU (21Pxx) and address 0007 in 1988 (26Pxx) ECU code

You can monitor 0007 (In RAM montior window) and it should show same voltage as pin 24. This is also the same value in O2 LHS on guages which should display. No changes to Nistune should have affected this display. Is your O2 feedback enabled in the ECU?
midian
 

Posts: 43
Joined: Wed Jan 14, 2015 10:16 am

Re: new problem:o2 readings

Post by midian »

Hi, Matt
O2 sensor input voltage
comes from memory address
0005 in 1987 ECU (21Pxx) and
address 0007 in 1988 (26Pxx)
ECU code
You can monitor 0007 (In
RAM montior window) and it
should show same voltage as
pin 24. This is also the same
value in O2 LHS on guages
which should display. No
changes to Nistune should
have affected this display.
will check today, but actually should (no 33error in nistune message, input on 24pin vary, greer light flashes)
Is
your O2 feedback enabled in
the ECU?
after primal tune been done-I turned o2 feedback switch 'on'
Matt
Site Admin
 

Posts: 8961
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: new problem:o2 readings

Post by Matt »

Image showing O2 sensor working fine on bench using 26P00 Z31 300ZX ECU
Attachments
Z31_26P0F_O2_test.png
(184.29 KiB) Downloaded 4893 times
midian
 

Posts: 43
Joined: Wed Jan 14, 2015 10:16 am

Re: new problem:o2 readings

Post by midian »

will check.
midian
 

Posts: 43
Joined: Wed Jan 14, 2015 10:16 am

Re: new problem:o2 readings

Post by midian »

rechecked several times, even continuity between ground and 24 pin-no readings, o2 sends, ecu blinks, the only thing didn't checked-testing variable resistor position, otherwise - internal ecu cirquits failure.
I'll upload screenshot in 10 hours.
rest, excluding lean at warming up from 45 to 70-all good, probably only under high boost (around 0.8) a little rich(10.4), rest ot (exhausts smells fine, as shoul cat-less).idle timing set +10 (as eudm, cause of longer to rest markets duration and closest to 280/270 cams), idle speed set 900(jumps±25) also as eudm catless manual
Matt
Site Admin
 

Posts: 8961
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: new problem:o2 readings

Post by Matt »

Check memory address firstly (in RAM tracer). Use start address 0000 length = 10 (and watch both values I specified before)
midian
 

Posts: 43
Joined: Wed Jan 14, 2015 10:16 am

Re: new problem:o2 readings

Post by midian »

Matt wrote:Check memory address firstly (in RAM tracer). Use start address 0000 length = 10 (and watch both values I specified before)
totally forget on, this, sorry Matt.
recheck today.
btw, yesterday you should recieve Nistune crush report.
midian
 

Posts: 43
Joined: Wed Jan 14, 2015 10:16 am

Re: new problem:o2 readings

Post by midian »

Matt, it's "playing"(checked 15 minutes ago), upload 2 screenshots asap.
still no readings.
btw, I didn't mention this - I lost readings in 2011/2012 after updet. I didn't pay attention on this, cause I thought my sensor is toasted (hadn't perform overall fsm check), and I did'n have 33 error in nistune gauges (so thought no signal cause toasted).
but when I removed sensor (after overall check by FSM, and checking heat element applying 12V DC from different supply, etc) - visually - it was ok still.
Attachments
matt1.jpg
(271.83 KiB) Downloaded 4860 times
matt2.jpg
(273.03 KiB) Downloaded 4860 times
Matt
Site Admin
 

Posts: 8961
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: new problem:o2 readings

Post by Matt »

Your ECU memory address for O2 sensor (Address 0007) is reporting 00

26P00 code here shows:
A949 : 86 03 ldaa #$03
A94B : BD 95 3A jsr SUB_953A_Read_AD_Input
A94E : 97 07 staa RAM_0007_LH_O2_VOLTAGE
Nistune code update would not cause problem
(a) It works fine on the ECU here (see picture before)
(b) Raw memory read from ECU shows 00 on your screenshot
(c) No one else has reported their O2 sensor not working for this ECU

Also using 26P00 is fine on 1987 ECU
A452 : 86 03 ldaa #$03
A454 : BD 91 E5 jsr L91E5
A457 : 97 05 staa LH_O2_VOLTAGE
The 21P00 code base reads AD register #$03 still but puts into memory address 0005 (instead of 0007 for 26P00)
midian
 

Posts: 43
Joined: Wed Jan 14, 2015 10:16 am

Re: new problem:o2 readings

Post by midian »

Matt wrote:Your ECU memory address for O2 sensor (Address 0007) is reporting 00

26P00 code here shows:
A949 : 86 03 ldaa #$03
A94B : BD 95 3A jsr SUB_953A_Read_AD_Input
A94E : 97 07 staa RAM_0007_LH_O2_VOLTAGE
Nistune code update would not cause problem
(a) It works fine on the ECU here (see picture before)
(b) Raw memory read from ECU shows 00 on your screenshot
(c) No one else has reported their O2 sensor not working for this ECU

Also using 26P00 is fine on 1987 ECU
A452 : 86 03 ldaa #$03
A454 : BD 91 E5 jsr L91E5
A457 : 97 05 staa LH_O2_VOLTAGE
The 21P00 code base reads AD register #$03 still but puts into memory address 0005 (instead of 0007 for 26P00)
other words - intarnal ECU error?
ECU is 23710-22p72 (A18-000 m10) btw=) J ECU
Post Reply