Connecting and setting up BiMatrix Mini

1. BiMatrix Mini inputs and outputs #

An input receives a signal. An output controls a device. Each CAN port supports both directions: data is received and transmitted over the same wire pair.

Wiring diagrams:

The circuit diagrams show the wire path; pin placement is schematic. Connector shape and viewing side are shown separately in the pinout. Pin numbers refer to BiMatrix Mini. Line colors help you read the diagram; actual wire colors depend on the harness. A dot where lines cross means a connection; a crossing without a dot means separate wires. Wide diagrams scroll horizontally on narrow screens.

In all language versions of the manual, screenshots show the app interface in English. The explanations accompanying the images are translated; the names of buttons, fields and modules within the screenshots remain in English.

Interface screenshots. The described modules include an overview and small detail images alongside the settings. Click any screenshot to enlarge it. The “100%” button displays the original size: you can scroll the image, including on a phone. Close the window with the “Close” button, the Escape key or by clicking the darkened area. The app 4.4.3 interface is shown with demonstration data and no device connection. DISCONNECTED status is expected; in some screenshots, CONNECTED is simulated to show the settings without a device. User-defined signal names may differ in your configuration.

1.1. Input and output functions #

The +12 V supply, GND ground and +5 V sensor supply output have separate purposes. Their wiring is described in section 1.6. For each circuit, check the pin number on the plug against the BiMatrix Mini schematic.

BiMatrix Mini: unit, connector and pin numbers #

Shown below is the unit connector viewed from the mating-plug side. The latch is at the top. For the mating plug, always account for the viewing side: pin side or wire side. Before connecting, check the number against the marking on the connector itself.

Analog triangles and AUX/PWM squares identify pin functions here. They do not represent the shape of the metal contacts or universal IEC/ANSI symbols for these inputs and outputs. The pin number and name remain the primary identifiers.

About standard symbols: IEC — graphical symbols and standards. CAN-H/CAN-L and GND are explicitly labeled.

How to read the table. The first column gives the connector pin number and the second its function. Pin numbers and channel numbers are different: for example, analog input 1 connects to pin 3.

All BiMatrix Mini devices use the same pinout, shown in this table.

1.2. CAN1 and CAN2: basic connection principles #

CAN is a message communication line between electronic control units. Two wires carry the signal: CAN-H and CAN-L. They are routed together as a twisted pair. BiMatrix Mini CAN-H connects to CAN-H of the chosen bus, and CAN-L to CAN-L of that same bus.

Devices connect in parallel to a shared line using short branches. Long separate branches from one point degrade the signal waveform. CAN-H and CAN-L are not used to supply power: each unit has separate power and ground circuits.

Physical connection: Texas Instruments — CAN Physical Layer Requirements.

CAN1 and CAN2 are separate ports. The gearbox, selector and other devices are connected according to the selected diagram and settings. CAN1 and CAN2 wires are not joined together to transfer data between ports; communication is configured in BiMatrix Mini.

Fixed CAN bit rate #

Before connecting, check that the selected vehicle CAN bus and the devices being connected operate at 500 kbit/s. Configuring BiMatrix Mini for a different bit rate is not possible in the current version.

The message format must also match for parameters to be exchanged. For supported 8HP versions, this format is already implemented in the built-in module. Bus selection, gearbox version and signal sources are covered in section 3.

Built-in 8HP module and additional CAN functions #

8HP module: settings overview ↗

The 8HP module is intended for supported versions of transmissions from BMW. A transmission from another brand having the same 8HP designation does not imply compatibility.

The 8HP module already includes a message generator for supported gearbox versions. In the interface, a value source is assigned to each required parameter. For example, engine speed may use a signal received from the ECU over CAN or calculated from the frequency on DIG2; torque may use a received value or the result of a configured map.

Gearbox version and CAN lines ↗

Signal sources for 8HP ↗

Processing sequence: data source → 8HP module input parameter → automatically generated CAN messages → gearbox.

Configurable CAN inputs and CAN outputs provide additional communication with other devices. These interface functions use the physical CAN1 and CAN2 ports:

• A CAN input extracts a parameter from another module's message. Examples include engine speed from an ECU or button state from a button module. The resulting value can be used in BiMatrix Mini logic, in a map, or as a signal source for the 8HP module.
• A CAN output creates an additional message for another module. An example is sending a selected value to a compatible instrument cluster. The format is specified by the receiving device's protocol.

Additional receive configuration is described in section 4, and additional transmission in section 5.

What the 120 Ω resistors are for #

A termination resistor is installed at each of the two physical ends of a high-speed CAN line: 120 Ω between CAN-H and CAN-L. It reduces signal reflections from the cable end that can cause communication errors.

• One line uses two 120 Ω termination resistors. A resistor is not required at every connected unit.
• A resistor may already be installed inside an end device or the harness. Existing termination must be taken into account before adding one.
• If BiMatrix Mini connects in the middle of an already terminated vehicle bus, do not add a third resistor.
• If CAN1 and CAN2 connect to different lines, check the termination of each line separately.

Line-end termination: Texas Instruments — CAN With Selectable Termination.

Measurement on an unpowered line: Kvaser — How to test your CAN termination.

CAN Monitor: checking buses and analyzing CAN messages #

CAN Monitor: overview ↗

CAN Monitor is recommended when connecting CAN buses and diagnosing faults. It displays CAN1 and CAN2 messages: their ID and data bytes. Byte values update as messages arrive, allowing you to see which data changes while the vehicle operates or a button is pressed.

ID is the message identifier. A set of bytes is transmitted under one ID and may contain several different parameters. To read one parameter, select the appropriate part of this data.

1. In CAN Monitor, select the physically connected bus — CAN 1 or CAN 2 — or All Interfaces to view both. For the recommended vehicle CAN connection, select CAN 2. Check whether messages are arriving on this bus.

   Selecting the CAN interface ↗

2. Observe byte changes while changing one known signal — for example, pressing and releasing a button.
3. Click the ID of the message of interest to open its analysis window. Here you can try the starting bit position (Position), value length and type (Data type), and byte order (Endianness). The decoded result of the selected value updates in real time.

   Analyzing the selected ID ↗

4. Compare the decoded value with the actual signal state. Repeat the check over several state or value changes.

Example: finding a button state. Pressing the button changes data in one of the messages. Select that message by ID, then use the analysis window to find the data area whose value corresponds to pressing and releasing the button. Verify the match with repeated presses.

Use the identified ID, format and scale when configuring a CAN input. For individual bits, account for the different Position numbering in CAN Monitor and CAN Inputs; verify the result in Live. The resulting value can be used in BiMatrix Mini logic or assigned as a signal source for the 8HP module. Messages for the gearbox are generated by the built-in 8HP module.

Messages in CAN Monitor confirm that data is being received from the bus. A specific signal's meaning is established using the module documentation and by comparing values; a changing byte alone does not identify the parameter it carries. Actual transmission of custom CAN Outputs messages is checked using an external CAN adapter and the receiving device.

1.3. Digital inputs #

Digital InputsClick to enlarge

DIG1 / Ignition IN, pin 16, is the ignition input, accepting a 5–12 V signal. Its state indicates ignition on and off. This input is involved in powering up and waking BiMatrix Mini, so its purpose is considered separately from the DIG2 measurement input.

DIG2 receives a digital or frequency signal. Depending on its configuration, it detects a 0/1 state, pulse frequency or incoming PWM duty cycle.

