TP170A RS232 Communication: Cable Wiring and Program Transfer

David Krause11 min read
HMI / SCADASiemensTutorial / How-to
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

Overview: Why the TP170A Will Not Talk to Your Laptop

The SIMATIC TP170A is a 5.7-inch operator panel from the Siemens TP170 family. Unlike its successor TP170B, the TP170A does not have an integrated Ethernet or USB configuration port. The only practical paths for moving a configuration PC ↔ TP170A in the field are the serial RS232 channel on the panel's underside and the MPI/PROFIBUS-DP port. The vast majority of "the cable does not work" incidents reported on TP170A projects come from three root causes:

  1. Using the MPI/DP cable (6ES7901-0BF00-0AA0) instead of the RS232 cable (6ES7901-1BF00-0AA0). The two part numbers differ by a single digit but are not interchangeable for project transfer.
  2. Connecting a USB-to-serial dongle in place of a true PC COM port. WinCC flexible 2005 and ProSave do not enumerate most generic USB-RS232 converters reliably on the TP170A transfer protocol.
  3. Attempting to read back the project from the panel with WinCC flexible. Only a one-way download is supported; reading/editing requires ProSave and a compressed backup file (.brf / .crc pair), not a recompilable WinCC flexible source.

This reference covers the correct cable, the pin assignment, the gender-changer caveat, the ProSave backup/restore flow, and how the same panel integrates with a SIMATIC S7-300 CPU315 over MPI.

Prerequisites

Item Specification
TP170A firmware Any factory-shipped version. Reverse-compatible with WinCC flexible 2005 SP1 / SP2 / 2007 and ProTool 6.0 SP3.
PC RS232 COM port (DE-9 male) or PCI/PCIe multi-port serial card (e.g. Moxa CP-118U, Brainboxes PX-101). Avoid USB-RS232 dongles.
Configuration software WinCC flexible 2005 SP2 (or later) for project transfer (download only).
Backup software ProSave (bundled with WinCC flexible / ProTool) for backup, restore, and OS update.
Transfer cable Siemens 6ES7901-1BF00-0AA0 (RS232, two female DE-9 ends).
Transfer cable (MPI alt.) Siemens 6ES7901-0BF00-0AA0 (MPI, two male ends) — for S7 connection, not for PC ↔ TP170A transfer.
Gender changer (if needed) Standard DE-9 male/male or female/female coupler. For the OP3/S7-300 application, a gender changer on the MPI cable is acceptable.
Critical: The PC USB-PPI / USB-MPI adapter (6ES7901-3DB30-0XA0) and the standard PC adapter USB (6GK1571-0BA00-0AA0) cannot be used for RS232 project transfer to the TP170A. They speak MPI/PROFIBUS, not the TP170A's serial transfer protocol.

Cable Selection: 6ES7901-0BF00-0AA0 vs 6ES7901-1BF00-0AA0

Siemens sells two visually similar 3 m PC-PP cables that are easy to confuse. The difference is a single character in the order number and the entire signal meaning.

Order number Type Connectors Use case
6ES7901-0BF00-0AA0 MPI / PROFIBUS Two DE-9 male S7-300/S7-400 ↔ TP170A ↔ PG (MPI). Not for PC COM port transfer.
6ES7901-1BF00-0AA0 RS232 (PtP) Two DE-9 female PC COM ↔ TP170A serial transfer. Required for WinCC flexible / ProSave.
6ES7705-0AA00-7BA0 PROFIBUS, pre-assembled with PG socket Male + PG socket Alternative to the MPI cable when the CPU end needs a PROFIBUS connector with a programming port.
Heads-up on the digit: 901-0BF00 = MPI, 901-1BF00 = RS232. The leading character after the dash (0 vs 1) is the only outward difference; a typo on a purchase requisition is the single most common reason a TP170A project transfer does not start.

RS232 Cable 6ES7901-1BF00-0AA0 Pin Assignment

The cable is a null-modem style crossover with handshaking. The TP170A is configured as DCE on its underside DE-9 female port, so the cable is the crossover variant. The factory cable ships with two female DE-9 connectors and the following internal wiring (identical on both ends):

Pin (DE-9) Signal Direction (PC → TP170A) Notes
2 RXD PC TX → TP RX Crossed
3 TXD PC RX ← TP TX Crossed
4 DTR PC DTR → TP DSR Crossed / looped
5 SGND — Common ground
6 DSR Looped to DTR on each side Local handshake loop
7 RTS PC RTS → TP CTS Crossed
8 CTS PC CTS ← TP RTS Crossed
1, 9 DCD / RI Not connected —

If you build the cable yourself, the minimum viable wiring is 2 ↔ 3, 4 ↔ 6 (each end), 5 ↔ 5, 7 ↔ 8. Pins 1 and 9 may be left open. Use shielded cable; the shield is bonded to the DE-9 metal shell on both ends. Total length should not exceed 15 m for reliable transfers, although Siemens rates the part at 3 m / 5 m / 10 m variants.

