Project Description: I’m new to this and don’t know anything about programming.
Hello,
I am looking for an automotive embedded systems engineer or an experienced vehicle network reverse-engineer to create a custom RealDash XML channel description file for my 2007 Chrysler Pacifica.
I am using RealDash on iOS paired with an OBLink
MX+ adapter.
The Problem:
Standard OBD2 protocol does not natively transmit most interior body electronics or advanced status lights. I need a custom XML file that bypasses standard OBD2 PID limitations to pull proprietary data directly from the vehicle networks. I need the XML file to map the following specific parameters to RealDash:
- Turn Signals (Lett and Right individual indicators)
- PRNDL Gear Positions (True physical shifter position from the BCM/TCM rather than driving calculation formulas)
- Headlights & Fog Lights (High beams, low beams, and fog light active statuses)
- Gauges & Telemetry (Odometer, fuel level, and trip mileage)
- Warning Lights / Indicators (Check Engine light status, Battery/Charging light, and ESP/Traction Control warning light status) Vehicle Technical Context:
The 2007 Chrysler Pacifica sits on a transitional platform. While it utilizes standard CAN-bus routing for major powertrain components, many of its interior electronics, body controllers (BCM), and cluster components communicate via Chrysler’s legacy PCI bus (single-wire J1850) or early CAN-B interior network. What I Need From You:
- Locate or Extract Chrysler PIDs/Hex Codes:
Utilize existing Chrysler database files (DBC), reverse-engineered community libraries, or help me sniff the data stream. - Build the RealDash XML File: Format these proprietary codes into a valid, structured
- RealDash OBD2 XML file mapping to the correct target IDs (matching ReaDash standard telemetry targets).