Example: engine speed. A compatible frequency-based tachometer signal used by the instrument cluster connects to DIG2. The input measures frequency, which is converted into engine speed using the configured relationship. The conversion depends on the number of pulses per revolution.

Check the electrical level of the tachometer signal before connecting it. Pulses alone do not guarantee compatibility with the input: if necessary, use a signal-conditioning circuit between the source and DIG2. A detailed example is provided in section 7.

1.4. Analog inputs #

Analog InputsClick to enlarge

Analog inputs 1–4 are used for 0–5 Vsignals. The voltage changes with the measured parameter. The settings define how this voltage is converted to a meaningful value.

• Pedal position. The 0–5 V signal connects to an analog input. Conversion to a percentage is configured using the end positions and the sensor characteristic.
• MAP pressure. The pressure sensor signal wire connects to another analog input. Voltage-to-pressure conversion is configured from the characteristic of that particular sensor.

The sensor signal and its power supply are separate circuits. Power is applied to the sensor supply pin, the signal connects to the analog input, and the reference ground is connected according to the sensor and BiMatrix Mini diagrams. The 0–5 V operating range does not allow vehicle 12 V to be applied to the signal input.

Analog input data can be used in maps, assigned as signal sources for the 8HP module, sent to other devices through CAN outputs, or used to control AUX/PWM.

1.5. AUX/PWM outputs #

AUX OutputsClick to enlarge

Output on: the internal switch connects AUX to GND, and current flows through the coil. Output off: the switch is open and supply current does not flow through it. Voltage on an inactive AUX output is not necessarily 0 V: the coil may pull it up to the positive supply.

AUX outputs turn devices on and control them using PWM — pulse-width modulation. With PWM, the output repeatedly switches on and off. Frequency specifies the number of cycles per second; duty cycle specifies the proportion of time spent on.

For example, a 25% duty cycle means that the output is on for one quarter of each period. At 0% it is off; at 100% it remains on continuously. How pressure, force or speed varies with duty cycle depends on the connected device.

Coil connection: relay terminal 86 → +12 V through F1; terminal 85 → AUX1, pin 18; GND Mini, pin 14 → common ground. The schematic current path when switched on is shown at the bottom of the figure.

Lamp connection: +12 V passes through F2 to relay terminal 30; terminal 87 connects to the lamp, and the lamp's other terminal to ground. When the relay operates, contacts 30 and 87 close and the lamp lights. The relay-coil current flows through AUX; the lamp current flows through contacts 30–87.

In the illustrated relay, the flyback diode is built into the housing: the cathode — the bar side of the diode symbol — connects to 86 (+12 V), and the anode to 85 (AUX). The 85/86 polarity must be observed for this relay type. For other relay or solenoid designs, check the protection in their documentation. Select F1 and F2 ratings according to the current of each circuit and the wire cross-section.

Terminal markings and built-in diode diagram: HELLA — four-pin 12 V relay with diode. The relay's load-contact current rating is not the AUX current rating.

Check. In Live add widgets for the command source and the required PWM output. As the source value changes, check the calculated duty cycle and then the actual operation of the connected device. The PWM value in Live shows the output command; it does not confirm that current is flowing through the load.

A load may be connected directly only if its current, voltage and protection circuit match the output specifications. If the permitted load is exceeded, use an external driver or a suitable relay. Determine the allowable current from the BiMatrix Mini documentation.

The output command can depend on an input parameter, condition or map. One example is switching a fan according to temperature. Configuration is covered in section 9.

1.6. Power, ground and ignition #

KL30G connects through a 2 A fuse to pin 7 — +12 V main power. Pin 14 — GND connects to the vehicle's common ground. Identify the KL30G connection point from the wiring diagram for the specific vehicle; select wire cross-sections and the fuse holder for the protected circuit, accounting for installation conditions.

The 5–12 V ignition signal connects separately, without delay, to pin 16 — Ignition IN / DIG1. When ignition is switched off, Mini immediately detects the signal change even though pin 7 remains powered. KL30G supplies main power; the IGN input receives the ignition-on signal.

Operating sequence with KL30G #

1. Ignition is switched on. With KL30G power present and a signal on input 16, BiMatrix Mini starts. The 8 — IGN OUT output sends a 12 V signal to the gearbox and selector logic enable inputs.
2. Ignition is switched off. The signal on input 16 disappears immediately. KL30G power remains, and Mini performs the intended shutdown sequence for the connected devices.
3. The vehicle enters sleep mode. The vehicle power system disconnects KL30G, removing Mini's main power supply.

KL30G shutdown timing is determined by the vehicle; it is not a fixed 60-second delay. When checking the connection, measure pin 7 voltage after ignition off and after the vehicle enters sleep mode, and pin 16 voltage immediately after ignition off.

General principle of delayed Terminal 30g shutdown: BMW — E93 Complete Vehicle, Electric Load Shut-down Terminal 30g Relay section. Check the specific circuit and its shutdown conditions in the vehicle documentation.

If no suitable KL30G circuit is available: permanent +12 V through a relay #

When using permanent +12 V, fit an external 60-second off-delay relay. The main battery positive connects through a 2 A fuse and the relay's power contact to Mini pin 7. Power turns on with ignition and remains for another 60 seconds after ignition off.

The ignition signal connects without delay to Mini pin 16 (Ignition IN, 5–12 V) and to a compatible control input on the delay relay. Mini therefore detects ignition off immediately, while the relay removes main power later.

Connect gearbox and selector power through separate protected circuits according to their diagrams. The 12 V IGN OUT is used only for logic enable control. Do not connect power loads directly to this output.

+5 V output is used to power compatible sensors. Total sensor current must stay within this output's allowable load. Check each sensor's power, signal and ground connections against its documentation.

1.7. USB-powered bench test #

For a bench test of BiMatrix Mini itself, power can be supplied through USB. Ignition IN / DIG1 accepts a 5–12 V signal. During the bench test, +5 V from Mini's own output is applied to this input so that the unit detects ignition on.

1. Perform the test outside the vehicle, with no external ignition circuit connected.
2. Use the connector and diagram numbers to identify the +5 V output and ignition input, then fit a jumper between them. Use the ignition input specifically; IGN OUT has a different purpose.
3. Connect BiMatrix Mini to a USB power source with a USB cable.
4. The green indicator should light and remain steadily on.

The jumper is only for a standalone bench test. Remove it before connecting to the vehicle: the +5 V output must not be connected to the vehicle's +12 V ignition circuit. For vehicle installation, use the KL30G supply diagram or, if unavailable, the off-delay relay arrangement.

USB powers BiMatrix Mini for this test. If the gearbox and selector are included in bench tests, their power supplies are connected separately according to their diagrams.

1.8. Common wiring errors #

1. Incorrect CAN wiring, missing or extra resistors. Check that CAN-H connects to CAN-H, CAN-L to CAN-L, and that both wires belong to the same bus. Then check the two 120 Ω termination resistors, including any already inside units or the harness. An additional resistor at every device is not required. The check sequence is described in the CAN termination section.
2. Incorrect identification of BiMatrix Mini pins. Compare the number of every used connector pin with its number on the diagram. Wire color or position in a photograph alone is not sufficient. The pin-identification rule is highlighted in red in section 1.1.

