PCS LAUER PCS009 Plus: Cable Fit Is Not Upload Proof

The engineer sees a PCS LAUER PCS009 Plus operating with a Siemens S5-95U, but neither PCSpro nor PCSproWIN immediately provides a confirmed upload path through the terminal’s 25-pin female COM (RS232/TTY) port. Treat connector fit, electrical interface, software compatibility, terminal state, and readback support as separate decision points.

Backup Target Identification

Before anything else, confirm what must be recovered. The HMI application and the PLC program are separate files held in separate devices. A connection to the PCS009 Plus cannot back up the S5-95U program merely because the HMI exchanges process data with that PLC.

1. Record the complete identification shown on the terminal nameplate and any software or firmware identification available from its local system screens.
2. Decide whether the objective is the editable HMI project, runtime data, or the PLC program.
3. Do not move on until the required artifact is tied to the device that actually stores it.

Physical Interface Check

The rear port is labeled COM (RS232/TTY) and uses a 25-pin female connector. The available cable has 25-pin and 9-pin ends and physically fits that port. This proves only mechanical compatibility. It does not prove the cable pinout, communication direction, handshaking arrangement, or electrical mode.

RS232 and TTY identify different electrical interfaces. A computer serial port normally cannot communicate directly with a current-loop TTY interface. Selecting the wrong interface can produce the same symptom as a terminal that is not in transfer mode: no response, repeated timeouts, or an immediate connection failure.

1. Read the cable identification, wiring drawing, or continuity record supplied with the cable. Confirm that it is intended for PCS engineering transfer, not merely PLC communication.
2. Determine whether the terminal transfer function uses the RS232 or TTY side of the combined port. Use the terminal documentation or configuration display; connector shape cannot answer this.
3. Confirm that the desktop port or adapter provides the same electrical interface.
4. Identify the actual operating-system COM port assigned to the 9-pin connection or serial adapter.
5. Do not move on until the cable function, electrical mode, and computer COM port are known.

Engineering Software Compatibility

PCSpro and PCSproWIN are both installed, but installation alone does not establish support for this terminal revision or for project readback. Legacy HMI families may use different project formats, communication drivers, or transfer utilities across software generations.

A terminal can contain executable runtime data without retaining the complete editable engineering source. Readback may therefore be unsupported, or the recovered object may be suitable only for restoration rather than editing. Establish that distinction from the selected software’s command description before communicating with the HMI.

Transfer-State Decision

The PCS009 Plus in this installation has no rear DIL switches. A programming-mode procedure written for a switched variant therefore does not apply. Do not search for or imitate an absent switch arrangement.

1. Keep the running application unchanged and inspect only documented local system, setup, or transfer screens.
2. If the terminal exposes a transfer state locally, select it without initializing memory or loading a default project.
3. If no transfer state is exposed, configure the correct terminal target and COM port in the compatible engineering package, then issue only a non-destructive connection or identification request.
4. If the HMI answers, record the identity returned by the software before attempting readback.
5. If it does not answer, return to the electrical-interface and cable checks. Do not interpret silence as proof that a hidden programming mode is required.

Programming state and electrical communication are independent gates. A correctly selected transfer state cannot compensate for an RS232/TTY mismatch, and a correctly wired cable cannot compensate for unsupported software.

Non-Destructive Readback Procedure

Proceed only after the engineering package explicitly identifies the PCS009 Plus and offers an upload, readback, or receive operation. A command labeled download, send, transfer to terminal, initialize, or clear can overwrite the only working copy.

1. Photograph or record the operating screens and communication status before interrupting runtime operation.
2. Open the compatible engineering package and select the exact terminal target shown by the software.
3. Select the verified computer COM port and the confirmed RS232 or TTY transfer path.
4. Place the HMI in its documented transfer state if the terminal requires a local action.
5. Run the software’s connection or device-identification function. Stop if the reported device differs from the installed terminal.
6. Select the direction from terminal to computer. Confirm the dialog describes receiving or reading from the terminal before accepting it.
7. Save the first recovered copy unchanged. Create a second working copy before opening, converting, or editing the project.

If no readback command exists for the exact target, the cable cannot create that capability. Recovery then requires an existing project archive or the manufacturer’s official support path for the terminal and software revision.

Result Verification and Recurring Pitfalls

Validate a recovered project without writing it back. Confirm that the engineering package can reopen it, that screen and communication objects are present, and that file copies retain stable sizes and hashes. A successful serial progress indication by itself proves data movement, not project completeness.

Frequently Asked Questions