Its a big frame but it does reply. What you can try is sending the request a few times with the engine off, starting it and sending it some more. If its a correct response RPM should be in there so you will see a byte change. There are bytes changing in there.90base wrote:Here is the first code I entered and the response that I got.
16:25:39.716 Tx'd Frame = F4, 56, 1, B5,
16:25:39.803 Rx'd Frame = F4, 95, 1, 26, F1, 0, 0, 0, AB, 6C, FF, 1B, 0, 0, 1, 0, 0, 0, 0, 0, 5, 0, 80, 50, 48, 74, 76, 0, 7B, 2, 3C, 80, 20, 0, 0, 56, 12, 26, 23, 37, 0, 0, 0, 0, 0, 48, 0, 0, 0, 4C, 0, 0, 1B, 0, 0, 0, 0, 0, 0, 0, 1, 0, A, 0, 1F, 40, CC,
Well its good you got something back, but the problem is the ECU is short changing you! Normally a mode 2 command returns 64 bytes of data from a particular address (the 0,0 in the command says from address 0x000), your only getting 63 bytes (which is what the flashtool reported when you tried to connect the other day).90base wrote:Here is the second ommand that I entered and the response that I got.
16:26:27.293 Tx'd Frame = F4, 58, 2, 0, 0, B2,
16:26:27.384 Rx'd Frame = F4, 95, 2, FF, FF, FF, FF, 7F, 0, 0, 0, 0, 0, 0, 12, 26, 20, 15, 0, 1, 0, 0, 0, 70, 70, 50, 0, F0, 74, 23, 1B, 13, 0, A, 0, 0, 1, 0, 0, 48, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 40, 20, 1, 0, 0, 0, 0, 0, 1, 0, 0, 0, 15, BC, 0, 0, 21,
Now the coincidence here is both requests returned the same frame length. The first request is for engine data, a 63 bytes payload for that is very large in the Aussie ECU world. I think the easiest thing is to read the memcal and then go through it that way. Could waste ages trying to get logging working but you still cant read the bin to even think about making any changes.