Hi, I use wago 750-8212 in conjunction with 750-432 module (there are 3 of them) and 750-600 at the end, I use target WAGO_750-8212/xxxx-0001 on codesys 2.3. I can’t count the modbus request that the module is working, although everything is visible through codesys. What solutions can there be?
Hello, what are you trying to do ?
Write the variables or read them ?
What is the function code ? Address ? size ?
It is modbus TCP ? UDP ? RTU ?
I’m trying to get responses via MODBUS TCP
I showed what firmware is on the device, and that using Codesys, I see that there is a short circuit on the 3rd input, I send a request and see that 0 comes instead of the values
Read in the manual of 750-8212 about MODBUS mapping and process image, it will be helpful.
for example you can read digital inputs (IX) directly via modbus without programming.
I have two instructions, in one I found that it is possible to configure modbus TCP using codesys 2.3, and in the other that it is only the codesys 3 version, but there are problems with version 3, I cannot download the targeting file library for the PFC200. Can I try to update the firmware?
Hello, here is a video showing different ways you can update the Firmware on a PFC200. Note that the newer FW only support C3.5.
I’ve rechecked a lot of firmware, but I still couldn’t get a modbus response, I close the jumper on the 750-432 module and the answer is 0 anyway, what could be the matter?
In Codesys 3.5 you cannot access the IO modules directly with modbus like in Codesys 2.3. There are some that actually prefer 2.3 for this reason, but 2.3 is now discontinued by Codesys.
What you need to do is add an Ethernet > Modbus TCP slave and then create an entry for your modbus registers. Then you can map the IO points to those registers. It is not difficult, but requires a few clicks to set it up.
I did the same thing in 2.3, same settings. I have a problem downloading 3.5 libraries, I can’t try it.
Hello, I recommend updating the Firmware to the latest if trying C3.5. The version that supports C2.3 is several years old and only supports WAGO’s e!COCKPIT (old version of C3.5).
I found how to do this, installed 3.5, found the wago libraries, but now it won’t let me access the device, it says “Local\Temp\mzpuddiu.1cj\ProductCodesIn.csv.out’” not found. and error C0018: ‘MBHolding[0].1’ is not a valid assignment object Compilation completed – 1 error, 0 warning : download is not possible, I did it based on your screenshot
I’ll start from the beginning, I have software, it should poll wago 8212 using ModbusTCP, it has 9 750-432 modules installed, I can close 1-4 inputs, and I want to receive an answer using ModbusTCP
It looks like your program is setup correctly. Maybe the issue is the client? You could try this free one → [CAS Modbus Scanner]
…or NodeRED works great for testing too.
Make sure IO Check is not in control mode when testing, it takes over the KBUS when running.
2 Likes
and then how do I make the address start with 1? or don’t even try, but also update the firmware and do 3.5
Hi,
when I decode your request correct, you are sending it directly with a TCP request, therefore the MBAP Header 00 01 00 00 00 06, then comes the actual modbus request 01 01 00 01 00 08.
This means Modbus ID 1 (normally for Modbus TCP it is 255, but the WAGO devices seem to ignore it).
Then FC 1 (Read Coils).
Starting Coil address is 1
Number of Coils to read 8
To read your output data, you have to use another FC and coil addresses.
Check your configuration in the modbus configurator, in column ‘Fieldbus access’ you see the FC to use and the address.
I set the offset flag to %MD0.0, but I still can’t see the data, I have 2 pcs of wago 750-8212, one on codesys 2.3 and the other on codesys 3.5, with 3.5 I realized more than once that I need to shift by 10 registers, but with 2.3 I don’t, I haven’t swapped them yet. it turned out, and so I decided to do it by analogy with 3.5, but without any results.
my task is to connect 128 750-432 modules, as I understand it, I need to name each module and then link it to the output in the same way? can this be simplified somehow? and I’m faced with limitations, so it turns out that you can have no more than 150 signals?
If you are only needing to read the addresses over modbus TCP you could use the Modbus API with Docker.
Also, for 128 modules please note that you will need to use KBUS extension modules (750-627 & 628).