Siemens OP7-DP Program Upload via Serial Cable: Pinout & Transfer

David Krause12 min read
HMI / SCADASiemensTechnical Reference
Licensed PE Working through this on a live machine? A Maine-licensed engineer can take it from here — included with IMD hardware, by the hour for everything else. Book an engineer

Siemens OP7-DP Program Upload via Serial Cable: Pinout, Transfer Mode, and Compatibility Reference

The Siemens SIMATIC OP7-DP operator panel, identified by MLFB (order number) 6AV3607-1JC20-0AX1, is a text-and-graphic HMI from the OP7 family that integrates a Profibus-DP interface for direct connection to SIMATIC S7 PLCs. Although the device was cancelled from the Siemens catalog effective 1 October 2007, it remains in service across legacy machine fleets worldwide. This reference consolidates the field-proven procedure for uploading the panel configuration, the serial cable pinout required to perform that upload, the keypress sequence that forces the panel into transfer mode, and the strict compatibility constraints that govern what can and cannot be recovered from the device.

Read first: An OP7 upload does not yield editable source code. The transfer extracts a compiled, runtime-only image that can be re-flashed only to a panel of the identical part number. Plan your recovery and archival workflow accordingly.

1. Product Identification and Lifecycle Status

The MLFB 6AV3607-1JC20-0AX1 decodes as follows:

Segment Value Meaning
6AV3 Siemens HMI / SIMATIC HMI prefix Operator panel family
607 OP7 series Compact text/graphic OP, 4-line LCD
1JC20 Variant code DP (Profibus-DP slave) variant, 24 V DC supply
0AX1 Hardware/firmware release Final catalog release before cancellation

Lifecycle facts every maintainer should record on the panel's asset tag:

  • Cancellation date: 2007-10-01. Siemens no longer manufactures new units.
  • Spare-parts availability: Subject to stock exhaustion; refurbished and pull-out units dominate the secondary market.
  • Successor products: SIMATIC OP 77B (6AV6641-0AA11-0AX0), SIMATIC KTP400 Basic (6AV2123-2DB03-0AX0), and later Comfort/Advanced lines. These are not drop-in replacements because the OP7's runtime image is not portable to KTP/Comfort firmware.
  • Configuration software: The OP7 is programmed exclusively with ProTool / ProTool Lite (V6.0 or earlier for the OP7 device family). ProTool was superseded by WinCC flexible (2004) and later TIA Portal. None of those newer tools can open OP7 source projects.

2. Communication Interfaces on the OP7-DP

The OP7-DP exposes two physically distinct communication ports:

Port Connector Protocol / Use
IF1A 9-pin sub-D male RS-232 point-to-point to a programming PC (ProTool / ProSave). Used for configuration transfer.
IF1B 9-pin sub-D female Profibus-DP slave, electrically isolated, up to 12 Mbit/s. Used at runtime to communicate with the S7 PLC.

The Profibus port cannot be used for configuration transfer. Configuration transfer always travels over the RS-232 configuration port (IF1A). This is a frequent source of confusion when engineers assume "DP" means "everything Profibus", or that an MPI/PPI multi-master cable will work.

3. Why a PPI Cable Will Not Work

The Siemens PPI (Point-to-Point Interface) protocol is a multi-drop, 11-bit RS-485 variant used exclusively between a SIMATIC S7-200 CPU and its programming software (STEP 7 Micro/WIN). The PPI cable integrates an RS-485 transceiver and the PPI firmware handshake inside the cable itself.

The OP7-DP configuration port is:

  • Electrical: RS-232 (single-ended, ±12 V levels), not RS-485.
  • Protocol: Siemens proprietary serial loader protocol handled by the OP7 bootloader, not PPI.
  • Handshake: Hardware handshaking using RTS/CTS and DTR/DSR, which a passive PPI cable does not provide.

