Hey there everyone, I’ve recently upgraded to V3 and where before on V2 I barely relied on DBW idle control because 0.5% TPA resolution with an 82mm DBW throttle on a 2jz was unusable, now with the new V3’s 0.1% I thought I’d have another go, but I’m facing another issue, though I’m not sure if it’s a software, wiring, or throttle issue
Basically, reducing the target from 4% by 0.1% each the throttle seems to get stuck above the target, the DC will wind up from the PID control as it should to try reach the target, then the DC will get to a point (normally -20 to -30) and the throttle will then move but over shoot the target before recovering to the target.
It’s bad because it’s right in my idle range and as the idle control slowly tries to close the throttle it’ll stick, overshoot to maybe 1-2%tps, then RPM will drop, which also makes the idle PID have a hard time keeping up.
It happens even with engine off and doing a DBW target override, slowing lowing by 0.1% at a time, the DBW PID will then wind up and over shoot. It also does it with just a DC over ride and decreasing the DC - so this seems to eliminate any engine config, idle config, DBW PID config. It seems to be less bad with the DBW frequently maxed at 8khz…
The log pictured is using target over ride - note the target lowering incrementally by 0.1%, before the the TPS gets stuck at 3.9% and then the I in PID winds up, winding the DC up, and then overshooting the TPS to 3.2%.
This isn’t the worst example, just a typical example. This is completely repeatable also.
I’ve cleaned the throttle and recalibrated a number of times.
Anyone have any suggestions before I conclude there’s a mechanical issue with the throttle?
Thanks for any helps
Overall v3 is a big improvement, and the reason I didn’t experience this before is because on V2 I had my DBW fixed at 3% at idle and just used ignition correction in open loop before.