Diagnostic tools

​

Log parser utility

​

Features

• Decodes I-Bus messages - Translates hex packets into meaningful commands and data
• Parses Bluetooth events - Interprets BM83 and BC127 Bluetooth module messages
• Adds timestamps - Correlates events with vehicle time (when GPS data available)
• Filters noise - Optionally ignores high-frequency status messages
• Statistics mode - Provides command frequency and device activity analysis

​

Installation

# Install required Perl modules
cpan DateTime
cpan Getopt::Long
cpan Data::Dumper

utility/log_parser.pl

​

Basic usage

./log_parser.pl your_bluebus_session.log

​

Command-line parameters

​

Time display options

./log_parser.pl --time your_log.log        # Show local time
./log_parser.pl --no-time your_log.log     # Hide local time

​

Raw data options

./log_parser.pl --raw your_log.log         # Show original lines

​

Payload display

./log_parser.pl --payload your_log.log     # Always show hex data

​

Filtering options

./log_parser.pl --no-unprocessed your_log.log  # Clean output

./log_parser.pl --stats your_log.log       # Show statistics

# Ignore default noisy commands
./log_parser.pl -i your_log.log

# Ignore specific commands
./log_parser.pl --ignore-commands=IKE_BROADCAST_SPEED_RPM_UPDATE,RAD_TMC_REQUEST your_log.log

# Ignore by hex ID
./log_parser.pl --ignore-commands=03,18,19 your_log.log

• RAD_TMC_REQUEST / RAD_TMC_RESPONSE - Radio traffic data
• TEL_TELEMATICS_LOCATION / TEL_TELEMATICS_COORDINATES - GPS data
• RAD_BMW_ASSIST_DATA / TEL_BMW_ASSIST_DATA - Telematics
• GM_RLS_STATUS / LCM_RLS_STATUS - Rain/light sensor
• IKE_BROADCAST_SPEED_RPM_UPDATE - Speed/RPM (very frequent)
• IKE_BROADCAST_TEMP_UPDATE - Temperature updates
• LCM_BROADCAST_INSTRUMENT_BACKLIGHTING - Lighting status
• LCM_BROADCAST_INDICATORS_RESP - Turn signals
• GM_BROADCAST_DOORS_STATUS_RESP - Door status
• IKE_BROADCAST_SENSOR_RESP - Sensor data
• RAD_BROADCAST_STATUS_RESP - Radio status
• BC127_AVRCP_MEDIA_RESPONSE - Media metadata

# Ignore by device name
./log_parser.pl --ignore-device=RAD,CDC your_log.log

# Ignore by hex address  
./log_parser.pl --ignore-device=68,18 your_log.log

​

Advanced examples

# 1. Start screen with logging
screen -L /dev/tty.usbserial-XXXXXXXX 115200

# 2. In another terminal, enable instant flush
screen -r -x -p0 -X logfile flush 0

# 3. Watch live parsed logs
tail -f screenlog.0 | ./log_parser.pl -

# Find all messages to/from GT (Graphics Terminal)
./log_parser.pl your_log.log | grep -a --context=5 ' -> GT'

# Find all messages from IKE (Instrument Cluster)
./log_parser.pl your_log.log | grep -a 'IKE ->'

# Find broadcast messages
./log_parser.pl your_log.log | grep -a ' B '

# Show only Bluetooth events
./log_parser.pl your_log.log | grep -a 'BT\|BBUS'

# Find pairing and connection events
./log_parser.pl your_log.log | grep -Ei 'pair|connect|disconnect|open'

# Track A2DP audio connection
./log_parser.pl your_log.log | grep -a 'A2DP'

# Show only errors and warnings
./log_parser.pl your_log.log | grep -Ei 'error|warning|fail'

# Count error types
./log_parser.pl your_log.log | grep 'ERROR' | sort | uniq -c

# Find I-Bus errors with context
./log_parser.pl your_log.log | grep -a --context=10 'IBus.*ERROR'

​

Understanding parsed output

​

Output format

[timestamp] (local_time) S B SRC  -> DST  CMD_HEX COMMAND_NAME (parsed_data)

• timestamp - Milliseconds since startup
• local_time - Real time from vehicle clock (if available)
• S - Self marker (* = message sent by BlueBus, = received)
• B - Broadcast marker (B = broadcast message, = direct)
• SRC - Source device (e.g., IKE, RAD, GT, BBUS)
• DST - Destination device
• CMD_HEX - Command ID in hex
• COMMAND_NAME - Human-readable command name
• parsed_data - Decoded parameters and values

​

Example output

 0: 0:00:00.000          *   BBUS -> RAD  06 RAD_CDC_REQUEST (command=CD_CHANGE)
 1: 0:00:00.010              CDC  -> RAD  39 CDC_RESPONSE (status=STOPPED, audio=STOPPED, ...)
 2: 0:00:00.125          * B IKE  -> GLO  18 IKE_BROADCAST_SPEED_RPM_UPDATE (speed=0 km/h, rpm=0)
 3: 0:00:00.250              GT   -> RAD  48 GT_BUTTON (button=NEXT, state=PRESS)

​

Statistics mode

./log_parser.pl --stats your_log.log

1. Command frequency
   • Count of each command type
   • Average payload size
   • Identifies noisy commands
2. Device activity
   • Messages sent by each I-Bus device
   • Helps identify chatty modules

Count,  Avg sz  of non-ignored commands:
1523    4       IKE_BROADCAST_SPEED_RPM_UPDATE
892     8       GT_BUTTON
234     12      BMBT_DIAL_KNOB
156     0       CDC_REQUEST
89      16      IKE_BROADCAST_SENSOR_RESP

