IMDHMIControls LibraryShop main store

Selection guide

Connecting ControlLogix to RS232 and RS485 serial devices

Industrial networks Published 8 min read

Short answer

Convert the RS232 devices to RS485 at the electrical layer, then pick one master for the whole pair: 1734 ASCII modules for fixed-length or delimited frames, an in-chassis Modbus RTU module for a pure Modbus bus, or an EtherNet/IP-to-serial gateway with a protocol builder when variable-length checksummed frames share the wire with Modbus RTU. One master serializes every transaction behind the 3.5-character silent gap, 3.65 ms at 9600 baud.

On this page
  1. Can a ControlLogix controller talk to RS232 and RS485 devices?
  2. Do RS232-to-RS485 converters put every device on one bus?
  3. Can ASCII and Modbus RTU share one RS485 line?
  4. Which POINT I/O module speaks ASCII over EtherNet/IP?
  5. Where do the 1734 ASCII modules stop working?
  6. Which gateway handles mixed binary protocols and Modbus RTU?
  7. Which option do I choose for each protocol mix?
  8. How do I terminate and bias the RS485 bus?
  9. How long does one full poll of all three devices take?
  10. Questions asked

Convert the two RS232 instruments to RS485 at the electrical layer, keep one master on that pair, and pick the master by protocol rather than by brand: the 1734-232ASC and 1734-485ASC ASCII modules when every frame is fixed-length or carries a delimiter, an in-chassis Modbus RTU module when the bus is pure Modbus, and an EtherNet/IP-to-serial gateway with a protocol builder when variable-length binary frames with CRC or LRC checksums ride the same pair as Modbus RTU. The converters merge wires, never protocols. The engineering decision is which single device owns the bus, builds every query and enforces the silent gap between transactions.

Can a ControlLogix controller talk to RS232 and RS485 devices? #

Yes. Current ControlLogix processors carry no serial port of their own, so serial instruments reach the controller through one of three additions: a POINT I/O ASCII module on EtherNet/IP, a Modbus RTU module in the 1756 backplane, or an EtherNet/IP-to-serial gateway — each ends up as ordinary controller tags.

Your EtherNet/IP backbone stays exactly as it is; the serial link is a local spur inside the cabinet. If you have already pulled Modbus registers into a ControlLogix over the network, the register model is the same on a serial wire — reading Modbus TCP from a ControlLogix PLC without a gateway covers that side. What changes on RS485 is framing, turnaround and scheduling: one master must sequence every transaction, where on Modbus TCP each server answers independently.

Do RS232-to-RS485 converters put every device on one bus? #

At the electrical layer, yes: two converters put the RS232 gauges on the same twisted pair as the Modbus RTU slave, and at the application layer nothing merges — each device still speaks only its own protocol.

RS232 is single-ended and point-to-point; RS485 is differential multidrop, which is why the conversion works. Pick converters with automatic transmit direction control, so no RTS handshake is needed on a half-duplex pair, and pick isolated ones. On a furnace with variable frequency drives in the same enclosure, use optically isolated converters and route the serial pair away from drive output cables, grounding the shield at one end only, so switching noise and ground potential stay off the controller I/O.

Can ASCII and Modbus RTU share one RS485 line? #

Yes, when one master owns the pair and separates every transaction by the Modbus silent interval of 3.5 character times — 3.65 ms at 9600 baud — so exactly one device drives the line at a time and each is polled with frames built for its own protocol.

RS485 is half duplex: two talkers at once corrupt both frames. The master interleaves a Modbus read, then the first gauge's query, then the second, each followed by the silent gap. One instrument protocol common on vacuum gauges looks like Modbus — address, length byte, function code, 16-bit CRC, query-response — but is not Modbus, and a Modbus driver will misparse it; its frames come from its own manual. Every device on the shared pair must agree on baud, parity and stop bits. Above 19200 baud the Modbus specification fixes the inter-frame gap at 1.75 ms instead of letting it shrink further, so raising baud stops paying beyond that point.

Which POINT I/O module speaks ASCII over EtherNet/IP? #

The 1734-485ASC is the RS485 ASCII module and the 1734-232ASC is its RS232 twin; each sits in a POINT I/O rack behind an EtherNet/IP adapter such as the 1734-AENTR and hands received bytes to the controller as strings.

