TunerPro RT data errors

[Tazzi]

Ahh right, I was wondering why the ECU was outputting a message. It did look like it was searching for a repsonse.

But that makes sense, no need to search for silence if there isnt going to be any traffic!. Might have to try simulate a valid bcm response to test out your current version!

[antus]

It will also make a difference if your logging via oseplugin or not. Obviously to tune real time you will need to be using the plugin. Oseplugin has to 'own' the data bus to share it between the data aquisition and 'emulating' (its not really emulating in the case of nvram as the changes are not written to intermediate storage but straight back to the storage device the car is running from). This introduces another minor timing thing which is part of it. If the laptop is already struggling (probably the case for most vista era machines) then this will be another factor.

I did create an oseplugin v1.51 and significantly changed the way the serial worked, but it seemed to cause more problems than it solved. I think it would be better on faster computers, but probably worse on slower computers. Because of this I didnt release it. If anyone wants to try it let me know and i'll make it available.

[Tazzi]

There should be no chatter constantly streaming from a VS PCM. Only on a bench will you see this if VATS is enabled with no BCM, the PCM will be sending frames every 100ms until there is a valid response from the BCM (which it never gets).

Anyway, give this one a shot. Changes are a small inter frame delay instead of a wait for silence (the inter frame delay time can be adjusted down to normally 5ms, longer using the normal wait for silence time it just slows logging WAY down). I have not tested the disable chatter response part, might need to disable it, but the idea is to search for the reply up to 5 times breaking once found. Looking for silence is hardly needed on pre VT though, only chatter is VATS burst at key on and VS V6 the low speed fan control (only a frame to turn on and frame for off).

Vs V6 engine and trans 1.10-tp5 - Credit to Jayme.adx

Alright Iv been at this for a while now. And seems tunerpro is glitching up, or the definition files are capturing the "frame request command" and incorporating this into the results providing invalid data!

This is the frame I get back for table 3:
F5, 80, 1, 0, 0, 0, 97, 2, 1, 12, 0, 0, 0, FF, 4, 0, 0, 68, 51, FF, 1, 67, 7F, FD, 7D, 80, 80, 80, 6, 0, 0, 0, 0, 0, 0, 0, C0, 80, 2, 0, 20, 40, 2, 0, 0, 98,

TunerPro starts at offset 0. Which is in BLUE
Then, it says the faults start at offset 32dec to offset 41dec

I checked out my guages screen on TunerPro, and my revs gauge is permantly set to 179rpm... which in hex is 0xB3... and funny enough that is the last byte of our F5,57,01,03,B3 request command!

Soooo... is there a way to clear the tunerpro RX buffer? Or to ignore the echo?

[The1]

i have updated all the enhanced adx's to include the 15ms delay between packets engine/trans and also 20/400 silence before connecting, have tested on both vs and vx and since have connected perfectly with no jumbled data or errors.

[Tazzi]

i have updated all the enhanced adx's to include the 15ms delay between packets engine/trans and also 20/400 silence before connecting, have tested on both vs and vx and since have connected perfectly with no jumbled data or errors.

Ill give that a go

[antus]

Awesome! Anyone else with a car to test on please let us know.

[0081(2)]

Ill have a go on my VY v6 flash PCM in the next few days, it always takes several goes to connect without errors

[antus]

Note that the1 updated only the adx's in his enhanced bins

[j_ds_au]

Sorry I haven't been able to try the above modified ADX'es posted recently. Unfortunately, I've been ill for several days and am still confined to bed. Hope to test them soon.

Joe.

[Tazzi]

i have updated all the enhanced adx's to include the 15ms delay between packets engine/trans and also 20/400 silence before connecting, have tested on both vs and vx and since have connected perfectly with no jumbled data or errors.

Id assume the enhanced definition files will only work if we have written an enhanced bin to the ecu? Or will most things work except for the unsupported parameters?

Ill give it a go tomorrow when Im in the VY testing.