I see right before the error occurs there are some random bytes changed in the message like 00 changed to 02 or 08 and the checksum byte is the same, so it it is really a checksum failure due to...
Type: Posts; User: kur4o
I see right before the error occurs there are some random bytes changed in the message like 00 changed to 02 or 08 and the checksum byte is the same, so it it is really a checksum failure due to...
I see some errors while reading e-side only. Doing some more verbose failed attemps can reveal some patterns.
I didn`t notice but did you try to read the 95 pcm in the 94 car. It is really odd...
Please do a read on the bad car with eehack, and post the verbose log. I need to see where it fails, Does it fail on the same place or fails on a fixed elapsed time, like between 20-30% . Now with...
Nothing unusual in the logs. It seems that only the ccm is talking and other modules are passive listeners, only the pcm response to the requests of the CCM. I am not sure if the CCM should talk with...
doublepost
That 94-95scan program is not configured for y-bodies at all. It tries to silence the f4 device, which is the pcm. On y-body the bus master is the CCM device with f1 id.
I think the aldl is...
I have noticed similar spikes in logs at random rate, and I was almost sure it was an error in spi communication between e and t side, due to some of the patches I had over that bus. Now that guy...
The easiest way to check if the checksum are altered is to compare the bin, if the OS part have some corrections it might be the issue. They might have changed the start-end points of checksum...