Version: 2024-03-17


Contents


Delivery contents

The FIS-Control consists of the main control unit and the car specific cable set.
The control unit is the same for all supported car models. With the correct cable set it can be used with all cars.

FIS-Control and FIS-Control Light

Example: Cable set for installation behind cluster

Example: Cable set for installation at the CAN gateway

Installation

Dependent on the car, the cable set is either inserted into the cable harness of the instrument cluster or plugged into the CAN gateway. There is no need to cut any wires to do so. Installation (and also removal) of the FIS-Control will not cause any modification or damage to the original cable harness.

The cable connectors are marked with shrinking hose in different colors.

The sockets of the FIS-Control are labeled A to F.

The FIS-Control Light does not have the connector "D".

Audi A2

Installation

  1. Turn off the ignition and pull the key out.
  2. Remove the cluster instrument.
  3. Plug the included cable set between the cluster and the original cable harness.
  4. Plug the connectors of the cable set into the FIS-Control.
  5. Please note: The 2-pin plug with yellow shrinking hose of the blue cable is not used and should not be plugged in.
  6. Insert cluster and place the FIS-Control box at a suitable location.

Coding of the instrument cluster

To be able to send data to the display of the instrument cluster, the FIS-Control uses the CAN bus addresses of the telematics and phone module. The instrument cluster only accepts these addresses when these both devices are enabled in the CAN bus installation list. This is done by coding the adaptation channel 62 of the instrument cluster to the values "15". More information about that in the related chapter.
Alternatively the FIS-Control also use the addresses of the navigation system and the radio. This is only possible when none of these devices is already installed. The adaptation channel 62 has to be coded to the value "5" in this case.
Please note: As long as the instrument cluster is not properly coded, the FIS-Control will not work and the normal board computer will not respond to button presses of the wiper control stalk.

Compatibility

No known limitations.

Audi A3/S3 8L (model year 1998 - 1999)
Audi A4/S4 B5 (model year 1998 - 1999)
Audi A6/S6 C5 (up to model year 2000)

Installation

  1. Turn off the ignition and pull the key out.
  2. Remove the cluster instrument.
  3. Plug the included cable set between the cluster and the original cable harness.
  4. Plug the connectors of the cable set into the FIS-Control.
  5. Insert cluster and place the FIS-Control box at a suitable location.

Coding of the instrument cluster

To be able to send data to the display of the instrument cluster, the FIS-Control uses the 3-wire-bus. The 3-wire-bus has to enabled in the instrument cluster if necessary. If the current coding value is less than "16000", then "16000" has to be added. More information about that in the related chapter.
Please note: As long as the instrument cluster is not properly coded, the FIS-Control will not work and the normal board computer will not respond to button presses of the wiper control stalk.

Compatibility

Unlike the FIS-Control, the FIS-Control Light does not support the 3-wire-bus and is not compatible.
If a radio is installed, that normally displays the station name in the cluster display, this will be dropped as soon as the FIS-Control is installed. The output from navigation systems (guiding directions and station names) will still be shown.

Audi A3/S3 8L (from model year 2000)

Installation

  1. Turn off the ignition and pull the key out.
  2. Remove the cluster instrument.
  3. Plug the included cable set between the cluster and the original cable harness.
  4. Plug the connectors of the cable set into the FIS-Control.
  5. Please note: The 2-pin plug with yellow shrinking hose of the blue cable is not used and should not be plugged in.
  6. Insert cluster and place the FIS-Control box at a suitable location.

Coding of the instrument cluster

To be able to send data to the display of the instrument cluster, the FIS-Control uses the CAN bus addresses of the telematics and phone module. The instrument cluster only accepts these addresses when these both devices are enabled in the CAN bus installation list. This is done by coding the adaptation channel 62 of the instrument cluster to the values "15". More information about that in the related chapter.
Alternatively the FIS-Control also use the addresses of the navigation system and the radio. This is only possible when none of these devices is already installed. The adaptation channel 62 has to be coded to the value "5" in this case.
If a navigation system is installed that is connected to the instrument cluster via 3-wire-bus, the FIS-Control should be also run in 3-wire-bus-mode. There is no need to change the cluster coding in that case.
Please note: As long as the instrument cluster is not properly coded, the FIS-Control will not work and the normal board computer will not respond to button presses of the wiper control stalk.

Compatibility

The instrument clusters with the part number "8L0 920 933 N" (software version "M73 D07") and part number "8L0 920 930 B" (software version "VDO D09") do not support the telematics channel on the CAN bus. Therefore the FIS-Control has to use the address of the navigation system or the 3-wire-bus (only available with the FIS-Control, not with the FIS-Control Light). So the FIS-Control can only be used with this cluster, if no navigation system (that displays data on the screen of the instrument cluster) is installed, or the navigation system uses the 3-wire-bus.
With the instrument cluster with the part number "8L0 920 930 A" and the software version "M73 D16" the FIS-Control can only be used in 3-wire-bus mode. Additionally it is not possible to display pixel graphics. That means: no startlogo, no line graphs, no boost bar graph, no snake game. The FIS-Control Light can not be used with this cluster.

Audi A4/S4/RS4 B5 (from model year 2000)

Installation

  1. Turn off the ignition and pull the key out.
  2. Remove the cluster instrument.
  3. Plug the included cable set between the cluster and the original cable harness.
  4. Plug the connectors of the cable set into the FIS-Control.
  5. Please note: The 2-pin plug with yellow shrinking hose of the blue cable is not used and should not be plugged in.
  6. Insert cluster and place the FIS-Control box at a suitable location.

Coding of the instrument cluster

To be able to send data to the display of the instrument cluster, the FIS-Control uses the CAN bus addresses of the telematics and phone module. The instrument cluster only accepts these addresses when these both devices are enabled in the CAN bus installation list. This is done by coding the adaptation channel 62 of the instrument cluster to the values "15". More information about that in the related chapter.
Alternatively the FIS-Control also use the addresses of the navigation system and the radio. This is only possible when none of these devices is already installed. The adaptation channel 62 has to be coded to the value "5" in this case.
If a navigation system is installed that is connected to the instrument cluster via 3-wire-bus, the FIS-Control should be also run in 3-wire-bus-mode. There is no need to change the cluster coding in that case.
Please note: As long as the instrument cluster is not properly coded, the FIS-Control will not work and the normal board computer will not respond to button presses of the wiper control stalk.

Compatibility

The instrument clusters with the part number "8D0 920 930 C" (software version "VDO D09") and part number "8D0 920 930 Q" (software version "VDO D07") do not support the telematics channel on the CAN bus. Therefore the FIS-Control has to use the address of the navigation system or the 3-wire-bus (only available with the FIS-Control, not with the FIS-Control Light). So the FIS-Control can only be used with this cluster, if no navigation system (that displays data on the screen of the instrument cluster) is installed, or the navigation system uses the 3-wire-bus.
With the instrument cluster with the part number "8D0 920 930 A" (software version "M73 D16") it is not possible to display pixel graphics. That means: no startlogo, no line graphs, no boost bar graph, no snake game. This cluster only supports the 3-wire-bus.

Audi A6/S6/RS6/Allroad C5 (from model year 2001)

