An SLC 5/03 has two serial channels, and the HMI goes on the one your project and drawing show free. Match the HMI driver to that channel's protocol, copy its baud, node address and framing settings exactly, and prove the link with a one-tag read-only screen. Channel 0 is point-to-point RS-232 up to 19200 bit/s; channel 1 is a DH-485 multidrop with up to 32 stations.
An SLC 5/03 on a running machine hands you two serial channels: channel 0 on the 9-pin RS-232 port and channel 1 on DH-485. The HMI connects through whichever channel your project and the machine drawing show free, and for a single new HMI that is usually channel 0 speaking DF1 full-duplex at 19200 bit/s. The order of work matters more than the wiring: read both channel configurations first, match the HMI driver to the protocol the free channel speaks, copy its serial settings exactly, then prove the link with one read-only tag. If you are swapping out an HMI that already talks to this processor, start with checking the PLC serial protocol before replacing a legacy HMI; the matching logic is the same.
What the SLC 5/03 gives you
Two channels, and each has a fixed personality:
| Channel | Port | Protocols you can configure | Speed | Layout |
|---|---|---|---|---|
| Channel 0 | 9-pin RS-232 | DF1 full-duplex, DF1 half-duplex, DH-485, ASCII | up to 19200 bit/s | point-to-point |
| Channel 1 | DH-485 port | DH-485 only | 19200 bit/s, fixed | multidrop, up to 32 stations |
Channel 0 is the flexible one and the usual home for a new HMI. DF1 full-duplex is point-to-point RS-232: one processor, one HMI, and the RS-232 standard's classic planning figure of 50 ft, about 15 m, at 20 kbit/s as the cable length to stay under at this speed. Channel 1 speaks DH-485 only, at the 19200 bit/s the DH-485 specification fixes, as a token-passing multidrop with room for station addresses 0 through 31.
Free means three records agree: the channel configuration in the project shows either no live service or a protocol nothing uses, the port is physically empty, and the machine communication drawing lists no device on it. The drawing outranks the empty jack, because maintenance gear gets unplugged and its record stays. The processor manual, the SLC 500 Modular Hardware Style User Manual, is the reference for the channel modes and settings named here.
What you need
- Your programming software and the PLC project file, to read both channel configurations.
- The HMI and its driver documentation. The driver list must name the channel's protocol; a widely used HMI family, for instance, lists DF1 full-duplex, DF1 half-duplex, DH-485 and both EtherNet/IP drivers, and on a serial-only 5/03 the serial entries are the ones that count.
- The serial cable both manuals specify. Build it exactly to the cable drawing in the documentation; a guessed cable costs an afternoon.
- The machine communication drawing.
- A dated note of the current channel settings, so any change can be put back.
Steps
- Read both channel configurations out of the project. For channel 0 and channel 1, write down protocol, baud rate, node address, parity, stop bits and error check. The channel settings block and its fields are described in SLC 5/03 ASCII channel settings and DF1 programming.
- Walk the panel with the drawing. Record what each port feeds today.
- Pick the free channel. For one new HMI on a 5/03 that is normally channel 0 as DF1 full-duplex: point-to-point, and it touches nothing on an existing DH-485 network.
- Match the HMI driver to that protocol. A plug that fits the jack tells you nothing about the driver; the driver list in the HMI documentation is the test.
- Copy the step 1 settings into the HMI driver: same baud, parity, stop bits and error check. Give the HMI its own node address, different from the processor's on that link; channel 0 node address configuration on the SLC 5/03 covers the address field.
- Build a one-tag screen: a single numeric display, read-only, pointed at an integer you know the meaning of, for example N7:0.
- Connect the documented cable to the empty port and power the HMI. No wiring move, no stop needed; any wiring move waits for an approved stop.
- Download the HMI project and open its communication status. Then run the checks below.
Never unplug a production cable to make a port free. The cable that looks spare may feed something the machine needs; if every port is live, the next section holds the supported paths.
Worked example: channel 0 free, channel 1 busy
Scenario. A machine cell runs an SLC 5/03. The project shows channel 1 as DH-485 feeding a data-collection network: the processor is station 1 and two collectors hold stations 2 and 3. Channel 0 is configured DF1 full-duplex, 19200 bit/s, node address 1, no parity, 1 stop bit, CRC error check. The 9-pin jack is empty and the drawing lists nothing on it. Free by all three records.
Decision: the HMI goes on channel 0. Driver DF1 full-duplex; HMI node address 2, because the processor holds 1 on this point-to-point link. Node addresses live per link, so 2 here is clean even though a station 2 exists on channel 1. Baud, parity, stop bits and error check come straight off the record.
Cable check. The HMI mounts 8 m from the panel. The planning line from the table section is 15 m at RS-232 speed, so 8 m fits with 7 m to spare. The numbers for other serial types are in HMI to PLC serial cable maximum distance by interface.
Link-time check. The screen polls 10 tags, one read per tag, once per second. A short DF1 read with its reply runs about 20 bytes each way, 40 bytes total. At 8 data bits, no parity and 1 stop bit, count 10 bits per byte: 40 × 10 = 400 bits per tag. Ten tags: 400 × 10 = 4000 bits per refresh. At 19200 bit/s: 4000 ÷ 19200 = 0.21 s of link time per second, about 21% of the channel. The rest sits idle for retries or more tags.
Result: download the project and all ten values track machine changes within about a second. Nothing on channel 1 changed, and the data collectors never noticed.
How to check it worked
- The HMI's communication status reads healthy and its timeout counter stays flat.
- The number on screen equals the number at N7:0 in your programming software. Change the value through normal machine action and watch the screen follow within about a second.
- The processor's channel 0 error count stays flat.
If the screen never comes online, compare the settings record against the HMI driver line by line: baud, parity and stop bits account for most first-test failures, and HMI panel not talking to the PLC: serial settings mismatch walks that comparison. If a value arrives but reads wrong, the tag's address or data type is off; fix the tag, and never bend ladder logic to suit a screen.
When the port you wanted is already busy
RS-232 is one device per jack, so channel 0 has no sharing arrangement. Three supported paths, in this order:
- Move the HMI to channel 1. DH-485 is built for several stations: inside the 32-station ceiling and with a free station address, the HMI joins the multidrop at the fixed 19200 bit/s and the machine network carries it as one more peer.
- Route the other device through the processor. The SLC 500 user manual documents channel-to-channel passthru, for example DH-485 to DF1 full-duplex, so a laptop or data collector can live on channel 1 while the HMI takes channel 0.
- When the PLC-side settings are fixed by a device you cannot reconfigure, match the HMI side to them; connecting an HMI to a PLC port with fixed serial settings is the how-to for that case.
Any rewiring waits for an approved stop, and the dated settings note is what you restore to if the test misbehaves. Decision: a free station on channel 1 takes the HMI; otherwise passthru frees channel 0 for it.
The decision
Recommendation: put a single new HMI on channel 0 as DF1 full-duplex at 19200 bit/s whenever the three records show channel 0 free and the HMI's driver list includes DF1. Choose channel 1 as a DH-485 station when channel 0 is busy, the DH-485 network has a free station address inside its 32-station limit and the HMI driver list includes DH-485. In both cases the first download is a one-tag read-only screen, and operator writes wait until the machine owner has reviewed them.
Keep one hardware boundary straight: an HMI reads and writes the PLC, and a signage display does neither. If the floor also needs a line-status or andon-style notice board that you refresh from a memory card, that is a separate screen doing a separate job, and it is the kind of display we build; see our shop-floor signage category.
Questions
Can the HMI and the programming laptop share channel 0?
No. DF1 full-duplex on channel 0 is point-to-point RS-232, one device per jack. Move programming to channel 1, or move the HMI to channel 1 as a DH-485 station if a free station address exists. The processor's documented channel-to-channel passthru can also carry one device through to the other channel. Schedule any rewiring for an approved stop and keep the dated settings note so the original state can be restored.
Can an offline signage display stand in for the HMI?
No. A signage display plays image and video files loaded on a memory card. It has no PLC driver, reads no data table and takes no video input, so it cannot show a live machine value or send a command. If the floor also wants a line-status or notice board that you refresh from your desk, that is a separate screen and a separate job, and it is the kind of display we sell.
Do I need to edit the PLC program to add the HMI?
Not for the first test. A read-only screen leaves the channel configuration and the ladder untouched; it needs one known integer address such as N7:0. When the HMI later writes setpoints or commands, add those tags deliberately, review the interlocks with the machine owner, and change no communication setting when you do.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.