IMDHMIControls LibraryShop main store

How-to

Passing SLC 5/03 data to a CompactLogix over Ethernet

Industrial networks Published 8 min read

Short answer

Put a DF1-to-Ethernet gateway on the SLC 5/03's free Channel 0 serial port: an ENI-style unit lets the CompactLogix message SLC data-table addresses, and a protocol-mapping converter moves SLC files into CompactLogix tags on its own schedule. For one analog value between nearby panels, wire an analog output straight to an analog input instead. Configure Channel 0 for DF1 full duplex, add staleness logic, and prove the link with two test values across the range.

On this page
  1. Why no cable change can fix this
  2. Choose the device that does the translation
  3. Free Channel 0 and set DF1 full duplex
  4. Configure the exchange in this order
  5. What the bridge costs in update time
  6. When a UDT will not browse
  7. One analog value between nearby panels
  8. When replacing the processor is the right call
  9. Questions asked

The SLC 5/03 has no Ethernet port: one RS-232 Channel 0 that speaks DF1 or DH-485, and nothing else. So the CompactLogix cannot reach it on the network it lives on, and no cable or address change fixes that. Put a DF1-to-Ethernet gateway on the free Channel 0 port and decide who drives the transfer: a protocol-mapping converter copies SLC data-table files into CompactLogix tags on its own schedule, which is the right tool for a small one-way set like an analog input value plus a few status words; an ENI-style unit lets the CompactLogix message the SLC data table directly when logic must own each transaction. If the whole job is one analog value and the panels sit in the same cabinet, wire an analog output to an analog input and skip the network entirely.

Why no cable change can fix this #

DF1 over RS-232 and EtherNet/IP over twisted pair share no medium, no framing and no addressing, so the two controllers will never meet without help. There are exactly three ways across: translate between DF1 and EtherNet/IP in a gateway, carry the one value as an analog signal on copper, or change what the SLC side is. Every other decision — gateway addressing, message pacing, mapping tables — lives inside one of those three. Pick the bridge first, then configure.

Choose the device that does the translation #

Two product families do the DF1-to-Ethernet job, and they differ in who owns the transfer.

The ENI pattern is the original. The 1761-NET-ENI spoke DF1 full duplex on its serial side to the attached controller, and on the Ethernet side it made that controller look like an Ethernet-capable SLC to whoever messaged it: the CompactLogix aims a message at the gateway, the gateway turns it into a serial transaction, the SLC answers, and the reply comes back. The module's documentation scopes it to DF1 full-duplex devices, which is exactly what Channel 0 in DF1 Full Duplex mode is. Rockwell discontinued the 1761-NET-ENI; current substitutes are built for the same role, among them the ProSoft PLX51-DF1-ENI and the RTA 515RTAENI, which advertises ten TCP connections against the original ENI's four.

A protocol-mapping converter runs the transfer itself. Its serial side reads SLC data-table files, its Ethernet side talks to CompactLogix tags, and a mapping table you configure moves values on a period you set — no message logic in either controller. The basic Red Lion DSPLE000 covers a small bidirectional exchange; the step-up model in that family adds a web server and features a two-register transfer will never use.

For one analog value and a handful of words moving one direction, buy the mapping converter: the SLC program gains one copy rung and the CompactLogix consumes a plain tag. Buy the ENI-style unit when the CompactLogix must own and time every transaction in logic. Routing a message through a bridge to an older SLC is the same discipline as a CompactLogix MSG to an SLC 5/04 through a DH+ gateway — the message path through the bridge is what you are really configuring.

Path Take it when What it costs
Protocol-mapping converter (DSPLE000 class) A fixed, small set of values crosses on a fixed period UDT layouts must be entered by hand in the gateway software
ENI-style unit (PLX51-DF1-ENI, 515RTAENI) CompactLogix logic must own and time each read and write You write and maintain message logic; the serial segment still sets the pace
Hardwired analog pair One analog value, same or adjacent cabinet One output and one input channel spent; only that value crosses

Free Channel 0 and set DF1 full duplex #

