It’s a common question that clients ask, “Which MicroLogix’s support Modbus?” In this article I’ll detail the answer.
MicroLogix 1000
Today’s MicroLogix 1000 still has just one Mini-Din RS-232 “Channel 0” communication port limited to DF1 and DH-485. So for applications requiring Modbus you’ll need to look elsewhere, as the MicroLogix 1000 does not support Modbus.
MicroLogix 1200
Series C versions of the MicroLogix 1200’s Mini-Din RS-232 “Channel 0” communications port supports DF1, DH-485, ASCII, MODBUS RTU SLAVE and MODBUS RTU MASTER. However, the series A and B models only support MODBUS RTU SLAVE.
Since “Channel 0” is limited to RS-232, to put the ML1200 on RS-485 I recommend the 1761-NET-AIC which is an isolated RS-232 to RS-485 interface converter. You’ll also want the 1761-CBL-HM02 cable to connect and power the AIC.
MicroLogix 1500
Series C versions of the MicroLogix 1500’s Mini-Din RS-232 “Channel 0” communications port supports DF1, DH-485, ASCII , and MODBUS RTU SLAVE and MODBUS RTU MASTER. The LRP models also support DF1, DH-485, ASCII , MODBUS RTU SLAVE and MODBUS RTU MASTER on its DB9 RS-232 communications port labeled “Channel 1.” While series A versions of the LSP model has no MODBUS support, series B versions of the LSP and LRP do support MODBUS RTU SLAVE.
Since “Channel 0” (and “Channel 1” on LRP models) is limited to RS-232, to put the ML1500 on RS-485 I recommend the 1761-NET-AIC. For “Channel 0″’s Mini-Din connection you’ll also want the 1761-CBL-HM02 cable to connect and power the AIC. For “Channel 1″’s DB9 connection you’ll need either a 1761-CBL-AC00 (17.7”) or 1747-CP3 (9.8′) (you’ll also need to provide 24vdc power to the AIC.)
MicroLogix 1100
All series of the MicroLogix 1100’s Mini-Din RS-232 “Channel 0” communications port support DF1, DH-485, ASCII, MODBUS RTU SLAVE and MODBUS RTU MASTER.
On the ML1100, Rockwell re-designed “Channel 0” removing the Mini-Din pins that previously provided 24vdc to accessories (like the AIC) and replaced them with RS-485 connections. So, to put the ML1100 on RS-485 you can use the Mini-Din to Terminal Block cable, the 1763-NC01.
MicroLogix 1400
All series of the MicroLogix 1400’s Mini-Din RS-232 “Channel 0” and DB9 “Channel 2” communications port support DF1, DH-485, ASCII, MODBUS RTU SLAVE and MODBUS RTU MASTER.
Like the ML1100, the ML1400’s “Channel 0” port has RS-485 connections in place of the 24vdc power pins, so to put the ML1400’s “Channel 0” on RS-485 you would use the Mini-Din to Terminal Block cable, the 1763-NC01.
To connect the ML1400 DB9 RS-232 “Channel 2″ communications port to RS-485 I recommend the 1761-NET-AIC with a 1761-CBL-AC00 (17.7”) or 1747-CP3 (9.8′) (and don’t forget you’ll also need to provide 24vdc power to the AIC.)
Unique to the series B versions of the MicroLogix 1400 is the added support for MODBUS TCP on the “Channel 1” Ethernet port. The port is the standard RJ-45 style and supports 10 MBPS Half Duplex through 100 MBPS Full Duplex.
I hope the above information on which models of MicroLogix support Modbus was helpful. Later in the week I’ll cover which CompactLogix and ControlLogix models support Modbus. Until then, if you have any comments or questions please feel free to leave them by filling out the “post a comment or question” link below.
Until next time, Peace ✌️
If you enjoy this episode please give it a Like, and consider Sharing as this is the best way for us to find new guests to come on the show.
Shawn M Tierney
Technology Enthusiast & Content Creator
Eliminate commercials and gain access to my weekly full length hands-on, news, and Q&A sessions by becoming a member at The Automation Blog or on YouTube. You'll also find all of my affordable PLC, HMI, and SCADA courses at TheAutomationSchool.com.
- 2024 Podcast Audience Polls: Vote before January 8th! - December 18, 2024
- All 2024 Audience Choice Polls: Vote before December 31st! - December 18, 2024
- Position Guided Vision (P232) - December 18, 2024
Discover more from The Automation Blog
Subscribe to get the latest posts sent to your email.
0
I am new to PLC Programming.
I am looking to connect AB Micrologix 1200 on Ethernet Network for Point Discovery through Software.
Port 0 is connected to Preprogrammed HMI and operating on Modbus RTU.
I want to use 1761-NET-AIC Card for this purpose, But I am confused how I should connect PLC with this card when already HMI is connected to PLC on Port 0.
The ultimate goal is to acquire real time data and store in DB.
I plan to use Python/C# to acquire the data once I am clear on hardware connecting.
Please Guide.
Not sure what your question is… the manual for the AIC+ is pretty straight forward, and if you have a Modbus RTU Python/C# Driver & Serial Port on your PC you what else could you need?
PS – If you’re looking for the Python/C# code, we don’t cover those here.
Shawn
Join my free community to follow along! You can also become a member and support our work at: Automation.Locals.com
Hello how are you. How can I use the modbus rtu slave on the same port 0 in the micrologix 1200, which is where it is programmed by DF1, it is programmed
Good morning Samy,
You’ll see in the channel configuration that you can only choose one protocol at a time.
That said, if you set it to Modbus, you can toggle it back to DF1 by hitting the Default Comms button, then toggle it back by hitting it again.
Hope this helps,
Shawn Tierney,
Instructor at http://www.TheAutomationSchool.com
Great write up, but I think overall it’s far more cost effective to just replace my ML1200 with a $99 Koyo Click which doesn’t require any converters and directly takes rs485 cable. I wish all the big automation folks would realize we’re past the “Tower of Babel” days and there is no excuse for making something as univeral as Modbus as difficult and costly as possible.
Thanks for your comment Curt!
I think many Automation folks in North American feel it worth the extra $100 to go with the MicroLogix over the Koyo because (1) they are familiar with it, and (2) it would honestly take more than $100 worth of time and effort to learn something new. And, that something new would now be the odd PLC out in their facility. I think this is also the reason why most haven’t used Rockwell’s $99 Click competitor, the Micro800.
Thanks again for your comment!
Shawn Tierney
Join my free community to follow along! You can also become a member and support our work at: Automation.Locals.com
Shawn, great write up!! Very informative. Did you ever do one on “which ControlLogix or CompactLogix models support Modbus”, specifically Modbus RTU as master and slave? I’m really having a tough time selecting a model. I’d like to be able to have Modbus RTU slave to respond to a remote master non-AB PLC, and Modbus RTU master to talk to local non-AB drives.
Thanks again!
Thanks William!
I do have a draft of just that article, but I haven’t finished the research yet. However, here’s my notes so far:
– For CompactLogix and ControlLogix processors with a “built-in” DB9 serial port, Rockwell includes with RSLogix 5000 sample code that allows you to communicate via MODBUS RTU using the serial port. The code works, but it’s a tad bit complicated, and I don’t know if a version exists for use with Rockwell’s Serial Port I/O Modules (so it can be used with new processors without serial ports.)
– New CompactLogix processors (with USB ports, aka 5370) have updated internal Ethernet cards which support “open sockets,” and sample code (AOI) exists on Rockwell’s sample code website for Modbus TCP using the built in Ethernet port.
– The old EWEB, and new EN2Tx/3TR also support open sockets, and in theory any L6 or L7 should be able to use the above sample code (AOI) for Modbus TCP, but I haven’t confirmed that.
– Finally, Prosoft recently released some newer lower cost Modbus modules, so if all else fails that’s always an option.
Well, those are all my notes! Would love to do all the fact checks and write it up as a blog but it will probably won’t be until February so hopefully these notes help some!
Thanks again Will, and have a great New Year’s day 🙂
Shawn Tierney
Join my free community to follow along! You can also become a member and support our work at: Automation.Locals.com