The module a supplier may call DeviceNet-only is a different catalog number — the DeviceNet adapter, not the ASCII module — so confirm the number on the label. Transmit and receive buffers default to 20 bytes each on the ASCII modules, so raise both whenever a frame runs longer than 20 bytes. Serial rates span 300 to 115,200 bps, and the module manual calls for shielded cable on the RS485 line to keep coupled noise from faulting module communications. Framing is a fixed byte count or one delimiter character: CR, LF or a byte you choose. It is the same adapter-level architecture as designing a 1734-AENT Point I/O fiber ring on EtherNet/IP when the rack sits far from the controller.

Where do the 1734 ASCII modules stop working? #

They stop at variable-length frames with no delimiter and at arithmetic: the modules frame on a fixed count or one delimiter byte, they compute no checksums, and they speak no Modbus — ladder has to do all three.

A fixed-length binary frame is comfortable for them, as is any stream that ends in CR or LF. A frame that carries only a length byte and a 16-bit CRC, with no delimiter, defeats the framing logic, and the controller STRING data type holds 82 characters, so longer frames need chunking and reassembly. Forcing Modbus RTU through these modules means generating frames, running the CRC16 with polynomial 0xA001 and timing the silent gaps in ladder — a large block of code nobody wants to own on a furnace that must run for years. Use these modules when framing is trivial and there is no checksum to honor.

Which gateway handles mixed binary protocols and Modbus RTU? #

An EtherNet/IP-to-serial gateway with a configurable protocol builder, such as the Anybus Communicator AB7007, decodes each instrument's frames, computes CRC and LRC checksums, runs a built-in Modbus RTU master and exposes the mapped values as EtherNet/IP I/O.

The serial side is configurable as RS232, RS422 or RS485 at 300 to 115,200 bps, the I/O image carries 512 input and 512 output bytes, supply is 10 to 30 VDC, and the orderable item is AB7007-C. You configure it from a PC in the Anybus Configuration Manager, defining transmit and receive frames byte by byte, choosing the checksum type and mapping response bytes into the I/O table the controller consumes. It sits between configurable and programmable: no ladder code, but real per-device decoder work. Gateways without a protocol builder shine on pure ASCII such as barcode readers; for binary variable-length protocols, send the instrument manuals to the gateway vendor and get written confirmation of support before ordering.

Which option do I choose for each protocol mix? #

Fixed-length or delimited frames everywhere: the ASCII modules. Pure Modbus RTU on the pair: an in-chassis backplane Modbus master. Variable-length checksummed frames mixed with Modbus RTU: the protocol-builder gateway — and that third case is exactly the vacuum furnace bus.

Integration option Bus it fits Framing handled Checksums Modbus RTU Hardware location
1734-232ASC / 1734-485ASC ASCII or binary, fixed length or delimited Fixed count or one delimiter byte Computed in ladder Not native POINT I/O rack behind 1734-AENTR
In-chassis Modbus RTU master Modbus RTU only Modbus framing with silent gaps CRC16 native Native master 1756 backplane slot
Protocol-builder gateway (AB7007) Mixed binary plus Modbus RTU Fixed, delimited and variable length CRC and LRC built in Built-in master DIN rail, EtherNet/IP adapter

Decisions: a plant bus that is all Modbus takes the backplane module and no gateway at all; a bus of barcode-style ASCII takes the ASCII modules or a plain gateway; the furnace's trio of two proprietary binary instruments and one Modbus slave takes the protocol-builder gateway, with the RS232-to-RS485 converters in front of the two gauges.

How do I terminate and bias the RS485 bus? #

Terminate the two physical ends of the pair with 120 Ω across A and B, bias the idle line with about 560 Ω per side, and let exactly one device on the bus supply that bias.

The idle pair must sit above the receiver's 200 mV threshold or the master reads garbage between transactions. With the two 120 Ω terminators in parallel giving 60 Ω across the pair, 5 V driving 560 + 60 + 560 = 1180 Ω pushes 4.2 mA through the line, and 4.2 mA × 60 Ω = 254 mV — above threshold with margin. Many converters carry built-in bias and termination: enable bias in one device only, or the parallel loading halves the differential voltage. Keep converter stubs as short as the layout allows.