Installation

  1. Turn off the ignition and pull the key out.
  2. Remove the cluster instrument.
  3. Plug the included cable set between the cluster and the original cable harness.
  4. Plug the connectors of the cable set into the FIS-Control.
  5. Please note: The 2-pin plug with yellow shrinking hose of the blue cable is not used and should not be plugged in.
  6. Insert cluster and place the FIS-Control box at a suitable location.
  7. Optional: To also reach the control units on the L-line, a wire between the screw terminal "L-Line" and pin 15 of the OBD socket has to be installed. Additionally the user mod "L-Line A6" has to be enabled in the settings menu.

Coding of the instrument cluster

To be able to send data to the display of the instrument cluster, the FIS-Control uses the CAN bus addresses of the telematics and phone module. The instrument cluster only accepts these addresses when these both devices are enabled in the CAN bus installation list. This is done by coding the adaptation channel 62 of the instrument cluster to the values "15". More information about that in the related chapter.
Alternatively the FIS-Control also use the addresses of the navigation system and the radio. This is only possible when none of these devices is already installed. The adaptation channel 62 has to be coded to the value "5" in this case.
Please note: As long as the instrument cluster is not properly coded, the FIS-Control will not work and the normal board computer will not respond to button presses of the wiper control stalk.

Compatibility

The FIS-Control Light does not have a connector for the L line. Therefore the following control units can not be reached via OBD: auto HVAC, auxiliary heat, central locks, navigation system, interior monitor, xenon range regulation, radio, tire pressure, park assist.
If a telephone module is installed, the upper two lines of the instrument cluster display can not be used by the FIS-Control.

Audi TT 8N (from model year 2000)

Installation

  1. Turn off the ignition and pull the key out.
  2. Remove the cluster instrument.
  3. Plug the included cable set between the cluster and the original cable harness.
  4. Plug the connectors of the cable set into the FIS-Control.
  5. Please note: The 2-pin plug with yellow shrinking hose of the blue cable is not used and should not be plugged in.
    Please note: The 6-pin plug with red shrinking hose of the gray cable is not used and should not be plugged in.
  6. Insert cluster and place the FIS-Control box at a suitable location.

Coding of the instrument cluster

To be able to send data to the display of the instrument cluster, the FIS-Control uses the CAN bus addresses of the telematics and phone module. The instrument cluster only accepts these addresses when these both devices are enabled in the CAN bus installation list. This is done by coding the adaptation channel 62 of the instrument cluster to the values "15". More information about that in the related chapter.
Alternatively the FIS-Control also use the addresses of the navigation system and the radio. This is only possible when none of these devices is already installed. The adaptation channel 62 has to be coded to the value "5" in this case.
Please note: As long as the instrument cluster is not properly coded, the FIS-Control will not work and the normal board computer will not respond to button presses of the wiper control stalk.
Please note: If a radio is installed that shows the station names on the upper segment of the instrument cluster display, an alternate firmware may be installed on the FIS-Control, so that it can also show data on the upper two lines of the display.

Compatibility

In the TT the FIS-Control only works together with instrument cluster with CAN bus. That are all cluster that have "920" as part of their part number, only exception is the cluster with the part number "8N1 920 880 A".
The instrument clusters with the following part numbers don't support the telematics channel on the CAN bus: "8N1 920 880 G", "8N1 920 880 H", "8N1 920 930 Q", "8N1 920 930 T". The FIS-Control has to use the address of the navigation system instead. Is there already a navigation system installed via CAN bus, the FIS-Control will not be useable with these clusters.
With the instrument cluster with the part numbers "8N1 920 880 G" and "8N1 920 880 C"it is not possible to display pixel graphics. That means: no startlogo, no line graphs, no boost bar graph, no snake game.

Audi A4/S4 B6
Audi A4/S4/RS4 B7
Seat Exeo 3R

Installation

  1. Turn off the ignition and pull the key out.
  2. Remove the cluster instrument.
  3. Plug the included cable set between the cluster and the original cable harness.
  4. Plug the connectors of the cable set into the FIS-Control.
  5. Insert cluster and place the FIS-Control box at a suitable location.
  6. Optional: To also reach the control units on the L-line, a wire between the screw terminal "L-Line" and pin 15 of the OBD socket has to be installed. Additionally the user mod "L-Line A4" has to be enabled in the settings menu.

Coding of the instrument cluster

To be able to send data to the display of the instrument cluster, the FIS-Control uses the CAN bus addresses of the telematics and phone module. The instrument cluster only accepts these addresses when these both devices are enabled in the CAN bus installation list. This is done by coding the adaptation channel 62 of the instrument cluster to the values "15". More information about that in the related chapter.
Alternatively the FIS-Control also use the addresses of the navigation system and the radio. This is only possible when none of these devices is already installed. The adaptation channel 62 has to be coded to the value "5" in this case.

Compatibility

If radio and telephone module are installed, the FIS-Control will not be able to use the two lines of the instrument cluster display.
With the cluster with the part number "8E0 920 932" display errors may occur when showing the startlogo, line graphs, the big speed view or the snake game.
For the Seat Exeo there might be control units that only support the UDS diagnostics protocol. They can't be reached with the FIS-Control.
The FIS-Control Light does not have a connector for the L line. Therefore the following control units can not be reached via OBD: navigation system, xenon range regulation, radio, TV tuner, tire pressure, trailer, park assist.
On clusters with the red monochrome screen, it might happen that the FIS-Control hangs when drawing pixel graphics. To solve this, enable SETTINGS -> USER MODS -> B6 CLUSTER.

VW Golf Mk4 (up to model year 2001)
VW Passat 3B (up to model year 2000)
VW Bus T4
Skoda Octavia 1U (up to model year 1999)

Installation

  1. Turn off the ignition and pull the key out.
  2. Remove the cluster instrument.
  3. Plug the included cable set between the cluster and the original cable harness.
  4. Plug the connectors of the cable set into the FIS-Control.
  5. Insert cluster and place the FIS-Control box at a suitable location.

Coding of the instrument cluster

To be able to send data to the display of the instrument cluster, the FIS-Control uses the 3-wire-bus. The 3-wire-bus has to enabled in the instrument cluster if necessary. If the current coding value is less than "16000", then "16000" has to be added. More information about that in the related chapter.
Please note: As long as the instrument cluster is not properly coded, the FIS-Control will not work and the normal board computer will not respond to button presses of the wiper control stalk.

Compatibility

Unlike the FIS-Control, the FIS-Control Light does not support the 3-wire-bus and is not compatible.
If a radio is installed, that normally displays the station name in the cluster display, this will be dropped as soon as the FIS-Control is installed. The output from navigation systems (guiding directions and station names) will still be shown.
For the T4 there is a restriction regarding the wiper control stalk. The FIS-Control is meant to be controlled with three buttons (up, down, set). The MFA button of the wiper control stalk only has one button and a slide switch. It is possible to control the FIS-Control with the slide switch, but the MFA1 level of the board computer will not be usable.
To emulate the functions of the normal wiper stalk with the one of the T4, apply the following assignment:

VW Golf Mk4 (from model year 2002)
VW Passat 3BG (from model year 2001)
VW Sharan I / Ford Galaxy WGR / Seat Alhambra I
Skoda Superb 3U
Skoda Octavia 1U (from model year 2000)

Installation

  1. Turn off the ignition and pull the key out.
  2. Remove the cluster instrument.
  3. Plug the included cable set between the cluster and the original cable harness.
  4. Plug the connectors of the cable set into the FIS-Control.
  5. Insert cluster and place the FIS-Control box at a suitable location.

Coding of the instrument cluster / CAN gateway