Before ordering anything, find out who owns the port today: programming terminal, operator interface, modem, radio. If Channel 0 is running DH-485 to a panel, moving it to DF1 strands that panel, and one port runs one protocol — settle that first. Then, in the SLC programming software, open the processor channel configuration, go to the Channel 0-System tab, set the Driver field to DF1 Full Duplex, assign a Source ID the gateway will target, and write down the baud and error checking before you disconnect anything. Make the change offline and download. On the hardware side, Channel 0 is a 9-pin RS-232 connector; cable it to the gateway with the gateway vendor's documented cable rather than an improvised pinout, and set the gateway's serial parameters to match the SLC exactly. A framing mismatch gives you flashing indicators and no data.

Configure the exchange in this order #

  1. Inventory the data first: every value, its direction, data type, engineering range and safe state. In the SLC, copy the analog value and its status words into one dedicated contiguous integer file — do not point the interface at raw I/O that ladder logic also manipulates.
  2. Reserve the port. Confirm nothing else claims Channel 0, and record what connects to the SLC today for programming.
  3. Set the SLC side: DF1 Full Duplex driver, a Source ID, known baud and error checking, downloaded offline.
  4. Set the gateway side. Match the serial parameters exactly, then give the Ethernet side an address on the CompactLogix's subnet and prove you can reach it before any logic depends on it.
  5. Build the transfer. On a mapping converter, declare the SLC file, element and length on the serial side, pick the destination tag on the CompactLogix side, and set direction and update period per value. On an ENI-style unit, configure the CompactLogix message as a typed read of the SLC data-table elements, aimed at the gateway's address, paced by a timer, with retry handling on the message status.
  6. Add freshness logic. Reset a CompactLogix timer on every update; when it times out, mark the value stale and run the failure response you defined in step 1 — never control silently from a frozen value. If this value feeds anything safety-related, this link is not a safety function: handle that failure in compliant safety design, not in a data path.
  7. Verify source to destination. Force a known value at the SLC rung level, confirm the transfer file changes, watch the gateway's transaction counters rather than its link lights, then read the raw destination tag before any HMI or calculation sees it.
  8. Test the corners. Two values across the range, around 20% and 80%, expose scaling, word-order and data-type faults that one matching point hides.
  9. Break it on purpose. Measure the real update interval under production load, then pull the serial connector in a controlled moment and confirm the stale handler fires and the process goes to its defined response.

What the bridge costs in update time #

An illustrative calculation on a documented mechanism, so you can judge the bridge before buying it:

  • Line capacity: 19200 baud at 10 bits per character (start, 8 data, stop) is 19200 ÷ 10 = 1920 characters per second, or 0.52 ms per character.
  • One transaction: a typed read of 8 words. Frame overhead runs roughly 24 characters each way, and each 16-bit word costs two more on the reply: 24 + (2 × 8) = 40 characters back, 64 characters round trip. The exact count moves a few characters with the command and embedded control bytes; the arithmetic does not care.
  • Wire time: 64 × 0.52 ms ≈ 33 ms.
  • Controller time: the SLC services a request at a scan boundary — with a 10 ms scan, budget 10 ms. Round trip ≈ 43 ms, under 50 ms once the gateway's turn is counted.
  • The poll: one read every 250 ms is 4 transactions per second × 64 characters = 256 characters per second, which is 256 ÷ 1920 ≈ 13% of the line. The value the CompactLogix acts on is at most 250 + 50 = 300 ms old.

The decision falls out of those inputs: 300 ms of staleness is fine for logging, sequencing and supervisory control, and it is not fine for a tight closed loop. If the CompactLogix control decision needs that value fresher than about 100 ms, do not build this bridge for that value — hardwire the analog pair or replace the processor. Sharing one serial port among slow transactions is the same physics that makes Modbus RTU drive polling on one serial port slow: the line and the scan, not the Ethernet side, set the pace.

When a UDT will not browse #

If the CompactLogix side uses a user-defined type and the converter's tag browser shows the name but nothing inside it, the browse reads names and base types, not member layouts. Enter the UDT's member layout by hand in the gateway software, or map plain DINT and REAL tags and assemble them into the type in ladder. A missing type entry is a definition problem, not a dead network — do not re-cable for it.

One analog value between nearby panels #

