After upgrading a 2007 Audi B7 S4 from Symphony to an RNS-E 193 (8P0 035 193 G), all functions except the phone work correctly. A Bluetooth module (8P0 862 335 J) is installed and responds to device 77 in VCDS 17.1.3 without error codes. However, the phone function remains inactive. This article explores potential solutions to this common issue, focusing on addressing the “VCDS 17.1.3 no response from controller” problem specifically related to the Bluetooth module.
While the RNS-E, radio, and navigation function flawlessly, the missing phone functionality points to a communication issue. A VCDS autoscan reveals the presence of several modules (01, 02, 03, 08, 09, 15, 16, 17, 25, 26, 36, 46, 55, 63, 73), but notably absent are modules 37 (Navigation), 56 (Radio), and 77 (Telephone). Modules 37 and 56 are expected to be integrated within the RNS-E and not addressed independently. However, module 77 (Bluetooth) should communicate, yet doesn’t function as intended.
The RNS-E primarily communicates via the K-line. The upgrade process involved disconnecting all connectors from the Symphony radio and connecting them to the RNS-E 193. Attempts to change the Bluetooth module coding from K-line (6) to CAN (4) resulted in communication errors, reverting back to K-line communication eliminated the errors but didn’t solve the phone issue. This suggests a potential incompatibility or misconfiguration between the Bluetooth module and the RNS-E’s communication protocol.
Possible solutions include verifying the correct wiring and pin assignments in the connector between the RNS-E and the Bluetooth module. Consulting wiring diagrams specific to the Audi B7 S4 and the RNS-E 193 is crucial. A pinout mismatch could prevent communication even if the module itself is functional.
Furthermore, exploring advanced VCDS functionalities like measuring blocks or adaptation channels for the Bluetooth module might reveal specific communication errors or configuration issues hindering its operation. Checking the RNS-E’s coding for telephone-related settings is also recommended. Specific coding adaptations might be necessary to enable Bluetooth functionality with the new head unit.
In conclusion, resolving the “VCDS 17.1.3 no response from controller” issue with the Bluetooth module in an RNS-E retrofit requires a methodical approach. Focus on verifying wiring, exploring advanced VCDS diagnostics, and confirming correct coding for both the Bluetooth module and the RNS-E unit. This systematic troubleshooting will likely pinpoint the root cause and restore the phone functionality to the upgraded system.
