Troubleshooting Siemens OP35 'Line Error 0' Program Load Failures

1. Problem Overview

The Siemens SIMATIC OP35 is a compact text/graphics operator panel from the early-generation SIMATIC HMI family, programmed with ProTool (versions up to 6.0 SP3) and managed with ProSave. On a field-recovered unit that has been sitting unused, has an interrupted firmware flash, or has corrupt flash sectors, the following symptoms appear during commissioning or re-deployment:

• Boot-time diagnostic line: Check Unexpcted Interrupts............................FAILED (note the spelling used by the OP35 BIOS).
• Transfer dialog from ProTool / ProSave returns: Line error 0, Init transfer 0, immediately when the transfer is initiated.
• The panel does not appear in the ProSave device list, preventing backup/restore operations.
• Firmware version is reported as 1.03 (early OP35 firmware revision).

Because the OP35 reached end-of-life in 1998, Siemens Industry Online Support will not issue RMA or firmware under standard entitlement, and the device is no longer listed in the ProSave device catalog of current ProTool/ProSave releases. The recovery procedures below work on the legacy device without manufacturer intervention.

2. Affected Hardware and Software Stack

3. Interpreting the Error Messages

3.1 "Line error 0, Init transfer 0,"

This message originates from the OP35 transfer subsystem during the initial handshake with ProTool. The two zeroed fields are significant:

• Line error 0 — no physical line/protocol violation was captured before the transfer aborted. This rules out cable, baud-rate, and MPI-address mismatch as primary causes.
• Init transfer 0 — the OP35 transfer-statemachine did not advance from the INIT state. This typically means the runtime image currently resident in flash is either corrupt, incomplete, or incompatible with the version of ProTool issuing the download.

When the flash-resident image cannot initialize the loader stub, the panel will refuse any inbound transfer and ProTool cannot take control of the device. The absence of a non-zero line error confirms the problem is internal to the OP35 flash partition, not the physical link.

3.2 "Check Unexpcted Interrupts...FAILED"

During power-on self-test, the OP35 BIOS executes a list of integrity checks. "Check Unexpected Interrupts" exercises the interrupt controller and verifies that no spurious IRQ vectors are pending. A FAILED result indicates a non-recoverable hardware fault or corrupted flash that the BIOS misreads as a stuck interrupt source. When combined with the transfer error, the most likely root cause is corrupted flash rather than a hardware defect — many panels recover fully after a full flash erase followed by a clean transfer.

4. Root Cause Analysis

Field reports of this combined symptom pair (transfer error 0 + Interrupt FAILED) on the OP35 trace back to one of three causes:

1. Incomplete or interrupted prior flash write. A power loss or transfer abort during a previous ProTool download leaves the flash image in a half-written state. The runtime cannot initialize, so the loader does not come up.
2. Mismatched firmware/config combination. Loading a ProTool V5.x compiled project onto a panel flashed with V6.0 SP3 firmware (or vice versa) can wedge the transfer handshake. The panel boots, but the loader cannot negotiate the INIT handshake.
3. Flash sector wear / aged panel. Early-1990s flash chips exceed their rated write-cycles after decades of compile/transfer cycles. The sector containing the loader stub returns garbage on read, producing the same symptom set.

Cause (1) and (2) are addressable with the procedures in Sections 5 and 6. Cause (3) — confirmed only when the panel still fails after a full flash erase and a clean transfer from a known-good source — requires board-level repair or retirement of the panel.

5. Recovery Procedure A — Flash Erase via Service Mode

The OP35 service-mode flash erase is invoked from the panel's built-in loader, not from ProTool. This is the same procedure Siemens documented in the original OP35 operating instructions manual (legacy order number 6AV3991-1AB05-0AB0, archived in the Siemens Industry Online Support legacy section at support.industry.siemens.com).

5.1 Prerequisites

• Functional ProTool/Pro V6.0 SP3 installation on the engineering station.
• Working PC ↔ OP35 transfer cable (MPI/PC-Adapter or null-modem serial).
• Verified project file (*.pdb / compiled *.f6b or earlier, depending on ProTool version) that matches the panel's intended configuration.
• Uninterrupted power to the panel for the full duration of the erase + transfer cycle (typically 3–6 minutes).

5.2 Erase Procedure

