all VE/boost spark tuning should be done in open loop. Then you can finish off the tune and go closed loop if you choose and do some logs and see how it looks and make adjustments as necessary.
all VE/boost spark tuning should be done in open loop. Then you can finish off the tune and go closed loop if you choose and do some logs and see how it looks and make adjustments as necessary.
Cheers. We will have a go again this afternoon.
+1 in OL.
( CL would be applying fueling corrections ahead of you while you're attempting to correct the VE table, i.e. your VE corrections would be frustrated ).
Ok cheers, we did some more tuning in OL and have it very close. One thing we have noticed is the PE does not work in OL so we have fudged the fuelling with th ve to get our afrs correct. What will happen when we go back to CL? Will the fuel trims try to correct to commanded afr and throw it all out? The commanded afr will be about 12.7:1
PE tuning most definitely works in OL. Can you post your latest tune? I didn't see what kind of car/truck this was, but some tunes have crazy PE delays based on rpm or map.
That is interesting!
I have attached the last log we did along with the tune file.
Cheers.
Log_0020.efi
SDautoVE_LQ4_0000.tun
You have table B3618 set to 14.49 across the RPM range. You need to update this table to transition your A/F down to ~11.2:1 or thereabouts. That is why it appears that its not kicking in in open loop.
Also this is a boosted setup and you have the MAF turned off, but are only running a 1 map VE table. This means the tune will NEVER see boost. You either need to go to a 2 bar map sensor and a custom operating system, or turn the MAF back on.
B3618 had been set to the figures below but it still didn't move into PE mode or have any effect when in open loop yet will change commanded AFR when in closed loop. We changed them all to 0.99 to rule out any changes which might effect our VE calibration. Im running COS5 and was under the impression this is 2BAR as I have a 2Bar MAP installed. The Boost VE is table A0009.
1.000000
1.000000
1.000000
1.000000
1.000000
1.000000
1.000000
1.000000
0.949907
0.930064
0.910222
0.889661
0.870008
0.849793
0.849793
0.849793
0.849793
0.849793
0.849793
Ah, missed the COS5 part, that makes me feel better
1)I would also set your B3616 to something more reasonable like a stock F body table. At light part throttle its trying to kick PE on. But that is a separate issue.
2)I would also set B0120 to 0 since your speed density.
3)Are you using the A0011 valet mode pin as a 2 step?
4)I looked through the PE tables and nothing jumped out at me except what you have the PE vs. RPM table set to. Can you try setting it to 11.0:1 across the RPM range and make a quick pull?
Originally Posted by ttls1
Posting Permissions
Reply With Quote