Hello, I have encountered a unique situation with a 1768-L43 PLC, equipped with input and output cards, along with a 1768-M04SE Sercos module that controls three Ultra 3000 drives. The system also includes an AB HMI connected via ethernet to a dumb switch. Recently, I introduced an Aventics valve assembly with an Ethernet IP communication module. However, when attempting to add the generic ethernet module to the program, I realized that the option was not available. I believe that I may need to incorporate a 1768-ENBT module first, and then add the generic module under it. Can someone confirm if this assumption is correct, or if there is a simpler solution I am overlooking? Please refer to the attached images for further clarification. Thank you.
If you mention that the PLC module is linked to a basic switch and communicating through Ethernet, what method is currently utilized to establish this connection? Due to the absence of a built-in RJ45 port, is it possible for the 1768-L43 to facilitate this type of communication?
To ensure proper functioning, it is necessary to incorporate the ENBT into the 1768 bus. The 1768 bus allows for the installation of up to 2 modules. It is worth noting that the SERCOS module occupies slot 2, leaving slot 1 empty. It is possible that there is already an ENBT in slot 1 of the 1768 bus (given that L43 lacks an Ethernet port), even though it may not be properly configured in the system. Placing the SERCOS module next to the controller in slot 2 may not be ideal for its performance. Would you be able to provide a photo of the chassis for further assessment?
You're absolutely right, Steve & dmroeder. While initially mistaken due to poor lighting in the panel, I discovered that there is indeed an Ethernet card situated to the left of the PLC module. However, it seems this card was never integrated into the project tree.
Thank you for the help, everyone! I have successfully incorporated the new component into the project and implemented a universal adapter for the valve assembly. Everything is now functioning as intended.
You're correct in your assumption. The 1768-L43 PLC doesn't support Ethernet IP on its own - it requires an external Ethernet module, such as the 1768-ENBT, to provide this functionality. After you've installed this module, you'll then have the ability to add other Ethernet IP devices like your Aventics valve assembly. Also, remember to do a firmware match between your PLC and your ENBT module, otherwise you might face compatibility issues. Alternatively, you could consider using a Point I/O with an Ethernet adapter if introducing a 1768-ENBT module is not feasible.
You're right on the money! Your PLC setup with the 1768-L43 does require a 1768-ENBT ethernet bridge to support generic ethernet modules for your Aventics valve assembly. This bridge will essentially manage the ethernet communication between your various components. Adding the 1768-ENBT ethernet bridge module first, then integrating your generic ethernet module under it, should work perfectly. However, don't forget to update your PLC configuration in RSLogix 5000 after putting your new module in place.
You're on the right track with your thinking! The 1768-ENBT module would indeed provide Ethernet/IP capabilities, allowing you to integrate the Aventics valve assembly properly. Once you have the ENBT in place, you should be able to add the generic Ethernet module. Just make sure that your software is set up to recognize the ENBT and that all firmware is updated. If you're still having issues after that, double-check the configuration settings in the program for any missing parameters, and don't forget to review the documentation for the Aventics module—it might have specific requirements. Good luck!
It sounds like you're on the right track with your assumption about needing the 1768-ENBT module to facilitate Ethernet/IP communication. The 1768-L43 doesn't support generic Ethernet/IP modules directly without an Ethernet port, so adding the 1768-ENBT to your existing setup should provide the necessary connection layer for the Aventics valve assembly. Once that’s installed, you should be able to configure the generic module in your program without any issues. Just make sure to check that you're using the right firmware versions for compatibility. Good luck, and let us know how it goes!
✅ 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: The generic Ethernet module may not be available because you need to first incorporate a 1768-ENBT module before adding the generic module under it.
Answer: Answer: To integrate the Aventics valve assembly with the Ethernet IP communication module, you may need to add a 1768-ENBT module and then proceed to add the generic Ethernet module for the valve assembly.
Answer: Answer: It seems that you may need to incorporate the 1768-ENBT module first before adding the generic Ethernet module for the Aventics valve assembly. This step could be necessary for proper integration and communication within the system.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.