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? [i…

If you are only needing to read the addresses over modbus TCP you could use the Modbus API with Docker. [WAGO PFC200 G2 Modbus Slave KBUS Docker Container] Also, for 128 modules please note that you will need to use KBUS extension modules (750-627 & 628).

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?

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. …

I did the same thing in 2.3, same settings. I have a problem downloading 3.5 libraries, I can’t try it. [image]

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…

Help me figure out wago 750-8212

CODESYS

WagoKurt February 24, 2025, 5:41pm 6

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.

Topic		Replies	Views
Modbus RTU an 750-653 codesys CODESYS	1	77	February 11, 2026
Wago 750-8212 cannot connect with Codesys 3.5 CODESYS pfc200	5	216	October 21, 2025
Codesys 2.3 Library CODESYS pfc200 , codesys	3	1444	April 21, 2025
Modbus RTU and 750-653 CODESYS pfc200	4	2676	October 9, 2024
Passwords in Wago libraries CODESYS	3	375	December 1, 2024

Help me figure out wago 750-8212

Related topics