Connect an old operator interface to a PLC: pick one protocol

What you need

• The DP-C321, its programming manual, and the programming software and cable that manual names. The communication driver is part of the panel's project, so you edit it on the PC and download it to the panel.
• The DL06 and its user manual. Its serial communications appendix, Appendix K, documents the ports and their settings.
• The panel-to-PLC cable with its wiring identified. A connector that fits can still be wired for the wrong pair of ports, so compare the cable's conductors with the wiring diagrams for your two ports before it goes on.
• One known, non-critical PLC location to read: a spare word whose value you can set from the PLC side and watch change.

Pick one protocol for both ends

The DP-C321's driver list offers K-Sequence and DirectNET for this PLC, and the DL06 supports both, so either choice finishes the job. They are alternatives. The panel's project selects one communication driver, the PLC port is set to one protocol, and the two names must match. With K-Sequence on the panel and DirectNET on the port, the cable stays electrically live and each end hears bytes it cannot parse, which looks exactly like a dead link.

Choose the protocol in the panel's configuration utility where the manual lists the drivers, set the PLC port to the same one, and write the choice down. The habit of reading the driver list before touching serial numbers pays off; Check the panel driver list before tuning serial settings walks it.

Recommendation: For a single DP-C321 returning to service on one DL06, select K-Sequence at both ends and put the panel on the fixed RS-232 port, whose documented settings take two knobs out of the job. Select DirectNET at both ends when your site documentation standardizes on it; the pairing treats the two protocols equally.

Match the serial settings at both ends

Port 1, the fixed RS-232 port, is documented in Appendix K: slave only, RS-232C only, with fixed settings of 9600 baud, 8 data bits, 1 start bit, 1 stop bit and odd parity. There is nothing to tune on the PLC side, so enter those exact numbers in the panel project. Slave-only means the PLC answers and the panel asks, which is the normal arrangement for an operator panel, so no role needs selecting.

The configurable port is where the speed choices live: its baud rate is limited to 19.2K or 38.4K, and the documented recommendation is to start at 19.2K baud, then change all devices on the link to 38.4K once communications are established.

The node address must match: enter the same value in the panel project and on the PLC port. Keep the RS-232 cable run inside the classic EIA-232 planning limit of 15 m (50 ft) at 20 kbit/s; the 38.4K setting wants a shorter run. When the port, not the panel, dictates every number, Connect an HMI to a PLC port with fixed serial settings shows the same discipline end to end.

Example: a box-stock DP-C321 on Port 1

A DL06 sits in a machine with Port 1 free, the DP-C321 comes off the spares shelf, and the drawer cable is the one documented for this pairing.

Set the panel's driver to K-Sequence, point it at the PLC's node address (1 works as an illustrative value; any address the manual allows is fine while both ends carry the same number), and enter Port 1's fixed settings in the panel project: 9600 baud, 8 data bits, 1 start bit, 1 stop bit, odd parity. On the PLC side there is nothing to enter. DirectNET on both ends runs through this same example with these same numbers; the port's fixed settings do not depend on which of the two protocols you picked.

Now check the line time. The framing is 1 start bit + 8 data bits + 1 odd parity bit + 1 stop bit, so each byte takes 11 bits on the wire. Take 30 bytes as the planning size of a single-register read exchange, request plus reply: 30 bytes × 11 bits/byte = 330 bits.

At 9600 bits/s, one exchange occupies the line for 330 ÷ 9600 bits/s = 34 ms. A screen reading 8 objects services all of them in 8 × 34 ms = 272 ms, about a quarter of a second, which reads as a live screen to an operator. The fixed 9600 port is therefore plenty for a one-panel job.

The configurable port's 19.2K setting brings one exchange down to 330 ÷ 19200 bits/s = 17 ms, and 38.4K brings it to 330 ÷ 38400 bits/s = 9 ms; that speed earns its keep when several devices share a link, not for one panel and a handful of registers.

Commissioning steps

1. Confirm the model and the ports. Check the DP-C321 label against its manual and identify which DL06 port the cable serves. If the cable's wiring is unknown, stop and verify it against both manuals; do not adapt a cable by trial and error.
2. Put the machine in a safe state, connect the cable, and power the panel and the PLC per their manuals.
3. Select the protocol at both ends and enter the serial settings from the sections above, writing down each change as you make it.
4. Watch the panel's communication status indicator and read its meaning in the panel manual. Treat an unfamiliar code as a lookup task, not a guess.
5. Test one known read. Set a value in the spare location from the PLC side, confirm the screen shows the same number, then change the value and confirm the screen follows. If the read fails, work the checklist in order: protocol name, baud, parity, stop bits, node address, cable. Change one item per test so a protocol mismatch stays distinguishable from a settings or address fault.
6. Test any writes on a scratch location with the machine still in its safe state. Outputs, motion commands and process setpoints come last, after the read path works. The full write-test discipline is in Operator panel PLC link setup: test writes before motion.
7. Draw the operator screens only now, object by object, from the tested read.

How to check it worked

• The panel's communication indicator shows its normal state, as the panel manual defines it.
• The tested read agrees: screen and PLC show the same value, and the screen follows a change within the line time you calculated in the example.
• A test write changes the one intended location and nothing next to it.
• A pass through the normal operating sequence shows every value the operator needs, updating as expected.
• The maintenance record carries the protocol, the port, the cable identity, the serial settings, the node address and the tested addresses, so the next swap or download reproduces the working configuration from paper.

When the link stays silent or a value reads wrong

• No data at all: work the checklist in the order it is written, one change per test.
• The indicator is normal but a screen value is wrong: the object's address notation or data type is off. Check both against the two manuals and retest on the single known location before trusting the screen.
• No K-Sequence and no DirectNET in the driver list: stop and confirm the unit against its manual before anything else. If the panel is a different legacy unit whose list offers Modbus RTU, the hookup discipline is the same; Connect a Modbus RTU HMI to a legacy PLC RS-232 port covers that pairing.

If the panel itself is beyond revival, the fix is a replacement operator panel that speaks the PLC's protocol, which is an industrial HMI decision. When the machine also deserves a status or notice board for the floor, we build shop-floor displays that play their own content offline; they sit beside the machine as signage and are not a substitute for the operator panel.

Questions