The more relevant code is the P17E0 than the 9707. 9707 is a DFCC, it just represents the involved component. It's not actually the error code, which is the "mechanical malfunction". The P17E0 better represents the error state.
And that's what you have out there, P17E0 through P17E3 for mechanical malfunction of gear actuator sensor 1 through 4.
"new circuit boards", specifically which circuit boards? There's three different ones, and the sensor of concern is on a specific one.
You should look at Audi SSP 429 (google search) pages 36 through 41, most specifically pages 40 and 41. Page 36 shows the overview with the valve body in gray in the middle, with the travel sensors 1 through 4 to the left. You see the hooks sticking out left from the hydraulic pistons. These are what the shift forks are latched to and what the solenoid valves move to actuate the shift forks. This is broken out on 38-39. And on 40-41, it demonstrates the hall sensors that are the "sensor for gear actuator", and their interaction with the magnets on the shift forks. This is how the TCM confirms the mechanical gearing is correctly positioned for the active intention.
This therefore is what I assume that P code means, the TCM is activating the solenoid and not seeing the correct position or the expected movement per the feedback from the travel sensor. Is the issue with the hydraulic solenoid, with the hydraulic piston, with the magnets, with the hall sensor? A break in any of that would not be known except through the failure of the expected reading from the travel sensor. Unless the solenoid was electrically defective, then the supply circuit to the solenoid would probably be aware and you'd get a different P code (one of the P173x or P174x codes). I don't know what different data would invoke the P176x codes, "gear selector cannot be regulated". I assume that would be "I've got no electrical error with control, and no mechanical error with travel reading, but the value won't stay in place".
http://wiki.ross-tech.com/wiki/index...rbox_(DSG/0B5)
Here, we see there was a software fix for the P17E1 (for the travel sensor for the 1st<>3rd fork for the clutch 1) -
https://static.nhtsa.gov/odi/tsbs/20...52520-6657.pdf
But you probably need to try and find a technical document detailing the specific trigger criteria for the P17Ex codes for the DL501-7Q (type 0B5), and then review measuring values comparing those related to travel sensor 1 (for gear selector 2nd-Rev for clutch 2) vs those for travel sensors 2,3,4. Could be the fork isn't even latched to the hydraulic piston correctly.
But something about this area is what your P code is directing towards.
Bookmarks