DME Error code 35
#2
Rennlist Member
Thread Starter
I cleared the code and it hasn't come back in several drives so....
Just for future reference, the car hadn't been started in a week so the battery could have been low. Initially, I couldn't connect with the T-ODB Scantool until I started the car and the first start attempt failed which is unusual. The car fired, sputtered and stalled. Second start, it fired right up, T-ODB connected and I got the mysterious code 35. Running fine now, just like it always has.
Just for future reference, the car hadn't been started in a week so the battery could have been low. Initially, I couldn't connect with the T-ODB Scantool until I started the car and the first start attempt failed which is unusual. The car fired, sputtered and stalled. Second start, it fired right up, T-ODB connected and I got the mysterious code 35. Running fine now, just like it always has.
#3
RL Technical Advisor
Hi Iain,
Fault code 35 is an ABS controller exhaust valve fault and given your circumstances, may be simply random, if the battery voltage was below 12 VDC. These cars are VERY sensitive to system voltages so battery condition is paramount.
I'd suggest checking the date code on the battery to see how old it is as well as checking alternator voltages at 2K RPM to make sure you have 13.2-13.8 VDC. If that battery is more than 4 years old, its suspect.
Hope this helps,
Fault code 35 is an ABS controller exhaust valve fault and given your circumstances, may be simply random, if the battery voltage was below 12 VDC. These cars are VERY sensitive to system voltages so battery condition is paramount.
I'd suggest checking the date code on the battery to see how old it is as well as checking alternator voltages at 2K RPM to make sure you have 13.2-13.8 VDC. If that battery is more than 4 years old, its suspect.
Hope this helps,
#4
RL Community Team
Rennlist Member
Rennlist Member
I use Durametric and find at times I get all kinds of codes that when retried disappear. I think if one gets more than two or three codes at a time they should rerun the codes as it can simply be a communication or other issue as above not a real issue. Also as said above most codes can be verified by clearing them and seeing if they come back especially for some oxygen sensor and ABS codes.
#5
Rennlist Member
Thread Starter
Thanks Steve,
The battery was replaced 2.5 yrs ago so I hope it's still good. Good thought about checking the alternator - I'll take care of that this weekend.
I'll send you a PM about the knock sensor error codes and other observations after the AX this sunday.
The battery was replaced 2.5 yrs ago so I hope it's still good. Good thought about checking the alternator - I'll take care of that this weekend.
I'll send you a PM about the knock sensor error codes and other observations after the AX this sunday.
#6
Rennlist Member
Thread Starter
I just got the mysterious error code 35 and when I googled it, I found this thread.
Update:
I left the car for 9 days and then first of all, checked codes and got the unknown code 35 reported. I didn't clear it, but instead went on a day long drive not using freeways.
When I checked codes the next day, the code was gone.
Next time, I'll get the multimeter out and measure Vbatt.
Update:
I left the car for 9 days and then first of all, checked codes and got the unknown code 35 reported. I didn't clear it, but instead went on a day long drive not using freeways.
When I checked codes the next day, the code was gone.
Next time, I'll get the multimeter out and measure Vbatt.
#7
Rennlist Member
Thread Starter
This is getting like Groundhog Day.
Am I the only '95 993 owner getting this code?
At this point my guess is that it's a use flag. If there's less than X hrs of usage in 1000Hr period set the flag, if there's more than Y hrs of usage in 1000Hr period then clear the flag.
Not feeling any loss of performance in the car at all. Seems like it really is a ghost code.
Am I the only '95 993 owner getting this code?
At this point my guess is that it's a use flag. If there's less than X hrs of usage in 1000Hr period set the flag, if there's more than Y hrs of usage in 1000Hr period then clear the flag.
Not feeling any loss of performance in the car at all. Seems like it really is a ghost code.
Trending Topics
The following users liked this post:
993pbug (05-13-2020)
#10
Rennlist Member
#12
Rennlist Member
Thread Starter
Hi Jason,
I've been distracted getting bigger issues resolved but would appreciate any insight you have on this.
I know it's an early version but all I have is the data from the Scantool:
Serial Number: 99361812404
Bosch Number: 0261203675
1267358948
last line has no name but maybe is part of the code.
Can you tell the versions from these numbers or let me know where to find them?
This code came back after clearing last time with new battery and no other codes. a few good long drives and still no codes but this 35. Car is running fine to me. Any info would be great.
I've been distracted getting bigger issues resolved but would appreciate any insight you have on this.
I know it's an early version but all I have is the data from the Scantool:
Serial Number: 99361812404
Bosch Number: 0261203675
1267358948
last line has no name but maybe is part of the code.
Can you tell the versions from these numbers or let me know where to find them?
This code came back after clearing last time with new battery and no other codes. a few good long drives and still no codes but this 35. Car is running fine to me. Any info would be great.