When the entire exchange is one analog value and the cabinets are within a cable run, the cheapest bridge is copper: an SLC analog output channel wired straight to a CompactLogix analog input channel. Match signal type and range at both ends — 4-20 mA is the usual choice — verify scaling in both controllers, and isolate between the two systems if they have separate grounds, with an isolated input or a signal isolator. Live zero buys wire-break detection: an open circuit reads below 4 mA, so configure the input's underrange response instead of letting a broken wire read as a valid zero. If the CompactLogix side has no free channel, adding 4-20 mA analog inputs when the CompactLogix rack is full covers the options. Same or adjacent cabinet and one value: hardwire it — no protocol stack to misconfigure, and it fails visibly.

When replacing the processor is the right call #

Swap the 5/03 for an Ethernet-capable processor, or migrate it outright, when any of these is true: the dataset grows past a dozen words, the refresh requirement drops below about 100 ms, the SLC program needs rework anyway, or spare support for the platform is the real problem. A gateway on Channel 0 carries a small dataset indefinitely; it does not make the processor young. Rebuilding the medium around DH-485 for the sake of one link drags every device onto a legacy network — DH-485 is what you build when the whole cell already speaks it, the way an SLC 5/05 and MicroLogix 1100 link over DH-485, not a detour for a single transfer. For one analog value and a few words, the converter on Channel 0 is the decision.

Questions asked

Is an installed 1761-NET-ENI still usable now that it is discontinued?

Yes. Discontinued means no new units, not a recall: an ENI that already moves your data keeps working until it fails or you outgrow its connection count. Plan the substitute for the day it dies rather than swapping a healthy link under pressure. The PLX51-DF1-ENI and 515RTAENI both target the same DF1-to-Ethernet role.

Does a faster serial speed fix a slow update?

Only the wire portion. Wire time falls in proportion to speed, so the 64-character read that costs about 33 ms at 19200 baud would cost about 17 ms at double the speed, but the SLC still answers at a scan boundary and the gateway still takes its turn, so a 45 ms round trip does not become 23 ms. Below roughly 50 ms per transaction, the scan is the floor, not the line.

Why does the converter list my tags but show nothing inside the UDT?

The browse reads tag names and base types, not type definitions, so a user-defined type looks empty until you enter its member layout in the gateway software. Prove the link first with one plain DINT or REAL moving both directions; if the simple tag travels and the UDT does not, the network is fine and the definition is missing.

How should the CompactLogix detect a dead link?

Reset a watchdog timer every time the destination tag updates, and set the preset to three missed periods, which is 750 ms at the 250 ms poll in this article. When it times out, mark the value stale and run your defined failure response; hold-last-value is acceptable only where the process tolerates the value's age. Keep the status flag separate from the process value.

Should I replace the 5/03 with a 5/05 while I am in here?

Not for one dataset. The 5/05 keeps the same chassis and instruction set, so the swap itself is small, but it still means a processor change, a program download and I/O verification on a running machine, all to avoid one gateway. Do it when the platform's spare parts, not the data transfer, are the actual problem, or when more links are coming.

Keep reading

  • How-to

    CompactLogix MSG to SLC 5/04 through a DH+ gateway

    The CIP path in the CompactLogix MSG ends at the 1756-DHRIO module in the remote chassis. On the MSG configuration tab, change the communication method from CIP to DH+, then enter Channel A and the SLC 5/04 node address in the DH+ fields; the SLC is never part of the path itself.

    Industrial networks

  • How-to

    How to connect PROFINET IO to a CompactLogix through a gateway

    A CompactLogix cannot act as a PROFINET IO controller, so an EtherNet/IP-to-PROFINET gateway does the job: it is an EtherNet/IP adapter to the controller's scanner and the PROFINET IO controller to the field devices. The one reported gotcha on a 1769-L18ER-BB1B with a PLX82-EIP-PNC was byte swapping on both the input and output maps, fixed in the gateway rather than in ladder.

    Industrial networks

  • How-to

    How to map a 1747-SDN scanner for DeviceNet drive control

    Seeing the drive in an RSNetWorx browse is not an I/O connection. Put the drive in the 1747-SDN scanlist, read the M-file words the scanner mapping assigns, and reference those mapped words in the SLC 5/04 ladder. A node address is not an integer-file offset: the mapping view, not node 10, decides where each command and status word lives.

    Industrial networks