Hello everyone, I require assistance in establishing a connection between a Micrologic 1400 PLC and Citect SCADA version 7.2. In my setup, I am utilizing the ABMLXEIP protocol to set up the IODevice in Citect. However, when attempting to read a bit address on the Micrologix 1400 PLC using Tag Debug after compiling the Citect project, I am unable to retrieve any data. I am unsure of how to determine if there is any communication between the PLC and Citect. According to the Schneider Electric FAQ on ABMLXEIP, a 1761 NET-ENI Module is necessary for the protocol to function properly. However, I do not have this module and instead am utilizing the RJ45 (COM Port 1) port configured as an Ethernet Channel on the Micrologix 1400. Could this lack of the 1761 NET-ENI Module be the reason for the issue? If so, what steps can I take to establish communication between my Micrologix 1400 PLC and Citect without the 1761 NET-ENI Module? Any assistance on this matter would be greatly appreciated. Thank you.
One important consideration is whether the IP address is correctly set up on the same subnet as the SCADA system. This configuration plays a crucial role in ensuring smooth communication and device interaction.
The 2008 FAQ does not include information on Ethernet/IP capabilities for the MicroLogix 1100 and 1400 series. However, based on your hardware setup, you should be in good shape.
Hello, to verify the communication between Citect and the PLC, it is important to create a test page in Citect with all the boards properly assigned. When connecting the test page, it should display the status as either "Comms Good" or "Comms Bad". This step is crucial in ensuring a successful connection between the Citect software and the PLC.
The MLX 1400 comes with built-in Ethernet which can be utilized as an option. I have experience working with this in version 6.1 and can demonstrate an Ethernet setup in Citect if needed. To verify if the server is functioning properly, you can use the kernel and examine the 'driver' section by scrolling through the page. If possible, please provide some screenshots of the communication setup. If there are communication issues, you may see #com on the screens, indicating a problem. For the 1000 and 1200 series MicroLogix PLCs, the serial driver is typically used.
Thank you for your assistance thus far. Have you ensured that the IP address is correctly configured on the same subnet as the SCADA system? It appears that both the PLC and Citect have matching Subnet Masks, and when I tested the connection by "pinging" the PLC from the Citect server, I received a response. The MLX 1400 comes equipped with onboard Ethernet - could that be a possible solution? I believe that's what I'm currently connected to, as I mentioned the RJ45 (COM Port 1) port. To Duckman and Roboregarding troubleshooting the communication between Citect and the PLC: I have examined the Citect Kernel and it seems that the IO device is offline. I have included images of the Kernel reading and the communication settings for the IO device. It seems that the ABMLXEIP board (BOARD4) is functioning well with other IO devices, but not with this one so far.
It indeed sounds like the missing 1761 NET-ENI Module could be causing your issue. The ABMLXEIP protocol relies on this module for proper function. Without it, the data exchange between Micrologix 1400 PLC and Citect SCADA may be impaired. A huge part of troubleshooting is to ensure that your hardware setup matches the specifications required for your protocols. In your situation, even though your PLC is effectively Ethernet-enabled via its RJ45 port, it might not adhere to the precise communication scheme of the ABMLXEIP protocol without the 1761 NET-ENI Module. However, you could try using the MODNET driver instead, which is also supported by MicroLogix and doesn't require the 1761 NET-ENI. This might be a good alternative if getting the 1761 NET-ENI isn't feasible.
It sounds like you might have identified the problem yourself. While it's true that you can configure the RJ45 as an Ethernet Channel on the Micrologix 1400, you might be missing some capabilities that the 1761 NET-ENI Module can offer. Have you tried any communication testing between the PLC and Citect? You could possibly use ping tests or cable testing to verify physical connection, assuming your configuration is correct. Without the NET-ENI module, you might face some challenges especially for a more complex SCADA system like Citect. Using Modbus TCP/IP protocol might be an alternative solution to look into. It can work over the regular Ethernet port and it might not require additional hardware, although it definitely needs proper configuration.
It seems like you've done a lot of work to troubleshoot this already, kudos for that. As you've noted, the lack of a 1761 NET-ENI Module could definitely be causing these issues, as this module is typically required for the ABMLXEIP protocol to function smoothly. However, you might be able to work around this by using the RJ45 Port directly. You should be able to do this by configuring the port as an Ethernet/IP Port instead of just an Ethernet Channel. Once you've made this change, be sure to verify all other related settings (like IP addresses and subnet masks) and then try compiling your project again. Hope this helps, and let us know how it goes!
Hi there, it sounds like you're on the right track with troubleshooting. The absence of the 1761 NET-ENI module could be why you're experiencing issues as the setup you've described generally requires it. As a workaround though, you could consider using the Ethernet/IP protocol, which your Micrologix 1400 should natively support, instead of the ABMLXEIP protocol. If switching protocols is not feasible, another possible solution to establish communication without the 1761 NET-ENI module might be encapsulating the DF1 or DH+ packets into Ethernet frames using a NET-ENI alternative such as a Prosoft MVI56E-MNET or a Molex SST-ENET module. Remember to update your IODevice in Citect accordingly to reflect these changes. Hope this helps!
✅ 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 ABMLXEIP protocol is being utilized to set up the IODevice in Citect.
Answer: Answer: There may be issues with the communication between the PLC and Citect.
Answer: Answer: The absence of the 1761 NET-ENI Module, and instead using the RJ45 port configured as an Ethernet Channel on the Micrologix 1400, could potentially be a reason for the communication problem.
Answer: Answer: Alternative steps or configurations may be required to establish communication without the 1761 NET-ENI Module, such as adjusting settings or using different modules.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.