How-to
Link an SLC 5/05 and MicroLogix 1100 over DH-485
Short answer
Run a dedicated DH-485 serial network: a 1761-NET-AIC+ on the SLC 5/05 serial channel and a 1763-NC01 from the MicroLogix 1100, unique node addresses at each end, 120 Ω termination at both bus ends. A 20-word exchange at a 1 s period loads 9600 bit/s to about 25%, and a heartbeat watchdog set to three missed cycles makes the link fail safe.
On this page
- What is the best way to link an SLC 5/05 to a MicroLogix 1100?
- Why not just use the Ethernet ports both controllers already have?
- What hardware goes between the two panels?
- What steps put the link on the air?
- Which node addresses and port settings do the two controllers need?
- Is a DH-485 serial link fast enough for interlock data?
- What should the logic do when the link goes down?
- Which link wins for this project: DH-485 or DF1?
- Questions asked
Put the exchange on its own copper: a dedicated DH-485 serial network between the two controllers. A 1761-NET-AIC+ adapter joins the SLC 5/05 serial channel to an RS-485 bus, a 1763-NC01 cable lands the MicroLogix 1100 serial channel on the same bus, each end gets a unique node address, and both controllers treat silence as a fault. Speed never enters the discussion — the worked example below shows a 20-word exchange at a 1 s update period loading a 9600 bit/s line to about 25% — so the design is chosen on isolation and fail-safe behavior, which is exactly what the client's objection to the shared plant Ethernet is about. The sections below give the reasoning, the parts, the steps, the settings and the failure logic.
What is the best way to link an SLC 5/05 to a MicroLogix 1100? #
Run a dedicated DH-485 serial network with the SLC 5/05 on one end through a 1761-NET-AIC+ and the MicroLogix 1100 on the other, unique node addresses at each end, and logic that invalidates exchanged data the moment the heartbeat stops.
The job moves a small block of data and accepts whole-second updates, so the design optimizes for isolation and fault detection rather than throughput. The MicroLogix 1100 is a fixed controller with no slots for network scanner modules, which removes DeviceNet and ControlNet from the menu; what it has is Ethernet and one serial channel, and DH-485 is the token-passing peer network that serial channel was built to speak. The SLC 5/05 side needs the electrical conversion an adapter provides, and that is the role the AIC+ fills.
Why not just use the Ethernet ports both controllers already have? #
Because those ports ride the same switches and cables as the corporate and SCADA systems, the interlock inherits every fault on them; a dedicated DH-485 link gives the exchange copper nothing else touches, so a plant-network problem cannot take mission-critical data down with it.
A private Ethernet run between just these two controllers would also isolate the exchange, but it adds a switch, addresses and management to a two-node job; DH-485 adds none. It is the same separation principle as How a PLC runs two Modbus networks at the same time: process-critical traffic belongs on transport you own. Two limits stay honest. Physical isolation is not cybersecurity — the serial link keeps unrelated plant traffic off the transport, and the receiving logic still has to reject stale or implausible words. And a serial link that quietly stops is worse than one that announces it, which is why the watchdog below is part of the design, not an add-on.
What hardware goes between the two panels? #
Three named parts and two cables cover it: a 1761-NET-AIC+ at the SLC 5/05 end fed by a 1747-CP3 or 1761CBLAC00, a 1763-NC01 at the MicroLogix 1100 end, and RS-485-spec twisted pair between the panels.
Mount and power the AIC+ per its documentation, clear of power conductors, with its leads serviceable behind the door. Where the NC01 splits onto terminals, take every conductor function from the AIC+ DH-485 connection documentation — never from wire color — and continue the panel-to-panel run on twisted-pair cable built to RS-485 practice under TIA/EIA-485-A. Both serial channels are consumed by this design, so confirm first that neither feeds an HMI, a modem or a programming laptop whose duty would have to move.
What steps put the link on the air? #
Work through port reservation, data map, cabling, node addresses, message logic and watchdog in that order; each step depends on the last, and the two classic failures — a stolen port and a doubled node address — are caught at steps 1 and 6.
- Reserve the serial channels. Confirm neither channel feeds an operator interface, a modem or routine programming, and record how programming access will be regained once the mode changes.
- Map the exchange. Define one contiguous block per direction and give every word a type, an engineering meaning, a valid range, an owner and a safe fallback value.
- Mount and power the 1761-NET-AIC+ away from power conductors, with its field wiring separable from the controller wiring.
- Cable the SLC 5/05 serial channel to the AIC+ with a 1747-CP3 or a 1761CBLAC00.
- Cable the MicroLogix 1100 serial channel to the AIC+ DH-485 side with the 1763-NC01, split onto terminals, and continue between the panels on RS-485-spec twisted pair.
- Terminate both physical ends of the bus: jumper Terminals 5 and 6 together at an AIC/AIC+ end to switch in its built-in 120 Ω terminator, and put 120 Ω across the pair at any end that lands on bare terminals.
- Bond the cable shield at a single point, following the AIC+ documentation's shield and reference rules — a shield grounded at both panels invites a ground loop.
- Set both serial channels to DH-485 with matching rate settings and unique node addresses; the values sit in the next section.
- Add one message instruction per direction, triggered by a timer, never retriggered while a transaction is outstanding, with its done and error status checked every cycle.
- Add the heartbeat and timeout logic before the exchange is allowed to drive anything.
Steps 6 and 7 are where RS-485 installs go wrong: termination belongs to the two physical ends only, and a shield bonded at both panels turns intermittent noise into a permanent mystery. The transaction discipline in step 9 — one outstanding message, judged on its own status bits — is the same discipline a CompactLogix MSG to SLC 5/04 through a DH+ gateway lives by, and for the same reason: retriggering before completion hides the fault you need to see.
Which node addresses and port settings do the two controllers need? #
Give each controller a different DH-485 node address and set both serial channels to the same protocol and rate — this design puts the SLC 5/05 at node 1 and the MicroLogix 1100 at node 2, and the only hard rule is that no two stations ever share an address.
DH-485 is a peer network with room to grow: a Rockwell interface manual sizes a remote DH-485 network at up to 31 SLC nodes, so two stations leave the address space untouched. Save the original port configuration before downloading new settings, because the mode you replace is the mode you will want back if the link has to come out. And be clear about what proves success: a powered adapter and continuity through the cable prove only that the parts are present — the first successfully addressed transaction in both directions is the proof the network is configured.
Is a DH-485 serial link fast enough for interlock data? #
Yes — a 20-word exchange in each direction at a 1 s update period loads a 9600 bit/s line to 8.3% for payload alone and about 25% once protocol overhead is counted, so throughput is nowhere near the constraint on this link.
The arithmetic, for the example block of 20 words each way at 9600 bit/s with a 1 s period:
- Payload: 20 words × 2 bytes = 40 bytes one way, 80 bytes per cycle; one cycle per second gives 80 bytes/s.
- Line bits: serial framing costs 10 bits per byte (1 start, 8 data, 1 stop), so 80 × 10 = 800 bit/s of payload.
- Occupancy: 800 ÷ 9600 bit/s = 0.083, an 8.3% raw load.
- With a 3× allowance for token passes, addressing and CRC: 2400 bit/s, a 25% load.
Pick the rate on noise margin and cable quality, not on headline speed — five times the necessary bandwidth buys nothing here. The load math degrades quickly when node counts rise and periods shrink, the same effect behind why Modbus RTU drive polling on one serial port is slow; two nodes at 1 s never get near it.
What should the logic do when the link goes down? #
Have each controller stamp a heartbeat word into its transmitted block and treat three cycles without a change as a dead link — 3 s at this design's 1 s period — then invalidate the partner's data, drive the exchange outputs to their safe state and raise an alarm.
Three cycles is the deliberate choice: one silent cycle is a normal token hiccup, three consecutive ones mean the transaction has stopped. Keep the message instruction cycling so the link recovers on its own, but hold every received word invalid until a heartbeat change arrives, and latch the alarm until a person clears it. The failure that hurts is the quiet one — a stopped link leaves the last good value sitting in the registers, the same mechanism that freezes HMI values when PLC communications to the HMI time out, except here nothing flags it for you.
If the safe state includes closing a valve or dropping a contactor, wire it so the de-energized condition is the safe one and the watchdog result drives it directly; the reasoning in adding fail-safe valve shutoff when a watchdog expires transfers unchanged. One safety line: a communications watchdog is process protection, not a safety function — data that guards a hazard needs the machine's own safety design behind the safe state.
Which link wins for this project: DH-485 or DF1? #
For panels separated by more than a few meters, or anywhere near drives and welders, the DH-485 link with the 1761-NET-AIC+ wins; direct DF1 over RS-232 is the right call only for a short, quiet, point-to-point run where both serial channels are genuinely spare.
Case by case:
- Electrically noisy plant, panels apart, a programming path wanted on the bus: DH-485 through the AIC+, exactly as wired above. Differential RS-485 signaling on twisted pair is built for that environment.
- Panels side by side in a clean room, both channels spare, no bus growth planned: DF1 point-to-point over RS-232, no adapter, same watchdog. Plan on the usual EIA-232 guideline of about 15 m for a direct RS-232 run.
- Off the table either way: DeviceNet and ControlNet, because the MicroLogix 1100 takes no scanner modules, and the shared plant Ethernet, because it reinstates the exact dependency the client removed.
The decision for this project — interlock data, a client unwilling to share transport with corporate and SCADA traffic, plant Ethernet with a history of problems — is the DH-485 link.
Questions asked
Can I still program the controllers once their serial channels run DH-485?
Yes. An AIC+ exists to put an RS-232 device onto a DH-485 bus, and a programming terminal is a standard one: hang a spare AIC+ off the bus, connect the laptop to its serial side, and reach either controller by node address. Write both node addresses on the panel door, because the address is now the only path in.
How far apart can the two panels be?
RS-485 distances dwarf a two-panel run: the classic planning figures cited for RS-485 are roughly 1200 m at 100 kbit/s on properly terminated twisted pair, and this link runs at a few thousand bits per second for whole-second updates. Keep the pair twisted, away from power cables, terminated at both ends, and length between panels in one building is a non-issue.
Can a third device, such as an HMI, join the same DH-485 link later?
Yes, DH-485 is a peer bus built for growth, and panels and interfaces ride it through their own AIC+ converters. Give the newcomer the next unused node address, daisy-chain it onto the twisted pair, and jumper Terminals 5 and 6 only on the two AICs that sit at the physical ends of the network, where the built-in 120 Ω terminators belong.
Does the MicroLogix 1100 need the AIC+ at all, or can a cable do it?
It needs the converter. The 1100's serial channel is RS-232 hardware and DH-485 runs on an RS-485 bus, so the electrical conversion has to happen somewhere, and that is the AIC+'s job. A bare cable such as the NC01 suits a port that is RS-485 native; the 1100 is not one of those.
How long does one message transaction take to cross the link?
At the 9600 bit/s example rate, the 40-byte block itself costs 40 × 10 = 400 bits, which is about 42 ms of line time; token-pass waiting at a two-node network adds little. That is why a 1 s update period is comfortable and why the three-cycle watchdog never trips on a healthy link.
What heartbeat value should the watchdog watch?
Use a rolling counter rather than a toggle: increment through 0–255 and wrap, because a counter that runs through many values exposes a half-working link a simple flip-flop bit can hide. Every received word is held invalid until the counter changes; three cycles with no change, 3 s here, is the declared dead-link point.