I have a WEG CFW 500 Drive with the Modbus TCP/IP adapter card (CFW500-CEMB-TCP), I am trying to communicate with it via a IR-ETN40R, however, it seems that the CodeSys is coming up that the Modbus TCP Slave is not running.
I have confirmed with another software (modbus poll) that the CFW500 is accessible on the set IP address/port (192.168.1.111/502). Information does come into the Modbus Poll. However, when I reconnect to the Codesys, I still can not see this information.
I am using a Modbus TCP Slave of: 3.5.10.0
Hi @jonmarc91,
Could you please provide the information below?
- Network device diagram with IP addresses (so we have a better idea of what you’re trying to accomplish)
- Codesys version
- User manual for WEG device
Good morning @cody.bearden,
I can draw this more officially in autocad if needed today, its quite a simple setup I have going on here with almost a direct connection between the two devices with an unmanaged switch in the middle. When I do the connection for the Modbus Poll, I connect to the unmanaged switch.
Codesys: 3.5 SP15 Patch 5+
The user manual is two parts:
-
The Modbus Module itself: https://static.weg.net/medias/downloadcenter/hc4/hf4/WEG-cfw500-ethernet-manual-10003256290-manual-english-dc.pdf
-
The CFW500 Drive (for all other parameters): https://static.weg.net/medias/downloadcenter/hb7/h52/WEG-CFW500-programming-manual-10006739425-en.pdf
Hi @jonmarc91,
Thanks for the clarification.
The iR-ETN40R is an Ethernet I/O module not a CODESYS based PLC so you cannot download a CODESYS program to it and it cannot control other devices.
Hi @cody.bearden,
Can you explain that a bit more? We have multiple systems now that have Codesys downloaded to the IR-ETN40R, running in the field.
Hey @jonmarc91,
The systems you mentioned may be using an HMI with Codesys soft PLC functionality (like ours). This is what’s required to control remote I/O devices such as the iR-ETN40R.
Additional info can be found here.
@cody.bearden,
This is what makes me confused on the IR-ETN40R being a module only and not the PLC section. Originally was under impression this IR-ETN40R was really a IR-ETN plus additional ‘Built-in’ modules for a space saving and cost reduction. There was no use of a soft PLC to my knowledge in these designs.
When looking at the other forum: How to connect an iR-ETN or iR-ETN40R to Codesys
and
comparing against another Codesys projects that I have created already:
But ultimately, what you are saying is that I need to use a HMI (like a CMT3162x I have) to communicate with the WEG CFW500? The IR-ETN40R can not do this despite being a Modbus TCP server with the up to 8 connections?
Hi @jonmarc91,
Correct, you would need to use one of our HMIs with Codesys enabled to communicate with the iR-ETN. The Codesys-enabled HMI would act as the client/master, while the iR-ETN would act as the server/slave.
The iR-ETN40R is a module that functions as an Ethernet I/O server, meaning it responds to commands from a master but does not initiate communication itself. In a typical system, the master device, such as a PLC or HMI, controls the flow of data, sending requests or commands to the iR-ETN40R which operates solely in a responsive role. It waits for commands from the master before taking any action and remains idle without input. As such, the iR-ETN40R does not have the capacity to ‘control’ a device and also does not support controller-level aspects like CODESYS.
Thank you @cody.bearden,
This does make sense and I can use the HMI instead. One last question then in regards to communicating with the WEG now over the HMI. Is there a suggested option for breaking out a word into multiple bits via Easy Builder Pro?
Example, in the CFW500 manual, parameter 680 is the status word. Is there a way to view the specific bit inside of the word?
I can see some basic information, such as INT/FLOAT values.
Typically this is done by:
- Transfer device data to LW memory.
- Use the LW_Bit register to access the desired bit.
