11p tuning

[Dylan]

Yeah that old trick. Mine doesn't read at all without it removed. I run my own PCM for tuning 11P. Has that and the write wire on it. Well worth removing.

[Jervies]

mine was about 3 numbers leaner than what it really was.
and 28' at 3000? not numbers i put in there?
just had a look over log, its seeing 31 in some spots? did u run that map i sent because it shouldnt of gone over 28 unless something is changing it?
and yeah looks rich and then wideband flatlines lean obviously not right

[jezza351]

mine was about 3 numbers leaner than what it really was.
and 28' at 3000? not numbers i put in there?
just had a look over log, its seeing 31 in some spots? did u run that map i sent because it shouldnt of gone over 28 unless something is changing it?
and yeah looks rich and then wideband flatlines lean obviously not right

Hey mate , yeah used that map so not sure why it was going up to 31, looking through the log it was more in the 3600rpm range at around 70kpa it was pinging a bit under light-med throttle, dropping it to 24 in that area got rid of it.

I did pull the pull up resistor off the board when I added the write wire a while ago, the wideband on the lm2 screen reads spot on to what is showing in the data while logging, I'm thinking my sensor is faulty as when its playing up is shows its really lean on the lm2 screen as well.

As for the histogram feature is that using the wideband data into the wideband conversion spreadsheet? I had a look at the spreadsheet and was having some trouble getting the numbers to line up in the correct columns as it seems to be setup for 12p , is there one available for 11p?

[jezza351]

looking at that log it seems to jump up to 30.2 degrees when DFCO kicks in, Does DFCO add initial timing when it activates?
when the timing goes into the 30 range its also commanding 16.5 afr

[Jervies]

vrjezza.adx

(148.54 KiB) Downloaded 211 times

ok then youll need to move anything higher than 60kpa timing to be in by 4000 area not 3600 and smooth it out. must have some good compression or bad fuel. Right you are that spreadsheet is not good for that adx. ive modded one for you to give you same tables as 12p. would be nicer with same res as 11p but. ill message antus about that. i also noticed the ve data trace doesnt move off 20 kpa colum

ahh yeah that could be right, havnt looked at that. maby drop your idle timing back to 24 or something

[jezza351]

vrjezza.adx

ok then youll need to move anything higher than 60kpa timing to be in by 4000 area not 3600 and smooth it out. must have some good compression or bad fuel. Right you are that spreadsheet is not good for that adx. ive modded one for you to give you same tables as 12p. would be nicer with same res as 11p but. ill message antus about that. i also noticed the ve data trace doesnt move off 20 kpa colum

ahh yeah that could be right, havnt looked at that. maby drop your idle timing back to 24 or something

Cheers for the help mate , yeah it's running 11.5:1 with alloy heads running premium 98 , I noticed the data tracing doesn't move off the first column but the rest of the adx is good and it has the calcve which seems to be getting the ve cells in the right area.

[Holden202T]

I noticed the data tracing doesn't move off the first column but the rest of the adx is good and it has the calcve which seems to be getting the ve cells in the right area.

That will be a setting wrong, which table is the data tracing not working properly in ?

[jezza351]

I noticed the data tracing doesn't move off the first column but the rest of the adx is good and it has the calcve which seems to be getting the ve cells in the right area.

That will be a setting wrong, which table is the data tracing not working properly in ?

Hey mate, the main ve table and afr table, it hovers in the 20kpa cells at the correct rpm but doesn't move out of the 20kpa area

[Holden202T]

ok according to the last bin file in this thread you are using $11P v1.04 and your adx appears to be an earlier version (v1.0), its missing some parameters which is the reason the map data tracing is not working.

download a fresh copy of the $11P zip file and use the correct adx (v1.03) from that should fix the tracing issues.

[VL400]

The ADX earlier in the thread is for a logger. Here is an updated version for use with 11P V104 and logger firmware v1.13.

11P_1baA.adx

(147.47 KiB) Downloaded 216 times