Is anyone aware of existing efforts to document the raw CAN/OBD2 codes for the Civic 11th generation and compile a .dbc database? I’ve recently ordered a Macchina A0 computer interface to use with SavvyCAN, with the aim of reverse-engineering the code sequences associated with specific events in my vehicle.
My primary focus is to understand the signals behind these warnings:
- The prominent red “Lane Departure” warning light on the instrument panel.
- The urgent red “Brake!” warning light that appears when the Adaptive Cruise Control (ACC) system detects slowing or stopped traffic ahead at high speeds but seems to react insufficiently, requiring manual braking.
- Instances where Lane Keeping Assist System (LKAS) disengages or struggles to maintain lane centering, indicated by the green lane lines becoming gray or disappearing.
My objective is to identify the precise code sequences that trigger these warnings. By connecting the Macchina A0 interface to an Android phone (possibly running AOSP) via OTG, I intend to develop a system that can independently produce loud, distinct alerts – separate from the car’s built-in warnings – in response to these specific signals. Ideally, this would also trigger a vibration on my Android watch as a supplementary alert, although Bluetooth reliability makes this a secondary consideration. My broader ambitions extend beyond this initial phase, but this is the crucial starting point.
It’s understood that the OBD2 port’s position relative to the CAN bus gateway limits direct access to the raw FCAN or BCAN bus, preventing command issuance for functions like steering or acceleration. However, considering the fundamental purpose of OBD2 as a diagnostic tool for mechanics, it would be surprising if the gateway didn’t relay the real-time status of the virtual instrument panel to any device connected via the OBD2 port. This access to diagnostic data is key to my project.
To delve deeper into understanding the OBD2 system in the Civic 11, exploring resources that document Obd2 11 implementations is crucial. These resources can offer insights into how manufacturers typically expose diagnostic information and which parameters are generally accessible through the OBD2 port. While direct manipulation of critical vehicle controls might be restricted, the diagnostic data stream should provide valuable information for monitoring and interpreting vehicle behavior.
Furthermore, investigating existing databases or community efforts focused on decoding CAN bus data for Honda vehicles, even if not specifically for the Civic 11, could provide a foundational understanding. The principles of CAN bus communication and diagnostic reporting are often consistent across models and manufacturers. Understanding the structure and common Parameter IDs (PIDs) used in Honda vehicles can significantly accelerate the reverse engineering process for the obd2 11 system.
The journey to decode obd2 11 and access the valuable data within modern vehicles is a complex but rewarding endeavor. By leveraging tools like Macchina A0 and SavvyCAN, combined with a systematic approach to reverse engineering, gaining insights into vehicle systems and potentially enhancing driver awareness becomes achievable. The diagnostic capabilities of the OBD2 port, even with its limitations, hold significant potential for those willing to explore its depths.