To be able to send data to the display of the instrument cluster, the FIS-Control uses the 3-wire-bus. The 3-wire-bus has to enabled in the instrument cluster if necessary. If the current coding value is less than "16000", then "16000" has to be added. More information about that in the related chapter.
If necessary the installation list of the CAN gateway has to be updated as well.
Please note: As long as the instrument cluster is not properly coded, the FIS-Control will not work and the normal board computer will not respond to button presses of the wiper control stalk.

Compatibility

Unlike the FIS-Control, the FIS-Control Light does not support the 3-wire-bus and is not compatible.
If a radio is installed, that normally displays the station name in the cluster display, this will be dropped as soon as the FIS-Control is installed. The output from navigation systems (guiding directions and station names) will still be shown.
For the Passat 3BG (model year 2005) with an instrument cluster with the part number "3B0 920 849" and Skoda Octavia it might be necessary to unplug the TMC box and the telephone module from the CAN bus in order to use the FIS-Control.
For the Golf Mk4 there must not be a navigation system installed that communicates via CAN bus with the instrument cluster (that is the MFD version G).

Audi A3/S3/RS3 8P
Audi TT/TTS/TTRS 8J
Audi R8 42

Installation

With the included cable set, the FIS-Control is plugged into the CAN gateway. The CAN gateway is located behind the footwell trim, above the brake pedal on the panel to the center console.
  1. Turn off the ignition and pull the key out.
  2. Remove the footwell trim
  3. Plug the included cable set between the CAN gateway and the original cable harness.
  4. Plug the connectors of the cable set into the FIS-Control.
  5. Place the FIS-Control box at a suitable location.

Coding of the instrument cluster / CAN gateway

Normally no coding has to be changed in the car.

Compatibility

To be able to send data to the display of the instrument cluster, the FIS-Control uses the CAN bus addresses of the telematics module, or alternatively of the navigation module.
As long as there is no navigation system installed that displays guiding directions on the instrument cluster display, that channel is free and can be used by the FIS-Control.
If a navigation system is installed, it has to be checked that the telematics channel can be used. Normally there is no telematics module installed, but not all clusters do support this channel.
Here is a list of the instrument clusters tested so far: If the navigation channel is occupied and the telematics channel is not supported by the cluster, the FIS-Control may work in a "parallel" mode with some restrictions (startlogo feature does not work, automatic start at engine start does not work, display errors of the FIS-Control occur if guidance of the satnav is active). For the RNS-E navigation system there is also a custom firmware available that allows to use the FIS-Control without these restrictions: https://rnse.pcbbc.co.uk. This firmware was created by Stuart from pcbbc and it offers a new "FIS-Control" option in the Engineering menu of the RNS-E. Once this option is activated, the FIS-Control can be coded to use the navigation channel. By default you will now see the output of the FIS-Control on the cluster screen, instead of the guidance from the RNS-E. But if you want the guidance back, you can disable the startlogo and autostart feature of the FIS-Control and enable the mod "CAN BRIDGE". If you now press and hold the up button of the wiper control stalk while turning on the ignition, the FIS-Control will stay disabled this time and the output of the RNS-E will be shown again on the cluster.
There are a few 8P/8J that have an engine control unit that speaks UDS instead of KWP2000 (e.g. the 2.0 TDI of 2010). They are not supported by the FIS-Control.

Golf Mk5 platform

Installation

With the included cable set, the FIS-Control is plugged into the CAN gateway. The CAN gateway is located behind the footwell trim, above the brake pedal on the panel to the center console.
  1. Turn off the ignition and pull the key out.
  2. Remove the footwell trim
  3. Plug the included cable set between the CAN gateway and the original cable harness.
  4. Plug the connectors of the cable set into the FIS-Control.
  5. Place the FIS-Control box at a suitable location.

Coding of the FIS-Control

The FIS-Control has to be configured to use the "DDP" channel to communicate with the instrument cluster. As the FIS-Control supports three communication channels to the cluster, a virgin FIS-Control tries one after the other, each time the ignition is started. So you may have to try up to three times to restart the ignition and call the FIS-Control. When the FIS-Control menu gets visible in the cluster, select SETTINGS -> SAVE SETTINGS so that the FIS-Control remembers the working communication channel. Another way to set the communication channel is with the FIS-Control Android app.

Coding of the CAN gateway

Sometimes it is needed to enable the item "75 - telematics" in the installation list of the CAN gateway.

Compatibility

The FIS-Control works in those cars that are equipped with the full multifunctional display (MFA+). These cars have a red screen in the instrument cluster (or a white screen in the case of the Octavia II) that can be controlled either by the buttons of the wiper control stalk or with the buttons of the multifunction steering wheel.

FIS-Control

The FIS-Control allows to access a wide range of measurement values and status information of vehicles of the VAG brands (Audi, Volkswagen, Seat, Skoda). The data is shown in real-time on the display of the instrument cluster. The system is controlled by the buttons of the wiper stalk. This way the FIS-Control integrates seamlessly into the car and can be installed perfectly invisible.
The focus of development was the fast and accurate monitoring of relevant data, especially of tuned cars: e.g. boost, oil temperature, air-fuel-ratio, exhaust gas temperature.
Many measurement values are already acquired by the stock control units and can be read out by the FIS-Control. Furthermore the FIS-Control has inputs for directly connecting additional sensors.

Supported cars

An instrument cluster with FIS / highline MFA is required.

The steps of evolution

To extend the feature set and to widen the number of supported cars, there is continuous process of development of the hardware and software of the FIS-Control 2.x.
Firmware updates are available for free download on my website www.fis-control.de. The firmware is compatible to all versions of the FIS-Control 2.x. The FIS-Control 1.0 is no longer supported.

FIS-Control 2.0

The FIS-Control 2.0 has the following features:

FIS-Control 2.1

In comparison to the previous version there are the following changes:

FIS-Control 2.2

In comparison to the previous version there are the following changes:

FIS-Control light

The FIS-Control light is the little brother of the normal FIS-Control. The hardware was reduced to only provide the essential features, namely the reading of OBD measurement values and showing them on the cluster screen. The FIS-Control light shares the same code base as the FIS-Control, but of course only the features that are possible with the downgraded hardware can be used.
In detail there are the following limitations:
FIS-Control 1.0 FIS-Control 2.0 FIS-Control 2.1 FIS-Control 2.2 FIS-Control Light
Display interface 3 wire bus 3 wire bus, CAN 3 wire bus, CAN 3 wire bus, CAN CAN
OBD interface K-Line K-Line, CAN K-Line, CAN K/L-Line, CAN K-Line, CAN
Diagnosis protocol KWP1281 KWP1281, KWP2000 KWP1281, KWP2000 KWP1281, KWP2000 KWP1281, KWP2000
Bluetooth no yes yes yes yes
0-5V sensor inputs 0 7 3 3 0
resistance inputs 0 0 4 4 0
EGT sensor inputs 0 2 2 2 0
relay drivers 0 4 4 4 0
ambient pressure sensor no yes yes yes no
data logging no yes yes yes no
CAN bridge no no no no yes

Connectors of the FIS-Control


