Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tampsa diag dtc
• “PSA diag DTC” most often refers to reading, interpreting, and clearing Diagnostic Trouble Codes on Peugeot-Citroën-DS-Opel/Stellantis vehicles.
• At workshop level this is done with DiagBox (dealer tool) or PSA-COM; at hobbyist level an open-source solution called “arduino-psa-diag” (CAN-bus + UDS/KWP frames) is popular.
• DTCs follow the standard SAE J2012 format (P/B/C/U + 4 digits) where “0” is generic and “1” is PSA-specific; clearing a code without fixing the root cause will make the fault return.
Key points
– Choose a tool that can address all ECUs (not only powertrain) and that speaks the correct protocol (ISO 9141, KWP2000, CAN-ISO 15765, UDS-ISO 14229).
– Typical hardware for DIY: Arduino Nano + MCP2515 CAN shield + OBD-II or direct BSI connector.
– Professional tools add guided troubleshooting, tele-coding, firmware flashing, and security-seed access.
PSA diagnostic ecosystem
• Dealer level DiagBox (supersedes PP2000/Lexia-3) with PSA VCI; full ECU coverage, guided diagnostics, coding/tele-coding, firmware flashing, secure key access.
• Independent pro PSA-COM, Autel, Launch etc.; near-dealer coverage but limited programming.
• Hobbyist / open-source arduino-psa-diag (GitHub ludwig-v) or similar; sends raw UDS/KWP frames over CAN to read/clear DTCs, dump BSI configuration, perform limited actuator tests.
Communication layers
• Physical:
– ISO 9141/K-Line (pre-2004, 10.4 kbps).
– CAN-HS 500 kbps (powertrain).
– CAN-LS 125 kbps (body/comfort), sometimes VAN multiplex (AEE2004).
– New models (DoIP) add Ethernet but still accept CAN for basic diagnosis.
• Application:
– OBD-II modes 01-0A (powertrain only).
– Manufacturer application layers: KWP2000-ISO 14230, UDS-ISO 14229.
Structure of PSA DTCs
• P – Powertrain, B – Body, C – Chassis, U – Network.
• 2nd digit 0 = generic, 1 = manufacturer-specific (e.g. P1351 Glow-plug relay, very common on HDi diesels).
• Remaining digits identify subsystem and exact fault. An example decode:
P0 301 – Cylinder 1 misfire (generic)
U1 118 – PSA-specific: “Communication fault on comfort CAN with BSI”
Arduino-based workflow (open source)
Hardware
– Arduino Nano/Uno/ESP32
– MCP2515 + TJA1050 or SN65HVD230 transceiver (8 MHz crystal recommended for 500 kbps).
– OBD-II 16-pin or direct pads on BSI (CAN-H pin CAN_LS-3, CAN-L pin 8 in many PSA body networks).
– 12 V feed, IGN wake-up line, common ground.
Sketch outline (simplified)
#include <SPI.h>
#include <mcp2515.h>
MCP2515 can(10); // CS
struct can_frame tx, rx;
void setup() {
Serial.begin(115200);
can.reset(); can.setBitrate(CAN_500KBPS, MCP_8MHZ);
can.setNormalMode();
}
void loop() {
// Request Mode 03 (stored DTCs) on functional ID 0x7DF
tx.can_id = 0x7DF;
tx.can_dlc = 8;
tx.data[0] = 0x02; tx.data[1] = 0x03; tx.data[2] = 0x00;
can.sendMessage(&tx);
if (can.readMessage(&rx) == MCP2515::ERROR_OK)
parseDTC(rx);
delay(1000);
}Important implementation details
– Multi-frame UDS: implement ISO-TP (ISO 15765-2) for > 8-byte responses.
– Security access (Seed/Key) needed for certain ECUs before clearing permanent DTCs or doing actuator tests.
– Proper 120 Ω termination and clean 12 V supply to avoid bus errors.
Troubleshooting matrix
• No communication → wrong baud rate or network, missing IGN supply, bad ground, missing termination.
• Only engine ECU visible → using generic OBD-II; switch to UDS global scan or use DiagBox.
• DTC immediately returns → hard fault, component or wiring still defective.
• Stellantis MY-2020+ platforms (CMP, EMP2-v3) start migrating to DoIP (Diagnostics over IP) while keeping fall-back CAN; open-source DoIP stacks are emerging.
• OEM secure gateways (SGW) similar to FCA/Hyundai are expected, making DIY access harder; token-based authentication may be required.
• Increasing use of over-the-air updates; future DTCs may include snapshot data and cloud upload.
• Analogy: Think of the CAN bus as an automotive Ethernet and UDS frames as “HTTP requests” asking each ECU for its error log.
• Example: Clearing P1351 (Glow-plug relay) on a DW10C diesel without fixing blown glow plugs will set the code again after next pre-heat cycle.
• Modifying ECU coding or clearing safety-related DTCs (airbag, ABS) without repair can endanger occupants and violate road-worthiness laws.
• DiagBox and PSA firmware are copyright-protected; use of unlicensed clones may infringe IP rights and breach EU Block Exemption Regulation if used commercially.
• Data privacy: reading telematics ECUs may expose user location/history – handle in compliance with GDPR.
• Arduino projects lack official support; risk of ECU lock if wrong frames are injected.
• Certain ECUs (e.g., BlueHDi SCR, Airbag) enter permanent fault state after X unsuccessful attempts – dealer intervention then mandatory.
• Implement ISO-TP/UDS stack on ESP32 with Wi-Fi for wireless PSA diagnostics.
• Explore DoIP open-source libraries (e.g., open-xc-doip) for 2020+ vehicles.
• Investigate secure-gateway bypass or OEM token provisioning methods compliant with upcoming UNECE R155 (cyber-security) and R156 (software update).
PSA diag DTC work ranges from quick MIL scans to deep ECU programming. Dealer-grade DiagBox offers full functionality, while the open-source arduino-psa-diag project demonstrates low-cost access via CAN and UDS/KWP frames. Understanding protocol layers, DTC structure, and security requirements is essential. Always diagnose methodically, repair the root cause, respect safety regulations, and keep abreast of Stellantis’ shift toward DoIP and secure gateways.