CAN2 is the recommended connection for vehicle CAN. Before diagnosis, in CAN Monitor check that this bus is selected. For the gearbox, selector and other devices, select the interface to which they are physically connected.

1.9. Live: widgets, graphs and data export #

Live: graphs and numeric values ↗

Live is a separate module for viewing BiMatrix Mini data in real time. It provides analog, digital and CAN input values, PWM output parameters, gearbox data and other available BiMatrix Mini parameters. The interface also uses the name Live data.

Adding widgets #

Live widget settings ↗

Add a widget in Live, then select the required data source and display type:

• Graph — a graph. Displays changes in the value over time. This is useful for tracking brief changes and comparing signals.
• Number value — a numeric display. Displays the current value of the selected parameter.

For example, to check an analog input, add its value and vary the sensor signal. Use the widget reading to confirm that the correct input was selected and that its value changes as expected. Check digital inputs, configured CAN input values and other incoming data in the same way.

Pausing the view and zooming into a graph interval #

Pausing and zooming in Live ↗

1. Add the parameters you need to compare to the graphs: for example, gear, engine speed and available torque values.
2. After the event of interest, pause the graph view. The time window is held in place so the event can be examined without the graph constantly moving.
3. Select the required interval by dragging across the graph from left to right with the mouse or by touch.
4. The zoom-selection button expands this interval to fill the graph width. The + and − buttons change the time scale.
5. After analysis, resume viewing incoming data.

Pausing applies to the graph view. Data reception and accumulation continue. Zooming lets you examine already received points in more detail; it does not increase the data acquisition rate.

Example: analyzing a gear change. Compare the gear change, engine-speed change, torque reduction and subsequent torque recovery over the same time interval. This allows closer examination of the shift point and torque reduction using the available signals.

Export to CSV #

LiveClick to enlarge

After pausing the view, accumulated Live data can be exported to CSV. The file can be used for further analysis or shared with a specialist.

CSV contains the entire available accumulated Live history and all parameters present in it. The selected graph interval and widget set do not limit the export contents. The file includes timestamps and parameter values.

2. Preparing for connection #

2.1. Connecting to the app #

The BiMatrix app is available only in English. The names of modules, buttons and fields in the manual are given exactly as they appear in the app.

Power BiMatrix Mini and switch on ignition. Use the BiMatrix application for configuration. The available connection method depends on the installed firmware variant: Bluetooth (BLE) or WiFi.

Connecting over Wi-Fi #

1. Select the BiMatrix Mini network in your phone or computer's Wi-Fi settings. Enter the device serial number.
2. Stay connected to this network even if the system reports no internet: local configuration does not require internet access.
3. In the application, select the connection method WiFi. If a password is requested, enter the serial number again.
4. Check the Connected status and that the connected device's parameters load.

Connecting over BLE #

1. Enable Bluetooth; allow the application to discover and connect to devices if the system requests permission.
2. In the application, select Bluetooth, then the discovered BiMatrix Mini.
3. Enter the serial number when authorization is requested. Check the status Connected.

USB is used in the bench test to power Mini. WiFi and Bluetooth are the working communication methods in the current application interface; a connected USB cable alone does not establish application communication.

2.2. Preparing signals and power #

Before assembling the harness, identify the gearbox version, actual selector connector and source of every parameter. Names such as engine speed or torque should include units and a signal description.

When connecting to a sensor already used by an ECU, check its supply and reference-ground arrangement. Do not connect Mini's +5 V output to the ECU's +5 V output. Identify pins on all connectors by their marked numbers.

2.3. Working with app parameters #

The Inputs section contains Analog inputs, CAN Inputs and Digital Inputs. The Outputs section contains AUX Outputs and CAN Outputs. Maps performs conversions, Live displays values, and 8HP Gearbox configures gearbox communication. The BiMatrix menu provides general settings, CAN Monitor and SD Card.

1. After connecting, wait for the module parameters to load.
2. Give an input, map or output a clear name, such as RPM CAN2, Pedal Analog1 or Fan duty.
3. Change the required form fields. If an Apply changesbutton appears, click it to send the changes to the device.
4. After transmission finishes, check the fields and values again. Also verify a source change in the module that uses that source.

Creating an input does not assign it to the gearbox. In the 8HP module parameter, separately select this input as the value source. Selecting another source changes the data path, not the physical wire connection.

A unit designation is a label. Changing V to % or bar alone does not convert the value: configure the coefficients or calibration table separately.

The physical ignition input 16 is connected according to the power supply diagram. The Ignition switch field in general settings is not a substitute for this wire during installation.

2.4. Controls: manual values and switches #

Controls: three item typesClick to enlarge

Controls sets a value from the app interface. The created item can be selected as a source in a map, output or another module — for example, to select a mode manually.

The screenshots show the real app interface with demonstration names and values. No device is connected; the CONNECTED status is simulated to display the screen.

Button: two statesClick to enlarge

Switch: selecting an optionClick to enlarge

How to add an item #

Adding a new ControlClick to enlarge

1. Open Controls and press + below the items.
2. In the window Control settings set Name and select Type: Button, Switch or Numeric.
3. Configure Round (value precision), Row (placement row) and Sort ID (item order).
4. For Button enable two options in Options and fill in Name, Value, Color. For Switch enable the required options one by one using the checkboxes and fill in the same fields. For Numeric this section is not used.
5. Press Apply. For Numeric, the number is set on the Controls page. To use the item in logic, select it in the source field of the required module and check the result in Live.

Numeric: number inputClick to enlarge

How to open item settingsClick to enlarge

Editing: press the row number on the left, then the gear icon on the required item. After changing the parameters, press Apply. The button Delete control deletes the item after confirmation.

Changing a manual value can immediately affect the assigned output. Before testing, make sure the correct source is selected. Controls does not confirm the presence of a physical brake, pedal or engine speed signal.

2.5. Saving and transferring the configuration #

Parameters are applied in their respective modules. To make a separate backup, use general settings BiMatrix and Export settings.

1. Open Export settings and wait for the modules to be read from the device.
2. Select whole modules or individual items. For a working configuration with linked inputs and maps, saving all used modules is preferable.
3. Click Export settings and save the .bmsfile. Check for a successful-save message and verify that the file exists.
4. Record the vehicle, gearbox, selector, date and a brief description of the configuration alongside the file.

To restore settings, select Import settings and the required .bms file. Selecting a whole module replaces its current settings; selecting individual named items adds them to free slots. The 8HP module is transferred as a whole. Back up the current configuration before replacing it.

After importing, check every source reference, especially when adding individual inputs or maps: item names and numbers may differ from the original configuration. If the import stops after writing one module, those changes may already have been saved — check the application message and the modules' actual state.

A .bms file stores BiMatrix settings. Calibration, coding and firmware of the gearbox itself are handled by separate operations in 8HP Tuner.

2.6. App versions and updating BiMatrix Mini #

Update BiMatrixClick to enlarge

The BiMatrix Mini firmware and the Windows/Android app are two separate programs. The firmware runs inside the device and controls its functions. The app is installed on a computer or phone and is used for setup, viewing data and transferring files.

Updates can be performed manually or with the built-in assistant. Before starting, the .bms settings file is saved, the SD card is checked and a stable power supply is provided for Mini. The connection to the app is also maintained during file transfer.

First, the firmware is chosen: BLE or WiFi

