IMDHMIControls LibraryShop main store

How-to

Configure MicroLogix 1100 Channel 0 for Modbus RTU

Industrial networks Published 6 min read

Short answer

On the tested MicroLogix 1100 (1763-L16BBB rev. B), Channel 0 is a serial port with a selectable driver — DF1, Modbus RTU Slave or Modbus RTU Master — set in RSLogix Micro under Channel Configuration while Channel 1 keeps carrying Ethernet. Slave mode creates the data files, binary for coils and contacts and integer for input and holding registers; master mode runs MSG instructions against the stations you poll.

On this page
  1. What the tested setup established
  2. Select the Channel 0 driver
  3. Configure Modbus RTU Slave mode
  4. Configure Modbus RTU Master mode
  5. Wire the RS-485 side
  6. Worked example: what one poll costs
  7. Decide slave or master
  8. Questions asked

Channel 0 on a MicroLogix 1100 is a serial port with a driver you select: DF1, Modbus RTU Slave or Modbus RTU Master. You make the change in RSLogix Micro, in Channel Configuration on the project tree, and the port then serves that one protocol while Channel 1 carries Ethernet in parallel — both channels ran together in the tested setup, a 1763-L16BBB rev. B with a USB-1761-CBL-PM02 cable and an Ethernet cable into the same PC. Pick Slave when a SCADA host or gateway reads and writes this controller. Pick Master when this controller has to poll drives or meters itself. One limit runs through everything below: the driver list is per-controller, so open Channel Configuration on your own unit and read the pull-down before you build the application.

What the tested setup established #

Part Role in the test
1763-L16BBB rev. B MicroLogix 1100 controller under test
Channel 0 Serial port; driver selectable between DF1, Modbus RTU Slave and Modbus RTU Master
Channel 1 Ethernet, passing traffic while Channel 0 ran serial
USB-1761-CBL-PM02 USB to round mini-DIN 8-pin programming cable; its COM port also carried the simulated slave stations
RSLogix Micro The software that changes the controller configuration and the ladder
ModRSsim2 Modbus slave simulator on the PC, standing in for the polled stations

That is the whole evidence base: one controller revision, proven with both channels active and a simulator in place of the slaves. The tested unit offered all three drivers in its Channel 0 list, and that list is the deciding fact on any other unit — the test does not extend to every MicroLogix 1100 revision. If your pull-down offers only DF1, that controller will not run Modbus on Channel 0, and nothing you change elsewhere alters that.

Select the Channel 0 driver #

  1. Open the project in RSLogix Micro and click Channel Configuration in the navigation tree at the left of the program window.
  2. Open the Driver pull-down for Channel 0 and select Modbus RTU Slave or Modbus RTU Master.
  3. Set the serial parameters — baud rate, parity, stop bits — and the station address to the values the other end of the wire uses. A mismatch produces silence, not an error message.
  4. Download, then reopen Channel Configuration and confirm the selection held.

The pull-down is a single choice, so putting Modbus on Channel 0 means programming moves to Channel 1 — exactly how the tested PC sat, holding the serial and Ethernet cables at once. If the serial link you actually need is DH-485 to an SLC 5/05 rather than Modbus, that is its own job: DH-485 has its own driver and network wiring, so configure it as a separate exercise before you commit Channel 0.

Configure Modbus RTU Slave mode #

Selecting Modbus RTU Slave creates the data files the Modbus master reaches, and the mapping is fixed by data class:

Modbus data class Data file type
Coils Binary
Contacts Binary
Input registers Integer
Holding registers Integer

Keep each class in its own file type and let the ladder move values between those files and the rest of the application: what you write, the master reads; what the master writes, your logic consumes. One safety limit belongs here — an external master can write a holding register at any moment, so range-check every value the ladder acts on before it reaches a speed command or a setpoint.

For the discipline on the host side of those writes, the pattern in safe Modbus writes to PLC output registers from SCADA applies unchanged: the master writes files, and your ladder owns what the machine does with them.

Configure Modbus RTU Master mode #

  1. Select Modbus RTU Master for Channel 0 and match the serial parameters to the slaves.
  2. Run a slave simulator on the programming PC — ModRSsim2 filled that role in the test — attached to the COM port the USB-1761-CBL-PM02 cable creates. The master transacts on that port, so a simulator on any other COM port proves nothing.
  3. Configure one MSG instruction per transaction: target station address, Modbus command, controller data file.
  4. Trigger each message from ladder on a rising edge and check its done and error bits.
  5. Watch the simulator: every station address you configured should show requests. If the wire carries requests addressed to station 0, the address in the message setup is the fault, unpacked in why Modbus RTU sends to slave address 0 instead of your device.

Master mode is the choice when the controller polls drives and meters — a documented application for this port drives PowerFlex 4 and 40 units over Modbus — and while the port polls, you program over Channel 1.

