Decoding Your Peugeot: A Deep Dive into Car Scanner Diagnostics

Venturing into the realm of vehicle diagnostics, especially with modern electric vehicles, presents unique challenges and exciting opportunities. My journey with the new Peugeot e-208 and integrating an Open Vehicle Monitoring System (OVMS) module has been exactly that. The e-208, built on a cutting-edge platform shared by both electric and combustion engine models, hints at a potentially intricate OBD system, typical of electric vehicles. After initiating the OVMS setup on my Peugeot e-208, initial signs pointed towards functionality, which was encouraging for deeper exploration with a Car Scanner Peugeot.

Delving into the wiring intricacies, I documented my findings directly from the OBD socket. Located conveniently on the driver’s side, behind a protective cover beneath the steering wheel, the OBD port in the Peugeot e-208 revealed a specific pin configuration. Notably, only pins 1, 3, 4, 5, 6, 8, 14, and 16 were active. The standard CAN bus, essential for generic car scanner peugeot operations, is wired to pins 6 (CAN high) and 14 (CAN low). Intriguingly, Peugeot employs a dedicated diagnostic CAN bus on pins 3 (CAN high) and 8 (CAN low), suggesting a more manufacturer-specific diagnostic approach might be necessary when using a car scanner peugeot for in-depth analysis.

Pin Details:
pin 1: + 12v after power
pin 3: CAN high Peugeot diagnostic bus
pin 4: Body ground
pin 5: Electro ground
pin 6: CAN high standard/regulatory bus
pin 8: CAN low Peugeot diagnostic bus
pin 14: CAN low standard/regulatory bus
pin 16: + 12v OBD power

On the OVMS module side, configuration is needed to align with Peugeot’s CAN bus setup. The OVMS module designates Can1 as the regulatory/standard CAN bus, which corresponds to the standard OBD pins. Crucially, Can2 on the OVMS needs to be remapped to pins 3 and 8 of the OBD socket to access Peugeot’s diagnostic CAN bus. This remapping involves connecting OBD pins 3 and 8 to connectors 13 and 12 respectively on the OVMS module, ensuring proper communication with the car scanner peugeot interface.

Following general guidelines for integrating new vehicle support into OVMS, the initial steps of physical connection seemed successful. However, subsequent stages presented more complexity. While connection to both CAN buses appears stable, evidenced by a high volume of data from Can 1, deciphering this data proved challenging. Utilizing Savvycan to capture CAN bus traffic revealed data fluctuations correlating with vehicle actions like door operation and power state changes. Despite this activity, extracting meaningful information for car scanner peugeot functionality remained elusive. OVMS, in its current configuration, doesn’t seem to recognize standard OBD Parameter IDs (PIDs), resulting in a lack of feedback on crucial metrics like State of Charge (SoC) or Vehicle Identification Number (VIN) on the dashboard. The novelty of the Peugeot e-208 platform means readily available documentation or forum resources are scarce, compounding the difficulty in leveraging a car scanner peugeot effectively for advanced diagnostics.

This experience leads to several key questions as I continue to explore car scanner peugeot capabilities with the e-208:

• Data Interpretation with Savvycan: How can the raw data captured in Savvycan be effectively translated into understandable parameters and values? Identifying real-world values within the data stream is crucial for deducing the corresponding vehicle functions and maximizing the car scanner peugeot utility.
• Peugeot Diagnostic CAN Bus Interaction: Assuming that the diagnostic CAN bus (Can2) operates on a request-response basis with the OVMS, what specific tests or requests can be initiated to validate communication and elicit responses from this bus? Understanding the communication protocol is vital for targeted car scanner peugeot diagnostics.
• OVMS Vehicle Type Configuration: For these investigative tests, is “OBDII” the most appropriate “vehicle type” setting within OVMS? Could a more specific setting be required to properly interface with the Peugeot e-208’s systems and unlock the full potential of a car scanner peugeot in this context?

To provide context and facilitate collaborative troubleshooting, a Savvycan data capture from vehicle startup is available here. Any insights or guidance from the community on interpreting this data or suggesting further diagnostic steps would be greatly appreciated as I continue to explore the car scanner peugeot interface with the Peugeot e-208.