Tunerpro Data issues-Help implementing a solution?

So this is the information Mark sent back to me about the bad data issues:

During the bad data, the ECM is sending the F0, F4, and E4 module data, when you’re only requesting the F4 module communication. I’m thinking the issue is that the other modules aren’t being silenced. I don’t know enough about the LT1 ECMs [EDIT: I'm using a P66 V6 ECM, not the LT1-but the communications appear similar, I guess?] to know why this might be happening, though. Perhaps it just comes down to adding silence commands to the connection macro.



Example of what I’m seeing in the logs:



DataAcq Write

0000: F4 57 01 00 B4 .W...

DataAcq Read

0000: E4 0A 58 00 03 ..X..

Looking for packet...

DataAcq Read

0000: DA C1 F4 57 01 00 B4 F4 95 01 16 16 60 24 00 02 ...W........`$..

0010: BF FF 00 D8 00 80 80 00 00 F5 C2 00 0C 7A 7B 00 .............z{.

0020: 00 3C 0D 90 00 00 00 00 05 00 00 00 00 40 44 00 .<...........@D.

0030: 20 00 03 00 00 21 20 30 02 00 5E 02 00 00 00 00 ....! 0..^.....

0040: 00 00 00 ...

52.448: Command/Reply Success

END MACRO: ECM Mode 1 Message 0 Reply

BEGIN MACRO: ECM Mode 1 Message 0 Macro

DataAcq Write

0000: F4 57 01 00 B4 .W...

DataAcq Read

0000: F0 56 E4 D6 0A



In the big read in this example, you can see the tail end of a previous packet, followed by the F4 57 01 00 B4 echo, followed by the (highlighted) start of the F4 module’s message 1 reply, then the packet.



You might be able to align on the reply’s static header data (F4 95 01).



-Mark

Anyone got any ideas how I can implement some of Mark's suggestions? I am not familiar with how Tunerpro currently aligns the incoming data, so I am not sure how to alter what it looks for.

If anyone has any other ideas that would help, please feel free to add them-I'll present a list of things I have tried below:

Reducing or eliminating the buffer size in the serial hardware-This reduces the data rate in tunerpro but seemed to help at one point.
Adding pause-for-silence commands to the communication macro, from 10 to 50 to 200ms by 10ms increments-didn't do anything at all.
Adding a mode 8 command to halt communications prior to sending a request for data-this didn't make any difference at all to the data.

I've linked a video of the normal data issues I see with tunerpro. This video shows what kind of data issues I've been fighting, and Mark's analysis of what might be causing it.

https://www.youtube.com/watch?v=pDauuA51N8Y