Fault code reader not showing codes?
Thread Starter
AudiWorld Junior Member
Joined: Oct 2022
Posts: 6
Likes: 0
Fault code reader not showing codes?
Hi,
I have a 2011 RS5 V8. Lately after driving the car for 30 minutes I am getting the "Do not exceed 6000rpm" error.
I bought an OBD2 fault code reader, but it says there are no fault codes found.
I thought these fault code readers where pretty much universal. Have I purchased an incorrect reader (seems to work fine, connecting and scanning for faults), this error I am seeing would record a fault code right?
tia
Shaun
I have a 2011 RS5 V8. Lately after driving the car for 30 minutes I am getting the "Do not exceed 6000rpm" error.
I bought an OBD2 fault code reader, but it says there are no fault codes found.
I thought these fault code readers where pretty much universal. Have I purchased an incorrect reader (seems to work fine, connecting and scanning for faults), this error I am seeing would record a fault code right?
tia
Shaun
AudiWorld Super User
Joined: Dec 2001
Posts: 13,996
Likes: 3,376
From: Georgia
The only tool worth buying first is a cable from Ross-Tech so you can use Ross-Tech's VCDS. If you want to spend more on nice tools like ODIS, Vag Com Pro, various Autel tablets, etc, that's fine. But for a normal Audi owner, VCDS gets it all done. It runs on Windows, so you'll need such a computer. If you did need something on a lesser scale, OBDeleven or Carista have Bluetooth modules that plug into the OBD-II port and interact with their app which runs on Android and iOS. They are at least full vehicle aware, but no, the scan log quality and the logging facilities are not on par with VCDS.
But those OBD-II generic mode Foxwell style hand helds. Yeah, I dislike those things. And OBD-II generic mode is missing a ton of stuff that Audi aware tools know how to access. And that interface UI is just slow and annoying.
I assume you mean "do not exceed 4000 rpm" message? Could be an oil pressure issue, or an EPC issue. You'd need to run the scan while the engine was still going once the message was live. Those types of error states tend to self clear on engine off.
https://www.ross-tech.com/distributors.php
HEX-V2 cable is $200 USD here in the US. Not sure what UK resellers would be trying to sell it for. OBDeleven and Carista can be looked up on their own same-named sites.
But those OBD-II generic mode Foxwell style hand helds. Yeah, I dislike those things. And OBD-II generic mode is missing a ton of stuff that Audi aware tools know how to access. And that interface UI is just slow and annoying.
I assume you mean "do not exceed 4000 rpm" message? Could be an oil pressure issue, or an EPC issue. You'd need to run the scan while the engine was still going once the message was live. Those types of error states tend to self clear on engine off.
https://www.ross-tech.com/distributors.php
HEX-V2 cable is $200 USD here in the US. Not sure what UK resellers would be trying to sell it for. OBDeleven and Carista can be looked up on their own same-named sites.
Thread Starter
AudiWorld Junior Member
Joined: Oct 2022
Posts: 6
Likes: 0
Thanks for the info.
Im sure I plugged the reader in while the engine was still running at one point. But cannot remember, so I guess I will do that next time it pops up.
And no, the message is definitely 6000rpm.
Im sure I plugged the reader in while the engine was still running at one point. But cannot remember, so I guess I will do that next time it pops up.
And no, the message is definitely 6000rpm.
AudiWorld Super User
Joined: Dec 2001
Posts: 13,996
Likes: 3,376
From: Georgia
Seems really high considering redline is 6500 rpm, no? But appears it's a message. Google search should always be a stop on path. https://www.audizine.com/forum/showt...-light-came-on
So overheating due to thermostat fault? What is the coolant temp measuring value reading at when you get the message?
So overheating due to thermostat fault? What is the coolant temp measuring value reading at when you get the message?
Thread
Thread Starter
Forum
Replies
Last Post
