TimvH

If it is a BOOL, then use: ...Error_Active := ALARM BOOL: ALARM INT: STATE

Do you mean this: https://content.helpme-codesys.com/en/CODESYS%20Communication/_comm_use_dynamic_opc_ua_server_comm_settings.html

Probably best to call the FB continuously. So something like this could solve it: IF xOpenLatchSettingDialog THEN xOpenLatchSettingDialog := FALSE; fbOpenLatchSettingsDialog.xExecute := TRUE; END_IF IF fbOpenLatchSettingsDialog.xDone OR fbOpenLatchSettingsDialog.xError THEN fbOpenLatchSettingsDialog.xExecute := FALSE; END_IF TopLeftDialog.iX := 100; TopLeftDialog.iY := 23; fbOpenLatchSettingsDialog( itfClientFilter:= VU.Globals.OnlyTargetVisu, sDialogName:= 'visu_AlarmLatchSettings', xModal:= TRUE,...

Minimum version is 3.5 SP19 Patch 3. See https://store.codesys.com/en/codesys-git.html But you could ask your PLC vendor if it is possible to program their PLC's which have Runtime version SP16 with development version 3.5 SP19 or higher (should normally be possible, but with Safety PLC's there could be some regulation limitations).

I don't know the details of jsonArrayWriter, but the common behaviour for an xExecute input is that the FB starts on the trigger that it gets TRUE. In your case xExecute is never FALSE, so it is never triggered again to start the jsonArrayWriter. So change the condition from TRUE to a variable which you set to TRUE with the "xFirst". Then when the jsonArrayWriter is done (xDone), or has an error (xError), then set this variable to FALSE.

If you use 3.5 SP10, then Git is not supported. SVN will work fine, but with this version you do need a USB key, because software licenses are not supported with this version. Off course you can work without SVN (or Git), but especially if you work with multiple developers on one project, it will save you a lot of time and you can keep track of all changes and improvements much easier. So how much is this worth to you?

What we are trying to explain is that, yes CODESYS creates the software, but Epis decides how they implement it on their hardware, which runtime version they use and they decide which functionality they support. So it is always a combination of the two. What CODESYS provides is a runtime with options for e.g. visualization or softmotion. Epis could add this softmotion license as default to their controller, but if they don't then CODESYS provides another option with a single license in a "Wibu CodeMeter"...

Maybe also good to know that you could use the CODESYS installer to switch between gateways. - open the CODESYS installer - Select the (hamburger) menu - Select Settings - Select Services Then select the Gateway you would like to use.