Connecting a PPI cable to the OP7 configuration port will not damage the panel, but ProTool / ProSave will time out without establishing a session. Use a null-modem RS-232 serial cable as detailed in the next section.

4. Required Cable Hardware

Component Specification
Cable type RS-232 null-modem (crossover) serial cable with full handshaking
Length Maximum 15 m per EIA-232 / V.24 specification; 3 m recommended for reliable loader transfer
OP7 connector 9-pin sub-D female, panel side, wired to OP7 IF1A port
PC connector 9-pin sub-D female (or male, depending on PC chassis) — verify the chassis before building
Shielding Overall foil + braid shield; shield bonded to metal shell at one end only to avoid ground loops
Equivalent catalog cable Siemens 6ES7 901-1BF00-0XA0 family (RS-232 null-modem). Third-party USB-to-serial adapters (FTDI FT232, ATEN UC-232A) may be used on modern PCs provided the driver enumerates as a standard COMx port.
USB-to-serial caveat: Many low-cost adapters omit the RTS/CTS handshake lines or buffer them through the UART. Use an industrial-grade adapter with full modem-signal pass-through. Set ProTool's transfer parameters to 38400 bit/s, 8 data bits, even parity, 1 stop bit when troubleshooting.

5. Serial Cable Pinout (PC ↔ OP7 IF1A)

The wiring below implements a complete null-modem configuration with hardware handshaking crossed on both pairs. This is the recommended pinout for reliable ProTool / ProSave loader sessions on the OP7-DP.

Signal PC DB-9 Pin Direction OP7 DB-9 Pin (IF1A) Notes
RXD 2 3 Data from OP7 to PC
TXD 3 2 Data from PC to OP7
GND 5 5 Signal ground, mandatory
DTR 4 6 Tied to DSR to assert "ready"
DSR 6 4 Loop to DTR
RTS 7 8 Loop to CTS for hardware flow control
CTS 8 7 Loop to RTS
CD (DCD) 1 1 Optional: tie to DTR/DSR pair if the OP7 loader monitors it
RI 9 9 Not connected
PC DB-9 (DTE) OP7 IF1A DB-9 (DTE) 2 RXD  ←  3 TXD 3 TXD  →  2 RXD 5 GND  —  5 GND 4 DTR  →  6 DSR 6 DSR  ←  4 DTR (loop) 7 RTS  →  8 CTS 8 CTS  ←  7 RTS (loop) 1 DCD optional loop 9 RI not connected

Figure 1 — Null-modem cable wiring between PC COM port and OP7 IF1A configuration port.

6. Entering Transfer Mode

The OP7 boots into either normal runtime (if a valid image exists) or transfer mode (if forced by the operator). To force transfer mode for an upload:

  1. Power down the panel completely.
  2. Locate the two physical keys on the OP7 membrane keypad: ESC (top-left cluster) and the up-arrow (Button up) on the cursor / navigation block.
  3. Press and hold both keys simultaneously.
  4. While holding the keys, apply 24 V DC to the panel's power terminals.
  5. Continue holding for approximately 3 to 5 seconds after the display becomes active.
  6. The LCD displays the message "Ready for transfer". Release the keys.

If the panel instead boots to the normal process screen, the keypress was mistimed. Power down, repeat the procedure, and ensure both keys are mechanically engaged before the backlight comes on.

Alternate trigger (corrupt image): If the existing runtime image is corrupted, the OP7 may enter transfer mode automatically on power-up without any keypress. In that case the same "Ready for transfer" prompt appears, and the upload procedure below proceeds identically.

7. ProTool / ProSave Configuration Workflow

Two software paths reach the OP7 configuration port:

Tool Source Typical Use
ProTool / ProTool Lite V6.0 + SP3 Siemens legacy DVD or the ProTool V6.0 service pack Editing and full project compilation; required for upload of projects back to a development PC
ProSave Bundled with ProTool, also available as a standalone utility Backup and restore of the compiled runtime image to/from the OP7

Recommended transfer parameters in ProTool under File → Transfer → Settings:

