Hello, I am relatively new to working with PLCs and have limited experience with GE PLCs. I am currently seeking assistance with downloading a pre-written PLC code using GE Proficy Machine Edition v9.5. The system consists of a Versamax Micro Plus Controller - IC200UDR064-EK, a QuickPanel+ HMI - IC755CSS06RDA-CR, and an ethernet module - IC200UEM001-DF. Additionally, a Weidmuller remote IO module - UR20-FBC-MOD-TCP-V2 is connected via ethernet to an unmanaged switch. I have successfully set IP addresses for all devices and confirmed connectivity through pinging. My query pertains to configuring the Weidmuller remote IO module within the GE program. Despite efforts to add the module as a target, I am unable to locate it within the hardware configurations. The option to add a module remains greyed out, and only GE modules are visible when attempting to add a target. Could the solution lie within PLC Access Drivers? Even after setting the IP for the "Device2" as the IP for the remote IO, communication with the PLC remains unsuccessful, evident by a Bus Failure LED on the remote IO. How can non-GE remote IO modules be integrated into a GE project and configured effectively? Where within the project tree can the remote IO data be accessed, particularly for viewing inputs and outputs related to the IO module?
The PLC model in question was not originally designed to work with remote I/O, so any solution will require a workaround to address this limitation. The Weidmuller remote I/O system utilizes Modbus TCP communication protocol. In order to integrate it with the PLC, the PLC would need to function as a Modbus TCP client, although this feature may not be supported. If it is supported, you would need to program logic using COMREQ instructions, although the speed may not be optimal. The IC200UEM001 'ethernet module' is actually a serial to ethernet converter. If the data from the remote I/O is solely for displaying on the HMI, you could consider having the Quick Panel serve as the Modbus TCP client instead of the PLC.
I want to express my gratitude for your assistance! I have located a device under Modicon TCP/IP within the PLC Access Drivers section, which I suspect to be the remote IO. This device is located under HMI, leading me to believe that the HMI serves as the Modbus TCP client.
Certainly! By utilizing the PLC access driver, you can configure the HMI to act as the Modbus TCP client. In the third screenshot you provided, make sure that "Device 2" is set to the IP address of the Weidmuller unit. As I do not have experience with Weidmuller remote I/O, I am unable to advise on how it maps its inputs and outputs to Modbus addresses. It is likely that discrete inputs are assigned 1xxxxx addresses, discrete outputs are assigned 0xxxx addresses, analog inputs are assigned 3xxxx addresses, and analog outputs are assigned 4xxxx addresses.
After troubleshooting, I discovered that "Device2" shares the same IP address as the remote IO, yet I am still experiencing a bus failure. Upon further investigation of the ethernet option module, I learned that the ethernet driver needs to be downloaded using the PumpKIN utility. Could this be the reason for the persistent fault? Additionally, the manual mentions that when the Ethernet option module is loaded with the Modbus image, it cannot communicate with PME (Proficy Machine Edition). What is the significance of this statement?
Although it is still causing a bus failure, what exactly is causing this fault message to appear? Additionally, the manual mentions that when the Ethernet option module is loaded with the Modbus image, it is unable to communicate with PME software. The VersaMax Micro ethernet option module acts as a serial to ethernet converter and can be configured to work with either ModbusTCP or GE's SRTP protocol, but not both at the same time. PME software relies on SRTP to communicate with the PLC.
It sounds like you’re on the right track so far, but from my understanding, GE's Proficy Machine Edition may not directly support the configuration of non-GE remote IO modules, like the Weidmuller one you're using. You might need to use the Weidmuller configuration software to setup the module first and then integrate it into your GE project. Regarding communication, I recommend re-checking the RSLogix 5000 settings; especially for the communication mode and correct data file pointers. The remote IO data, once incorporated effectively, should be accessible under the controller tag section to view the inputs/outputs associated with the IO module. Always remember to perform an upload/download cycle whenever changes are made to ensure the PLC and your Machine Edition project are in sync.
Hi there! You've got a pretty interesting setup. Working with external modules can sometimes be tricky with GE systems. From my experience, most GE PLC software doesn't support direct integration of non-GE modules. That might explain why you're only seeing GE modules when trying to add a target. However, for your Weidmuller IO module, there might be a work-around. Some have found success using OPC (OLE for Process Control) servers to integrate non-GE hardware. Essentially, the server acts as a translator between your PLC and the external module. Regarding your PLC Access Drivers, keeping your drivers up to date is crucial, so make sure they're in the latest version. As for accessing the IO data, for external modules, you would often see this within the server software, but again this can depend on the specific setup and software versions in use. Hope that helps and good luck with your project!
It sounds like you're off to a good start with your setup! When dealing with non-GE remote I/O modules like the Weidmuller, one common pitfall is ensuring that you've configured the relevant communication settings properly in the PLC program. Since you're using Ethernet, make sure that you've selected the correct Ethernet driver for the Weidmuller module in your Proficy Machine Edition project. You might also need to manually set up the connection parameters for the remote I/O module by adding it as a generic Ethernet device if it doesn’t show up automatically. Once it’s properly configured, you should be able to map your inputs and outputs in the project tree—typically under “I/O Configuration” or a similar section. If the issue persists, reviewing the TCP/IP settings and any potential firewall settings on your network can also help. Good luck, and don't hesitate to reach out if you need more detailed steps!
âś… 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: - To integrate non-GE remote IO modules into your GE project, you may need to use PLC Access Drivers or specific communication protocols supported by both the GE PLC and the remote IO module. Ensure that the IP addresses are correctly configured and that communication settings are properly set up.
Answer: - The option to add a module as a target may be greyed out because the software may not automatically recognize non-GE modules. In such cases, you may need to manually configure the communication settings and possibly use PLC Access Drivers to establish communication with the non-GE remote IO module.
Answer: - To access the remote IO data within your project tree, you will likely need to create specific data structures or tags that correspond to the inputs and outputs of the remote IO module. These tags can then be referenced in your ladder logic or HMI screens to interact with the remote IO module effectively.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.