Originally Posted by
steveo
large amounts of comm errors definitely aren't normal affair for datalogging but corvettes do have a lot on the aldl bus, maybe a device is waking up and interfering with communications. if it rejects a data packet it wont record it in the datastream...
there are some instances where the checksum isn't checked, that'll be fixed in the next version, but nobody has even really noticed since usually the datastream is really reliable.
it also rejects packets that are the wrong size, and most of the time, a garbled packet will be the wrong size.
when you see your knock counts go up during communication error events, do they go down again (to where they were before the error) right after the errors stop, and is there any other erroneous information displayed?