Introduction
The I-BUS is a communication protocol used in BMW vehicles to facilitate communication between various control modules, reducing the need for extensive wiring. In models like the E39, the I-BUS is instrumental in managing components such as the radio, navigation, and CD systems. It allows for integration of comfort features, including central locking and remote access, which are controlled through the GM5 (ZKE) module.
The I-BUS, along with the K-BUS, forms the backbone of BMW's in-vehicle communication network. While the I-BUS handles multimedia and comfort functions, the K-BUS is more focused on body electronics. Understanding these systems is crucial for retrofitting features like central locking and comfort access in the E39.
Physical Layer
The I-BUS operates on a single-wire communication system, utilizing an open collector topology. This means that the bus is normally at a high voltage level, approximately +12V, which can be pulled low by connected devices to transmit data. The wire itself is typically colored white/red/yellow in BMW vehicles.
This setup is robust, allowing the bus to function even if the wire is shorted to ground or broken. The open collector design ensures that multiple devices can communicate without interfering with each other, making it ideal for the complex networking required in modern vehicles.
Communication Parameters
The I-BUS communicates at a baud rate of 9600 bps, using 8 data bits, even parity, and 1 stop bit. These parameters are essential for ensuring reliable data transmission across the vehicle's network.
Packet timing is also a critical aspect of I-BUS communication. Each message must be carefully timed to avoid collisions on the bus, which can lead to data corruption or loss. Understanding these parameters is vital for anyone looking to work with BMW's I-BUS system.
Packet Structure
An I-BUS packet is structured as follows: it begins with a source device ID, followed by the length of the packet (excluding the source ID and length byte itself), the destination device ID, the data payload, and finally an XOR checksum. The checksum is used to verify the integrity of the packet, ensuring that data has not been corrupted during transmission.
Source ID | Length | Dest ID | Data | XOR ChecksumFor example, a packet could look like this: 68 03 18 01 72, where 68 is the source ID, 03 is the length, 18 is the destination ID, 01 is the data, and 72 is the checksum.
Device ID Table
The I-BUS uses specific device IDs to identify different components within the vehicle. Here are some of the device IDs:
- 00 - Broadcast
- 18 - CDW - CDC CD-Player
- 3B - NAV Navigation/Videomodule
- 50 - MFL Multi Functional Steering Wheel Buttons
- 68 - RAD Radio
- 80 - IKE Instrument Kombi Electronics
- C8 - TEL Telephone
- FF - Broadcast
These IDs are crucial for directing messages to the appropriate modules within the vehicle's network.
Collision Detection & Arbitration
Collision detection and arbitration are managed by the Instrument Kombi Electronics (IKE) module. The IKE ensures that only one device communicates on the bus at a time, using a priority-based system to resolve conflicts.
When a device wants to send a message, it checks if the bus is free. If another device is already transmitting, it waits for the bus to clear before attempting to send its message. This process helps maintain orderly communication and prevents data loss.
Hardware Interfacing
Interfacing with the I-BUS requires specific hardware components. For basic interfacing, a simple circuit with a MAX232A chip can convert RS232 levels to TTL levels, allowing a PC to communicate with the bus.
For more advanced applications, a contention detection circuit using logical gates and an RS latch can be used to manage bus access and detect collisions. This setup is essential for developing reliable aftermarket solutions and diagnostic tools.
Software Tools
Several software tools are available for analyzing and interacting with the I-BUS. The I-Bus Analyser software, for instance, allows users to view messages in real-time, load and save logs, and filter messages by source or destination ID.
Other tools like INPA, NCS Expert, and WinKFP are used for coding and diagnosing BMW vehicles. These tools provide deep access to the vehicle's electronic systems, allowing for customization and troubleshooting of various modules, including the GM5 for central locking and comfort access.
Practical Example
Consider a practical example of sending a message to the CD player. The packet structure might be: 68 00 18 01. Here, 68 is the source ID for the radio, 00 is the length placeholder, 18 is the destination ID for the CD player, and 01 is the command to poll the CD player.
When constructing such a packet, the checksum is automatically calculated by the software, ensuring message integrity. This example highlights the importance of understanding I-BUS communication for effective retrofitting and diagnostics in the BMW E39.