I thought I knew what I was doing but apparently not so here I am asking for help. Two questions:
Why does the boost duty cycle not follow the table unless you have PID active? Shouldn’t it just be following it exactly as an “open loop” type control? This is shown in 4.0Trying and noresponse log. Happens though the entire log, but is most noticeable at 1:13
in the 3.9Boost and Boost log, why is the duty cycle following the table perfectly, and then suddenly slamming shut, causing me to spool and over boost? Happens at 8:36
Mind you, 10 is wastegate full closed and 66 is full open in regards to duty cycle.
Ok I just noticed something, The boost DC drops to 10 when the margin above target is exceeded. and then when it is back within the range it goes back to DC feedback table value before once again exceeding the upper margin and defaulting to DC of 10. Is the software assuming that a lower DC is to open the wastegate to bring the boost level back down? and if so, do I simply need to invert the output, and invert all my tables to reflect lower DC = less boost? because as it is right now, less duty cycle is more boost.