Wire the RS-485 side #

The Modbus link is the serial pins of Channel 0 — an RS-485 physical connection, not the Ethernet jack. Where the link reaches the network through a 1763-NC01 cable, two field fixes are reported for a MicroLogix 1100 that stays silent as an RTU slave:

  • Swap the data-wire polarity at the 1763-NC01; reversed data lines give a clean-looking link with zero responses.
  • Confirm the Common pin on the 1763-NC01 has its connection, because without the common the data lines have no reference.

Worked example: what one poll costs #

Illustrative arithmetic, wire time only. Assume 19,200 bit/s and RTU framing of 11 bits per character — 1 start, 8 data, even parity, 1 stop:

  • One character takes 11 / 19,200 = 0.573 ms.
  • Reading 20 holding registers in one request: the request is 8 bytes, the response is 5 + 2 × 20 = 45 bytes, so 53 bytes cross the wire. 53 × 11 = 583 bits, and 583 / 19,200 = 30.4 ms.
  • Reading the same 20 registers one at a time: 20 requests of 8 bytes plus 20 responses of 7 bytes = 20 × 15 = 300 bytes = 3,300 bits, and 3,300 / 19,200 = 171.9 ms.

Same data, 171.9 / 30.4 = 5.7 times the wire time — before the silent gaps between frames, the slaves' response delay and the controller scan add their share to both cases. The decision follows directly: group registers so one MSG reads a contiguous block, and keep station and message counts as low as the process allows, because a single serial port serves every station in sequence. The cycle-time arithmetic for that situation is worked through in why Modbus RTU drive polling on one serial port is slow.

Decide slave or master #

  • The MicroLogix is the data source — a SCADA host, gateway or logger reads and writes it: Modbus RTU Slave, with the binary and integer files as the whole interface.
  • The MicroLogix is the interrogator — it polls drives, meters or another controller: Modbus RTU Master, one MSG per transaction, programming over Channel 1.
  • Both roles on one machine: keep the host link on Channel 1 and dedicate Channel 0 to the polling side.

Questions asked

Can Channel 0 Modbus RTU and Channel 1 Ethernet run at the same time?

Yes. On the tested controller the two channels ran in parallel: Modbus RTU on Channel 0, Ethernet on Channel 1. That matters for maintenance, because Channel 1 keeps your RSLogix Micro programming path alive while Channel 0 is dedicated to Modbus — you never have to pull the protocol off the port to go online.

Are the Modbus data files special, or ordinary data files?

Ordinary ones. The slave driver maps coils and contacts to binary files and input and holding registers to integer files, and from the ladder's point of view they are standard B and N files — your existing moves, compares, math and bit instructions work on them unchanged. Keep each Modbus class in its own file type so the mapping stays legible.

How do I bench-test master mode before the slaves are wired?

Put a Modbus slave simulator on the programming PC — ModRSsim2 served that role in the test — and attach it to the COM port the USB-1761-CBL-PM02 cable creates, with one station address per simulated slave. When your MSG instructions hit those stations, the port, the serial framing and the message configuration are all proven before any field wiring exists.

The MicroLogix answers nothing as a Modbus slave — where do I look?

Work three checks in order. First, the serial parameters and station address must be identical at both ends, because a mismatch produces silence rather than an error. Second, on a 1763-NC01 RS-485 connection, swap the data-wire polarity — reversed lines are the classic silent-link cause. Third, confirm the Common pin on the 1763-NC01 actually has its connection.

Why does my MSG instruction read the slaves only once?

The rung probably never goes false. These message instructions re-fire on a false-to-true transition, so a trigger left high executes one time and then sits there while the register data goes stale — which looks like a dead port. Pulse the trigger from a timer or a step sequence and the polling repeats.

Keep reading

  • 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

  • Troubleshooting

    Reading Modbus RTU writes into a CJ1W-SCU31-V1 slave area

    The CJ1W-SCU31-V1, configured as a Modbus RTU slave, stores each master write in its allocated slave data area by itself, so there is no ladder receive instruction to add. If the area starts at D0, holding register 40001 maps to D0 and 40010 to D9, and the CJ2M ladder reads those D words directly. Fix the Micro850 MSG_MODBUS errorID 21 local channel configuration error before testing any data.

    Industrial networks

  • Troubleshooting

    Why Modbus RTU drive polling on one serial port is slow

    Modbus RTU carries one request-response transaction at a time, and at 19.2 kbit/s each drive transaction costs 40-60 ms, so 18 drives polled with a read and a write each need about 1.5-2.5 s per cycle no matter how the messages are chained. Cut the transaction count, schedule command writes ahead of status reads, set each drive's communication-loss timeout above the finished cycle, and change networks when the arithmetic cannot meet the update rate.

    Industrial networks