Displaying data via CAN on the Audi FIS

Hello everyone,

To display data on an Audi (A3/S3 8L facelift) instrument cluster, which is located outside of a vehicle (without a radio/navigation system) and connected to the FIS, the following messages must be sent to the bus via a CAN interface:
ID 436 6 08 01 00 00 00 00
ID 661 8 83 01 12 A0 00 00 00 00

With these messages, the instrument cluster is informed that a radio is connected and turned on. I sent the messages to the bus every 500 milliseconds.
To access the two upper FIS lines, you only need to address the IDs 261 (line 1) and 263 (line 2).
Okay, I understand. Please provide the German text you want me to translate.
ID 261 8 01 02 03 04 05 06 07 08
ID 263 8 31 32 33 34 35 36 37 38

The following information is then displayed in the two FIS lines:
abcdefgh
12345678

Now, the only thing that would be interesting to know is how to access the middle section of the FIS. Does anyone know any more details?

Regards,
Thomas.

I have now logged the communication between the navigation system (RNS-E) and the instrument cluster and played back the logs using the can tool. Unfortunately, I can't reconstruct the display in the middle section of the FIS in that way (i.e., only showing the navigation arrows through the log in the FIS).

Does anyone have any more information on how to access or interact with this display component?

Hello,
Unfortunately, I have no idea how things work at FIS, but...
Can you please provide a trace here?

Perhaps there are similarities with the MFA+ display in the VW Passat, because in that system, I can customize the text displayed in the central section.
At least the first part, concerning network management (Ring IDs), seems to be almost the same.

What about IDs 680 and 681? Could they also contain display data, similar to what's found in the Passat?

Best regards,
Andi.

Here are two traces (navigation was started shortly after the logging began). When starting, ID 6C0 generated a lot of traffic (which suggests it's somehow related to the display).

Unfortunately, I don't know if the FIS system in Audi is structurally comparable to the MFA system in VW...

Hello Thomas,

The basic principle seems to be very similar to that of the Passat.
'6C0 definitely refers to the display data, as all the text from your photo is contained within it.'
To determine what each individual control bit represents for the display, you would need to program your own module that precisely reads the data from your small log.
The AI sends something, and you initially receive the same output, but then you can modify individual bits.

If you have the option to program your own module, I would first try the following (the RNS unit should not be connected to the CAN bus):

1. Step: The module must register itself with the ring, following these principles:

- After powering on (connecting the power supply for the first time), you wait until you have received the CAN message with ID 428 five times.

- then you send it once:

436 6 16 02 C0 04 00 00 // RING-ID Navimodul : Statusmessage um sich im Ring anzumelden
// D0=16: eigene Adresse (16 + 420 = 436)
// D1=02: Status Gerät will in den Ring
// D2,D3: irgendwelche Status Bits


- now you are only responding to the message:

428 6 16 01 00 00 00 00 // Ring-ID KI: KI spricht das nächste Gerät im Ring an
// D0: Adresse vom nächsten Gerät im Ring (16+420 =436)
// D1: 01 = normale Ringmessage


and then send the answer:

436 6 08 01 00 00 00 00 // Ring-ID Navigation: Navigation spricht das nächste Modul an ( da nur 2 Gerät im Ring sind, ist dies wieder das KI)
// D0: Adresse vom nächsten Gerät im Ring (KI) (08+420 =428)
// D1: 01=normale Ringmessage Gerät ist betriebsbereit)


You also send a message in response to:


6C1 2 A1 0F

die Antwort:

6C0 1 A3



Don't forget your message 661, which also needs to be sent periodically.


This should be enough for your tests to ensure that the ring is running normally. Note for later: When the ignition is off, you should send a different value to D1 so that the bus can enter sleep mode. However, you need to log this separately first.

Probably, a connection test between 6c0 and 6c1 hasn't been run yet. This would be the next step you would need to address.

Once you have this running, please get back to me here, and I'll provide further information on how you can continue programming it.

Nevertheless, here are a few more details about the display data (much of this is based on assumptions
6C0 8 13 52 05 82 00 1B 40 30 // Single message 5 Datenbytes werden an das KI übermittelt
// D0: 0x13 Highnibble 1=Single message, Low Nibble= 3 = 3.Message
// D1: Datentype ob Cursurmessage=52,Textmessage=57
// D2: LEN: Anzahl der Datenbytes für die Message (incl. Options Bytes)
// D3-D5 Optionsbytes
// D6-D7 Textdaten
and not actual knowledge, but it helped me with my Passat):

The data exchange with the display can occur either using a single message or through a multi-part message.

Single:

6C0 8 24 52 05 02 00 1B 40 30 // Multipart 1.Teil (Aufbau wie oben beschrieben) Cursurmessage=52, 5 Datenbytes ( 3 Optionbytes u. 2 Datenbytes)

6C0 8 25 57 07 06 00 01 2D 2D // 2.Teil Textmessage=57, 7 Datenbytes ( 3 Optionsbytes + 4 Datenbytes) ==> '----'
6C0 8 26 2D 2D 57 05 06 00 09 // 3.Teil Textmessage=57, 5 Datenbytes (3 Options + 2 Data)
6C0 8 27 65 65 57 05 06 00 09 // 4.Teil Textmessage=57, 5 Datenbytes (3 Options + 2Data) ==>
6C0 8 28 4B 4D 52 05 02 14 1B // 5.Teil ==> 'km', Cursurmessage
6C0 8 29 2C 14 52 05 02 00 2D // 6.Teil Cursurmessage=52, 5 Datenbytes
6C0 3 1A 39 16


Multimessage: (Send multiple display lines at once)

6C1 1 BB // Quttierungs byte vom KI (Bx= LowNibble(vom letzten D0-Byte + 1): BB= B+ LowNibble(1A)+1


The first data byte (high nibble) serves as an identifier for the message type: 2x = multipart message, x = sequential counter.

The low nibble includes a continuous counter used to verify the communication. This counter is also used for the low nibble in the receipt byte (Bx).

Each data block is acknowledged by the AI.
:-)


