Good afternoon, I am sad to realize but I have 8212 and exactly the same problem. If you connect a couple of times and disconnect the OPC UA Server falls and the issue is resolved by restarting the medium. Previously, they wrote that there are any bypass methods, what methods? What can be done?
I have a question, which firmware version of the firmware is stable OPC UA? What would be without this mistake?
Hello, soon a FW29 for codesys 3.5.21.10 will be available.
I personally haven’t been able to test it yet but it should solve a lot of OPC-UA problems.
Are there any exact dates for the firmware?
1 Like
FW29 for PFC100/200 (and accompanying WAGO support for CS 3.5.21.10) was released today. You can find it at
3 Likes
Installed, now I’m testing. There is an error, I don’t understand what is wrong? If you press the ignore button, everything connects without problems. I understand that there is some problem with the certificate?
Hallo TomasD,
do you work with the IP address or hostname? If you are working with the hostname, you also need to establish the connection accordingly with opc.tcp://PFC200V3-XXXXX and have a DNS resolution. If you are working with the IP address, you would need to make settings for encrypted communication. By default, without setting up, you need a connection via the hostname. A DNS resolution is then required in the network.
Setting at CODESYS:
After adjusting the settings, I would create the certificates again.
1 Like
Thank you. I made a video from YouTube officially about OPC UA. It was not said about these settings. In Help, I also did not see such a settings.
It feels like OPC UA use only I alone, since so many nuances are found.
Hello TomasD,
the feature/setting is new. CODESYS probably hasn’t updated the help for this yet. Previously, encrypted communication could only be done with the hostname.