Extra byte in Message6?

[festy]

Looks like tp5 does use byte 2:

Code: Select all

00000280	3.59842968	[3140] Sending 6 byte packet to device F4	
00000281	3.59845138	[3140] Packet length: 6	
00000282	3.59855819	[3140] TX: 	
00000283	3.59862494	[3140]   0: F4	
00000284	3.59869123	[3140]   1: 58	
00000285	3.59875798	[3140]   2: 0D	
00000286	3.59882450	[3140]   3: FF	
00000287	3.59889102	[3140]   4: 80	
00000288	3.59898758	[3140]   5: 28	
00000289	3.59911609	[3140] F4 58 0D FF 80 28 	
00000290	3.60018277	[3140] write complete, ok	
00000291	3.60937595	[3140] read 0xF4 from ecu, ok	
00000292	3.60945630	[3140] read 0xD6 from ecu, ok	
00000293	3.60953164	[3140] Incoming 132 byte ALDL packet from device F4	   <------ here
00000294	3.60960698	[3140] read 0x0D from ecu, ok	
00000295	3.60968184	[3140] read 0x4F from ecu, ok	
00000296	3.60975671	[3140] read 0x53 from ecu, ok	

[VL400]

Thats with the antus' OSE Plugin yeah? That does use byte 2 for determining the length

[festy]

Yep, that log is from the plugin.

[festy]

I've changed my code to expect the packet length to be as specified in the ADX initially - then once it's coming in, check byte 2 and adjust the message buffer if they disagree.
I'm still able to maintain 33Hz logging with message6 so it didn't impact the speed like I thought it might - and it now works for both 12P ADXs without changing anything so happy again