pcmhacking.net

nah its not lambda, it appears to just be a multiplier

should still be able to use BLM LTFT % on a history table to scale the multiplier?

yeah i've made a histogram to put the info from blms into the table the same axis as the injector offset table, so then its just a matter of some excel calcs to get it to take the current table and spit out a new one based on blms ..... but i'm just not sure if the calc needs to be a 1 to 1 multiple or if i need to halve the blms before i multiply that table etc.

yeh can't tell you that one, i know it's ruffly 50% of the BLM LTFT % Value to change the MAF Tables, ive attached a spreadsheet i made to adjust open loop fueling table, might help you get started.

Try doing a compare between CNPD (VS Series 3 V8) and CFZD (VT V8 220kW), both available in the1's tool.
Both these bins use the $A6C XDF.
You can then copy and paste over the different bits (the injector offsets are different, but not by much from a quick look).
An alternative you could try would be grab from $2000 to $53B1 from CFZD and paste into CNPD, adjust MAF tables back to 5.0 litre MAF and checksums.

yoda69

that spreadsheet is the same as what i made for the injector constant offset table to use blms to adjust it ....

ok what i've done tonight, i have changed the injector rate to that of 5.7 motor which is 325 ..... so then i went for a drive and started playing with blms ...... in the end i've applied the blm offsets to the injector offset table and it seems to be showing blms pretty close to 100% so i will go with that for the time being and see how it ends up.

anyone found a setting to change speed on the dashboard vl400 gave me one location and thought it would change the ecu reading and dash reading .i changed it and the laptop now reads perfect withen 1kmh of real life gps reading but dash reads out by the same amount as before hand my mates not happy at his car gaining extra km's LOL he did get the dash PPK changed or something at holden when he got the 4.11's installed but they said they couldnt go high enough value to correct 4.11 so its still out

This sounds a bit like the VS V8 code, where somewhere they had hard programmed an output value that didn't reference the variable that every other area uses.
https://pcmhacking.net/forums/view ... =ppk#p9280

I never got a chance to check on the VS, as they guy got rid of the car at the same time as I got the info to try.

yoda69

Hmmm, the ALDL data stream for logging gets the same KPH value as the dash. So it should also get the change The dash must do some sort of conversion to the value if GM can calibrate the tash via Tech-2. Will have another look at the code later.

GM used a ppk value in the instruments to finetune with the dash calibration based on tyre sizes.
This avoided the need for a heap of different memcals for all the different tyre sizes available (15-17") in VT.

yoda69