So I've discovered that the CCM doesn't seem to appreciate foreign devices impersonating it. Wakes up and starts fouling up the bus straight-away.

After some experimentation I think I have a semi-workable logging methodology that grabs about 16 frames before yielding the bus to the CCM (for a whopping 5 frames in the same time space).

The aldl based gauges in the digital dash do! update so I'm hoping everything works ok in a real-world scenario but I'm anticipating some issues with the fuel consumption calculations.

steveo I might want to pick your brains on the .eedata layout. Think I have a handle on about 85% of the data and I have no problem reading the source but I might beg you to save me some time spent reading!