Even with the correct driver, problems arise. Here are the top 5 issues and fixes.
The Actia PSA XSight (or older "Pass-Thru" VCI) is the OEM-level diagnostic interface for PSA Group vehicles. It connects your Windows laptop to the vehicle’s OBD2 port to run dealer-level software (DiagBox, Lexia, PP2000).
Unlike generic ELM327 interfaces, the Actia unit requires proper signed drivers to work with PSA software in "Vehicle Communication Interface (VCI)" mode. actia psa interface driver
Cause: The COM port number is above 4.
Fix: Reassign to COM1 or COM2 as described above. Also, ensure no other software (e.g., Bluetooth, legacy modems) is using that COM port.
The driver allows Windows to communicate with the ACTIA hardware via USB. Once installed, the interface appears as a standard D-PDU (Pass-Thru) device, enabling J2534-compatible software to send and receive diagnostic commands. Even with the correct driver, problems arise
Before diving into driver specifics, it is crucial to understand the hardware. The Actia PSA XS01 (often referred to simply as the "Full Chip" or "Rev B" interface) is a multiplexer designed specifically for PSA Group vehicles. It supports four main communication protocols:
The Actia interface requires a specific hardware driver to function because it does not use standard USB-to-serial chips (like FTDI or CH340). Instead, it uses a proprietary USB 2.0 Full-Speed controller. You cannot use generic drivers; you must install the dedicated Actia driver package. Cause: The COM port number is above 4
There are two common scenarios:
| Interface version | Typical driver | Notes | |------------------|----------------|-------| | ACTIA PSA XS (original) | ACTIA D-PDU driver | Works with DiagBox, PP2000, Lexia, and generic J2534 apps | | Clone / Chinese “ACTIA” | Often modified or older driver (e.g., version 2.18 or 2.24) | May require specific driver + firmware combo; standard D-PDU driver might not work |