How trentseed/bmw_e46_android_rpi_ibus_controller works
Project type and purpose
• This is an IoT-style, full-stack “connected car” system.
• Purpose: Provide an Android (tablet/phone) + Android Wear UI to control a BMW’s IBUS network via a Raspberry Pi acting as a bridge between Bluetooth and the car’s IBUS USB adapter, running a Python-based controller service.
File structure
• connected_car_app/
• app/ → Android mobile/tablet application (Activities, Adapters, layouts, resources)
• common/ → Shared Android library: BluetoothInterface, IBUSPacket, ControllerMessage, etc.
• ibuswear/ → Android Wear standalone app (Fragments, layouts, grid pager)
• connected_car_controller/
• controllers/ → Model-specific logic (base, BMW e46 implementation)
• interfaces/ → Abstractions for BT, CAN bus, IBUS protocols
• start_controller.py → Entry point for Python app (CLI “bmw-e46” driver)
• etc/config.ini → Runtime configuration (BT MAC, ports)
• Dockerfile + docker-compose.yml → Containerized deployment
• tests/ → Unit tests for controllers and interfaces
• setup.py, requirements.txt → Packaging and Python dependencies
README for additional insights
• Three physical/hardware components: Android Tablet, Raspberry Pi, IBUS USB Adapter
• Bluetooth pairing used between Android devices and Pi
• Optionally containerized via Docker
• Workflow: UI ↔ Bluetooth ↔ Python controller ↔ USB/UART ↔ IBUS network
• Blue for Android components
• Green for Python/controller components
• Gray for hardware (Bluetooth radio, USB Adapter, IBUS network)
• Annotations of protocols/ports (e.g., Bluetooth SPP UUID, USB-tty device, config.ini path)