TunerPro RT data errors

[j_ds_au]

OK, I'm up and about today, so gave those ADX files (for VS) a go ...

"Vs V6 engine and trans 1.09-tp5 - Credit to Jayme.adx" and "Vs V6 engine and trans 1.10-tp5 - Credit to Jayme.adx" : Both ran for 5 minutes without data errors. However, I'm not convinced all data is correctly decoded, eg. DTC codes 16 & 17 were shown, though not really present.

"VS_V6_$51_Enhanced_v1.4d.adx" : Took about 8 minutes to clock up 20 data errors. Data looked good. Made a few tweaks and now it runs for 5 minutes without data errors. Data looks good. Tweaked "VS_V6_$51_Enhanced_v1.4e.adx" is attached ...

VS_V6_$51_Enhanced_v1.4e.adx

(155.81 KiB) Downloaded 491 times

Joe.

[The1]

sounds like you have other issues, what did you change? it 1.10 looks the same as yours, enhanced is the same as 1.10 so your results are random

[Tazzi]

OK, I'm up and about today, so gave those ADX files (for VS) a go ...

"Vs V6 engine and trans 1.09-tp5 - Credit to Jayme.adx" and "Vs V6 engine and trans 1.10-tp5 - Credit to Jayme.adx" : Both ran for 5 minutes without data errors. However, I'm not convinced all data is correctly decoded, eg. DTC codes 16 & 17 were shown, though not really present.

"VS_V6_$51_Enhanced_v1.4d.adx" : Took about 8 minutes to clock up 20 data errors. Data looked good. Made a few tweaks and now it runs for 5 minutes without data errors. Data looks good. Tweaked "VS_V6_$51_Enhanced_v1.4e.adx" is attached ...

VS_V6_$51_Enhanced_v1.4e.adx

Joe.

Sounds like you are getting the same issues as I was Joe. Does the RPM show something like 180rpm or something like that without the engine even on? I was getting that constantly because TunerPro was including part of the "request" frame which threw out all the results by 5bytes.

I had no dramas with the enhanced versions on the VS V6 ecu or on the VY V6. Ill try out the VT adx on the VT V6 ecu I have here.

[j_ds_au]

@The1 : I changed the timeouts from 100ms to 400ms and increased the Engine data and Transmission data payload lengths by 1 byte.

@Tazzi : Yes, I saw the same issue with RPM! Decided to concentrate my efforts on the Enhanced ADX instead, since it showed sensible numbers and provides more functionality.

Joe.

[Tazzi]

Yes, I saw the same issue with RPM! Decided to concentrate my efforts on the Enhanced ADX instead, since it showed sensible numbers and provides more functionality.

Joe.

Yeah mine was saying no errors.. but the data was just so off!

On a VS, it sends a request of: F5,57,01,00,XX (XX is checksum)
And gets a response back of something like: F5,80,01,YY,YY,YY,YY,YY,YY,YY,YY,YY,YY ect

But what TunerPro is doing, is its capturing this: F5,57,01,00,XX,F5,80,01,YY,YY,YY,YY,YY,YY,YY,YY,YY,YY
Its only meant to get the second, and not grab the initial request frame

[slewinson]

Yes, I saw the same issue with RPM! Decided to concentrate my efforts on the Enhanced ADX instead, since it showed sensible numbers and provides more functionality.

Joe.

Yeah mine was saying no errors.. but the data was just so off!

On a VS, it sends a request of: F5,57,01,00,XX (XX is checksum)
And gets a response back of something like: F5,80,01,YY,YY,YY,YY,YY,YY,YY,YY,YY,YY ect

But what TunerPro is doing, is its capturing this: F5,57,01,00,XX,F5,80,01,YY,YY,YY,YY,YY,YY,YY,YY,YY,YY
Its only meant to get the second, and not grab the initial request frame

Looks like echo is on.

Simon

[antus]

You mean off but should be on? Yes the first F5 packet is the echo of the request and when echo is on the software should eat it so only the proper payload is treated as the reply.

[Tazzi]

You mean off but should be on? Yes the first F5 packet is the echo of the request and when echo is on the software should eat it so only the proper payload is treated as the reply.

Exactly what I thought. Echo is definately clicked on the adx's

*Edit
Oh, take that back, looks like all the VS adx's have the echo box disabled
Bet thats gonna make a difference

[j_ds_au]

Oh, take that back, looks like all the VS adx's have the echo box disabled
Bet thats gonna make a difference

Well, that takes the cake! That's such a dumb/unexpected mistake, I didn't even check for it. How many years have those files been out, yet nobody noticed? Crazy!

BTW, it would have helped if TunerPro RT didn't just ignore the checksum byte.

Joe.

[antus]

If using oseplugin (eg using the1's enhanced) then it'll use its own echo setting and pass tunerpro whatever it is expecting (echo or not echo). Thats probably how it wasnt noticed.