Installation (for example in the Audi A4 B7)

  1. Turn off the ignition and remove the keys.
    Important: To avoid problems with the immobilizer, don't turn on the ignition while the instrument cluster is disconnected.
  2. Pull the steering wheel to you and push it down as far as possible. So you have more space to remove the cluster. Please put some cloth or towel on the steering column, to avoid scratches on the plastic when removing the cluster.
  3. Remove the cover at the bottom of the cluster. This can be done without tools. Just pull it towards you.
  4. Remove the two Torx screws.
  5. Remove the side cover of the instrument panel.
  6. Now you can reach behind the cluster and push it out to the front.
  7. At the backside of the cluster you will see two 32-pin connectors. To unplug them you can push down the snap-in nose with a screw driver. Now you have to disengage the lever. There might be an additional 4-pin connector. Also unplug it.
  8. Plug the included cable sets between the cluster and the cluster harness.
  9. Find a place to install the FIS-Control main unit. There might be enough space for it behind the cluster or near the fuse panel.
  10. When installing the main unit under the fuse panel, you have to remove the cover of the driver footwell.
  11. Depending on the car, the cable set of the FIS-Control consist of either two or three pieces. The connectors that have to be plugged into the FIS-Control main unit are marked with shrinking hose in different colors. The connectors at the FIS-Control box are labeled A to F. The assignment is shown in the following table. The columns represent the color of the connectors at the backside of the cluster and the colors of the shrinking hose of the cable set.
    Hint: The blue cable has a yellow marked connector. This connector is not used in all cars. In this case, don't plug it into the FIS-Control. Warning: Don't confuse it with the yellow marked connector of the green cable.

CAN bus or 3-wire-bus?

For VW (except Golf Mk5) and Skoda cars, the FIS-Control only supports the 3-wire-bus to send data to the cluster screen. For some Audis it is possible to use the CAN bus instead. There are a few Audis (A2, some A3 8L, A4 B6, A4 B7, some A6 C5) and the Seat Exeo that don't offer the 3-wire-bus anymore. Only the CAN bus can be used there.
On the 3-wire-bus, the FIS-Control behaves like a navigation system. Because it is occupying the bus only as long as it wants to show data on the screen, an installed satnav (with 3-wire-bus) is still able to access the cluster screen and therefore can be used without restrictions.
On the CAN bus, the FIS-Controls sends data like a telematics module would do.
Info: For the VW Golf Mk4/Bora it is not possible to use the FIS-Control if a navigation system or radio is installed that sends data to the cluster screen via CAN bus. 3-wire-bus works fine.
Info: For the Audi A4 (B6/B7) it is not possible to use the FIS-Control when a telematics module is installed. If a telephone module is installed, the FIS-Control can not access the upper two lines of the cluster screen, but the lower part of the screen is usable.
Info: Some older radios that are showing the current radio station via 3-wire-bus on the cluster screen are not compatible to the FIS-Control. As soon as the FIS-Control is installed, they will not be able to show data on the cluster.
If the FIS-Control should be used in 3-wire-bus mode or in CAN bus mode depends on the car and the installed devices. For example, if a satnav is installed that uses the CAN bus to send data to the cluster screen, the FIS-Control should work in CAN bus mode as well.
The FIS-Control automatically detects which bus to use, when the cluster is properly coded.

Coding of the instrument cluster

3-wire-bus mode

To tell the cluster, that the FIS-Control will send data via 3-wire-bus, the so called softcoding of the cluster has to be changed accordingly. The coding has to be set to a value larger than "16000". If the current value is lower, you have to add "16000" to it.
For Audi cars it might be necessary to also change the adaptation channel 62 of the cluster. This channel is the installation list of the devices that are connected to the infotainment CAN of the car. Because no devices shall write data to the cluster via CAN, change the value to "0". For VW cars the installation list often gets updated automatically when the CAN gateway (control unit 19) is recoded with its current value.
Info: If a radio or telephone module is installed, that uses the CAN bus to write to the upper two lines of the cluster screen, you can still keep these devices in the installation list. In this case the devices are still able to show data on the upper part of the screen. The FIS-Control will only use the lower part of the screen.
The coding value for radio is "1", for telephone "2". If both devices are installed, the sum ("3") has to be coded.

CAN bus mode

The FIS-Control identifies itself as a telematics module on the CAN bus. Therefore a telematics module has to be added to installation list of the infotainment CAN. If there is not already a telephone module installed, the FIS-Control can also access the upper two lines of the cluster screen. In this case a telephone module has also to be added to the installation list.
The configuration of the installation list is done in the adaptation channel 62 of the instrument cluster.
The coding value is the sum of the device identification numbers:
If there is already a radio and navigation system installed, the coding value sums up to "15" when you install the FIS-Control. If you are not sure, what value to set, "15" should always work, no matter what devices are installed. If no radio of navigation system is installed, the cluster will add some error entries to the diagnostic trouble codes that will tell that the communication to the satnav and radio has failed.

How to change the coding of the cluster?

The coding of the cluster can be done by a VAG workshop. Or you can do the coding yourself. All you need is a laptop, an OBD-dongle and an OBD software.
The FIS-Control can be used as OBD-dongle via its RS-232 interface or via Bluetooth (but only for the K line, not for the diagnosis CAN bus).
With RS-232 it is compatible to VAG-COM (up to version 409.1), VCDS-lite, CarPort and WBH-Diag (up to version 0.89).
With Bluetooth it is compatible to WBH-Diag (above version 1.0) and the Android app Torque Pro (not Torque Lite). Torque only shows the measurement values, but has no option to change the coding of the cluster.
To start the FIS-Control in "OBD-dongle"-mode, press and hold the Up key (for connection via RS-232) or the Down key (for Bluetooth) while turning on the ignition.
The FIS-Control will identify itself as "FIS-CONTROL" when you search for Bluetooth devices. The PIN for bluetooth pairing is "1234".
Info: The Bluetooth module of the FIS-Control is disabled during normal operation. It can only be discovered when it is set to the corresponding mode, like the "OBD-dongle"-mode.

Coding with WBH-Diag

WBH-Diag is available for free from the developer Florian Schaeffer. His website is: https://www.blafusel.de/obd/obd2_wbhdiag.html
The software is available in two versions. The older version 0.89 is meant for wired OBD with a serial cable. Therefore you will have to connect the FIS-Control to the RS-232 port of your laptop with a straight serial cable.
The newer versions, WBH-Diag 1.41 and 2.x are working over Bluetooth.
The user interface of both versions is almost identical.
Info: Please use a battery powered laptop in your car.
For wired connection it works best to connect the FIS-Control to a "real" serial port of the laptop. If the laptop does not have a native RS-232 interface, USB-to-serial adapters can also be used. With some of them the connection to the car can be unstable. I had some good experience with cables with FTDI-chipset.
Info: In the program folder of WBH-Diag, there is a configuration file called "wbh-diag.ini". There you can set the language of the tool: "Sprache=de" or "Sprache=en". And you can preconfigure the correct COM-port to use. The splash screen that is shown when the tool is started can be disabled here: "Splash=nein".
After starting the tool, select the Control Unit "023 (17) - Instruments" and choose the correct COM-port.
Now press "Connect".

The softcoding of the cluster can be changed in the tab "Software Config". The adaptation channels can be accessed in the tab "Channel Adaption".

When changing the value of the adaptation channel, there can be an error message, that the value could not be set. Often this is a wrong error. Most of the time the value is set correctly. Just check if the "Actual values" is the value you want to have.

Coding with VCDS

To check or change the coding of the instrument cluster, press the button "Select" in the main menu of VCDS and choose "17-Instruments" in the list of control units.

The current coding of the cluster is shown in the field "Soft. Coding".

To change the coding, select "Recode - 07".

Info: With the free version of VCDS-lite it is not possible to access the adaptation channel 62. In this case you can use WBH-Diag instead.

