In our efforts to integrate a new Omron PLC (NX/NS Series) with Citect / Aveva Plant SCADA, we are utilizing the Ethernet/IP CIP Protocol to access status and alarm tags from the system. Unlike our previous experience with older PLCs such as the CJ2M-CPUxx using the OMFINS3 driver and FINS protocol, the new NX102-1100 OEM PLCs have FINS disabled and exclusively use Ethernet/IP CIP for tag publication to the HMI. Although the PLC unit has 3 RJ45 Ports (P1/P2 for EIP & P3 for EtherCAT), the OEM has disabled P2, the only port capable of using FINS. Despite the OPC-UA Server capability being built-in, it has also been disabled. After seeking support from Schneider, we were advised to continue using the OMFINS3 driver. However, there is no mention of this driver supporting the Ethernet/IP CIP protocol in the documentation. Aveva's knowledge and support center mentions a driver, OMRON 1.24, that supports Omron Ethernet/CIP, but it seems to be a Wonderware Driver rather than one for Citect. If the OMFINS3 driver could potentially work with EIP CIP, it is noted that name-based/tag-based addressing in OMRON NJ/NS/NX Series is not supported with Citect's current OMFINS driver offering. This might require a workaround involving address translation in Omron's Sysmac studio to convert the tags to a traditional memory register format. Unfortunately, as we are unable to modify the PLC code and only have a list of EIP tags, we are facing limitations in this integration process. We are seeking advice or suggestions on successfully setting up these systems with Citect / Aveva Plant SCADA. Any insights or workarounds would be greatly appreciated. Thank you.
If you are unable to use port 2, FINS will not be a viable option for you. One alternative solution could be to utilize Kepware as a middleware and establish communication between Citect and Kepware using OPC. Kepware offers support for Ethernet/IP communications with the latest Omron PLC models.
Thank you, Chelton! I will definitely give this a try. Let's see how it goes.
While the transition to newer Omron PLCs and moving away from FINS protocol can be a bit challenging, you've arrived at a few reasonable approaches. Firstly, if you can't change the driver from OMFINS3 due to reasons at your end, explore using the Implicit Messaging of Ethernet/IP. Omron's NX102 PLCs do support CIP Implicit I/O Messaging—which might serve as a workaround for communication. Secondly, despite the provided limitations, I'd recommend checking with Aveva support again regarding the OMRON 1.24 driver supporting Ethernet/IP. Even though it's mainly used for Wonderware, due to the debate in its documentation, there might be a way to get it to work with Citect as well. Also, if it's an option, I would recommend considering third-party OPC servers like Kepware from PTC or Matrikon from Honeywell, which have comprehensive support for a wide range of protocols and better driver management, especially with such specific application requirements. Lastly, it's crucial to continuously communicate these issues to your OEM, as they also possess the technical insights and potential leverage with Omron/Schneider to offer a feasible solution or workaround. Best of luck with your integration task!
I understand the complexities you're dealing with. Having worked previously with Omron's NX Series PLCs, I can tell that Omron's native implementation of Ethernet/IP is different from what we typically encounter with other systems. The protocol is commonly used as a multi-coinstantiable, specific IP Port-based protocol, but Omron has chosen to use it differently, causing potential compatibility problems with third-party SCADA systems. While I don't have a direct solution, I recommend exploring the option of using a protocol gateway to convert EIP CIP to a different protocol that Citect can more easily handle. OPC UA would have been a good alternative, but since it's not activated, Modbus TCP might be a decent choice. Modbus TCP support is usually quite good in most brand PLCs and SCADA systems. Finally, a less preferred solution would be to adapt your SCADA system and use a Wonderware platform which you mentioned has a driver which allegedly supports Omron's EIP implementation, even if it's not the ideal path. I hope this provides some direction to your problem. Please continue to share your insights as you work through this issue. We all learn from each other's experiences.
It sounds like a complex problem you're dealing with, integrating the NX/NS Series with Citect / Aveva Plant SCADA. Although Schneider suggested to continue using the OMFINS3 driver, it seems that it doesn't support Ethernet/IP CIP. While it's not an ideal situation to not be able to use name-based/tag-based addressing, you might be onto something with creating a workaround through Omron's Sysmac Studio for address translation. Additionally, have you considered involving a third-party middleware that specializes in linking incompatible systems? If that's a possibility, it could potentially bridge the gap between the PLC and SCADA systems. This may bypass the limitations you're encountering with the proprietary PLC code and the OMFINS3 driver.
✅ 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: - Integrating Omron NX/NS PLCs with Citect SCADA using Ethernet/IP CIP protocol might pose challenges due to the differences in protocols and limitations in the PLC setup, such as disabled ports and protocols. Workarounds involving address translation may be required.
Answer: - While the OMFINS3 driver has been suggested for use with Omron PLCs, it is important to note that the documentation does not explicitly mention support for Ethernet/IP CIP protocol. Aveva's knowledge and support center mentions a driver called OMRON 1.24 that supports Omron Ethernet/CIP, but it may be specific to Wonderware rather than Citect.
Answer: - Yes, the current OMFINS driver offering with Citect might not support name-based/tag-based addressing in Omron NJ/NS/NX Series PLCs. This limitation could require address translation in Omron's Sysmac studio to convert tags to a traditional memory register format, which may be challenging if PLC code modification is not possible.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.