1. Power down the OP35.
2. Hold down the ESC and F1 keys simultaneously (on the membrane keypad) while applying power. Continue holding until the service-mode menu appears — this takes approximately 5–8 seconds.
3. The service menu displays a list of internal tests and maintenance functions. Navigate to Flash Memory → Erase.
4. Confirm the erase with F4 (or the panel's designated confirm key as shown on-screen). The erase takes 30–90 seconds; the panel displays progress as a percentage or block counter. Do not interrupt power during the erase.
5. On completion, the service menu returns. Select Reboot or power-cycle the panel.
6. The panel reboots into a clean, unconfigured state. It will display the OP35 logo and the prompt: Wait for transfer... — this is the loader stub waiting for a ProTool transfer.

6. Recovery Procedure B — PCMCIA Memory Module Transfer

The OP35 supports a PCMCIA SRAM memory module that can be programmed from a working panel and then transplanted to a faulty panel. This method is preferred when the engineering station does not have a working serial/MPI link to the broken unit, or when you want to bypass ProTool's transfer handshaking entirely.

6.1 Program the Memory Module from a Known-Good OP35

1. Insert a blank or reusable PCMCIA SRAM card into the working OP35 (card slot located behind the access cover on the rear of the panel).
2. On the working panel, enter service mode (ESC + F1 at power-up).
3. Navigate to Memory Card → Backup. Confirm. The panel writes the active project, recipes, and configuration to the SRAM card. Duration: typically 20–60 seconds.
4. When the write completes, power down the panel and remove the card.

6.2 Deploy the Memory Module to the Faulty OP35

1. Insert the SRAM card into the faulty OP35 (powered down).
2. Hold ESC + F2 while powering up to force the panel to boot from the memory card rather than the corrupt internal flash.
3. The panel initializes from the card and displays the project. It may or may not auto-commit the image back to internal flash — this depends on the firmware revision. On OP35 firmware 1.03, the panel boots from the card and runs the project directly without writing to internal flash.
4. To permanently restore the panel, perform Procedure A (flash erase) and then transfer the project from ProTool while the panel sits in Wait for transfer... state.

7. ProSave Backup/Restore Considerations

ProSave is the recommended utility for backing up and restoring OP35 projects. However, on a panel that has not completed its transfer handshake, ProSave will not see the device on the MPI/serial bus. The procedure for backing up an OP35 with ProSave is:

1. Launch ProSave on the engineering station.
2. Set the device type to OP35. If OP35 is not in the device list (typical on modern ProSave versions that have dropped legacy support), the panel cannot be addressed — use the PCMCIA backup path described in Section 6 instead.
3. Select Backup → choose the target folder → click Start.
4. ProSave reads the project directly from the panel's internal flash. The download takes 1–3 minutes over MPI at 187.5 kbps.
5. To restore, reverse the direction: Restore → point to the *.pdb or *.brf backup file → Start.

For panels that do not enumerate in ProSave, an alternative is to use the PROTOOL/Pro integrated transfer dialog: File → Transfer → Download. This uses the same transport but is more tolerant of older device firmware because it uses the V5/V6 combined protocol. On wedged panels it will still fail until the flash is erased.

8. Verification Steps

After a successful recovery, verify the panel is fully operational:

1. Boot integrity — power-cycle the panel three times in succession. The POST line "Check Unexpected Interrupts" should now display OK rather than FAILED.
2. Project display — confirm the configured start screen, language, and at least two process screens render correctly. Touch/function-key inputs must map to the configured actions.
3. Tag polling — using the ProTool online test, force a known value on a tag connected to the panel. The displayed value should update within one configured acquisition cycle (default 1 s).
4. Alarm handling — trigger a configured alarm from the PLC. The panel should display the alarm text and the configured acknowledgment behavior must work.
5. Recipe round-trip (if recipes are configured) — write a recipe dataset from the panel, power-cycle, and confirm the dataset is retained. This validates that the recipe partition in flash was rewritten cleanly.

9. Firmware and Cross-Compatibility Matrix

Mismatched firmware/project combinations will transfer cleanly (no error message) but will hang at boot or display the project with corrupt text. Always match the project compilation to the target firmware revision.

10. When the Panel Cannot Be Recovered

If both Procedure A (flash erase) and Procedure B (card transplant from a known-good donor) fail to bring the OP35 back into service, the root cause is most likely a hardware fault on the main PCB (failed flash chip, failed interrupt controller, or aged capacitors affecting the reset circuit). At that point, the practical options are:

• Retire the panel. Modern replacements in the same form factor / wiring class are the SIMATIC KTP400 Basic (6AV2 123-2DB03-0AX0) or the SIMATIC TP700 Comfort (6AV2 124-0GC01-0AX0), programmed with WinCC Comfort / TIA Portal. A migration adapter plate is generally required.
• Source a donor OP35 from the surplus market. Verify the donor's firmware version, test the POST output, and confirm the touch/function keys respond before committing to the swap.
• Board-level repair. Only viable for organizations with in-house component-level repair capability. Replace the flash IC (typically a 29F040 or 29F080 in a PLCC package) and re-burn the OP35 runtime image. The runtime image is no longer publicly distributed by Siemens; archives of the OP35 runtime (*.upd files) are sometimes available through Siemens partner channels.

11. Troubleshooting Matrix

12. Field-Commissioning Checklist

1. Confirm panel model and firmware: power up, read the version string on the POST screen.
2. Confirm ProTool V6.0 SP3 installed with matching ProSave on the engineering station.
3. Verify transfer cable continuity; confirm the PC-Adapter MPI/serial indicator LED shows link activity.
4. Run a read-back from the panel using ProSave to capture a baseline backup before any modification.
5. Document the current project hash (if versioned) so that the recovered panel can be compared to a known-good.
6. Schedule the recovery window with operations; ensure the controlled process is in a safe state.
7. Execute Procedure A or B as appropriate.
8. Run the verification steps in Section 8.
9. Update the asset register with the new firmware/project version and the date of recovery.

FAQ