Fred wrote:I captured all that text into a file and catted it out, similar CPU usageStill, it is a LOT of text : 1 meg
I'll zip and send. You can clearly find good packets in amongst it though which means your error handling is dodgy. It should never be possible to get massive blocks like that. Each AA start byte should mean a new block. Not sure what you are up to, but hopefully the text dump helps you out!
Fred.
EDIT BZIP2 FTW : 1meg >> 5k LOL must be a bit of parse-able repetition in there ey
Hey Fred,
I went through this log file, and apart from spewing out far too much debug information (it includes the rest of the buffer in debug messages - which I have now fixed) it does everything right.
I think your code is off! Checksums wrong in some packets.
Tell me this is right?!?:
Code: Select all
0xAA,0x08,0x01,0x91,0x00,0x60,0x63,0x25,0x64,0x5E,0x00,0x00,0x62,0x80,0xF3,0x1C,0x43,0x7C,0xE3,
0x51,0x60,0x63,0x25,0x64,0x5E,0x00,0x00,0x62,0x80,0xF3,0x1C,0x43,0x7C,0xE3,0x51,0x71,0xCA,0x27,
0x10,0x80,0x00,0x00,0x03,0x00,0x00,0x00,0x00,0xFD,0xD4,0x00,0x00,0x00,0x00,0xF3,0x1C,0xFD,0xD3,
0x5F,0xC8,0x34,0x89,0x34,0x27,0x3F,0x3B,0x00,0x00,0x00,0x00,0x00,0x00,0x3F,0x3B,0x3F,0x3B,0x00,
0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x03,0x86,0x03,0x6F,0x02,0x32,0x02,0x13,0x03,0x63,
0x03,0x98,0x03,0xD5,0x02,0x07,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x00,
0x00,0x00,0x00,0xA0,0xCC
My awesome tuner aka keeping Fred in line wrote:Checksum is incorrect! Provided: 160, generated: 46