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 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?