Skip to content

Search is only available in production builds. Try building and previewing the site to test it out locally.

Writing text to the cluster display

What one 2016 capture of an A4 B6 shows about putting text on the cluster's centre display: two lines of 8 bytes each on 0x261/0x263, a high-priority pair used by the phone on 0x265/0x267, and a status message. How to turn a string into the bytes, and what is still unknown.

Applies to: B6 onlyCommunity write-upFrom an owner’s write-up or forum thread. Not checked against factory documentation.

The instrument cluster (J285) has a centre display for the driver information system; on the highline cluster it is a colour display (Instrument cluster). The source calls it the FIS, and describes text reaching it over the infotainment CAN, from the phone and from the RNS-E. This page puts together what one 2016 capture shows about how.

All on the infotainment CAN, bytes counted from 0. Full entries in the infotainment catalogue.

ID What the source says Example frame DLC
0x261 First line of content on FIS 54 45 53 54 20 20 20 20 8
0x263 Second line of content on FIS 54 45 53 54 20 20 20 20 8
0x265 First line of content on FIS (high priority / used by phone) 54 45 53 54 20 20 20 20 8
0x267 Second line of content on FIS (high priority / used by phone) 54 45 53 54 20 20 20 20 8
0x627 Driver’s door and FIS status (printed in red in the source) 80 3A 3A 3A 3A 28 28 28 8
0x6C0 Used for RNS-E to FIS screen (explained in another post) none given 8
0x6C1 Used for RNS-E to FIS screen (explained in another post) none given 8

The source marks 0x261 to 0x267, 0x6C0 and 0x6C1 as ASCII (text) messages.

Each example frame is the text TEST followed by four spaces: 54 45 53 54 is T E S T and 20 is a space. So each frame carries 8 bytes, one character per byte, and a shorter text is padded with 0x20 to fill the frame. The source does not say whether the display shows exactly 8 characters per line, or what happens with fewer than 8 bytes.

0x261 and 0x263 are the first and second line. 0x265 and 0x267 are a second pair for the same two lines, described as “high priority” and “used by phone”. The source does not say how the cluster chooses between the two pairs.

The source describes 0x627 in three rows, all printed in red. (A search-engine summary of the post says red marks IDs whose meaning is not exactly known; the post itself could not be retrieved to confirm this.)

  • Byte 0, first hex digit: the driver’s door, 0 closed, 8 open. (The source says only “byte 0”; that it is the first digit follows from the next row.)
  • Byte 0, second hex digit: the status of the FIS screen: 0 default, 1 FIS registration, 4 P (gear).
  • Bytes 1 to 7: 28 by default. Bytes 1 to 4 become 3A when the FIS is active. All 00 when there is no FIS activity.

In the example 80 3A 3A 3A 3A 28 28 28, the door digit is 8 (open), the status digit 0 (default), and bytes 1 to 4 are 3A (FIS active).

The source says these carry text from the RNS-E to the FIS screen and that this is “explained in another post”. That post has not been found, and the source gives no example frames. How these messages work is an open question.

The cluster does not use plain ASCII for every character. The FIS character set gives the code for each one. Upper-case letters, digits and most punctuation are at their ASCII codes, but the lower-case letters a to o are moved to 0x01 to 0x0F, and p to 0x10; q to z stay at their ASCII codes.

To build the frame for one line:

  1. Look up each character in the character set. Prefer cells marked certain.
  2. Write the codes in order, first character in byte 0.
  3. Pad with 0x20 (space) up to 8 bytes, as in the source’s example.

Example: TEST. T = 0x54, E = 0x45, S = 0x53, T = 0x54, then four spaces: 54 45 53 54 20 20 20 20. This is exactly the source’s example frame.

Example: Test. T = 0x54; e is one of the moved letters, 0x05; s = 0x73 and t = 0x74 are at their ASCII codes. Padded: 54 05 73 74 20 20 20 20. In plain ASCII e would be 0x65, which in the cluster’s table is a space symbol, so the text would not show as intended. This example follows the character table; it has not been tried on a car.

The wiki’s code has the same rule as a function, encodeFisText in site/src/lib/protocols.ts, which reports characters the table lacks (such as °) and characters taken from uncertain cells.

  • Repetition. How often must 0x261/0x263 (or 0x265/0x267) be sent for the text to stay on the display, and what does the cluster show when they stop?
  • Joining the bus first. Does a device have to take part in the ring or answer the keep-alive (see Network management) before the cluster accepts text? Does the FIS status in 0x627 have to show “FIS registration” first?
  • Line length. Does the display show exactly 8 characters per line? Are shorter frames accepted?
  • Priority. How does the cluster choose between 0x261/0x263 and 0x265/0x267, and what does “used by phone” mean in practice?
  • 0x6C0/0x6C1. The protocol the RNS-E uses on these IDs is not documented here.
  • Who sends 0x261 to 0x267. The source does not say which module sends the frames it captured.
  • Cluster type. Whether lowline and highline clusters behave the same.
  • B7. Whether a B7 cluster uses the same IDs and the same character set.

Parts in the wiring data

CodeNameModelsLocation
J285Control module with indicator unit in instrument panel insertB6 and B7Behind display unit

Sources

  • Known CANID's (janssuuh, 18 March 2016) — janssuuh
    The message IDs, example frames and descriptions. Read from a screenshot of an English machine translation of the Dutch post; the original could not be retrieved to check against the screenshot.
  • Audi ASCII table (janssuuh, 1 April 2016) — janssuuh
    The character table and the remark that the letters a to o are moved. Original not retrieved (URL unknown); read from a screenshot of an English machine translation.