Coding of the FIS-Control

The FIS-Control supports multiple data protocols for communicating with the screens of the instrument clusters.
Directly after installation, there is no protocol defined. Every time the ignition is turned on, the FIS-Control will try to use the next protocol. If you can launch the FIS-Control main menu by doing a long press (about 2 seconds) to the Up key, a working protocol has been found. If you now select "SAVE SETTINGS" in the settings menu of the FIS-Control, the FIS-Control will remember the current protocol and no longer probe the other ones.
A second way to select the display protocol is to use the FIS-Control Android app. Therefore the FIS-Control has to be set into configuration mode. This mode is activated automatically when the FIS-Control can't communicate with the instrument cluster, or by holding the Down key on the side of the wiper control stalk while turning on the ignition.
In this mode, the FIS-Control can be paired with the Android device via bluetooth. The PIN code is '1234'. In the app you can now select the FIS-Control unit. With the item "Firmware version" in the selection list of the app and SEND you can test that the FIS-Control is connected successfully. If this is the case, you can choose the display protocol for the FIS-Control in the selection list and click SEND to save this settings in the FIS-Control.
For cars where the cluster can be coded via K line, this can also be done here by choosing the appropriate item in the selection list. So you don't need VCDS or WBH-Diag for this.


Configuration of the FIS-Control

The easiest way is to configure all the options of the FIS-Control is with the FIS-Control online configurator.
This also allows to label the measurement values and the presets.

Using the FIS-Control

The main menu

After turning on the ignition, the FIS-Control is in inactive mode by default. This means that you will see the normal board computer in the cluster display. To activate the FIS-Control, do a longpress (about 2 seconds) to the Up key at the side of the wiper control stalk. This will bring up the main menu. You can navigate in the menu with the direction keys (Up key and Down key). To choose an item, press the Select key (that is the Reset key on the bottom of the wiper stalk).
When you leave the main menu, the normal board computer will be shown again.
Info: For the Audi A3 8P and Audi A4 B6/B7, the Reset key can not be used by the FIS-Control. Selection of menu items is done by doing a long press on either the Up or Down key.

Presets

The preset function is the main function of the FIS-Control. It allows a quick access to the desired measurement values. Every preset is actually one page on the screen that can be configured to show one or more measurement values in a defined view. With the direction keys you can browse through the presets, just like you can do with the values of the standard board computer.
The configuration of the preset page is done at "SETTINGS"" -> "PRESETS" (see corresponding chapter).

Measurement

With the "MEASUREMENT", any measurement values can be displayed. The values are either read out from a control unit or are measured from sensors that are directly connected to the FIS-Control. A measurement group consists of up to four individual readings. In the first line on the screen, the FIS-Control shows with which control unit it is connected. For example "E: 01" for the ECU 1 (that is the engine control unit). The FIS-Control will read the values from the control unit that is selected at "SETTINGS" -> "CONTROL UNIT", or the control unit that was last used by a preset.
Besides the ECU number, the first line also indicates the number of the current measurement group. For example "G: 115" for the measurement group 115. You can browse through the groups with the direction keys.
To display the data from the sensors that are directly connected to the FIS-Control, select the control unit "EXT. SENSORS". The readings from the sensor inputs 1 to 4 are shown in measurement group 1. Inputs 5, 6, 7 and the reading of the ambient pressure sensor that is integrated into the FIS-Control are in group 2. The 3rd group has the values of the two exhaust gas temperature inputs and, if a GPS receiver is connected, the speed and time. The 4th group has some more GPS data: Position (longitude and latitude), altitude and direction.
Info: On some clusters there is a moving dot below the first line of the screen. Each time the FIS-Control updates its data from the control units or the external sensors, the dot will move one step. So the moving dot indicates the refresh rate of the measurement values.

To stop the current measurement, press the Set button. From here you have three options:
  1. With "BACK" you can go back to the main menu again.
  2. Pressing the Up key will bring you to a screen which shows the current refresh rate of the readings. 10 FPS for example means, that the FIS-Control gets updated data 10 times per second from the current control unit.
    If data logging is enabled, you have to possibility to set a marker here. This allows to identify specific events when analyzing the logs on a PC. Each marker gets a unique number. The number of the latest marker is shown.
    Pressing the Down key will bring you back to the measurement screen.
  3. With the directions keys you can select one single value of the current measurement group. This will bring you to three sub-pages that can be browsed with the Down key. To get back to the measurement screen, press the Set key while in the line graph view.

Line graph

"SCALE" (see corresponding chapter in this manual). With the Up key you can change to any of the four configurable scales.

Maximum/minimum view / Stopwatch timer

In the maximum/minimum view you will see four lines. The upper and lower line are indicating the currently selected scale settings for the line graph. The two lines in the middle are showing the highest and lowest value that was observed while monitoring the current measurement value. With the Set key, you can reset this view.
Like in the line graph view, you can go through the four predefined scales. The corresponding scale values are shown in the up-most and bottom line.
Pressing the Set key also activates the stopwatch timer. The timer is set to "0.00". In this mode, the upper and lower line not longer show the limits of the scale, but the positions of the orientation lines of the line graph that are also the start and stop trigger for the stopwatch timer.
The timer starts running as soon as the current reading crosses the lower orientation line and is stopped as soon as the value reaches the upper orientation line. Therefore the configuration of the timer is actually done by setting the orientation lines of the graph view at "SETTINGS" -> "SCALE".
Tip: Even when the stopwatch timer is activated in the max/min view, it still stays active in the other views. So you can browse to the line graph view and watch the current value.

Board computer view

The board computer view shows the currently selected measurement value in the upper segment of the cluster screen, while the middle segment is free for the normal board computer. With the Up and Set key the board computer can be operated as usual, while the Down button will bring you back to the line graph view.

Read DTC

Here you can read out the diagnostic trouble codes (DTC) of the currently selected control unit. Up to four errors are shown on each page. With the direction keys you can browse the pages.
Every error code consists of two numbers. The first one is the identifier for the error itself. The second gives additional information. An asterisk behind the code tells, that this is not a permanent but a sporadic error.
To leave the DTC list, press the Set key. Now you can either select "BACK" to go back to the main menu, or you can select one of the error codes to get a description of the error code. Pressing the Up key instead will bring you to a menu where you can clear the error codes of the current control unit.

If the descriptions of the error codes are not yet available on the FIS-Control (for example after a factory reset) this can be done by loading the description file from my website. To transfer the file to the FIS-Control select "SETTINGS" -> "FLASH MEMORY" -> "LOAD DESCRIPTIONS". Then send the file via RS-232 or via Bluetooth the same way you would transfer a firmware update to the FIS-Control (see corresponding chapter).
Info: Some control units only show one error on each page.

Settings

Control unit

Here you can choose the ECU from which you want to read measurement values via OBD, or if you want to have the readings of the sensors that are connected directly to the FIS-Control ("EXT. SENSORS"). All control units are listed twice. If there is no asterisk behind the ECU number, then the FIS-Control will use the K-line to communicate with the ECU. If there is an asterisk, the FIS-Control will use the CAN bus instead. The most interesting readings will come from the engine control unit. This has the number "1" or "1*". Of course you can select any of the ECU numbers. Most of them, but not all, have labels.

Scale

