Check the panel driver list before tuning serial settings

What a missing driver means

A serial link has two layers, and both have to match. RS-232 is the electrical layer: voltage levels, the connector, one transmitter to one receiver, point-to-point. DF1 is the protocol layer: how each message is framed, addressed and checked on the wire. A panel needs a DF1 driver to build and parse those messages, and a list holding K-sequence, DirectNet, Koyo Modbus and Modbus RTU describes a panel that speaks four protocols, with DF1 absent.

Published DF1 documentation puts the serial protocol at 9600 baud to 56K baud, with 19200 baud the common choice. Those numbers describe how fast two DF1 devices exchange messages once both ends have the driver. Raising a port from 9600 baud to 19200 baud cannot help a panel with no DF1 driver; it only changes the speed of frames the panel cannot parse. A connector that fits does not establish that the protocols match. The driver list is the evidence, and it either names the controller port's protocol or it does not.

Symptoms and what each points to

Match the failure you see to the layer it lives in:

• No reply to any poll. Protocol mismatch. Check the driver list first; this is the signature of a panel speaking a protocol the controller port is not.
• Garbage or framing errors once a compatible driver is selected. Serial settings differ between the ends. Set baud rate, data bits, parity and stop bits to the same four values at both ends, read from each manual.
• No reply or an address error on a Modbus RTU link after the driver exists. Settings or station addressing. The checklist on Modbus RTU master no-reply and address errors works that failure down in order.
• One panel works and the link breaks when a second panel joins the same cable. Topology. Full-duplex DF1 is a two-device link and RS-232 has no multidrop; the example below works the count.
• Reads work and writes fail over Modbus RTU. A documented capability limit on controllers whose native protocols are K-sequence and DirectNet: a Modbus master reaches data registers and cannot write the ladder program. The K-sequence and DirectNET write-limits page documents that boundary.
• Errors come and go with cable length, or when a cabinet door opens. Physical layer. DF1 RS-232 distance has its own limits, worked out in the article on how far an HMI can be from the PLC on DF1 RS-232.

Check the driver list first

Work the checks in this order:

1. Record the panel model and its project software version, the controller model, and the protocol configured on the port you plan to use.
2. Open the driver list. It lives in the panel's project software, in the step where you add a controller to the project: a pick list of protocol drivers for the serial port. Screenshot or print it.
3. Compare the list with the port's protocol. In this case the list holds four entries and the port speaks DF1, so the overlap is zero and the tuning stops here.
4. If a driver does match, compare the four serial values and the station address at both ends against each manual. One published DF1 slave driver defaults to 9600 baud, 8 data bits, no parity, 1 stop bit, and the controller channel may hold different values.
5. If your driver list came from an older datasheet, pull the current document for the exact model and software version. Driver lists grow as firmware is released, and a decision on an outdated list sends the project down the wrong path.
6. Once K-sequence or DirectNet is the shared protocol, plan the addresses too: the panel points into the controller's V-memory, configured per model, and the V-memory configuration notes for K-sequence and DirectNet slave show what that mapping looks like on one controller.

Example: three panels on one DF1 RS-232 port at 19200 baud

Inputs. The controller's serial channel is configured for DF1 full-duplex at 19200 baud, wired on RS-232; 19200 baud is the common DF1 setting inside the documented 9600 to 56K baud range. The panel's driver list shows the four drivers named above and no DF1 entry. For the alternative topology, the RS-485 standard budgets 32 unit loads per segment.

Rule. A protocol link needs a driver both ends share. A full-duplex DF1 link is peer-to-peer: exactly 2 devices, over RS-232 or RS-422. RS-232 is electrically point-to-point and has no multidrop.

Arithmetic.

1. Protocol overlap: the port speaks 1 protocol and the panel lists 4 drivers, 0 of them DF1. Overlap = 0, so the link cannot start at any baud rate.
2. Station count: the design requests 1 controller port + 3 panels = 4 stations on one link. Full-duplex DF1 supports 2. The design is 4 - 2 = 2 stations over the limit.
3. Settings, for the panel that could talk if its list included DF1: controller at 19200 baud against the driver's 9600 baud default is a 9600 baud difference, enough to corrupt every frame until the panel is set to 19200 baud as well.

Result. The design fails twice: 0 matching drivers at the protocol layer, and 4 stations on a 2-station link at the topology layer.

Decision. No setting repairs either failure. With no DF1 driver on the panel, run Modbus RTU if the controller port documents it, add a gateway whose documentation covers both sides, or pick a panel whose list includes DF1. To put 3 or more panels on one port, move to half-duplex DF1 on RS-485, size the segment to the 32-unit-load budget and the node limit in the controller manual, and give each panel its own station address. Above 2 devices, full-duplex DF1 on RS-232 is invalid at any baud rate.

The fix: choose an interface both manuals document

Each option assumes the panel's current driver list and the controller manual for the exact port are in hand.

Modbus RTU on the panel's list does not mean the controller port offers it; both manuals have to name the same protocol for the same port. If several panels each poll as Modbus RTU masters on one shared RS-485 bus, the bus contends and traffic stalls; that failure and the fix are in the article on two Modbus RTU masters on one RS-485 bus.

Verify the link before the panel controls anything

1. Wire one panel over the documented protocol at the documented settings, with the station address both manuals agree on.
2. Read a value the plant can verify, such as a counter in the controller's data table, and watch it update on the panel.
3. Write to a non-critical address before the panel drives anything. The procedure in operator panel PLC link setup: test writes before motion is built for that step.
4. Power-cycle both devices and repeat the read. Configuration that survives a restart is the configuration you have.
5. Add panels only when both manuals document the topology. Give each panel a unique station address, test each panel on its own, then run all panels together and watch the port's error counters over a shift.

A two-panel link that works does not prove a third panel can join. The limit comes from the topology rules in the example: 2 devices on full-duplex DF1, and the node and unit-load limits on a shared segment.

Recommendation: Read the driver list before you change a single serial setting. If DF1 is absent, as on a panel showing only K-sequence, DirectNet, Koyo Modbus and Modbus RTU, stop tuning: run the panel over Modbus RTU where the controller port documents it, add a gateway only when its documentation names DF1, your baud rate and your data map, or choose a panel that lists DF1. Keep a full-duplex DF1 link on RS-232 to 2 stations; for 3 or more panels on one port, design half-duplex DF1 on RS-485 within the segment's unit-load budget and the node limit in the controller manual.

Questions