Audi Forum banner
61 - 80 of 98 Posts
Discussion starter · #61 ·
A quick note about the wire harness. There are three connections which I consider 'options' and not everybody has a use for them:

Pin 2 - GRY - Reverse - only used by people installing reverse camera in older cars.
Pin 7 - BRN - MFSW - only used by people hooking up to the non-CAN MFSW controller.
Pin 8 - BLU - PTT - used by many people without MFSW to initiate BT or SDS.

If you are not going to use one or more of these options, it is a good idea to cut the wire off, at least make it much shorter and make sure it can not short to anything.

Bjarne
 
Discussion starter · #63 ·
By now everybody who expressed an interest in CANGate has been notified (a couple of weeks ago) and everybody who paid has been shipped. As usually happens a number of people who expressed interest did not get back to me to actually buy one, so I have some left over.

If anybody still wants one let me know, and thank you to all of you who purchased from this batch.:D

If you have any installation problems or questions, it will benefit everybody if you post it here.

Bjarne
 
Huge thank you to bjarne!!

Wanted to give a big Thank You to bjarne for helping me to get the MFSW buttons working on my allroad with TIP buttons on the steering wheel as oddly, the signals that the TIP wheel sends to the RNS-E is different than those that the non TIP steering wheel sends. Through logging by me and very few firmware edits by bjarne, my MFSW now works great to control the RNS-E and I saved the money on having to buy a CAN capable MFSW module from Audi for $200+.

During the install I took a couple pics of the wire to tap into for the MFSW feed to the CANGagte module, so here they are. I put some notes on each pic describing what I did also. I then tucked my CANGate box into the center console into a small cubby hole in the drivers footwell as the space behind the RNS-E is limited and also this allows for easy access to hook up the USB cable for future updates if needed.

Rich






















Here is where I put my CANGate module:







 
Discussion starter · #69 ·
Rich, thank you for all your help, I am glad we got your MFSW working. I noticed that your MFSW controller is 621, and not the 'standard' 608 controller. Of course because of your TIP SW, but as you said it was surprising to see that the codes were different.

Also thank you for the install pictures, I am sure they are going to help someone. They may even entice me to clean up my tap. I originally was in a hurry to just get some data to investigate the communication, that I just soldered the wire into the controller itself. It has been working this way for some 3.5 year so maybe I will just leave it :D

Bjarne
 
Discussion starter · #77 ·
I have not updated the feature list for CANGate for a long time, and I have received several request for an explanation of the features, so here is an attempt to update it.

CANGate can be used to log data from the CAN bus and will tell if the data is from the cluster or from the RNS-E. The commands to set up logging and filtering are documented in the instruction sheet that comes with CANGate.

The following applies to firmware version 2.04.1, but also to version 2.03.0 except for the addition of the TIP steering wheel to the MFSW decodes in 2.04.1 (thanks ricam78 ).


A couple of things are automatic:

CANGate detects whether clock translation is needed and does the translation (B5/C5).

If GALA data is missing in the Speed Message (B5/C5) CANGate will insert it. This allows the RNS-E to be coded for A4 (or Lambo) in the B5/C5, giving the option for the S4/RS4 startup screens outside US.

If a momentary switch is connected between the PTT wire (blue) and ground, it will initiate a PTT action for the OEM BT module. This has successfully been used outside US for SDS.

If the Reverse wire (Gray) is connected to a 12V reverse signal then CANGate will insert the reverse bit in the proper CAN Message. I believe this is primarily used by people installing Backup Cameras.

Other options are controlled by the Option Code:

?XXXXXXX VIN mode (option[0])
0 - Normal mode
1 - Send VIN information

This option sends the VIN message to the RNS-E. The VIN itself is set with the 'v' command. The original reason for this was that some people had the RNS-E constantly asking for the code, and this seemed to help. More recently I have been told that the 2010 and newer RNS-E requires the VIN to operate correctly, and I have had one user confirm that it worked for him.

X?XXXXXX Turn off mode (option[1]) (Only for US RNS-E)
0 - Normal mode (turn off with ignition)
1 - Key mode (turn off when key removed)

This option makes the US firmware operate like the EU firmware in that the RNS-E does not turn off until the key is removed from the ignition.

XX?XXXXX Turn on mode (option[2])
0 - Normal mode (turn on with ignition)
X - (X = 1-9) Key mode (turn on X sec after ignition)

This option delays the turn on of the RNS-E for X seconds. Was implemented for some experiments with the red DIS, but does not have any real use.

XXXX?XXX Video (option[4])
0 - Normal mode (no action)
+1 - Enable TV mode

This option will send the TV present message to enable the TV option on the RNS-E. This was implemented for people installing CarPC in the car. TV option is gone in US firmware 250 and later. This should not be confused with VIM enabling, which requires the VIM hack.

XXXXX?XX MFSW (option[5])
0 - Normal mode
1 - Decode MFSW data (608 Controller)
2 - Decode MFSW data (621 Controller - TIP MFSW)
3 - Enable Switch for BT full function

This option, when combined with connecting the MFSW wire (brown) to pin 18 of the MFSW controller, will decode the bit stream from the MFSW buttons and create the proper CAN messages. Both the 608 and 621 controllers are now supported.

The last setting (3) is an attempts to get more function out of a single button, if the button is held for a couple of seconds it will tell the BT module to display the phone book in the DIS. Short pushes will then cycle through the list and finally a long push again will dial the number. This last option is purely experimental and I don't think anybody is using it.

XXXXXX?X Illumination (option[6])
0 - Normal mode
+1 - Use fixed button dimmer value with day/night mode (+4)
+4 - Day/night mode based on dimmer value

This option (+4) determines how the RNS-E sees light on/off. In normal mode the light message is based on the position of the light switch, where when turning the switch will turn RNS-E illumination on and also switch the display to night mode (if in auto). In +4 mode the light message is based on the brightness in the car (cluster photocell) and the RNS-E will turn the button illumination and night mode (if in auto) when the brightness in the car is below a certain threshold. It will switch back to day mode when the brightness exceed another threshold. The low and high thresholds are set with the 'dl' and 'dh' commands, respectively. dl must always be less then dh, and the difference defines the hysteresis.

+1 sets a fixed light level in the RNS-E. Probably useless, and I forget why it is there, probably to solve somebody's problem :)

XXXXXXX? Second DIS Line (option[7])
0 - Normal mode (Normal display)
1 - Display speed in DIS (MPH)
2 - Display speed in DIS (Km/h)
3 - Display Dimmer Values

This option controls the second top line in the DIS. While is primarily meant to provide me with a way to debug certain firmware computations, some people like to see the speed here.
 
Quick question about fitting this with a bluetooth handsfree kit. Which side of the cangate should it go? Car bus side or RNS-E side? Or does it make a difference?

Are there any other considerations?

Many thanks

Doug
 
61 - 80 of 98 Posts