To use the functions "line graph" and "stopwatch timer" during a measurement, a scale has to be configured first. For example if you want to line graph the boost pressure, you can set the "UPPER LIMIT" of the scale to match the highest expected pressure. The values are always in the unit in which they are displayed. If you expect a boost pressure of up to 2500 mbar, set the "UPPER LIMIT" to "+002500.000" (the point is a decimal point). If the boost pressure is shown in Bar instead, enter "+000002.500".
With the direction keys you can change the sign or digit at the cursor position of the number. The cursor is moved with the Set key.
With "UPPER LINE" and "LOWER LINE" you can add to dotted orientation lines to the line graph view.
Info: If the lower orientation line is set to the same value as the lower limit, this will give a solid line instead of a dotted one. This is helpful for displays that don't show a lower borderline by themselves.
Info: If only want one or no orientation line visible on the screen, you can place it outside of the scale, for example to the value "-999999.999".

Presets

Up to nine presets can be configured. For every preset the following settings are needed:

Save settings

All changes that are done in "SETTINGS" are only valid until you turn off the ignition. If you want to save them permanently, select "SAVE SETTINGS". Now the settings will be loaded again, when the ignition is turned on.

Sensors

The FIS-Control offers inputs for several sensors.

The connector block has the following layout:

Configuration of the sensors

Up to seven analog sensors can be connected to the FIS-Control. The FIS-Control has an 8-channel analog/digital-converter with a voltage range from 0 to 5 volts. Input 8 is internally connected to an ambient pressure sensor.
Info: For hardware version 2.0, sensors that have a changing resistance instead of a signal voltage can not be connected directly to the FIS-Control. A separate voltage divider will be needed to interface such sensors. I can give a more detailed explanation on request.
Info: Starting with hardware version 2.1, the FIS-Control has integrated voltage dividers for the first four sensor inputs. This allows to directly connect sensors that have an output resistance instead of an output voltage.
Inputs 1 and 2 have an internal voltage divider with an 1.1 kOhms resistor. Inputs 3 and 4 have a voltage divider with 220 ohms.
In the settings menu of the FIS-Control you can choose the characteristic curves of some typical sensors. Missing sensors can be added by me. Just ask.
The following sensors are already supported: This are the characteristic curves of the sensors: Info: Sensors that have 5 volts power supply, that have an output signal that is relative to the power supply (ratiometric), should be powered from the 5 volt output of the FIS-Control to achieve best measurement precision.
Info: For precise and reliable measurements, the sensor ground should be equal to the GND of the FIS-Control. Some sensor are using the chassis to connect to ground. In this case, it could be a good idea to have a separate ground wire from the FIS-Control to a GND near the sensor. Please make sure, that no high currents can go over this wire. This could happen, for example when the ground connection to the engine block fails.
Info: Don't use extension cables for the signal wires of the Type-K thermocouples to avoid measurement errors.

Displaying the sensor measurements

To select the sensors, choose "Control unit 0". Like for other measurement groups, the sensor values are packed in groups to up to four values each. Group 1 has the measurement values of the first four sensor inputs. Group 2 has the sensor 5 to 7 and the internal ambient pressure sensor. In group 3 are the two exhaust gas temperature sensors.
Features and using of the sensors is like for the OBD control units.
So it is also possible to use the "boost option" that allows to convert the boost reading from absolute to gauge boost.

Mask

In principle every control unit can have up to 255 different measurement groups. Most of them are not used, though, or have readings that are not of interest. During a running measurement, you can browse through the measurement groups with the direction keys. To not waste time browsing all measurement groups, you can hide the ones that are not of interest for you.
First select the control unit for which you want to hide groups. Now you can go to the menu item "MASK". There you can either make a group visible (checkmark set) or hide it (checkmark not set). At the end of the list, there are two options to enable or disable all measurement groups of the current control unit at once.
Hint: If you disable all groups of a control unit, the whole control unit will be invisible in many control unit lists. So if you spend the time to hide all unneeded control units and measurement groups, this will make it more comfortable to use the FIS-Control from then on.
Hint:Often it is easier to disable all control units and then only enable the ones that are installed. To do this, choose one of the control units and click three times on "DISABLE ALL" in the mask list. Now all control units are hidden. To enable a control unit again, select it and change its mask settings, for example by disabling and enabling one group of it.
Hint: To distinguish between enabled and hidden control units, the control unit number of hidden control units is set in braces.

Startlogo

The FIS-Control can show a customizable welcome screen when turning on the ignition. For clusters with the monochrome screen, you can create the startlogo yourself and copy it to the FIS-Control. For the color screens there is a collection of logos available at https://fis-control.de/startlogos/. More startlogos can be created on request.
In the settings menu you can pick one of nine monochrome logos. But first these logos have to be provided. There is a windows tool that allows to generate the collection of startlogos.
First the startlogos have to be created. You can either load some templates from the internet or draw your own, for example with Paint. The images have to have a resolution of 64x88 or 64x48 pixels and have to be stored in the TIFF format.

With the "Startlogo for FIS-Control" tool you can build the startlogo-collection that can be transferred to the FIS-Control.
First select one empty slot on the left, then choose a valid TIFF file with a startlogo. A preview of the logo will be shown. When you added your logos to the collection, you can "Save file". The filename doesn't matter. Just remember where you saved the file.

Now connect your laptop to the FIS-Control via a serial connection or bluetooth as described in the chapter "Firmware update". Instead of startling the FIS-Control in software loading mode, just go to the settings menu and select the "Flash Memory" options. Select "Load Startlogo" and choose the used connection type. Then send the startlogo file to the FIS-Control using HyperTerminal.
Info: There are a few clusters out there that will not show the startlogo right away. Often this can be solved by setting a delay time before the FIS-Control tries to display the logo. The delay time can be set in the settings menu of the FIS-Control. Select "Tweaks" and set a "Logo delay" in milliseconds.

Autostart

After turning on the ignition, the FIS-Control is inactive by default. A longpress to the Up key will bring you to the main menu of the FIS-Control and allows to start actions from there.
The autostart feature allows to directly load the "PRESET 1" instead of the main menu, if you set it to "BUTTON".
Additionally there is the option "ENGINE START". With this enabled, the FIS-Control will launch the "PRESET 1" automatically when the engine is started.
Info: Precondition for the autostart feature is a valid configuration of Preset 1. For some cars it is needed to enable the user mod "RPM CAN".
With the setting "UART<->FIS" the FIS-Control directly enters a mode where you can send data over the RS-232 of the FIS-Control to the cluster screen, e.g. with a CarPC.

Boost

The control units in VAG cars typically don't measure the actual boost pressure, but the MAP (manifold absolute pressure). To get the boost pressure like normal boost gauges are showing it, the ambient pressure (about 1 Bar) has to be subtracted from the MAP reading. The FIS-Control can do this. Therefore it has an on board ambient pressure sensor.
In the settings menu is the item "BOOST". Here you can select the control unit that provides the MAP reading (usually the engine control unit) and in which measurement group the value is found. The pressure is displayed in the unit "mbar" by default, but this can be changed here to BAR or PSI. With the scale option you can choose if the value shall be shown as absolute or relative (gauge) pressure.

Headline