Count   of non-ignored devices sending packets:
1523    IKE
892     GT  
234     BMBT
156     RAD
89      GM

​

Decoded I-Bus devices

​

Bluetooth message types

​

BC127 (older modules)

[timestamp] (time) * BBUS -> BT   BC127_COMMAND data
[timestamp] (time)   BT   -> BBUS BC127_EVENT_RESPONSE data

• BC127_LIST - List paired devices
• BC127_STATUS - Request connection status
• BC127_MUSIC - Media control (play/pause/next/prev)
• BC127_AVRCP - Request track metadata

​

BM83 (newer modules)

[timestamp] (time) * BBUS -> BT   CMD_HEX BM83_CMD_Name (parsed_params)
[timestamp] (time)   BT   -> BBUS EVT_HEX BM83_EVT_Name (parsed_params)

• BM83_CMD_Music_Control - Playback control
• BM83_CMD_MMI_Action - Phone actions (accept/reject call)
• BM83_CMD_Profiles_Link_Back - Reconnect last device
• BM83_CMD_AVC_Vendor_Dependent_Cmd - AVRCP metadata requests

• BM83_EVT_BTM_Status - Connection status changes
• BM83_EVT_Call_Status - Phone call state
• BM83_EVT_AVC_Specific_Rsp - Metadata responses
• BM83_EVT_Read_Linked_Device_Information_Reply - Device details

​

Firmware update tools

​

Console firmware tool

python3 console_firmware_tool.py --port /dev/ttyUSB0 --file firmware.hex

• --port - Serial port (e.g., /dev/ttyUSB0, COM3)
• --file - Firmware hex file to flash
• --bt-mode - Enter Bluetooth module update mode
• --read-sn - Read device serial number
• --read-build - Read firmware build date

• Automatic platform detection
• Flash erase and verification
• Progress indication
• Error recovery

​

GUI firmware tool

• Graphical interface for firmware updates
• Automatic serial port detection
• Progress bar with status updates
• Platform compatibility verification

pip install pyserial intelhex tk-tools

• BLUEBUS_BOOTLOADER_1_3 through 2_3
• Automatic version detection

​

Update process

1. Enter bootloader mode
   • Connect BlueBus via USB
   • Power on with ignition
   • Device should identify as bootloader
2. Platform detection
   • Tool sends PROTOCOL_CMD_PLATFORM_REQUEST
   • Bootloader responds with version
   • Compatibility verified
3. Flash erase
   • Application memory erased (0x1800 to 0xAA800)
   • Bootloader memory protected
   • Takes ~10 seconds
4. Write firmware
   • Firmware written in 246-byte chunks
   • Each packet acknowledged
   • Checksum verified
5. Start application
   • Bootloader jumps to application code
   • BlueBus boots normally

​

Serial debugging

​

Connection settings

• Baud rate: 115200
• Data bits: 8
• Parity: None (or Odd for bootloader)
• Stop bits: 1
• Flow control: None

​

Terminal software

screen /dev/ttyUSB0 115200

​

Debug log levels

• DEBUG - Detailed I-Bus and Bluetooth packet traces
• INFO - Status messages and state changes
• WARNING - Non-critical issues (retryable errors)
• ERROR - Critical failures requiring attention

​

Enabling debug logging

// Log sources (can be enabled/disabled individually)
LOG_SOURCE_SYSTEM    // System events
LOG_SOURCE_IBUS      // I-Bus messages
LOG_SOURCE_BT        // Bluetooth events  
LOG_SOURCE_UI        // UI updates

​

Common log patterns

​

Normal operation

[100] INFO: System: BlueBus v1.x.x starting
[150] DEBUG: IBus: Detected GT Version: MKIV
[200] INFO: BT: Module ready
[250] DEBUG: BT: Power state: ON
[500] DEBUG: IBus: IKE -> Ignition: POS_2
[1000] INFO: BT: Device connected
[1050] DEBUG: BT: A2DP link opened
[1100] DEBUG: BT: AVRCP link opened

​

Bluetooth connection

[1000] DEBUG: BT: Link back to last device
[1200] INFO: BT: Device connected - MAC: XXXXXXXXXXXX
[1250] DEBUG: BT: HFP profile opened
[1300] DEBUG: BT: A2DP profile opened  
[1350] DEBUG: BT: AVRCP profile opened
[1400] INFO: Handler: Device fully connected

​

Profile error recovery

[5000] WARNING: BT: OPEN_ERROR AVRCP
[5001] INFO: Handler: Set pairing error for AVRCP
[10000] DEBUG: Handler: Resolve pairing error
[10100] INFO: BT: Retry AVRCP connection
[12000] DEBUG: BT: AVRCP profile opened
[12001] INFO: Handler: Pairing error resolved

​

I-Bus error

[50000] ERROR: IBus: RX Invalid Length [45 - 0x2D]: 68 05 FF 2A 01 ...
[50001] DEBUG: IBus: Buffer reset
[50100] DEBUG: IBus: Normal operation resumed

​

Generating diagnostic reports

1. Hardware information
   • BlueBus hardware version
   • Bluetooth module type (BC127/BM83)
   • Vehicle make/model/year
   • Display type (BMBT/MID/CD53)
2. Firmware version
   • Application version
   • Bootloader version
   • Build date
3. Parsed logs
   # Generate comprehensive diagnostic log
   ./log_parser.pl --time --stats raw_log.log > diagnostic_report.txt
   
4. Configuration settings
   • Audio settings (DAC gain, DSP mode)
   • Bluetooth settings
   • UI preferences
5. Problem description
   • When issue occurs (startup, during operation, specific trigger)
   • Frequency (always, intermittent, once)
   • Steps to reproduce