How long does one full poll of all three devices take? #

About 94 ms at 9600 baud allowing 10 ms of turnaround per device, so a 100 ms poll timer covers the furnace bus; a 50 ms cycle is out of reach at 9600 and needs 19200 baud, which brings the cycle to about 62 ms.

Worked example, 9600 baud, 10 bits per character (start, 8 data, 1 stop):

  • Character time: 10 ÷ 9600 = 1.042 ms.
  • Query frame of 8 bytes (address, function, two register-address bytes, two count bytes, two CRC bytes): 80 bits ÷ 9600 = 8.33 ms.
  • Response of 9 bytes (address, function, byte count, four data bytes, two CRC bytes): 90 bits ÷ 9600 = 9.38 ms.
  • Silent gap between transactions: 3.5 characters = 35 bits ÷ 9600 = 3.65 ms.
  • Turnaround allowance per device: 10 ms.
  • One device: 8.33 + 9.38 + 3.65 + 10 = 31.36 ms. Three devices: 3 × 31.36 = 94.1 ms.

At 19200 baud the wire portions halve — 4.17 + 4.69 + 1.82 + 10 = 20.68 ms per device, 62 ms for the bus. Below that, device turnaround dominates rather than wire time, so the next lever is splitting the Modbus slave onto its own serial port instead of raising baud further. It is the same serialization that makes Modbus RTU drive polling on one serial port slow: a shared pair serves one transaction at a time, and the timer has to respect that.

Questions asked

Why did my supplier say the RS485 POINT I/O module is DeviceNet only?

They were describing the DeviceNet adapter for POINT I/O, not the ASCII module. The RS485 ASCII module is catalog number 1734-485ASC and its RS232 counterpart is 1734-232ASC; both sit behind an EtherNet/IP adapter such as the 1734-AENTR. Read the catalog number off the module label before wiring anything.

Can I skip the converters and give each RS232 device its own module?

Yes. The 1734-232ASC is point-to-point RS232, so two modules on one adapter run both gauges without converters and without touching the Modbus pair. You trade two module slots and two cables for a cleaner bus: the Modbus RTU slave then runs alone on RS485 behind its own master.

Do I have to calculate checksums in ladder logic?

Only on the ASCII modules, which frame and move bytes but compute nothing. A backplane Modbus RTU module generates the CRC16 for Modbus frames itself, and a protocol-builder gateway such as the AB7007 calculates both CRC and LRC for custom frames and writes the verified bytes straight into the I/O image the controller reads.

What baud rate should the shared RS485 bus run?

One rate for the whole pair: set it to the best speed all three devices support, which with mixed vacuum-instrument controllers is usually 9600 baud. Every device must be configured for the same baud, parity and stop bits, because a slave set differently will not answer and will corrupt the line for the others.

Does the gateway appear as an EtherNet/IP adapter or as a Modbus device?

The AB7007 presents itself as an EtherNet/IP adapter, so the ControlLogix owns the connection and consumes the serial data as cyclic I/O, up to 512 input and 512 output bytes. The controller never sees the serial protocols, only the mapped values sitting in its tag database.

Keep reading

  • Explainer

    Designing a 1734-AENT Point I/O fiber ring on EtherNet/IP

    Yes — enable IGMP snooping on all seventeen switches: the input data a 1734-AENT adapter produces is multicast, so without it every switch floods the ring and all sixteen adapters reject each other's packets. Full-duplex switching ends collisions but not congestion, each fiber span must meet its own optic's distance limit, and ring recovery must beat four times the RPI.

    Industrial networks

  • How-to

    How a PLC runs two Modbus networks at the same time

    Yes. Each serial port is its own independent link: the HMI polls the PLC on one port while the PLC acts as master, or slave, on a separate RS-485 Modbus RTU network. The two links share no settings — only their endpoints must match — and PLC copy logic moves any data between them.

    Industrial networks

  • How-to

    How to read CompactLogix tags from a C# SCADA application

    Yes: a C# application reads a CompactLogix by acting as an EtherNet/IP client that requests the controller's symbolic tag read and write services over TCP port 44818. For ten tags, build that client directly and skip the OPC server; choose the documented Modbus TCP sample code for 5370 processors only when you need a register interface.

    Industrial networks