Hello dear community members, I am trying to use the CtrlX-Core as Ethernet/Ip adapter (eth1 port) under an Allen-Bradley plc (Ethernet/ip scanner) I am still trying to manually configure the Assembly Instances here, but unfortunately my AB plc still can not communicate with the CtrlX-Core. I am still using a Generic Ethernet/Ip Adapter module in my RSLogix project. This is the configuration I am using now (I can “ping” all the devices): CtrlX-Core (eth0) - only engineering via tcp/ip (192.168.1.25) CtrlX-Core (eth1) - only Ethernet/Ip (Adapter as 192.168.1.50) Allen-Bradley Scanner with 192.168.1.1 I have also set my Allen-Bradley plc (Scanner) with the Assembly Instances of 64 (O-->T) and 65 (T-->O), according to the Ethernet/Ip Module page on CtrlX-Works project. I am leaving the configuration instance as 110. I am using a pretty old AB controls here (Logix5555) which does not allow to import EDS libraries into my RSLogix project. My RSLogix >> Tools option does not have the option to install an EDS file. However, I was able to install the EDS by using the RSLinx, which pretty much recognizes and accepts the Ethernet/Ip Adapter (no question mark icon anymore). One weird thing is that my “Ethernet_IP_Adapter” device points out an error to open the port 192.168.1.1, even though I have configured the “Ethernet” device at Eth1 to use the 192.168.1.50 address. My “Ethernet” device status appears to be Running. In the past, I could easily connect this AB plc to my IndraDrive by using the Assembly Instances of 110 (configuration), 101 (Scanner to Adapter) and 102 (Adapter to Scanner). But now, with the CtrlX-Core I am having some hard time to find the E/ip adapter. Am I missing something here? I am attaching the CtrlX-Core EXPORT file here, as well as the screenshots. Any help is much appreciated! 😊
... View more
