KT200II Peugeot EDC17C60 Bench Error: Why the Ignition Prompt Repeats
The KT200II asks you to switch ignition off and on, waits, and then returns to the beginning instead of identifying the ECU. Repeating the same command can feel like progress, but it does not tell you whether the ECU, cable, driver or switched input is responsible.
Direct answer: in a reported Peugeot Partner EDC17C60 bench case, ECUHELP identified poor or incorrect pin contact as the likely reason the ignition-cycle prompt kept returning. The documented setup used the multifunction cable and the Bench Tricore driver for Peugeot/Citroën TC1793 EDC17C60. Treat that report as a troubleshooting clue, not a universal diagnosis. Power down, verify the exact ECU and current driver, inspect every contact against the licensed software diagram, confirm the power and host paths, and make one controlled retry. Do not improvise pins or continue to a write until identification and a valid original read succeed.
The source case in context
The supplier's EDC17C60 ignition-prompt case note describes a 2017 Peugeot Partner fitted with a Bosch EDC17C60. The user could not read it on the bench: the software requested an ignition cycle and then returned to the start screen.
The case note associates the ECU with a TC1793 processor context, identifies the multifunction cable and points to the Bench Tricore Peugeot/Citroën EDC17C60 driver. Its proposed cause is incorrect or poor contact. The page does not publish a measured voltage log, cable continuity report or independent reproduction. That limits the conclusion to this: contact is the first item to inspect when the expected switched transition is not seen.
| Field | Reported case | What your workshop must verify |
|---|---|---|
| Vehicle | Peugeot Partner, 2017 | Actual vehicle, market, engine and ECU label. |
| ECU | Bosch EDC17C60 | Full hardware and software identification; do not rely on casing shape. |
| Processor context | TC1793 | Current KT200II driver information for the exact unit. |
| Mode | Bench Tricore | Whether bench is supported for the identified revision. |
| Accessory | KT200II multifunction cable | Cable condition, continuity and the diagram supplied by current licensed software. |
| Reported symptom | Ignition-cycle prompt returns to start | Exact message, stage, software version and behavior on one controlled retry. |
For the fundamentals of service-mode connection, review the KT200II Bench Mode guide before troubleshooting a model-specific failure.
What does the repeating prompt actually mean?
In bench mode, “ignition” usually represents a controlled electrical input in the bench setup rather than a physical key barrel. The driver expects to observe a defined state change. If that transition never reaches the ECU or programmer, the software can ask again or abandon the identification sequence.
The message is therefore a symptom, not a component diagnosis. A weak contact may prevent the switched line from changing. A wrong driver may expect a different sequence. A damaged harness may carry main power but not the control signal. Unstable power or an unreliable host connection can interrupt the same stage. An ECU fault is possible, but it should not be the first assumption when the setup has not been proven.
Four fault groups to separate
- Identity: the ECU family or hardware revision was selected from memory rather than the label and current list.
- Connection: one contact is loose, displaced, oxidized or assigned from a diagram for another revision.
- Power state: the main and switched paths do not remain stable through the requested transition.
- Communication: the PC, USB lead, interface or software session drops before the ECU responds.
Change one group at a time. If you reseat the harness, replace USB and switch drivers simultaneously, a successful retry will not reveal what fixed the fault.
Start with identity, not wire color
- Photograph the ECU label. Capture every readable hardware and software reference, the connector face and the untouched casing.
- Open the current support data. Locate the exact Peugeot/Citroën EDC17C60 entry in the installed KT200II software. The seller's case used Bench Tricore and a TC1793 PSA entry, but the current menu remains the authority for your licensed version.
- Confirm the mode and accessory. Verify that the driver calls for bench mode and the multifunction cable. A similar connector does not prove a compatible harness.
- Save the software context. Record KT200II edition, version, driver path and interface serial number before changing the setup.
The KT200II workstation and troubleshooting guide can help establish whether the PC and tool were stable before the ECU was introduced.
Inspect the connection with all power removed
Disconnect the bench supply and USB connection before touching the harness. Check that the ECU connector shell is intact and that the cable-side terminals have not backed out. Look for contamination, bent retainers, poor strain relief and a lead that is pulled tight enough to lift a contact.
Compare every connection with the diagram displayed by the exact current driver. This article intentionally does not reproduce pin numbers or wire colors: EDC17C60 hardware and cable revisions can differ, and a generic diagram is unsafe. If the software image is unclear, stop and request the revision-specific document from support.
Use suitable continuity testing only while the harness is disconnected from the ECU and power source. Do not probe powered ECU contacts or bridge adjacent terminals. If the lead fails continuity or changes when gently moved, replace or repair the approved harness before another ECU attempt.
Rebuild the test in a fixed order
- Place the ECU on an ESD-safe, non-conductive surface and secure the harness so it cannot pull sideways.
- Connect the approved harness to the programmer according to the current driver instructions.
- Attach the documented power source and confirm that it is suitable for this exact operation; do not copy a voltage from an unrelated forum case.
- Use a direct, known-good USB connection to the workstation and prevent sleep or automatic restart.
- Open the verified EDC17C60 driver and start with identification or read, not write.
- Follow the software's ignition-cycle prompt once, observing power and communication behavior without moving the connector.
If the sequence again returns to the start, save the message and stop. Repeated cycles with no new evidence can heat components, disturb a marginal contact and make support diagnosis harder.
How to interpret the next result
| Result | Most useful next check | Unsafe shortcut to avoid |
|---|---|---|
| No tool detection | PC, USB, driver installation and KT200II interface. | Changing ECU pins. |
| Tool detected, ECU not identified | Exact driver, harness contact and power path. | Attempting a blind write. |
| Identification succeeds, read fails | Driver notes, stable power, memory operation and file path. | Assuming the earlier contact issue is fully solved. |
| Original read completes | Validate identification, file size and backup copies. | Editing before preserving the original. |
A complete original read is the next evidence threshold. Save it in two locations, record the checksum behavior reported by the tool and keep the unmodified file separate from any working copy. Do not promise that a successful identification guarantees writing or recovery.
When should you contact support?
Escalate after one controlled retry if the exact driver and connection have been checked. Send the ECU label, case and connector photos, KT200II edition and version, driver path, cable overview, power-source model, exact message and the point at which the process returns to the beginning. Do not send customer credentials or unredacted personal information.
The KT200II product page provides the current product configuration context, but compatibility for this job still depends on the exact ECU entry and accessories.
Frequently asked questions
Does the ignition prompt prove the EDC17C60 is damaged?
No. The reported case points first to poor or incorrect contact. Driver choice, harness continuity, power stability and host communication can produce a similar failure stage.
Which driver was used in the reported case?
The seller identifies the Bench Tricore Peugeot/Citroën TC1793 EDC17C60 path. Verify the current path inside your own licensed software before connecting.
Can I follow a pinout from another EDC17C60?
Do not assume so. Confirm the exact ECU hardware and the diagram supplied for the current driver and cable. Similar family names do not guarantee identical connections.
Should I keep cycling ignition until it works?
No. Perform one controlled retry after correcting a verified issue. If the prompt repeats, capture the evidence and stop rather than cycling without a new diagnosis.
What should I do after identification succeeds?
Perform the supported original read, verify the ECU identification and file result, and preserve multiple unmodified backups before considering any authorized modification or write.
Is this procedure suitable for every Peugeot or Citroën diesel ECU?
No. It addresses a reported Bosch EDC17C60 bench symptom. Other ECU families, processors and vehicles require their own current driver and connection instructions.
Fix the missing transition, not the message
The repeating prompt is useful only when it changes the troubleshooting plan. Confirm the ECU and driver, inspect the disconnected harness, prove the power and host paths, and retry once without moving the setup.
If you need a compatibility check, send ECUToolStore clear ECU label and connector photos, the KT200II version, selected driver and requested operation. That is enough to begin a responsible review without guessing at pin assignments.