pcmhacking.net

Getting some weird numbers for the long and short fuel trims (VX SC enhanced v1.3), sometimes the numbers are in fairly normal ranges like -2 to -4% but then they jump to -180 to -200?

Any idea what might be causing it?

probably bad data, the Percentage calc couldn't get -200, it's feed value is 0-256 as a BLM Value then calcd via X/1.28-100 so extremes are 100 and -100%, VT-VY are known for data issues due to the extra devices on the bus. Are you using 1.3c adx?

No, still using and older ADX as it has been modified for use with VL400's data logger. Might have to have a go at modifying the latest ADX and see what that does.

I'm fairly certain it has always done it but I've not paid to much attention in the past however the cars had a few mods now so the base tune is probably a fair bit out now so I think it's about time to tweak it a bit.

Is there a way to limit the data? message 4 or 6(never used those functions)?

you could try using calc (X/1.28)-100 with the brackets, sometimes tunerpro has a random bug to.

OK, will do.

edit: original calc was x -128, changed the calc as per above but I'm still getting numbers between 0 to -200.

edit2: looks like a the latest ADX has changed a fair bit.

Will need to test and run the new ADX with the logger and see if the data is any different.

looks like your talking about BLM, i was talking about BLM %, BLM is 0-256 with 128 being the middle or 14.7 AFR the calc X-128 just makes 128=0 so negative BLM is richer and positive BLM is leaner. You can just run with X calc if you want the real BLM number.

Right, I was looking at the wrong calc in the ADX. Run the log monitoring BLM using the original calc ( X - 128) and the BLM shows -256.....

Something weird here.

edit:Tunerpro has frozen 3 times on me today,llaptop would not reboot properly either. I downloaded an update not long ago but checked and there was another update so we will see what happens.

edit2: nope, no difference.

My tunerpro was crashing every time I logged on the vB this week opened an old version then back to New version all fixed lol.think my dead bios battery is the culprit but it's so deep inside the laptop I can't replace it lol

currently running latest versions of everything and havn't rebooted laptop in weeks, still all logging fine, win10 here. You on 8853 version of tunerpro?

-256 isn't possible with x-128 calc lol lowest X Value is 0 so -128 is lowest and 128 is highest. If you have a log change it back to X only and see what the value is at the same point it's probably a dropped packet.

Yep, 8853.

I re-ran the log with just X. The first number that appeared was -128