Connecting the TP170A to a PC COM Port

  1. Power the TP170A. The unit must complete its boot cycle to the configuration menu (it will display "Connect to host..." or enter transfer mode automatically on first power-up with no project).
  2. On the TP170A, enter Control Panel → Transfer and confirm that the channel is set to Serial, baud 9600, even parity, 8 data bits, 1 stop bit (these are the TP170A factory defaults; do not change them for project transfer).
  3. Plug the female DE-9 end of 6ES7901-1BF00-0AA0 into the TP170A's underside serial port.
  4. Plug the other female DE-9 into the PC's COM1 (or COM2). The PC end requires a gender changer (DE-9 male/male) if your PC cable is terminated male, OR a short male-to-female serial extension if your PC port is male. Most desktop PCs ship with a male DE-9 COM port, so a standard male-male gender changer is the most common field fix.
  5. Verify the COM port number in Windows Device Manager → Ports (COM & LPT). Note the COM number — you will need it in WinCC flexible.
USB-to-serial caveat: If the laptop has no native COM port, use a PCIe/ExpressCard multi-port serial card with a real 16550-compatible UART (e.g. Moxa CP-118U, StarTech PEX2S553). A $4 USB-RS232 dongle will enumerate as COMx but WinCC flexible 2005 / ProSave will fail at "Establish connection" with timeout. This is a known driver-stack issue, not a cable issue.

Transferring the Project with WinCC flexible 2005

  1. Open WinCC flexible 2005 SP2 (or later). Open the TP170A project (.hmi) and select Project → Transfer → Transfer (Ctrl+Shift+Alt+F5 in the classic UI).
  2. Choose Serial as the mode. The default target is the PC's COM1; change it to the COM port you noted earlier.
  3. Tick "Overwrite existing project" if you are replacing a working program. The TP170A will not refuse the new project; the old one is overwritten in place. The system files (firmware, OS image) are left untouched.
  4. Click Transfer. The progress bar should begin advancing within 3 s. A 256 KB project typically completes in 40-90 s at 9600 baud; a fully populated 1 MB project can take 6-8 min.
  5. The TP170A will restart automatically once the new project has been written and verified.
First-time transfer on a brand-new TP170A: The panel will not start WinCE on its own if no project is present. Hold the blank screen for 5 s, then connect the serial cable — the panel enters transfer mode automatically. Once a project has been downloaded once, the panel will boot the project on every subsequent power-up.

Backup and Restore with ProSave

WinCC flexible can only download to the TP170A. To make an editable archive you must use ProSave, which is installed alongside WinCC flexible (Start → Siemens Automation → SIMATIC → ProSave).

  1. Launch ProSave. From the General tab select Device type: TP170A and Connection: Serial. Set the COM port.
  2. Click Backup. ProSave creates two files on the PC: <panelname>.brf (compressed image, contains runtime, project, recipes, passwords) and <panelname>.crc (checksum). Both must be kept together.
  3. To restore, choose Restore, point at the .brf file, and click Transfer. The TP170A is restored exactly to the backed-up state, including any panel-side passwords.
  4. The .brf archive is not editable. You cannot open it in WinCC flexible, change a screen, and recompile. Restoration is intended for disaster recovery on the same TP170A model only — restoring a TP170A backup onto a TP170B or TP170micro will fail the device-type check.
Why this matters in the field: A common support case is "I lost the WinCC flexible source, can I read the program back from the panel?" The answer is yes, via ProSave, but the recovered .brf is binary and cannot be re-imported. Treat the WinCC flexible .hmi source as the master copy and ProSave as a runtime snapshot only.

Connecting the TP170A to a SIMATIC S7-300 CPU315 over MPI

For the online link (panel → PLC), use the MPI cable 6ES7901-0BF00-0AA0 (or the pre-assembled 6ES7 705-0AA00-7BA0 PROFIBUS cable with integrated PG socket). The two ends differ from the RS232 cable:

  • Cable 6ES7901-0BF00-0AA0 has two male DE-9 connectors. The TP170A MPI port is female, and the CPU315 MPI port is also female — so the cable plugs straight in on both sides with no gender changer.
  • The cable cannot be used to connect a CPU315 to a SIMATIC OP3 in the same wiring path (OP3 uses a different pinout on its programming port). A dedicated OP3 cable is required for that scenario.
  • Default MPI address: TP170A = 1, CPU315 = 2. Verify in STEP7 → Set PG/PC Interface → MPI and in WinCC flexible → Connections → S7-300 MPI.

If you have a PROFIBUS DP connector with a PG socket (6ES7972-0BB12-0XA0) on the CPU end, simply unplug the PG cable from the panel and re-route the bus through the connector — no re-wiring is needed; the bus is just daisy-chained.

Verification Checklist

