It is a known issue. It only happens with CODESYS and Wago controllers and the Persistent Variables. It seems related to using 64 bit variables in the PV list (e.g. LREAL). Internally in the PLC everything works okay. It is just a monitoring issue.
It seems like a bug in FBD. Work-around: If you click on the small line between the box and the output variable and delete this, the variable is removed. When you then assign a variable again (Ctrl-A), then you will see that the line will be a bit longer. If you then select the previous variable, you will see that it works.
have you tried: VisuElems.VisuStructClientData ?
For the Virtual Control you need to use a "Network license". The Virtual Control has parameters of which one is the reference to the license server. This can be the device itself, but you need to activate the license on the host system (not in the container). For this, CODESYS has a Network License server with WBM (web based management). See for the Network License configuration: https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_license_controller_linux.html If it is only for evaluation,...
Yes, this is possible with the Toolkit. We only server customers in the Benelux that do this, so contact your local CODESYS distributor, or contact the sales team of CODESYS Germany.
it should be something like: fbWebClient : WEB_CLIENT.WebClient; You need to use the "Namespace" of the library, not the name of the library itself.
If you are a vendor of controllers and want to have your own CODESYS Runtime on your device, then you need to contact the CODESYS Sales team and ask for the runtime Toolkit. For resellers of CODESYS devices, this can be interesting. If it is only for a few devices, then why not just take the standard runtime?
In the VPLC configuration settings there is an entry for the IP address of the license server. In this setting fill in the IP address of your device (host IP address). Then when the virtual PLC starts up, it will get the license from the license container on the host. You can do this for all VPLC's running on your device. The VPLC will always take the smallest license which fits the required license. So if you have 2 licenses for VPLC's with small and large applications, then this will work fine...