Interface:          Serial (IF1A)
COM port:           COM1 (or the COMx number assigned to the USB-serial adapter)
Baud rate:          38400 bit/s
Data bits:          8
Parity:             Even
Stop bits:          1
Handshake:          RTS/CTS (hardware)
Timeout:            60 s

8. Upload Procedure (Step-by-Step)

  1. Build or verify the null-modem serial cable per Section 5.
  2. Connect the cable between the PC's COM port and the OP7 IF1A connector.
  3. Launch ProTool / ProTool Lite V6.0 SP3.
  4. Choose File → Transfer → Upload from device.
  5. ProTool prompts for a target folder; choose a directory with full NTFS write permission. The image is typically 512 KB to 1 MB depending on the project size.
  6. Force the OP7 into transfer mode using the Section 6 keypress procedure.
  7. ProTool displays "Establishing connection"; this can take up to 30 s on the first attempt.
  8. When the upload completes, ProTool logs the file as .pwl (ProTool configuration) or a binary .img-equivalent runtime file depending on the OP7 firmware variant.
  9. Power-cycle the OP7 to return to runtime, or leave the panel in transfer mode for a subsequent restore operation.

9. Image-File Compatibility Constraints

This is the most misunderstood aspect of the OP7 upload workflow and must be communicated to anyone commissioning the spare panel:

  • What is uploaded: A compiled, tokenized runtime image. Variables, screens, alarm logs, and recipes are preserved. Source code, screen layout, and tag names are not readable or editable.
  • What is not uploaded: The original .pwl source project. There is no "decompile" path on OP7 firmware.
  • Restore target: The image can only be downloaded back to a panel carrying the identical MLFB. In practice this means 6AV3607-1JC20-0AX1 to 6AV3607-1JC20-0AX1. Cross-flashing to a different OP7 variant (e.g. 6AV3607-1JC30-0AX1) is rejected by the bootloader.
  • Checksum: The OP7 bootloader verifies a CRC over the image. Any modification, truncation, or sector error during transfer will abort the upload with a "Transfer error" message and the panel remains in transfer mode awaiting a retry.
Engineering implication: Always archive the upload with a paper record of the source machine, the PLC tag list, and the Profibus node address of the OP7. Without the original ProTool source, you cannot edit text, alarms, or screen layouts — you can only re-flash the same image byte-for-byte.

10. Troubleshooting Matrix

Symptom Likely Root Cause Corrective Action
ProTool "No connection to device" Cable wired straight-through instead of null-modem, or wrong COM port selected Verify pinout per Section 5; confirm COM number in Windows Device Manager
Connection drops after 3–5 s Hardware handshaking absent (3-wire cable) Use full null-modem wiring with RTS/CTS and DTR/DSR loops
Panel never shows "Ready for transfer" Keypress timing wrong, or panel boots to runtime Hold ESC + Button up before applying 24 V DC; hold for at least 5 s after power-up
Upload completes but file is 0 KB Insufficient NTFS permission, or transfer aborted on parity error Move target folder off a read-only share; lower baud to 19200 and retry
Download to spare panel rejected with "Wrong firmware version" Spare panel has a different hardware/firmware release Replace with a panel of identical MLFB, including the trailing 0AX1 suffix
Garbled characters during transfer Parity mismatch, EMI, or baud rate too high for cable length Set parity to Even; reduce baud to 19200; shorten cable below 3 m
USB-serial adapter not enumerated Driver not installed, or adapter requires vendor-specific INF Install FTDI / CH340 / Prolific driver per adapter chip; reboot
Panel stuck in transfer mode after upload Expected behavior; OP7 awaits next command Power-cycle, or issue "Start runtime" command from ProTool

11. Verification Procedure