The app supports both connection methods: BLE and WiFi. On BiMatrix Mini, the connection method is determined by the installed firmware. Before a manual update, the file for the required variant, BLE or WiFi, is chosen and downloaded in advance.

After WiFi firmware is installed, the connection uses WiFi; after BLE firmware is installed, it uses BLE. When the variant is changed, the previous connection will stop working. BLE does not require pairing in the Bluetooth settings of the phone or computer.

Manually updating Mini using a card reader

1. All power is disconnected from BiMatrix Mini, including USB. The SD card is removed and connected to a computer using a card reader.
2. The selected firmware file is copied to the root of the SD card, without a subfolder, and renamed exactly to firmware_ota.bin. The filename is checked to make sure the .bin extension has not been added twice.
3. The card is safely ejected from the computer and inserted into Mini. The device is powered on again.
4. At startup, Mini detects the file and begins checking and installing it. The green indicator flashes three times, then the red indicator lights up.
5. While the red indicator is lit, power remains connected and the SD card stays in place. Usually, after about 30 seconds, the green indicator lights up and Mini automatically starts the new firmware.
6. The connection is re-established. The SW / FW bar is checked to confirm the installed version and that it matches the app.

Uploading firmware through the app: SD Card

SD CardClick to enlarge

The file can be transferred to the SD card over the current connection to Mini. No card reader is required.

1. The menu is opened by pressing the BiMatrix logo. The following section is selected: SD Card.
2. Press Upload file and the previously downloaded firmware file is selected. Its original name is retained, for example firmware_ota_ble_4.4.3.bin; renaming it to firmware_ota.bin is not required.
3. The upload is allowed to finish. The green button next to the file is pressed: Reflash BiMatrix, then the action is confirmed with Yes.
4. Mini prepares the selected file and restarts to install it. The power supply remains stable until writing is complete and the device has restarted.
5. After startup, the connection is re-established and the FW version is checked.

Several firmware files can be stored on the card, and the required one can be selected using Reflash BiMatrix. After changing the Mini version, the corresponding app version is also installed.

The Reflash BiMatrix button is shown for files whose names begin with firmware_ota and end in .bin, except for the exact name firmware_ota.bin: this is reserved for automatic installation at startup. If the button is missing, the filename and upload completion are checked.

Manually installing the app on Windows or Android

After installation, the app is opened and connected to Mini. SW and FW are checked for a match. The .exe and .apk files are installed on the computer or phone; the .bin firmware file is transferred to the Mini SD card.

Automatic update: Check available versions

Release / BetaClick to enlarge

The built-in assistant retrieves the release list, downloads the appropriate app and helps install the corresponding Mini firmware. Internet access is required to retrieve the catalogue and installer; actions in the Windows or Android system installer are confirmed by the user.

1. General settings are opened by pressing the BiMatrix logo. For BiMatrix Update select Release only for regular releases or Beta testing for access to test releases. The setting is saved with Apply changes.
2. After connecting to Mini, the following top bar is pressed: SW / FW. In the window Update BiMatrix press Check available versions.
3. An available release is selected, the changes are reviewed and the following button is pressed: Update. The Bluetooth (BLE) or WiFi variant is shown next to the version. The assistant selects it based on the current Mini firmware; this list is not used to switch the connection method.
4. If a different app version is required, it is installed. The app is then opened again and connected to Mini.
5. If SW and FW do not match, the following message appears: Difference in versions detected!. The button Update BiMatrix firmware starts transferring and installing the corresponding firmware from the app.
6. The update is allowed to finish and Mini to restart. After reconnecting, the SW and FW versions are checked for a match.

Check available versionsClick to enlarge

If the selected firmware is already included in the installed app, the assistant transfers it directly to Mini without reinstalling the app. Internet access is not required to transfer the included firmware.

Continue without update postpones the update but does not resolve the version mismatch. A download or installation error message does not mean the update succeeded: the reported cause is resolved first, then the check is repeated.

3. CAN connection and 8HP module setup #

First select the gearbox and the actual selector connector. The diagram below changes with the selection, showing the required CAN lines, pin numbers and power circuits. The basis for F-series is the BiMatrix 8HP45/70 diagram.

3.1. Selecting the transmission and selector #

3.2. CAN lines and resistors #

CAN1 and CAN2 are two separate buses. Do not connect them together. Each uses an H/L twisted pair with short device branches. Each bus must have 120 Ω between H and Lat both ends, including resistors inside devices. Add a resistor only if a required termination resistor is missing.

With all power removed from the bus being checked, resistance between H and L is usually about 60 Ω: two 120 Ω resistors in parallel. About 120 Ω indicates one resistor; about 40 Ω indicates three. Connected-device state can affect the measurement; detailed diagrams are in the CAN termination section.

3.3. Connecting the vehicle CAN #

Vehicle CAN should preferably connect to CAN2: CAN-H → pin 15, CAN-L → pin 6. The vehicle bus bit rate must be 500 kbit/s; the BiMatrix Mini port speed cannot be changed in the current software.

Built-in termination resistors on the vehicle bus are counted together with all other terminators. Vehicle CAN is not added automatically to the interactive diagram: its connection point depends on the vehicle.

3.4. Setting up the 8HP module after connection #

8HP GearboxClick to enlarge

In 8HP Gearbox the connected equipment is selected and a source is assigned to each signal. A source can be a configured CAN input, an analog or digital input, a map result, or another available BiMatrix Mini parameter. The built-in module generates the message format, transmission intervals, counters and checksums required by the protocol.

Each parameter is selected according to its physical meaning and unit of measurement. For example, Engine RPM is assigned an engine speed in rpm, not a pulse frequency in hertz. Throttle position is assigned a pedal position in percent, not the raw sensor voltage.

1. Before power is applied, check the pin numbers, common ground and CAN termination. Check that Mini remains powered after ignition is switched off: from KL30G until the vehicle switches it off, or from a permanent +12 V supply through a delay relay for another 60 seconds.
2. For the initial check of incoming data, in Gearbox control type select No gearbox control and press Apply changes. 8HP message generation is disabled. Check the CAN buses in CAN Monitor, and the prepared input signals in Live. The 8HP module also pauses decoding of the gearbox's own parameters in this mode.
3. In Gearbox type select the actual gearbox type: E-Series, F-Series, G-Series or G-Series Gen3. In Selector type select the selector type. Both F-Series selector variants with different connectors correspond to F-Series selector.
4. Gearbox CAN1 and Gearbox CAN2 are assigned to Mini's physical ports according to the selected wiring diagram. These are assignments of the gearbox protocol buses and must match the wiring. Connecting vehicle CAN to Mini CAN2 is recommended.
5. Assign signal sources from the tables below and enter the vehicle parameters. For normal operation, Gearbox reflash mode must be set to 0, Dyno mode — 0.
6. After checking the assignments in Gearbox control type select BiMatrix and press Apply changes. Check the gearbox response data and faults. Changing a setting on screen without pressing Apply changes does not save it to Mini.

Main signals and parameters #

Check engine speed, pedal position, brake, torque values and vehicle speed before engaging a gear. The application allows an incomplete configuration to be saved: the absence of a warning when saving does not confirm that every source is correct.

Additional functions #

Assign these fields when the corresponding function is actually used. Do not select sources merely to fill every row.

If a selector is installed, select its actual type. No selector is used for a configuration without a physical selector; the ability to generate service messages does not replace configuring P/R/N/D commands. Having no selector and having fully verified gear control are different conditions.

