fixed.... and added rom. I blame it on taco mac and their Belgian ale selection i need to dial in the base duty cycle and desired boost tables to cut down on the correction. Once i get the boost curve where I want it (till the X swap) I will start to dial in the fuel and timing.

 

You should log WGDCcorrection to see if it really is correcting (although you can cross reference your base WGDC tables too but logging WGDCcorrection is faster/easier)

 

I will do that along with the next revision of the base duty cycle tables and get some more logs. Though I think the attached screen shot makes it easier to see that correction is going on.. at least to my eye.. the flow rate drops correspond to the boost error as do the the base duty cycles... Thanks for taking a look Bryan.

 

Yo Bryan.. what offset / rpn are you using with the stand alone logger for duty cycle correction?

I have the following and it is not working properly as can be seen from the attached logs from this AM:
paramname=WGDCCorr
paramid=0x808783
databits=8
scalingrpn=x,0.5,*,64,-

Did not feel the hesitation in either pull (log 6 is 3rd into 4th, log 7 is 4th). Though it looks a little bit like I might be getting some rich missfire from time to time.

I still need to drop the base duty cycles a bit and tone down either the correction interval or the correction magnitude in the first couple cells either side of zero boost error.

I also need to start working on the fueling. I have lean spool turned off so that may account for the rich condition during shifts.. or it could just be the way the load is tracking... one more revision to the boost config and I should be ready to dig in on the fueling.

 

I use BoostError since I am using PSI-Target

238085A2

 

Yup, already logging psi boost error:

paramname=BoostError
paramid=0x8085A2
databits=16
scalingrpn=x,128,-,0.0483675,*