The headline is the upper two text lines of the cluster display. The FIS-Control uses the headline mainly to show the title of the current menu. Therefore the headline is expendable in most cases. Instead you can have the output of your radio or the telephone (if they are sending this data via CAN bus to the cluster). The both text lines can also be used to display data from a Car-PC that is connected to the FIS-Control via RS-232. (For more info about this, please write me an email).
Additionally it is possible to use the headline as monitor for the "Valentine One" radar warner. The FIS-Control provides an RJ11 jack where you can plug the cable of the V1. The FIS-Control is also the power supply for the radar warner.
Info: In cars equipped with a telephone module, this module occupies the headline of the cluster screen permanently (even when it doesn't show actual data there). When the FIS-Control also sends data to the headline, you will see a flickering, because the display switches between the data from the telephone module and the FIS-Control quickly. The headline can not be used in this case. To stop the FIS-Control from sending data to the headline, select the item "RADIO".

Flash memory

The FIS-Control has an on board memory chip to store the user settings, the descriptions of the DTC error codes, the startlogos (only the ones for the monochrome cluster display). Also it can log all measurement values here when data logging is active.
At "SETTINGS" -> "FLASH MEMORY" it is possible to transfer data between the flash memory of the FIS-Control and a PC via RS-232 or Bluetooth.
With "SEND LOGS" you can send the logged measurements to the PC.
With "SEND SETTINGS" and "LOAD SETTINGS" the configuration of the FIS-Control can be exported to a PC via XModem protocol and imported from it. With the online configurator it is possible to edit the configuration file:
https://fis-control.de/config_en.html
Important: After uploading the settings file, don't select "SETTINGS" -> "SAVE SETTINGS". The new configuration gets active automatically next time the ignition is switched on.
With "LOAD STARTLOGO" you can bring own startlogos to the FIS-Control.
With "LOAD DESCRIPTIONS" you can load the clear text descriptions of the DTC error codes to the FIS-Control. The needed file is available on my website.
With "FACTORY RESET" you can clear the whole flash memory of the FIS-Control. This will delete all user settings, startlogos, error descriptions and logs.
The erase process will take about one minute.

Units

The control units are normally using the metric unit system for their readings.
But you can also choose imperial or US unit system. The FIS-Control will convert the readings accordingly.
So liters will be gallons, kilometers will be miles and Bar will be PSI.

Tweaks

The communication protocol in the car is time critical. The FIS-Control uses default values that should be working without problems in most cars. At "SETTINGS" -> "TWEAKS" you can adjust some timing values. This can be needed, if an OBD connection with a control unit is too slow or unstable.
At "OBD TIMING" are two values that can be set.

Interbyte Delay

This is the delay between each byte that the FIS-Control sends over die diagnosis wire. This value is only relevant for control units that are using the KWP1281 protocol. The unit is "tenth of milliseconds". The default value is "50", so there is a delay of 5 milliseconds before sending a new byte. Some control units don't need any delay at all, this can improve the communication speed, so that the FIS-Control can read new measurement data more often.

Block Delay

This is the delay in milliseconds, that the FIS-Control uses before sending a new command on the diagnostic wire. Most control units with KWP1281 don't need a delay here. For control units with KWP2000 this is different. They are telling the FIS-Control a delay time that should work. Although the FIS-Control uses the given delay time, some connections are not stable. So you can set a block delay time here, that overrides the timing. A block delay of 85 milliseconds has proved as working and should be set for all control units with KWP2000.
The block delay is also relevant for the measurement of the external sensors, that are directly connected to the FIS-Control. If you select "EXT SENORS" as control unit, you can set the delay between two measurements. If you want to read the sensors 10 times per seconds, set the delay to 100 milliseconds.

Fast Init

This option shortens the time for establishing a new connection to a control unit about one second. This helps when browsing through presets with different control units, because every time the control unit is changed, a connection has to be closed and a new has to be established.
Some control units do not support fast init. If you have problems when connecting to a control unit, disable the fast init option.

OBD delay

When browsing through presets that are reading data from different control units, the FIS-Control has to close and open an OBD connection each time. There has to be an idle time between two connections. This time can differ between control units, so you can configure it here. Short delays allow faster browsing through the presets, longer delays are more stable.
Info: The FIS-Control does more than one attempt to connect to a control unit in case the first connection fails. If the OBD delay is set too short, it is possible that the FIS-Control has to try many times before it can connect to the control unit. This may take longer as if a longer delay was set that works on first try.
The number of attempts can be seen in the main menu when selecting "ECU INFO".

Logo delay

When the startlogo feature is enabled, the FIS-Control tries to send the startlogo to the cluster as soon as the ignition is turned on. Some clusters don't accept data at this time. Often it helps to just wait a few milliseconds before sending the logo. This delay can be set here.

Alternative bar graph

The preset view "boost" shows a bar graph. The bars are filled dependent of the current boost pressure. For some cluster, this works only when the "ALT. BAR GRAPH" is selected.

Logging

During an active measurement, the FIS-Control can log all measurement values to its internal memory. The memory is designed to hold a few days, up to some weeks of data. If the memory is filled completely, the oldest data is overwritten by the new data.
Following data is logged: The data logging can be enabled or disabled in the settings menu in the sub-menu "LOGGING".
The loggings are splitted into single sessions. A new session is started automatically when the logging is enabled in the settings menu, or (when permanent logging is enabled) as soon as the ignition is switched on.
To manually start a new session, it is possible to disable and re-enable the logging in the settings menu.
The current time and date is assigned to each logging session. Therefore you have to set the clock first. This can be done in the logging menu. To keep the clock running even when the ignition is switched off, you have to insert a coin cell battery into the FIS-Control (type CR1220 3V).
During an active logging session, it is possible to set markers. This makes it easier to find events in the logfile later.
To set a marker, you have to go to the measurement group view of the current measurement. Now press the Set key to enter the page with the selection for single values. Instead of choosing a single value, press the Up key to open an additional menu page. There is the item "SET MARKER". Also there is a counter for the markers. The number of the just set marker is shown.
The logfiles can be transferred to a PC using RS-232 or bluetooth. In the settings menu there is the submenu "FLASH MEMORY" with the option "SEND LOGS". Here you can select the logging sessions you want to transfer. Now click "SEND".
On the PC side you have to start a tool that supports file transfer via XModem protocol, e.g. HyperTerminal.
Some tools allow to define the XModem protocol in more detail. For the transfer of the logfiles, the FIS-Control uses "1K-XModem with CRC".
The logfile can be saved with any name.
The tool "logfile-converter" that is provided on my website will convert the received logfile into CSV format. CSV-files can be opened with Microsoft Excel or OpenOffice Calc.

GPS Mouse

You can connect a GPS receiver to the RS-232 port if the FIS-Control. All GPS receivers with an RS-232 interface that are using the NMEA0183 protocol are compatible. Usually the baudrate for the NMEA protocol is 4800. Other baudrates can be configured in the FIS-Control.

User mods

I included some features and modifications that were requested by single users. Because those features are not relevant for most users, they are disabled by default. Please enable them only, if you know what they are doing.
To prevent accidental activation, the features will not get active immediately when they are selected. You first have to save the settings and switch the ignition off and on again.
These feature are included:

Language

Here you can set the menu language of the FIS-Control.
Available languages: English, German, Danish, Czech, Dutch, Polish, French, Spanish, Italian and Lithuanian. Other languages can be added on request.

Collections

It is possible to define four collections for the preset view "collection". A collection is a set of up to six measurement values. These readings may be taken from different measurement groups of a control unit. You can also include the measurements of external sensors to a collection.
First pick the collection you want to configure (1 to 4). Now you can setup each line (1 to 6). For every line you can select the measurement group that contains the specific value and which of the values you want.
This has to be repeated for all lines and all collections.
To select a collection go to SETTINGS -> PRESETS and choose the view COLLECTION for the preset. The FIS-Control will read the measurement group that is defined as GROUP directly after connecting to the defined control unit. So it is best to select a GROUP for the preset that is also used in the collection.
The meaning of the preset value is the number of the collection to use (1 to 4).
To include measurements from the external sensors to a collection, got to the collection configuration menu and set the GROUP to "0". The VALUE will specify, which external sensor to use. The assignment is as follows:

ECU Info

Here are three pages with informations about the current control unit.
The first page shows the part number and the name of the control unit. Often the name includes the software version. Also the soft coding is shown.
The second page shows the address of the control unit and the actual baudrate that is used on the K line, or the nominal baudrate of the CAN bus.
Additionally you can see the workshop code. That is an identifier of the last workshop that changed the coding of the control unit. In the lower two lines, there is the amount of connection attempts that were needed to establish the current OBD connection and also which communication protocol is used (KWP1281, KWP2000, KWP2000 over CAN).
The third page shows additional text, if provided by the control unit.

K-LINE<->UART

The FIS-Control can be used as OBD dongle.
Via RS-232 it is compatible to VAG-COM (up to version 409.1), VCDS-lite, CarPort and WBH-Diag (up to version 0.89).
Via bluetooth it is compatible to WBH-Diag (version 1.0 an newer) and the Torque Pro Android app (not Torque Lite).

UART<->DIS

It is possible to send data to the cluster screen via the FIS-Control using RS-232 or bluetooth. Please contact me fore more information, if you want to use this feature.

Snake

The FIS-Control offers many useful features... but there is also a useless one. Control a little snake in the cluster display using the buttons of the wiper stalk. Try to pick up as many fruits as possible without hitting the snakes tail or the walls.
Info: Snake is not running in some Audi A4 (B6/B7).

Relay drivers

The FIS-Control offers four relay outputs. This is helpful to switch lights or other stuff on and off.
Every relay output can drive up to 600 mA.
Warning: A short circuit to ground of the relay output can permanently damage the FIS-Control.

Info: Via the I2C interface of the terminal block of the FIS-Control it is possible to connect even more relays. Please contact me for more information.

About

Here you can see, which firmware version is installed on the FIS-Control. On a second page there is a unique serial number for every FIS-Control.

Firmware updates

The FIS-Control can be updated to newer firmware that offers new features or has improvements and bugfixes.
You may either use the RS-232 port or a wireless bluetooth connection to transfer the firmware file to the FIS-Control.
Info: The latest software is available on my website for free downloading.
The file always includes a complete firmware. There is no need to install prior updates. Just load the latest file to the unit.
Warning: Only use a battery powered laptop in the car.

The easiest way is to update the FIS-Control with the Android app.

  1. Turn off the ignition of your car
  2. Press and hold the Reset button on the bottom side of the wiper control stalk
  3. Turn on the ignition
  4. Wait about 5 seconds then release the button
  5. Repeat steps 1 to 4 again one time
Now the bluetooth module of the FIS-Control is activated. Pair your Android device with the FIS-Control. The PIN code is '1234'. Now start the app. The FIS-Control will be shown in the selection list. Select it there. On the next screen press the Update button that matches your FIS-Control device. The update will take about 3 minutes.

If the firmware shall be loaded via the serial port, you'll need a laptop with an RS232 interface or an USB-serial-adaptor.
Use a 9-pin straight cable. The so called null-modem cables don't work here,

  1. To update the firmware, the FIS-Control has to be started in software loading mode. This is done by press and holding the the Set button (not the Up or Down button) of the wiper stalk while the ignition is switched on.
    Info: For the Audi A4 (B6/B7) wait about five seconds after turning on the ignition. Than switch off and on the ignition again without pressing any buttons of the wiper stalk.
  2. (only needed for bluetooth)
    Let the laptop search for bluetooth devices in range. The device "FIS-CONTROL" should be found. Pair the FIS-Control with the laptop. The PIN number is "1234".
    The operating system should assign a COM-port to the new connection.
  3. Start HyperTerminal (this tool comes with Windows XP: Start -> Programs -> Accessories -> Communications) or an other terminal tool, like TeraTerm or ZOC.
    Choose the correct COM-port. If you are using the RS-232 port, use the following settings:
    • Bits per second: 115200
    • Data bits: 8
    • Parity: None
    • Stop bits: 1
    • Flow control: None
    If the connection is established successfully, you should see the character "C" printed in the terminal window about every second.
  4. Now the firmware can be transferred to the FIS-Control. Select "Transfer" -> "Send File" in the menu bar of HyperTerminal.
    Now choose the firmware file and set the transfer protocol to "XModem". Now "Send".
    The transfer should not take longer than 5 minutes.
  5. Switch the ignition off and on again. In the "ABOUT" menu of the FIS-Control you can see the date of the currently loaded firmware version. This should match to the software you just loaded.

Troubleshooting

The FIS-Control does not start

If the FIS-Control does not appear after a long press to the Up key (at the side of the wiper stalk), this can have several reasons. If the FIS-Control has not worked before in the car, you should first check the cable connections.
Next you can check if the FIS-Control is visible via Bluetooth after the ignition is turned on. You can use a laptop or an Android phone. An iPhone doesn't help.
If the FIS-Control is visible via Bluetooth, the good news is, that it is alive. The bad news is, that it has not entered its normal operating mode. In the normal operating mode, the Bluetooth module of the FIS-Control is disabled. An enabled Bluetooth module means, that the FIS-Control is either in software loading mode or in configuration mode.
If the FIS-Control could not establish a connection to the instrument cluster, it starts in configuration mode. Normally that means, that the FIS-Control or the instrument cluster are not properly coded. Both codings can easily be done with the FIS-Control Android app (download at www.fis-control.de).
Coding of the FIS-Control is explained here in the user manual: Coding of the FIS-Control
For most cars the setting "FIS-Control: Telematics/3LB" is correct. If the instrument cluster does not support the telematics channel (e.g. some Audi TT 8N and newer Audi A3 8P and TT 8J), you can use the setting "FIS-Control: Navigation" instead. This only works as long as there is no navigation system installed that already occupies that communication channel. If the FIS-Control shall share the navigation channel with the navigation system, you could set the mode "FIS-Control: Parallel". There are some restrictions in useability in this mode, though.
For cars of the Golf Mk5 platform, the mode "FIS-Control: DDP" is correct.
With the Android app, you can read the current coding with "firmware version".
Even without a phone or laptop, it is at least possible to switch between the two channels "Telematics/3LB" and "Navigation". Therefore you have to hold the Down button (at the side of the wiper stalk) and turn on the ignition. Now press the Up key one time and then restart the ignition.

The FIS-Control can't connect to a control unit

In most cases, this is because the FIS-Control tries to use the wrong interface to establish the connection. Depending on the car, the diagnosis is done either over the so called K line or via CAN bus. Therefore the FIS-Control lists every control unit twice in its selection lists. One time with an asterisk behind the control unit number and one time without. For example "01* Engine" and "01 Engine". For the entry with the asterisk, the connection is established over CAN bus, without the asterisk it is done over K line. To check if the communication with the selected control unit works, you should select ECU INFO in the main menu of the FIS-Control. There you can also see which diagnosis protocol is used. If it says "KWP1281", there is nothing more to do. If it is "KWP2000" or "KWP OVER CAN" you should go to SETTINGS -> TWEAKS -> OBD TIMING and set a BLOCK DELAY of "085" for that control unit. The will make the communication to the control unit more stable.