With over 25 years of experience using AB SLC, Micro, and Logix PLC's, I have a strong grasp of their programming environment. While I have a lot of reusable programming and receive repeat business for similar equipment, I am open to exploring cost-saving opportunities in the I/O hardware department. One option I am considering is Automation Direct I/O, known for being affordable, user-friendly, and quick to deliver. Specifically, I am interested in the Automation Direct Stride I/O, which boasts Modbus TCP capability. I am curious about the compatibility of this I/O with CompactLogix, which is also Modbus TCP compatible as a client or server. Although AB may have reservations about the synchronization of update times, I believe it is worth investigating further. If you have experience integrating Automation Direct Stride I/O with CompactLogix or similar systems, I would greatly appreciate hearing about your results. Thank you in advance for any insights you can provide.
After using AB SLC, Micro, and Logix PLCs for over 25 years, I have become quite adept at the programming environment. Despite being set in my ways due to the extensive programming I re-use, I am open to exploring cost-saving opportunities, particularly in the realm of I/O hardware. I have recently taken a closer look at Automation Direct I/O options, such as the Automation Direct Stride I/O with Modbus TCP capability. I am curious about the compatibility of this system with a CompactLogix, which also supports Modbus TCP communication. Have any of you tried integrating Automation Direct I/O with a CompactLogix PLC? Despite potential skepticism from AB about non-synchronous updates, I believe it is a worthwhile endeavor to explore. If you have attempted this, I would love to hear about your experiences and results. In my own programming practices, I have found that even with Rockwell claiming synchronous updates, I still mirror I/O to designated status bits and words within my program. This approach simplifies the process of replacing limit switches and sensors. Additionally, I have leveraged off-line testing through simulation, ranging from basic inputs driving outputs in a subroutine to comprehensive process simulations using high-end software packages. By the way, age is merely a reflection of one's willingness to embrace new ideas and technologies. Let's continue to share our experiences and insights in the field of PLC programming.
I cannot provide feedback on Stride I/O, but I have had success using Click as Ethernet/IP Remote I/O. The accompanying AD software can create an EDS file for your configuration, seamlessly integrating the Click into the Studio 5000 setup. This solution is the most budget-friendly I/O option available.
I am aware of the updated Modbus AOI for Logix5000, but I prefer seeking I/O devices compatible with Ethernet IP instead of attempting to integrate Modbus with Logix5000, knowing they have incompatible nature.
OkiePC mentioned the availability of a new and improved Modbus AOI for Logix5000, but I advise considering EtherNet/IP I/O for better compatibility. It is important to note the performance limitations of Client AOI as outlined in the user manual, as there is a restriction on the amount of data AOI can process per second. Therefore, I suggest opting for EtherNet/IP I/O with built-in Logix support for optimal performance.
There are a variety of third-party options available, including Automation Direct, Turck, and Phoenix Contact, among others.
I've had some experience integrating Automation Direct products with AB CompactLogix. Even though there were a few hurdles, it was manageable overall. The main issue was differences in data representation between the two systems, but it was nothing a bit of mapping inside the PLC couldn't sort out. About update times, it depends on the size of your system. Delays were negligible in my applications, but I can see them being an issue in larger installations. A tip though, leave a comfortable headroom on your Ethernet load, it can get heavy with many devices! I saved a significant amount of my budget using Stride I/O over AB equivalent, so it might be worth looking into for your case!
I've integrated Automation Direct Stride I/O with CompactLogix in a few projects, and from my experience, the modules work well. Though you're right about AB being a bit wary about synchronization, I found that the update times lined up adequately for my applications. I suggest you go ahead and give it a try, obviously perform extensive testing before rolling it out in a production environment. One thing I can assure you, it definitely helped in reducing the overall cost.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - Answer: Automation Direct Stride I/O is known for being affordable, user-friendly, and quick to deliver, making it a cost-effective option for I/O hardware.
Answer: - Answer: Yes, Automation Direct Stride I/O boasts Modbus TCP capability, which is compatible with CompactLogix PLCs that are also Modbus TCP compatible as a client or server.
Answer: - Answer: While there may be reservations from AB regarding synchronization of update times, it is worth investigating further for potential compatibility.
Answer: - Answer: It would be beneficial to hear about any results or insights from individuals who have experience integrating Automation Direct Stride I/O with CompactLogix or similar systems.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.