Hi there.
This is seriously annoying issue i have, the famous 65535 code in my 3b. Well, that is a 200 20v 3b.
This:
65535 - internal control module memory error
35-00 - -
I know this was discussed before, but I have a very strange way to trigger it.
It is not there all the time. I know, all the grounds have been cleaned, tested for Vdrop to chassis and no luck here. I have actually measured that at ecu pins on a running car. Vdrop to chasis is zero to none, or just a little bit.
Next culprit is the chips i have. And they are not good. They run 1.3bar of boost with 200kpa sensor (read: unsafe). I know i have to change that to proper software.
this is my soft http://www.s2forum.com/forum/showthread.php?t=74832
But lets get back to 65535.
It is never triggered on cold start and running the engine to normal temperature. It is even not triggered when restarting a hot engine. BUT IT IS ALWAYS TRIGGERED WHEN RESTARTING A WARM ENGINE i.e. if the car was used normally, I go home from work, the engine cools down to ~50-60 deg. C, then upon restarting a car and driving for approx 1-2 minutes, it comes on. Always like this. ofc it is not always triggered, but if it is, it is on the aforementioned conditions. CEL comes on, i have to connect vcds or pull the fuse to clear the code. This is my daily.. Annoying.
So the question is: is this weird *** behavior similar to you? was it chips or grounds in the end? Maybe there are conditions on how ecu tests checksum of EEPROM in chips?
Honestly i do not expect for somebody to know. But there is hope
This is seriously annoying issue i have, the famous 65535 code in my 3b. Well, that is a 200 20v 3b.
This:
65535 - internal control module memory error
35-00 - -
I know this was discussed before, but I have a very strange way to trigger it.
It is not there all the time. I know, all the grounds have been cleaned, tested for Vdrop to chassis and no luck here. I have actually measured that at ecu pins on a running car. Vdrop to chasis is zero to none, or just a little bit.
Next culprit is the chips i have. And they are not good. They run 1.3bar of boost with 200kpa sensor (read: unsafe). I know i have to change that to proper software.
this is my soft http://www.s2forum.com/forum/showthread.php?t=74832
But lets get back to 65535.
It is never triggered on cold start and running the engine to normal temperature. It is even not triggered when restarting a hot engine. BUT IT IS ALWAYS TRIGGERED WHEN RESTARTING A WARM ENGINE i.e. if the car was used normally, I go home from work, the engine cools down to ~50-60 deg. C, then upon restarting a car and driving for approx 1-2 minutes, it comes on. Always like this. ofc it is not always triggered, but if it is, it is on the aforementioned conditions. CEL comes on, i have to connect vcds or pull the fuse to clear the code. This is my daily.. Annoying.
So the question is: is this weird *** behavior similar to you? was it chips or grounds in the end? Maybe there are conditions on how ecu tests checksum of EEPROM in chips?
Honestly i do not expect for somebody to know. But there is hope
Comment