One input for both paddles #

In the Paddle state field, assign a single source that reports the state of both paddles. This can be a CAN input, a calibrated analog input, a map result or a Controls item for bench testing.

Paddle state: one sourceClick to enlarge

For factory BMW E6x/E8x/E9x paddles, there are separate diagrams and configuration tables: resistive LCI paddles, dry contacts and the Sport/SAT distinction.

Only integer values are used 0, 1, 2, 3. For example, a map result of 3.00 also means state 3. A fractional or out-of-range value is treated as release. After switching from two separate fields, the source for Paddle state must be assigned again; the old binding is not transferred automatically.

Before configuration, measure the four actual voltages and compare them with the Mini input readings. To view them in Live, first configure the analog input to output voltage in volts. Use Mini readings for the table after checking calibration. Then in Analog Inputs configure the conversion from voltages to states. For this circuit, the following initial table of 10 points can be used; Round = 1 means an integer result.

Equal values at adjacent points create constant-result regions around each measured voltage. Interpolation applies between the regions: a transient voltage can briefly produce a different state, including a shift command. The table does not provide automatic wiring diagnostics or contact debouncing. Check the boundaries and transitions against measurements from the specific harness before using it to control the transmission. For factory resistive paddles, first check their own circuit: the resistor values in this example do not automatically apply to them.

1. After Apply changes assign the analog input as the sole source for Paddle state. If additional logic is required, the voltage can be converted by a separate map whose result is assigned to this field.
2. In Live check all four states, holding each one and releasing. Values must remain stable; separately check simultaneous pressing and releasing one of two held paddles.
3. In CAN Monitor check the resulting message and the transmission response. A value appearing in Live does not by itself confirm that a shift has occurred.

3.5. Engine torque and transmission feedback #

Engine data is sent to the gearbox, while its state and requests are received in return. A received value can be displayed in Live, used by a map and transmitted to another device at the same time.

Four torque values #

The example numbers explain the difference between the fields; they are not engine settings. Do not assign the same value to all four fields without checking its meaning. For a vehicle without ECU torque data, a model is created in Maps; the accuracy of transmitted torque depends on how this model is configured and whether the firmware supports the selected source.

Checking torque reduction #

During a shift, the gearbox may request a torque reduction. The module provides EGS_TOR_RED_FAST and EGS_TOR_RED_SLOW — calculated percentages for fast and slow reduction. A request appearing in Live does not, by itself, mean that the engine has carried it out.

For the supported BMW integration, in the Engine ECU select BMW E60/E70/E90 engine ECU and specify the physical CAN port connected to the ECU. This setting generates messages for the corresponding protocol, including the torque request. Another ECU requires a separately agreed compatible CAN protocol or an external control interface. Selecting a gearbox type does not provide universal torque control for any engine.

To check this, display the reduction request, Target torque, Actual torque, engine speed and EGS_GEAR_SW_STATEon one Live graph. Pause and zoom into the shift interval. Assess when the request appears and how actual torque changes. Export the recording to CSV if needed. Confirm the connection using ECU and gearbox data, not just the presence of CAN traffic.

Data returned by the gearbox #

The available feedback parameters and their updates depend on the gearbox type and incoming messages. Check an unchanging value together with the presence of the corresponding traffic in CAN Monitor.

3.6. 8HP Diagnose: faults and adaptations #

8HP DiagnoseClick to enlarge

8HP Diagnose sends diagnostic requests to the gearbox. Error memory shows fault codes, while Info memory shows information entries. The refresh-arrow button repeats the read.

1. Open 8HP Diagnose and wait for reading to finish. If there is no response, check gearbox power, wake-up and the selected CAN port.
2. Save the fault numbers and descriptions before clearing them. For a missing CAN message fault, check the specified ID in CAN Monitor; for an electrical or mechanical fault, check the relevant circuit and gearbox documentation.
3. After correcting the cause, press Clear errors.
4. Read again. If the fault returns, its triggering condition remains present or has occurred again.

In Adaptations shows pressure and filling-time adaptations for clutch packs A–E, along with available counters. Current — current data; History — saved records. Comparing the history helps reveal changes; a single adaptation value without operating conditions is not a complete diagnosis.

3.7. 8HP Tuner: transmission data, calibrations and coding #

8HP TunerClick to enlarge

In 8HP Tuner reads gearbox identifiers: hardware version, bootloader, software, coding, VIN and other available information. These are used to check compatibility before writing. Normal BiMatrix input setup and the first CAN check do not require reflashing the gearbox.

During writing, maintain stable power to Mini and the gearbox, keep ignition on, and keep the vehicle stationary with its engine stopped. Perform operations one at a time. Once erasing or writing has started, do not disconnect power; completion is confirmed by the final status, not merely by a filled progress bar.

4. Additional communication with modules: CAN inputs #

CAN InputsClick to enlarge

In the CAN Inputs module, the required parameter is extracted from a received CAN message: engine speed, pedal position, button state or another value. A separate input is created for each parameter. Several inputs can read different parts of the same message.

A created CAN input becomes a data source for Maps, the 8HP module and additional outputs. Creating an input does not assign it to the gearbox: select the required source separately in the corresponding 8HP signal settings.

4.1. What a message contains #

A message is identified by the selected bus and its CAN ID. Its data contains up to 8 bytes. Each byte contains 8 bits; one bit can represent an off/on state, while several bits can represent a number.

In the CAN ID(HEX) field, enter the identifier in hexadecimal digits without the 0xprefix. For example, 5A0. This is a message number, not a pin number or a separate wire address. The same ID on CAN1 and CAN2 may contain different data.

4.2. Creating and checking a CAN input #

CAN Inputs: input setup ↗

1. In CAN Monitor check the required bus and find the message. Confirm the signal format using the protocol description; verify that it matches the real parameter at several values.
2. In CAN Inputs press Add input. In Name enter a clear name, for example Engine RPM; in Unit — rpm.
3. In Interface select CAN1 or CAN2; in CAN ID(HEX) enter the ID. The – option disables reception by this input.
4. Set Position, Data type and byte order. Select the field length within Data type; there is no separate Data length field here.
5. Set the conversion, Round and Timeout. For the first check, leave Filter set to No filter.
6. Press Apply changes. In Live add a numeric widget or graph for the created CAN input. Check the minimum, an intermediate value and the maximum, then its response when messages stop.
7. Select the verified CAN input as the source for a map axis, the required 8HP signal or an additional output value. After assignment, check the entire data path again.

4.3. How to determine Position #

CAN InputsClick to enlarge

In CAN Inputs and CAN Outputs Bit 0 is the least significant bit of the first byte, with a weight of 1. Bit 7 is the most significant bit of the same byte, with a weight of 128. In the next byte these are Bit 8 and Bit 15 respectively.

In the analysis window of CAN Monitor bits are displayed and selected from left to right, so an individual bit's number within a byte differs from Position in CAN Inputs. For example, if Byte 0 switches between 00 and 01, the required single bit is at position 7 in Monitor, while CAN Inputs is set to Position = 0 and Data type = 1 Bit.

When reading whole bytes from a byte boundary, Position matches: use 8 for Byte 1, and also 8 for the Byte 1–2 pair, but select a length of 16 bits. For fields crossing a byte boundary, verify the settings against the original message bits and the result in Live. Copy a Start bit number from an external description or DBC only after checking its numbering convention.