After a successful upload, validate the image before archiving or restoring:

  1. Open the saved image in ProTool under File → Open → Restore device backup. ProTool reports the panel's MLFB and firmware revision; verify both match the source machine's asset record.
  2. Compare the file size to a known-good reference (typically 384 KB to 1 MB for OP7 projects). A file truncated below this range indicates a partial transfer.
  3. Compute a CRC32 over the saved file and log it on the asset record. This CRC must match the CRC computed on a subsequent re-upload of the same panel.
  4. If the spare panel is on hand, perform a restore followed by a manual power-cycle and verify that all configured screens and alarms appear as expected.
  5. Reconnect the panel to its target S7 PLC over Profibus and verify that the configured tag polling starts; absence of tag updates indicates the image was corrupted in transfer.

12. Field-Proven Caveats and Best Practices

  • Document before you disconnect. Photograph the OP7's Profibus node address, the configured baud rate (visible in the panel's diagnostics menu), and the DP master GSD file version. The uploaded image contains none of this metadata in human-readable form.
  • Power supply stability matters. Brown-outs during the upload can corrupt the image and require a re-upload. Power the OP7 from a clean 24 V supply or a UPS during the procedure.
  • Prefer ProTool over ProSave when you need to inspect alarms. ProSave is faster for a binary backup, but ProTool presents the tag database and alarm class configuration, which is invaluable when reverse-engineering a legacy project.
  • Lock the spare panel's part number. Many OP7 spare panels in stockrooms have been "upgraded" to OP17 or OP27 variants over the years. Always read the MLFB label and confirm 6AV3607-1JC20-0AX1 before attempting a restore.
  • Avoid serial ports on docking stations. Internal COM ports on industrial PCs are preferred over USB-serial bridges for production transfers; if a bridge must be used, isolate it electrically and keep cable length under 2 m.

13. Frequently Asked Questions

Is the Siemens OP7-DP (6AV3607-1JC20-0AX1) still available for purchase new?

No. Siemens cancelled the OP7 family effective 1 October 2007. New units are no longer manufactured. Refurbished and used pulls remain available through secondary-market suppliers, but lead times and warranty coverage vary.

Can I upload an OP7 program using a Siemens PPI cable?

No. The PPI cable uses RS-485 levels and the PPI multi-drop protocol designed for the SIMATIC S7-200. The OP7 configuration port is RS-232 with a Siemens-proprietary loader protocol. Use a null-modem RS-232 serial cable wired per Section 5 of this reference.

What is the correct keypress to put the OP7 into transfer mode?

Power the panel down, then press and hold ESC and the up-arrow (Button up) simultaneously while you re-apply 24 V DC. Hold both keys for at least 5 seconds after the display activates. The LCD will read "Ready for transfer" once the panel is in loader mode.

What file format is produced when I upload an OP7 program?

ProTool and ProSave store the upload as a compiled runtime image, typically with a .pwl extension for ProTool-configured backups or a binary image file for raw runtime captures. The image contains tokens for screens, tags, alarms, and recipes but does not contain editable source code.

Can I download the uploaded image to a different OP7 part number?

No. The OP7 bootloader verifies that the target panel's MLFB matches the image's source MLFB exactly. A backup of a 6AV3607-1JC20-0AX1 can only be restored to another 6AV3607-1JC20-0AX1, including the trailing firmware suffix. Cross-flashing to a different OP7 variant is rejected with a firmware-mismatch error.

Which software do I need to open and edit the uploaded image?

ProTool / ProTool Lite V6.0 SP3 is the only tool that recognizes OP7 runtime images. WinCC flexible, TIA Portal, and other newer Siemens HMI tools cannot open OP7 backups. If the original ProTool source project is unavailable, only the compiled image can be transferred; you will not be able to modify screen text or tag names.

What transfer parameters should I use for reliable OP7 uploads?

Configure ProTool for COMx, 38400 bit/s, 8 data bits, even parity, 1 stop bit, with hardware RTS/CTS handshake. If the transfer is unstable, drop to 19200 bit/s and shorten the serial cable to under 3 m.

Back to blog