Showing returned data from ecu...

[cosmic_splatter]

Hello…

I am working in Tuner Pro on a barely understood ecu.

I have a couple of questions…

1. How does Tuner Pro RT handle list items? Below is a request being made for a list of variables…

Get Flag Data
0x13 0x09

Request Flag Data...
0x13 0x09 0x1A 0x1B 0x00 0x01 0x02 0x03

Is there some documentation on how tuner pro is processing the responses? I’ve back engineered most of a ADX file I received, but I’m having trouble finding the closed loop flag, so I wanted to experiment with setting up some test data so I can identify the closed loop address.

2. Is there a way to request a batch of addresses and watch the values? should I just setup a dash for this? Or, is there built in functionality on TunerPro to help display ecu data?

3. Can anyone provide some documentation or help files which shows how to handle returned data? I think the request above brings back lists of data. But, I’m not certain how the operand function works on the post process. Specifically the variables being matched. Is there a raw data viewer within the tool that will show the raw ecu data before bitmasks are applied?

thanks,
John

[Mangus]

How TunerPro processes the responses depends entirely on how you tell it do so in the ADX. TunerPro will send what you tell it to send via a SendCommand object in the ADX. TunerPro will then read the response however you tell it to via the ListenPacket object. If you tell it that the response is 10 bytes in length (body length = 10), then all 10 bytes will be read in. You can then tell TunerPro that the portion of the response that you care about starts within that 10-byte at offset 2 and is 6 bytes in length, for example. TunerPro will then copy off 6 bytes starting at (zero-based) offset 2 and store it away. You then define Values that reference that 6-byte packet, where the offset specified in the value object is the offset within the 6-byte packet where the value's data lives.

If you want to see the raw, unadulterated data, use a serial port monitor (portmon from sysinternals.com is a good example). You could certainly define values for every byte in the response and set the output type to raw hex, then add them to an output list if you want to see the raw value of each byte in the response, but that's a little harder to parse when troubleshooting.

You didn't mention what vehicle you're working on. It would first be good for you to understand how your vehicle communicates. It sounds like you're unsure whether the command you reference will return a list of data or not, or what the response from the ECU looks like.

[cosmic_splatter]

Thanks Mark!

Is there any documentation on using the adx "SendCommand object?"

thanks,
John