4.4. Scaling, precision and signal loss #

CAN Inputs: position and conversion ↗

CAN input value = (received number − Offset) × Multiplier / Divider. Offset is subtracted first, then multiplication and division are applied. To pass a value without conversion, set Multiplier = 1, Divider = 1, Offset = 0.

For the example message in the diagram, set Position = 0, 16-bit unsigned, Little Endian, Multiplier = 1, Divider = 4, Offset = 0 and Round = 1. The bytes 40 1F give 8000 / 4 = 2000 rpm. With an example interval of 100 ms, Timeout = 500 ms, for instance, lets you check the reset after the transmitter stops. These numbers are examples; actual vehicle parameters are set according to its protocol.

Timeout = 0 is not used to hold the last value. When messages disappear, a periodic check at approximately 100 ms intervals performs the reset. A zero result may mean either a real zero or signal loss, so check its cause in CAN Monitor.

When checking a button, filtering is normally left off so the 0 ↔ 1 transition is not delayed. For a smoothly varying analog parameter, add smoothing after verifying the format and scale.

4.5. If the value does not match the signal #

CAN InputsClick to enlarge

CAN Inputs reads a specified field by ID; it does not automatically determine message meaning or check the counter and checksum of an arbitrary vehicle protocol. For signals whose format changes within one ID, the rules of that protocol must be understood separately.

5. Additional communication with modules: CAN outputs #

CAN OutputsClick to enlarge

In the CAN Outputs creates additional periodic messages for a compatible instrument cluster, ECU or another device. A message can contain a constant number, an input value, a map result or an available gearbox parameter.

5.1. Creating a message #

CAN Outputs: additional message ↗

1. Use the recipient's protocol to determine the bus, ID, message length, interval, location of all fields and their scale. Also identify required constant bytes, counters and checksums.
2. In CAN Outputs press Add output. While filling in the settings, in Interface set to –so the message is not transmitted.
3. Enter CAN ID(HEX), Length and Interval. Length is the total message size in bytes, from 1 to 8. Interval is the transmission interval in milliseconds.
4. Use the Add dynamic value button to add a field. In Value select the required source or Fixed value for a constant number. Set Position, Data type, Endian, Multiplier, Divider and Offset for each field.
5. If needed, configure Rules — transmission conditions. Check that fields do not overlap and fit within Length × 8 bits.
6. Select the physically connected CAN1 or CAN2 and press Apply changes. The message starts transmitting periodically when the conditions are met and the bus is ready.
7. Check the bytes and interval using an external CAN adapter on the same bus, then check the recipient's response. To stop transmission, assign Interface = – to this output and apply the changes.

The interval range is 10…65535 ms. For example, 100 ms corresponds to about 10 messages per second, and 20 ms to 50. Values of 1…9 ms are raised to 10 ms; Interval = 0 disables transmission. This is periodic transmission, not a send-once command.

One message supports up to 15 fields. Each field in the interface occupies 1 to 16 bits. Unfilled bits are sent as zeros; add any constants required by the protocol as separate Fixed value fields.

5.2. How the value is written to bytes #

CAN Outputs: inverse conversion ↗

Number written to CAN = source value × Divider / Multiplier + Offset. This is the inverse of the CAN Inputs conversion. The result is rounded to an integer and written into the selected field.

For example, the recipient requires engine speed × 4. For a source of 2000 rpm, set Multiplier = 1, Divider = 4 and Offset = 0: the message receives 8000. With Position = 0, 16-bit unsigned and Little Endian, the first bytes are 40 1F.

Select Position and byte order using the same rules as for CAN inputs. For example, an 8-bit field at Position = 8 is written into the second byte. Two fields must not occupy the same bits.

The number must fit within Data type: 8-bit unsigned allows 0…255, while 8-bit signed allows −128…127. On overflow, excess bits are not transmitted and the recipient sees a different number. For unsigned, a negative result is replaced with zero; this does not replace checking the source's validity.

5.3. Rules transmission conditions #

CAN OutputsClick to enlarge

Two checks are available. For each, select a source on the left, then the comparison == (equal to), > (greater than) or < (less than), and another source or a constant number on the right. Leave an unused check set to Rule #1 not in use or Rule #2 not in use.

The message is transmitted when all enabled checks are satisfied. If both are disabled, transmission runs continuously at the specified Interval. If a condition becomes false, transmission stops; a separate zero-valued message is not generated automatically.

Example: Rule #1: engine speed > 500; Rule #2: engine speed < 3000. The message is sent only between these limits. Exactly 500 and exactly 3000 do not satisfy the condition. Comparisons use integer values: for fractional thresholds, first create a suitable integer value in the logic.

If the source is a CAN input, loss of its messages causes its value to become zero after Timeout. Configure rules with this behaviour in mind. With Rules disabled, the message continues to be generated, including a zero value from the missing input.

5.4. Transferring a value between buses #

CAN OutputsClick to enlarge

To transfer a parameter from CAN2 to CAN1, first create a CAN input on CAN2. Then select this input in Value for a CAN1 output in CAN Outputs. Add a map between them if necessary. Configure the output format separately to match the recipient's expectations.

This chain transfers the selected value with a new interval and format. All other messages and bytes from the original bus are not automatically forwarded to the other port. Do not join the CAN1 and CAN2 wires for this purpose.

Standard identifiers up to 7FF are transmitted in 11-bit format. Identifiers from 800 to 1FFFFFFF are transmitted in extended 29-bit format. Both Mini ports remain at 500 kbit/s; selecting another ID does not change the speed.

5.5. Checking a message and common errors #

CAN OutputsClick to enlarge

Live is used to check the source value and map results. CAN Monitor shows received messages; it does not provide TX echo of messages sent by CAN Outputs. To verify the actual bytes of your CAN output, use an external CAN adapter on the same bus; also confirm recipient operation using its readings or response messages.

CAN Outputs has no separate setting for an automatic counter or checksum for an arbitrary protocol. If the recipient requires these fields, a constant number is insufficient. The built-in module generates the required service fields for 8HP; do not duplicate its messages manually.

6. Maps: maps and logic #

MapsClick to enlarge

The Maps module converts input values into a result using a configured table. Input signals and results from other created maps can serve as data sources.

6.1. Linked maps #

MapsClick to enlarge

This separates the calculation into clear stages: obtaining a base value, applying a correction, and selecting a characteristic from input data. Assign the final map's result to the required 8HP parameter, CAN output or AUX/PWM.

6.2. Correction map #

MapsClick to enlarge

The Values table type is used for an ordinary table of values. The Correction table type is used for percentage correction: in the Correction of field select the original value, and enter a percentage of that value in the cells.

Corrected result = original value × table percentage / 100. 100% preserves the original value; 80% reduces it to 80% of the original.

Assignments are configured separately: X/Y Axis source determines where the table is read, while Correction of determines which value is corrected. Selecting map A as an axis does not, by itself, assign it as the correction's original value.

6.3. Switching characteristics based on input data #

MapsClick to enlarge

An input signal can be used as a mode-selection axis. For example, assign a button state received through a digital input or CAN to the Y axis. Set different table characteristics for states 0 and 1.

For more complex logic, a separate map can calculate the mode value. Assign its result as an axis of the next map. This creates a chain of linked maps whose behaviour changes according to the input data.

6.4. Checking linked maps #

MapsClick to enlarge

