Issue Track Testing Wideband Closed Loop
Added 2023-05-28 00:45:22 +0000 UTCEdit 2: I tested the fix and was able to confirm that both issues are fixed. I've uploaded a new version of the Boost OS Patcher (V1.4) that will allow you to upgrade to BOS V4.4 that includes the fixes.
Edit: I believe I found the bugs and hope to get the fix tested soon for both issues.
It looks like I’ve found another bug with logging the EGR (wideband), but It’s a simple fix. I also had an issue testing the wideband closed loop at wide open throttle. I’m not sure the source of that issue but I’ll do more testing to try and pin it down. The closed loop works well with the wideband at cruising loads, but I wouldn’t recommend using it at wide open.
Thanks,
Branden
Comments
i know this is an older post but after reading it i got an idea based on the min and max % the fuel trims are allowed to move. it seems the defaults do in fact work fine for cruising as most peoples tuning stays within the window for both STFT and LTFT min and max %. what im thinking is that there needs to be separate min and max values for full throttle/high load situations. like if the engine is overly rich at full throttle the STFT can only move 0.80% at most in a stock calibration. if the persons mapping is setup far richer than this threshold well than it cant follow the target AFR and trim enough injector away because its not allowed to. setup some other constant values like if above X MPH, TPS is above X, and maybe something like above X amount of manifold pressure to switch to min and max constants that have a wider range of allowed adjustment. could also do this for idle situations as well too to have constants that tighten up the constraints when idling.
scott bradford
2024-09-04 22:09:11 +0000 UTCSorry for the delay was in vacation. WOT in closed loop has no issues now.
Stokes1114
2023-06-18 00:43:44 +0000 UTCSomething else. This issue was resolved in the latest update.
Branden Butella
2023-06-12 13:13:55 +0000 UTCBranden, what happens with closed loop wideband with engine running wide open? Is it a cpu loading issue, i.e., not enough cpu cycles going around or is it something else?
gilius
2023-06-12 13:08:20 +0000 UTCthanks for the patch. it worked! on the last version i thought i had to disable the CL control in the stock area.... let me know if you want a log
00blksalgt
2023-06-01 02:02:46 +0000 UTCWill do
Stokes1114
2023-05-30 17:09:42 +0000 UTCIf you are able to re-test with the fix I'd be interested to know how it works for you.
Branden Butella
2023-05-30 16:34:06 +0000 UTCYep exactly. Now you know the vve trick. Gm ecm with vve have ve tables you can modify the axis of to match your boost OS. This just makes it easier to make a large change. If I'm just changing a few cells I will usually just do it in tunerpro manually but if Im changing a lot I do it this way
Billy Bowerman
2023-05-30 01:28:23 +0000 UTCAh ok I get it now. You just can’t copy and paste the error as a multiplier right into TunerPro. Yeah I’ve done that with a spreadsheet before.
Branden Butella
2023-05-30 01:25:44 +0000 UTCThe reason I use eq ratio error instead of afr is I run both e85 and pump gas and lambda is the same regardless of what fuel I'm running.
Billy Bowerman
2023-05-30 01:24:20 +0000 UTCI made a histogram in the vcm scanner that does eq ratio error. The histogram uses the axis of the boost os ve tables, that histogram is showing the % error difference of my commanded eq ratio and the actual eq ratio reported from the wideband. I can copy and paste that error into hptuners using paste special and multiply by percent to fix the ve table this is the fastest way to get the ve table dialed in. I don't really care about if the map is smooth or not I really only care that the commanded afr is matching the wideband afr. I can do the same thing in tunerpro but I would have to do each cell individually instead of just copying in the correction.
Billy Bowerman
2023-05-30 01:23:22 +0000 UTCInteresting. What do you do that for? Does it do smoothing for you?
Branden Butella
2023-05-30 01:18:00 +0000 UTCCool deal I haven't used the CL much. I've dialed in the ve really good and I get the afr in the ve table 99% of the time so I never got to test the CL in boost. I wish that tunerpro had the paste special option like hptuners has. For now I've taken an hpt file modified a vve tables axis to the 4bar boost os axis I will copy my ve table to it and then use the feature in hpt and copy the whole table back into boost os. But you can't save the vve file because it will extrapolate it and mess with the value #s lots of copy and paste but it works good for me.
Billy Bowerman
2023-05-30 01:09:47 +0000 UTCCool, thanks :). I am currently not boosted but the wideband CL works great.
Chad R
2023-05-28 22:38:10 +0000 UTCYa I had an issue where at wot it goes extremely lean so I disabled CL.
Stokes1114
2023-05-28 01:05:43 +0000 UTC
