PSA SuperScan Peugeot and Citroën Diagnostic Suite 10.2.13

PSA SuperScan is a Windows diagnostic suite for Peugeot and Citroën vehicles. It combines vehicle-wide fault discovery, controller identification, live measurements and supported service or configuration procedures through compatible communication hardware.

The illustrated BSI session exposes electrical-supply, ignition, alternator-excitation, energy-management and starting-status parameters. Coverage depends on the exact vehicle profile, ECU protocol and installed application data, so diagnosis should begin with identification and a complete scan.

PSA SuperScan BSI quick test and live electrical measurements.

What This Package Is For

Use the suite to determine which controllers respond, record fault codes, inspect measured values under known conditions and follow the service functions supported for the identified ECU. Compare the scan and symptoms with wiring diagrams and manufacturer service data before selecting a configuration or repair action.

Main Functions

• Perform a vehicle-wide quick test to discover responding modules.
• Read diagnostic trouble codes, preserve the initial state and clear codes when appropriate after diagnosis or repair.
• Display supported live parameters and status flags.
• Open diagnostic menus specific to the selected model and system.
• Organize vehicle or customer records for a workshop session.
• Access available configuration and service procedures.
• Inspect supply-voltage, ignition and energy-management values during diagnosis.

Supported Vehicles, Systems and Control Units

• Peugeot and Citroën passenger-vehicle profiles present in the installed database.
• Body Systems Interface (BSI) and related body-electronics functions where listed.
• Engine and transmission controllers where supported by the selected profile.
• ABS / ESP, airbag, instrument, climate and comfort systems where exposed by that profile.
• The supplied diagnostic example shows BSI DS3/C3 and CITROEN C3 PICASSO context.

Confirm coverage for the exact model year, vehicle identity and ECU software inside the application. Similarly named PSA modules can offer different parameters or coding paths. Renault compatibility is not established by the available information.

BSI Quick Test and Live Electrical Values

The displayed session is labeled Diagnosis: Peugeot - BSI DS3/C3 with Vehicle: QUICK_TEST and Model: CITROEN C3 PICASSO. The live-data table includes:

• Battery voltage.
• Protected battery voltage.
• Alternator excitation voltage.
• Request to produce electrical energy.
• Request for regulation of the generation of electrical energy.
• Emergency mode of the vehicle's electrical system.
• Ignition controlled +ve (ignition positive).
• Positive ignition-on information sent to the Engine Relay Unit.
• Engine start request.
• Output check with the engine running, including heated-seats authorisation.
• Status of the power train.
• Main status of the electrical system.

The example shows battery voltage 11.9 Volt(s), also repeated in Item Information and the minimum / maximum cells. This is the captured example value, not a recommended voltage for a live service procedure. The other displayed value cells are unfilled.

Package Contents

• A SuperScan Manager installer identified in the package notes as a DEC Automotive application.
• The main diagnostic and live-data screenshot.
• An additional screenshot of the application menu.
• No customer records, saved vehicle scans or proprietary ECU files.

The documented software version is 10.2.13. The main-menu screenshot separately displays firmware 3.1.0 and Offline Mode; those labels do not change the application version.

PC, Interface and Workshop Requirements

• A dedicated Windows workshop computer with local administrator rights for installation and drivers.
• Suitable stable battery support for the vehicle during a diagnostic session.
• The correct communication interface, cable and driver for the target system.
• A PSA-compatible interface supported by this software release.
• Correct USB or serial drivers and, where possible, a stable connection outside virtualization.
• Confirmed controller identification and a complete diagnostic scan before work begins.
• Storage for the extracted package, logs and untouched backups.

Exact Windows versions, architecture, runtime dependencies and specific interface models are not documented here.

Recommended Workflow

1. Record the exact vehicle, model year, ECU identity, software number and symptoms.
2. Install or extract the package offline and verify the required interface driver.
3. Connect suitable stable power, identify the vehicle and run a complete scan before any function that can write data.
4. Save the original report or memory file and create a separate working copy.
5. Use only the procedure documented for the recognized vehicle and controller.
6. Cycle power only when instructed by the service procedure, then rescan and verify the repair.

Important Limitations

• A brand or menu entry does not establish compatibility with every model year, market or controller revision.
• The package supplements current OEM service information, wiring diagrams and the necessary security authorization.
• Do not perform configuration, key, immobilizer or programming work on an unidentified module.
• Never use the only original EEPROM, flash, configuration or diagnostic capture as a working file.
• Configuration changes can affect multiple vehicle systems immediately; record the complete original settings first.

Troubleshooting Checklist

• No connection: inspect ignition state, battery voltage, interface driver, protocol selection and connector pins.
• Module missing: confirm model year, platform, controller family and software coverage before proceeding.
• Implausible readings: compare units and test conditions with an approved diagnostic platform.
• Write or configuration refused: stop, preserve the logs and check authorization, diagnostic-session state and power support.
• Application does not start: use a clean, supported Windows environment with only the documented prerequisites.

Safety and Data Handling

Work from a verified backup, keep the original read unchanged and document the vehicle, controller label, interface and power conditions before changing anything. Remove VINs, security credentials, customer records, diagnostic seeds and responses, and proprietary module files before sharing support information publicly.

The package-preparation notes describe static executable inspection without launching the software. No independent ECUDB execution or vehicle-session test is claimed.

Additional Interface Preview

The SuperScan Manager menu shows Diagnosis, MechNet Forum, Customer, Configure and Exit. Its status panel reports software 10.2.13, firmware 3.1.0 and Offline Mode.

SuperScan Manager main menu and offline application status.