In Live add the original signals and each map's result. When an input changes, check the entire chain: the first map's result, the value on the next map's axis, and the final result. For mode switching, check both input signal states separately.

6.5. Creating and filling a map #

MapsClick to enlarge

1. In Maps select Add map. In Map settings set Name — a clear name, Group — the map group, and Unit — the result unit.
2. For an ordinary calculation, select Map type → Values table. For percentage correction, select Correction table and separately assign Correction of, as in the example above.
3. In X Axis source and Y Axis source assign signals that have already been checked, for example engine speed and pressure. Axis values use the selected sources' units: rpm, kPa, %, °C. Renaming a unit does not convert the value.
4. In X/Y Axis length set 2 to 12 points on each axis. A small table is sufficient to start. Fill the axes in order without accidental duplicates or rearrangements; the range must include a stopped engine and all expected operating values.
5. Round sets the result increment: 1, 0.1 or 0.01. Whole units are usually sufficient for torque in N·m, for example. More decimal places reduce the available numeric cell range; the interface limits this range.
6. Confirm the settings with the Applybutton. Then enter the axis and cell values. Double-press to open an individual cell. A selected area supports Enter value, Copy cells, Paste cells and horizontal or vertical interpolation. Save table changes with the Apply changes.
7. In Live display both axes and the map result. Check table points, intermediate values and boundaries. Only then assign the result to the required 8HP parameter, CAN Outputs or AUX Outputs.

Interpolation means smooth calculation between neighbouring cells. For example, halfway between results of 100 and 200, the result is 150. With two changing axes, four neighbouring cells are used. The interpolation command in the editor fills selected cells; interpolation between points during operation happens automatically.

Create linked maps in order: first the original map, then maps that use its result. Do not use a closed loop where A depends on B and B depends on A for this setup. After changing a source's units or precision, recheck the axes of all dependent maps. A numeric Maps result does not, by itself, confirm that the original sensor is working or that a fresh CAN message is available.

7. Vehicle without CAN #

If suitable data is unavailable on vehicle CAN, engine speed, pedal position and pressure can be measured through separate BiMatrix Mini inputs. Communication with the gearbox itself and a CAN selector remains over CAN. Check each input first, then use its value in maps and assign it to 8HP module parameters.

7.1. Which wires to connect #

DIG1 / Ignition IN, pin 16, is used for 5–12 V ignition. If DIG2 is already used for the tachometer signal, do not attach a second brake wire to it. First convert a 12 V brake signal to a compatible 0–5 V level for a free analog input, or obtain it through a separate CAN module. For the Brake force parameter, convert the discrete state to 0/100 %; a raw 0/1 value is insufficient for all brake-applied flags.

Identify the tachometer signal wire from the vehicle diagram and check it with an oscilloscope: amplitude, polarity and voltage spikes matter. An ignition-coil terminal or crankshaft sensor is not a ready-to-use tachometer output. Use a signal conditioner if necessary. For an original electronic pedal, retain its power supply and ECU connection; do not join the +5 V supplies of two devices. Detailed diagrams: DIG2 and analog sensor.

7.2. DIG2 frequency → RPM #

Digital InputsClick to enlarge

1. In Digital Inputs create or open a row. Interface — Digital input #2; in Measuring type select Frequency.
2. For the first check, enter the name “Tacho, Hz” and unit Hz. In all 12 points of the Input values and Output values table, enter matching numbers so the result equals the measured frequency.
3. After Apply changes check the frequency in Live at known engine speeds. Determine the number of pulses per engine revolution, N. Obtain it from the source documentation or verify it by measurement; do not assign it solely from the cylinder count.
4. In Input values retains frequency in Hz; in Output values enter the corresponding engine speeds using the formula below. Change the name to “DIG2 RPM” and the unit to rpm. Fill all 12 points and apply the changes.
5. Compare readings with an independent instrument at several engine speeds. Check that the value returns to zero when the engine stops.

Engine speed, rpm = frequency, Hz × 60 / N.
Example only for a source with N = 2: 20 Hz → 600 rpm; 50 Hz → 1500 rpm; 100 Hz → 3000 rpm; 200 Hz → 6000 rpm.

Conversion between points is linear. Outside the digital calibration range, the nearest point is used. If pulses stop, frequency and calculated engine speed become zero after a timeout: at least 1 second or three measured periods, but no more than 30 seconds. For a typical tachometer signal, this is about 1 second.

7.3. Pedal and MAP: 0–5 V calibration #

Analog InputsClick to enlarge

1. In Analog inputs select the required row or Add input. In Interface assign the physical input: in this example the pedal is Analog input #2, MAP — Analog input #1.
2. To check voltage, set Unit = V, Round = 0.01, and at each of the 10 points in Values repeat the corresponding voltage from Voltages. After applying, the result in Live should match the voltage measured relative to the reference ground.
3. In Voltages enter voltages in ascending order; in Values enter the corresponding pedal position or pressure. Fill all 10 points. For a nonlinear sensor, obtain intermediate points from its characteristic.
4. For the pedal, select the unit %; for MAP, select the unit that will be used on the map axis, for example kPa. Press Apply changes. Check the pedal's end and intermediate positions in Live, and compare pressure with a known reference value.

For this table, set Round = 0.1. For MAP, separately determine whether its characteristic represents absolute or gauge pressure: these scales have different zero references. Between neighbouring points, the result is interpolated; below or above the entire analog table, its endpoint value is used.

7.4. Calculating torque and assigning it in 8HP #

MAP measures pressure, while the pedal measures position. Neither signal alone measures engine torque. In Maps create an estimated characteristic, for example with engine speed on X and pressure on Y; enter cell values in N·m using data for the actual engine. The pedal can be used in a separate request or correction map. The creation and checking procedure is described in section 6.5.

Requested torque, actual torque and engine losses are different parameters. Do not assign one arbitrary table to all these inputs at once. After calibration, assign the corresponding source to each 8HP module parameter, then check transmitted values and validity flags.

Sending a torque estimate to the gearbox informs it of the estimated load. It does not physically reduce engine torque. If torque control during shifts is required, compatible interaction with the engine ECU must be provided separately.

8. Mixed connection #

Sources are assigned separately for each parameter. Engine speed can therefore come from vehicle CAN, the pedal from Analog 2, and additional pressure from Analog 1. Vehicle CAN connects to CAN2 according to the selected wiring layout; additional wires do not replace power, ignition or communication with the gearbox.

8.1. Source table #

Prepare a short table before configuration. Include the signal origin in names, such as “RPM CAN2”, “Pedal Analog2” and “MAP Analog1”. This prevents confusion between similarly named values when selecting a source.

Having a signal available in two places does not create automatic redundancy. For example, when “RPM CAN2” is assigned, loss of CAN does not switch the source to DIG2. Such switching requires separately designed and verified logic.

8.2. Checking signal loss #

Display the original signals, map results and assigned 8HP parameters together in Live. Check on a stationary vehicle or test bench: disconnect one signal source at a time, then observe the entire dependent chain and its recovery after reconnection.

For F-series actual torque, an intermediate map does not replace a direct CAN source of valid data in the current generator. Even if a map simply repeats a CAN value, its result is treated as a different source. Check assignments against the 8HP module description.

9. AUX/PWM output setup #

AUX OutputsClick to enlarge