I hope this is enough to get you started for now. I need a break now .

Best regards,
Andi.

PS: If anyone has more information, please let me know.




-

Hello Andi,

Wow, thanks for the really detailed information! I'll definitely try that out soon. I will update you here again if I have any news regarding this.

Hello Andi,

Thank you for the detailed post! I've also been analyzing my logs for a few weeks, trying to identify as much as possible from the infotainment CAN bus. I can confirm your observations about the protocol on identifiers 0x6C0 and 0x6C1; I had derived the same conclusions myself. However, I wouldn't have figured out the ring messages so quickly! My CAN interface and a combination instrument will arrive in the next few days, and then I can start working more practically. So far, I have been preparing everything in Excel.
6C0 2 19 39 // D0: High Nibble = 1 (Single Message)
// D0: Low Nibble = Message Index
// D1: 39 = show buffered content on display


I have one more thing to add:
With the news, number 52.
'First, the numbers 5 and 7 are written into a buffer before being displayed.' This is likely reported using the code '39'.
:roll:

Best regards,
Sven.

Hello,

Check out this thread: http://www.canhack.de/en/viewtopic.php?t=911

The lower part of the FIS is not used by me.

hello
Martin.

Look, look, the snowman is back on board .
Welcome back Martin

Best regards,
Maxx.

Hello,

I am also experimenting with an A4 AI with ColorFIS, and I have finally managed to get it to display something.

Code:

1264097374.078; STD    ; 000006C0; 8; 24 7A 09 82 00 00 78 00  ; $z....x. 1264097374.093; STD    ; 000006C0; 5; 15 DC 00 F0 00           ; .....    1264097374.093; STD    ; 000006C1; 1; B6                       ; .        1264097374.093; STD    ; 000006C1; 3; 14 7B 85                 ; .{.      1264097374.093; STD    ; 000006C0; 1; B5                       ; .        1264097374.109; STD    ; 000006C0; 8; 26 7A 09 02 00 00 78 00  ; &z....x. 1264097374.125; STD    ; 000006C0; 8; 27 DC 00 F0 00 69 08 15  ; '....i.. 1264097374.140; STD    ; 000006C0; 8; 28 03 30 01 00 03 2F 01  ; (.0.../. 1264097374.140; STD    ; 000006C0; 8; 29 83 09 00 19 00 8F 00  ; )....... 1264097374.156; STD    ; 000006C0; 8; 2A 94 00 2A 00 5F 08 28  ; *..*._.( 1264097374.171; STD    ; 000006C0; 8; 2B 70 58 8F 5A 49 45 4C  ; +pX.ZIEL 1264097374.171; STD    ; 000006C0; 8; 2C 83 09 00 04 00 06 00  ; ,....... 1264097374.187; STD    ; 000006C0; 8; 2D 29 00 2A 00 5F 06 0A  ; -).*._.. 1264097374.203; STD    ; 000006C0; 8; 2E 70 04 06 34 39 69 04  ; .p..49i. 1264097374.203; STD    ; 000006C0; 8; 2F 04 35 2C 01 83 09 00  ; /.5,.... 1264097374.218; STD    ; 000006C0; 8; 20 2D 00 34 00 97 00 5B  ; .-.4...[ 1264097374.218; STD    ; 000006C0; 8; 21 00 69 0C 72 37 9E 00  ; !.i.r7.. 1264097374.234; STD    ; 000006C0; 8; 22 5E 38 0B 00 57 54 9F  ; "^8..WT. 1264097374.250; STD    ; 000006C0; 2; 13 00                    ; ..      1264097374.250; STD    ; 000006C1; 1; B4                       ; .        1264097374.265; STD    ; 000006C0; 2; 14 39                    ; .9      1264097374.265; STD    ; 000006C1; 1; B5                       ; .

text
The following code generates an image.



Has anyone decoded the command set yet? Or any individual commands, for that matter? It seems to work differently than with monochrome FIS.

Sure, here's the translation:

"Addendum:"

I also found out the following:

This command either deletes or switches to the navigation screen.

Code:

6C0    8 26 7A 09 02 00 00 78 00  // D0: High Nibble = 2 (Multi Message)                                   // D0: Low Nibble = Message Index                                   // D1: Befehl                                   // D2: LEN: Anzahl der Datenbytes für die Message 6C0    5 17 DC 00 F0 00  // D0: High Nibble = 1 (Singel Message)                          // D0: Low Nibble = Message Index

This command outputs a text.

Code:

6C0   8 28 5F 0B 21 70 00 10 4A   // D0: High Nibble = 2 (Multi Message)                                   // D0: Low Nibble = Message Index                                   // D1: Befehl (5F = Textausgabe)                                   // D2: LEN: Anzahl der Datenbytes für die Message, hier 11 Byte                                   // D3 hat irgendwas mit der Schriftgröße und der x Position zu tun, bzw. ob Zentriert                                   // D4 hat irgendwas mit der Farbe und Negativschrift zu tun                                   // D5 ??? eventl. x Position ???                                   // D6 y Position                                   // D7 Textdaten                                  6C0   7 19 41 43 4B 53 4F 4E   // D0: High Nibble = 1 (Singel Message)                                // D0: Low Nibble = Message Index                                // D1-D6 restlichen Textdaten

Hello Jackson,

Congratulations, you're already quite far in understanding the protocol!
You understood what the first byte in each CAN message means, as shown in your second image. Now, use this knowledge to break down the entire data stream into individual message blocks, or combine the individual CAN messages into message blocks. Then, start with the first one: for example, it begins with 7A, followed by the number of subsequent bytes. But there might be even more after that... another command? You'll discover some more patterns and meanings this way.

Have fun!
Sven.

Here's a little something extra...


However, it doesn't seem suitable for taking quick pictures... http://www.youtube.com/watch?v=zG5QBSweB6M

reieg99 wrote:

Hello Thomas, The basic principle seems to be very similar to that of the Passat.

Hello Andy,

Does the Passat FIS seem to be identical to the Touran FIS?

At the very least, both cars should have the same CAN gateway (1K0 907 530).

Do you have more detailed information on how to register for this "am Ring" event? Or, how many devices can be registered at most?
During my experiments, I didn't register for the ring, and it also works (6C0/6C1).

I saw in an IT-Can log for a Touran that the display is being controlled with the values 680/681, 682/683, and 684/685.
There were definitely a navigation system and a Bluetooth hands-free system installed.

I also have an org. "I installed a BT-FSE in my A4, and it's communicating with the 6C4/6C5 system, but I can't make or receive calls."
displayed only on the RNS-E, not on the central display unit.

Do you know on which ID the BC navigation buttons (up, down, reset) are transmitted in the IT bus?

Hello Jackson,


Does the Passat FIS seem to be identical to the Touran FIS?


Yes, at least with my module, I was able to read the FIS data in both vehicles.



Do you have more detailed information on how to register for this 'am Ring' event? Or, how many devices can be registered at most?
During my experiments, I didn't register for the ring, and it also works (6C0/6C1).


Not really . But I had described it in more detail before on the T5 board. After that, others also managed to register their module in the ring. Here is the link to the post: Passat 3C / TP 1.6 / CAN-Bus - Telephone module emulation

I've also heard that ring registration isn't required. However, with my module, I want to simulate the original phone module. Therefore, I have implemented the same approach with rings in my own system.


I saw in an IT-Can log for a Touran that the display is being controlled with the values 680/681, 682/683, and 684/685.
There were definitely a navigation system and a Bluetooth hands-free system installed.


680/681 = Radio/Navigation
684/685 = Telephone module
682/683 = ???


Do you know on which ID the BC navigation buttons (up, down, reset) are sent on the IT bus?
No. But someone here probably knows .

Best regards, Andy.

Hello Andy,

Thank you for the answer. The link for the T5 board is good; I will take a closer look at it later.

"These are definitely parallel to the A4 format."

For the A4 model, the part numbers appear to be 428, 436, and 43A.

Yesterday, I tried again to output the same data via interfaces 672/683 and 684/685 as I had previously done via 680/681, but...
Does the AI not respond as expected, or does it not respond to the provided addresses at all?

I suspect that higher-tier addresses require a mandatory registration process.

Apparently, the BC (Basic Control) buttons on models like the Passat use the ID 2C1 communication protocol. I'm still looking for the relevant information for the A4.

By the way, the MC chip that controls the color-FIS is a BOSCH Rainbow 1.1.
I would like more information about him, but unfortunately, I can't find anything about him online.