Put %f in the "text" field and rValue in the "Text variable" field. You could also have a look at the possible placeholders: https://content.helpme-codesys.com/en/CODESYS%20Visualization/_visu_placeholder_with_formatting_sequence_in_a_string.html
I would definitely try using the "Reconfigure" function block from "CAA Device Diagnosis@ library. https://content.helpme-codesys.com/en/libs/CAA%20Device%20Diagnosis/3.5.17.0/CAA-Device-Diagnosis/Function-Blocks/Reconfigure/Reconfigure.html#:~:text=This%20function%20block%20reads%20and,take%20effect. Although I have not tried it with Modbus, I had great success with EtherNet/IP, Profinet and EtherCAT. You can also have a look at the other functions in this library. There are useful functions to...
I have been running Codesys IDE in VirtualBox on a Linux Mint host for many many years without issues. I use it every day and it works great. I wouldn't mess around with wine. Would probably just be a waste of time. Codesys Go might be the future of PLC programming on Linux! Can't wait to test it.
Not sure this will help you but I had the same issue and was able to activate the license on a Windows PC using the Web Depot in a web browser. https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_installing_license.html
Hello, I tried installing ControlWin 3.5.20.40 and still have the same issue. I tried on 2 different PCs running Win10 Enterprise 2016 LTSB So I then installed the Gateway from 3.5.20.20 and it works. Is there an issue using ControlWin 3.5.20.40 with Gateway from 3.5.20.20? Thank you
Using Wireshark, I can see that the broker sends the QoS 1 or 2 messages when Codesys MQTT client reconnects but they are just discarded and not acknowledged by Codesys MQTT Client. So the broker holds on to them and tries to send them back to Codesys every time the client reconnects but they are always discarded by Codesys. There really seems to be an issue with QoS 1 & 2 in Codesys. It really does not behaves like it should.
Using Wireshark, I can see that the broker sends the QoS 1 or 2 messages when Codesys MQTT client reconnects but they are just discarded and not acknowledged by Codesys MQTT Client. So the broker holds on to them and tries to send them back to Codesys every time the client reconnects but they are always discarded by Codesys. There really seems to be an issue with QoS 1 & 2 in Codesys. It really not behaves like it should.
Hello, After some more tests, here is what I found out. It seems we have to increase the uiKeepAlive and tPingInterval parameters. If I increase the uiKeepAlive value to 60s and the tPingInterval to 30s, then if I disconnect the ethernet cable from Codesys and publish some messages to which Codesys subscribes to and then reconnect within 30s, I will get the messages. If I don't reconnect the cable within 30s (ping interval), the client goes in error with "ACKNOWLEDGE_TIMEOUT". When this happens,...