AUX Outputs converts a selected value into a PWM duty cycle from 0 to 100%. Physical outputs: AUX1 — pin 18, AUX2 — 9, AUX3 — 10, AUX4 — 1. Each switches to ground. Pin 8 — Ignition OUT 12 V — is for ignition logic control and is not used in place of AUX.

9.1. Source and Values/PWM table #

AUX OutputsClick to enlarge

1. In AUX Outputs open a row or select Add output. In Name enter the load name, for example “Lamp relay”.
2. In Source assign a verified signal: CAN Input, Analog input, Digital input, a manual Controls value or a Maps result. In Output select the required AUX. Assign one physical output to one row.
3. In Frequency set the frequency. In the Values/PWM table, the Values row contains source values, and the PWM row contains corresponding duty cycles of 0–100%. There are 10 points in total; select Round to match the source value precision.
4. Fill the entire required range, including the possible value on source loss. Conversion between points is linear. After Apply changes display the source and AUX result in Live, then check the output's physical switching.

9.2. Example: switching a lamp through a relay #

AUX OutputsClick to enlarge

Connect according to the lamp and relay diagram: the coil receives +12 V through its own fuse, and AUX1 switches its other terminal to ground. The lamp's power current passes through relay contacts 30–87. Use voltage-spike suppression on the coil with the polarity shown in the diagram.

For a source that reliably takes only 0 or 1, use the table below. At 0 the coil is off; at 1 it is continuously on. An intermediate value produces PWM, so this source must not vary smoothly. Do not use the relay for PWM brightness or speed control.

For this example, an ordinary frequency of 100 Hzcan be selected: at strictly 0% and 100%, no pulsed switching occurs. If Source produces, for example, −1 during a fault, add that point with the required state and rearrange the other points in ascending order. The original 0–9 table does not cover −1.

9.3. PWM frequency and duty cycle #

AUX OutputsClick to enlarge

Frequency sets the number of cycles per second. Duty cycle sets the proportion of each cycle during which AUX is connected to ground: 0% is off, 100% is continuously on. For example, at 100 Hz the period is 10 ms; at 30%, the switch is on for about 3 ms and off for 7 ms.

The list provides ordinary frequencies 5–500 Hz and High frequency #1 / #2. These two options use shared configurable timers. Their values and Hz/KHz/MHz units are set separately in the same module. If several AUX outputs use one timer, changing its frequency affects all those outputs; each output retains its own duty cycle.

The MHz field does not mean the connected coil, wiring or power switch is suitable for that frequency. Check the operating frequency and actual waveform for the chosen load. For a fan's PWM control input, also check polarity, required pull-up and permitted voltage.

9.4. Solenoid, fan and external control #

AUX OutputsClick to enlarge

The permitted AUX current cannot be determined from the PWM name, an individual transistor's rating or the BiMatrix Mini power fuse. Before directly connecting a coil, confirm load current, starting conditions, heat dissipation and output protection. If no rating has been confirmed, use a compatible external driver. Ignition OUT must not power coils, lamps, solenoids or fans.

9.5. Checking control operation #

AUX OutputsClick to enlarge

First check the 0% command and open state, then the required operating values. For PWM, verify waveform, frequency and duty cycle with an oscilloscope; an average multimeter reading does not replace this check. Observe Source and AUX together in Live, then check the load's actual response.

For temperature-based activation, a table can define duty cycle against temperature or receive a prepared command from Maps. AUX Outputs itself has no separate hysteresis field for different switch-on and switch-off temperatures. An ordinary table does not remember the direction of temperature change. For temperature control with this logic, use an appropriate controller or a separately verified solution.

Finally, check source loss, signal recovery, ignition off and ignition on again. The final criterion is the connected device's state, not merely the PWM number on screen. Save the working configuration after checking every AUX output in use.

10. Connection checks and first start #

Check in sequence: power → communication → input values → 8HP module → gearbox response. If a stage fails, correct its cause first.

10.1. Before applying power #

1. Check that the installed transmission is an 8HP automatic transmission from BMW and that its version matches the type selected in the 8HP module.
2. Compare harness pin numbers with the Mini pinout and selected gearbox and selector wiring diagram.
3. Check for no supply-to-ground short, separation of 12 V and 0–5 V signals, a common ground and separate fuses for power branches.
4. With all devices unpowered, measure resistance between H and L on each CAN bus. Two 120 Ω terminators should give approximately 60 Ω. Accounting for resistors →
5. Check that +12 V is not applied to CAN pins, analog inputs or the +5 V output. Remove the USB test jumper between 2 and 16 before connecting vehicle ignition.

10.2. Power and communication without starting the engine #

1. Apply power to pin 7 and a 5–12 V ignition signal to 16. Check that the green indicator stays steadily lit.
2. Establish a connection to the application. Check that parameters load.
3. For an initial inspection of the buses, you can use No gearbox control. In this mode, check CAN Monitor and the configured inputs; the 8HP module's feedback parameters must not be treated as functioning passive gearbox monitoring.
4. Select the actual interface in CAN Monitor. Check IDs, message reception and byte changes when the corresponding vehicle control is operated.

10.3. Checking values #

A plausible number in Live does not yet confirm that the message on the wire is correct. For additional messages — CAN output check.

10.4. Checking the transmission and selector #

1. Select the actual Gearbox type and Selector type, CAN roles and control mode according to section 3.4.
2. With the vehicle stationary, parking brake applied and brake pedal held, check selector positions and gearbox response. Clear the area around the vehicle before engaging a gear.
3. Compare the selector command, lever position, actual gear and gearbox status. A command value is not confirmation that a gear is engaged.
4. Read faults through 8HP Diagnose. Save their codes and triggering conditions first, then correct the causes.
5. Check ignition shutdown: the signal on 16 is removed, IGN OUT stops commanding activation, and Mini remains powered from KL30G until sleep or from a delay relay for another 60 s. Check switching on again too.

10.5. Saving the check results #

After checking, save the .bms configuration. To analyse shifts, display engine, input-shaft and output-shaft speeds, gear, pedal, torque and the available torque correction request in Live. Pause the recording for viewing, zoom into the required interval and export it to CSV.

For a road check, configure recording before driving. A passenger operates the application, or it is operated after stopping. Perform initial checks at low load; resolve unstable input signals and active faults before testing under load.

11. Common faults and reference diagrams #

11.1. Where to look for the cause #

Check the input signal first, then its conversion and assignment. If the original value is wrong, changing a map or gearbox setting does not correct the cause.

11.2. What to save for troubleshooting #

Record the application and Mini firmware versions, vehicle, gearbox and selector, power arrangement, and the exact sequence that causes the fault. Include a diagram of the actual harness with pin numbers, the .bms configuration, fault codes and a data recording covering the relevant interval.

In BiMatrix → SD Card select a file for download. Finish recording first, then save the completed file. CSV shows calculated parameters, while a CAN recording shows messages; both types of data are useful for a complex case.

11.3. Quick links to diagrams #

• Device, connector and colour-coded 18-pin table.
• Wiring for the selected gearbox and selector.
• Two 120 Ω resistors and CAN bus measurement.
• KL30G power supply and delay-relay option.
• DIG2 tachometer signal, MAP sensor and lamp through an AUX relay.

11.4. Glossary of terms #

Instructions were checked against the local device schematic, firmware and application interface on 9 September 2026. Example values explain configuration. Unconfirmed gearbox/selector combinations and current software limitations are identified in the relevant sections.