2009 Audi Q7 3.6L - Not cranking
Thread Starter
AudiWorld Junior Member
Joined: Dec 2018
Posts: 25
Likes: 1
2009 Audi Q7 3.6L - Not cranking
Unlock car (with fob) and dome lights come on but nothing on the instrument cluster. Turn the key and steering wheel doesn't unlock not does the car crank. Note that I do not have the push button start. It’s the physical key on fob that turns in the ignition switch
Found faults in the Control Module for Access and Start Control
00456 - Control Module for Access and Start Control (J518)
004 - No Signal/Communication - Intermittent
01176 - Key
004 - No Signal/Communication
Looks like this may be the dreaded issue with the steering wheel lock but how can I confirm its not the ignition module or something else?
Found faults in the Control Module for Access and Start Control
00456 - Control Module for Access and Start Control (J518)
004 - No Signal/Communication - Intermittent
01176 - Key
004 - No Signal/Communication
Looks like this may be the dreaded issue with the steering wheel lock but how can I confirm its not the ignition module or something else?
AudiWorld Super User
Joined: Jan 2021
Posts: 4,568
Likes: 1,456
From: USA - NM
If it's the steering wheel lock/failed microswitches issue, then you would have had to use the special, three-step protocol to even be able to scan the car for fault codes, as that is how you bypass the security lockout function, etc. Normally you can then reset the fault code via scan tool and it will be fine/normal for awhile, but no telling how long that will last, so keep the scan tool handy, or when it is unlocked you can de-pin the wiring connection or snip the wire (see videos) that energized that steering lock mechanism, but only while it is unlocked!!!. 
Like always on a Q7, look up the specific fault codes it gives you, and review related threads on same topic that come up via that error code search, etc. There are plenty of videos online and archival threads on this and other websites that discuss this topic/error codes. Always ensure your battery is well charged and the key fob battery is fresh as well.
Like always on a Q7, look up the specific fault codes it gives you, and review related threads on same topic that come up via that error code search, etc. There are plenty of videos online and archival threads on this and other websites that discuss this topic/error codes. Always ensure your battery is well charged and the key fob battery is fresh as well.
Thread Starter
AudiWorld Junior Member
Joined: Dec 2018
Posts: 25
Likes: 1
I did look up the fault codes on Ross tech and have read many threads on the J518 module but none really address how to be certain that is the fault or how to diagnose a failing ignition module.
I have reset the error code and the only one coming back every time I turn the key is the 004 Key - no communication
also note that to do a scan I am either turning on the emergency lights and holding the brake pedal or jumping pin 1 and 16 on the odb
I have reset the error code and the only one coming back every time I turn the key is the 004 Key - no communication
also note that to do a scan I am either turning on the emergency lights and holding the brake pedal or jumping pin 1 and 16 on the odb
Last edited by njfive; Jan 11, 2025 at 04:41 PM.
AudiWorld Super User
Joined: Jan 2021
Posts: 4,568
Likes: 1,456
From: USA - NM
The key not recognized intermittent fault code could be a unique issue, but I'll leave that up to you to review the other cases where it was the steering lock control module as the underlying problem to see if both those fault codes are/were present initially also.
Follow the codes, and be sure to pay attention to the date/time stamps present on each code in VCDS, along with how many times the code has popped/auto-reset, etc. That error code history data can tell you which came first, the chicken or the egg...figuratively speaking, and that's important when you have competing fault codes.
Follow the codes, and be sure to pay attention to the date/time stamps present on each code in VCDS, along with how many times the code has popped/auto-reset, etc. That error code history data can tell you which came first, the chicken or the egg...figuratively speaking, and that's important when you have competing fault codes.
Thread
Thread Starter
Forum
Replies
Last Post
enatman
Q7 MK 1 Discussion
2
Jul 23, 2022 04:28 AM
jimjpublic
A6 / S6 (C6 Platform) Discussion
3
Jul 1, 2021 05:40 AM
jackj518
Q7 MK 1 Discussion
1
Nov 5, 2020 12:19 PM