Check Expected result
TP170A Control Panel → Transfer Channel = Serial, 9600, 8/E/1
PC Device Manager COM port present, no yellow warning triangle
Loopback test (TX/RX shorted at panel end with a DE-9 loopback plug) WinCC flexible "Test connection" returns OK
First project transfer Progress bar advances within 5 s; no "timeout" or "checksum" errors
ProSave → Backup .brf and .crc files appear in the chosen folder; file sizes are > 0
CPU315 ↔ TP170A MPI link STEP7 online → "Accessible nodes" lists TP170A at address 1
Panel restart after transfer TP170A boots directly to the new project screen; no error 1001 / 1005

Troubleshooting Matrix

Symptom Likely cause Fix
WinCC flexible "Transfer timeout" after 30 s USB-RS232 dongle, wrong COM port, or wrong cable (MPI in place of RS232) Use native COM, verify 6ES7901-1BF00-0AA0, loopback-test the PC port
ProSave "Cannot establish connection" ProSave is set to Ethernet/PPI on a serial device In ProSave, set Connection to Serial and pick the right COM
Transfer starts, then "checksum error" mid-way EMI on a self-built cable, missing shield bond, or cable > 15 m Replace with OEM cable, shorten to ≤ 10 m, ground the DE-9 shell
TP170A boots, shows "Connect to host…", no project Project not yet transferred, or download was cancelled Re-run the WinCC flexible transfer, ensure power is not interrupted
OP3 / CPU315 not responding on MPI Wrong cable (RS232 cable used where MPI was needed) or male/female mismatch Use 6ES7901-0BF00-0AA0, add male-male gender changer only if both ends are female-male
TP170A panel error 1001 / 1005 / 1101 at boot Corrupt runtime image after interrupted transfer Re-transfer the project; if persistent, ProSave → Restore the last .brf
Restore from .brf fails with "Wrong device type" Restoring a TP170A backup onto a different panel model Restore only onto the same TP170A model/firmware family

Cable Build Notes and Field Practice

When you must build the RS232 cable yourself, three rules keep it working the first time:

  1. Cross 2 ↔ 3, cross 4 ↔ 6, cross 7 ↔ 8, and tie 5 to 5. Pins 1 and 9 are unused. Do not wire them to anything; a stray jumper on pin 1 is enough to confuse the TP170A's DCD sense logic.
  2. Loop 4 ↔ 6 and 7 ↔ 8 on each end of the cable (DTR-DSR and RTS-CTS local handshakes) — this is a true null-modem with full handshaking, not a three-wire cable.
  3. Bond the shield to the metal shell of both DE-9 hoods. The shield is the only return path for high-frequency noise on a 10 m run next to a VFD or motor contactor.

Mark the cable clearly with a label or heat-shrink tag reading "RS232 — TP170A ↔ PC" to prevent the next shift from grabbing it for an MPI job. Most broken projects in the field are traced to a mis-cabled MPI cable, not a defective TP170A.

When to Upgrade Off the TP170A

The TP170A was made obsolete by Siemens in the early 2010s. It uses a custom Windows CE image, the last WinCC flexible revision that targets it cleanly is WinCC flexible 2008 SP2. If you are starting a new project, choose the TP700 Comfort, KTP700, or KTP1200 Basic instead — they are Ethernet-native, support TIA Portal, and are still in production. The TP170A remains in service largely in legacy S7-300 cells where the cost of re-engineering a screen outweighs the benefit of TIA Portal integration.

Which cable do I need to transfer a project from PC to TP170A?

Use Siemens RS232 cable 6ES7901-1BF00-0AA0. It has two female DE-9 connectors and is a null-modem crossover. Do not use the MPI cable 6ES7901-0BF00-0AA0 (one digit different) — it speaks MPI, not the TP170A's serial transfer protocol, and the transfer will time out.

Can I use a USB-to-serial adapter with the TP170A?

Not reliably. WinCC flexible 2005 and ProSave depend on the COM-port enumerating with a 16550-compatible UART and an exact baud-rate generator. Most USB-RS232 dongles fail the connection step with a timeout. If your PC has no COM port, install a PCIe serial card (Moxa CP-118U, StarTech PEX2S553) instead.

How do I read the project back from the TP170A into WinCC flexible?

You cannot. WinCC flexible only writes to the panel. To back up the running image, launch ProSave (bundled with WinCC flexible), set Device type to TP170A and Connection to Serial, then click Backup. The result is a .brf/.crc pair that can only be restored to a TP170A — it is not editable source code.

What cable connects a CPU315 to the TP170A for the online link?

Use the MPI cable 6ES7901-0BF00-0AA0, or the pre-assembled PROFIBUS lead 6ES7 705-0AA00-7BA0 with an integrated PG socket. Both have male DE-9 connectors and plug directly into the female MPI ports on the CPU and the panel. No gender changer is required in this configuration.

Will a ProTool / WinCC flexible project from a TP170A run on a TP170B?

Not without conversion. The TP170A uses one device integration and a different OS image. Open the source in WinCC flexible 2005 SP2 or later, change the target device to TP170B, recompile, and re-transfer. The PLC tag interface stays identical, but the runtime files, screen resolutions, and any TP170A-specific objects must be re-resolved by the compiler.

Back to blog