avincar

Thanks to Ted, Lee, and Scott at Rival, I have a OEM BT module connected to a 2006 A3 3.2 S-line with OEM nav.

We are getting a "Your phone might not be properly connected" message on the RNS.

We can't "see" the BT module with either of two BT-equipped cellphones. The VAG-COM can see it and program to it, which as I understand it involves the K line.

One theory is that the BT module is not "seeing" the ignition flag from the CAN bus. Our CAN connections seem to be OK - if we disconnect either one we get a different error message - "Your phone is not available". We are definitely on the CAN H and L wires at the back of the RNS. We

We are going nuts trying to determine what this might be. I am about to upgrade my allroad to RNS and I'm afraid that I won't know how to get that one going

I feel as if I must be missing something simple. I have tried two modules and we get the same result with either. Suggestions are appreciated.

Oh, and I can't post this at navplus.us because I can't get a reg response back from their email server.

avincar

We have also tried two antennas, and the FW is 0110

DirkM

IIRC the phone interface needs to see the instrumet cluster before a phone can see it. The cluster need to be coded for phone support as well as the RNS-E. In the A3 everyting is supposed to happen over CAN. You connect the VAg-COM via CAN to the RNS-E as well as the phone interface. The interface talks over CAN to the RNS-E (and mutes it) and it talks over CAN to the cluster (to show the number/name).

The "not available" message indicates that the RNS-E cannot see the phone interface while lthe "not properly connected" message tells you that the interface can't find a phone.

The frist step would be to get the VAG-COM talk to the RNS-E and cluster and check the coding there. If everything looks fine, connect the phone interface and check #77. If the phone interface is coded for K-line diagnostics only it may not work in the A3 because the k-line is not used there for diagnostics. The phone interface should be coded for CAN&K&Head unit.

avincar

... but I don't recall being able to get the DIS settings right. THe accomodation settings recommended didn't work, but I heard they weren't required?

DirkM

The leading 1 makes it a talk to the RNS-E. Or 12877 if you have the multifunction steering wheel. In the A3 the DIS may not need to be coded but you should confirm the long coding in the CAN Gateway (#19, Byte 03 Bit 7) has the phone enabled.

NSX JR

not sure if 0012877 will work with the A3 or not.

But, I think the big problem is that the phones will not discover the Audi bt module for handsfree pairing.

Do you guys have something in the shop that may be causing some strange interference on the BT wavelength? Long shot...

avincar

So I think that the 2.4 gig freq is clear.

DirkM

until I connected and coded the cluster correctly. If the CAN gateway doesn't know about the ohone interface, the interface may still be in standby mode (invisible to the phone) until the gateway (in the A3) or cluster (in the A4 and/or A6) gets coded properly.

avincar

Good to know... anyone know A3 cluster codes/accomodations?