TimvH

To get the current visu for all your individual web clients, you could iterate over them, using the same library 1) Create a new function block which implements VU.IVisualizationClientIteration 2) Create an instance of this function block + add an instance of the "iterate" function block fbIterateCallBack : FB_IterateOverClients; // this implements VU.IVisualizationClientIteration fbVuIterate : VU.FbIterateClients; // this FB iterates over all clients 3) Call the fbVuIterate and set the reference...

To change the current visualization for (all) webclients: Add the library “Visu Utils” and use the following example code: VAR xChangeVisu: BOOL; fbChangeVisu : VU.FbChangeVisu; END_VAR // Change to Visu2 when setting xChangeVisu to TRUE fbChangeVisu( xExecute:= xChangeVisu, xDone=> , xBusy=> , xError=> , itfClientFilter:= VU.Globals.OnlyWebVisu, //itfFilter, eError=> , sVisuName:= 'Visu2'); IF fbChangeVisu.xDone OR fbChangeVisu.xError THEN xChangeVisu := FALSE; END_IF

As far as I remember, the Reconfigure functionality doesn't work for Modbus devices. But... Each Modbus device in your device tree has a name. You can set the property "Enable" of this device to FALSE to stop communicating with it. So if one of your Modbus Slave devices name is "MbSlave1" in the device tree, then in your code you can set the Enable to FALSE to let it stop communicating: MbSlave1.Enable := FALSE; Please let us know if this worked on your controller with your application and your CODESYS...

In the Control Loop Library package are multiple example projects, including one for the filters. Program containing: GVL.filterIIR( xEnable:= GVL.xEnableFilter, lrValue:= GVL.lrYOriginal, lrFilteredValue=> GVL.lrOutputIIR); GVL.filterFIR( xEnable:= GVL.xEnableFilter, lrValue:= GVL.lrYOriginal, lrFilteredValue=> GVL.lrOutputFIR); GVL.filterSOS( xEnable:= GVL.xEnableFilter, lrValue:= GVL.lrYOriginal, lrFilteredValue=> GVL.lrOutputSOS); GVL containing aCoefficientsA_IIR : ARRAY[0.. 4] OF LREAL := [1,-2.3695130071820376,2.31398841441588,-1.0546654058785676,0.18737949236818494];...

There has been a fix in SP21. I tried it in this version with the option "Use unicodestring" enabled in the Visualization Manager and it worked if the variables used for the function are declared as WSTRING variables wsFormat : WSTRING := "%t[HH:mm:ss dd.MM.yyyy]"; wsTime : WSTRING; IECStringUtils.FormatDateTime(cbpResult := ADR(wsTime), uiResultCapacity := SIZEOF(wsTime), cbpFormat := ADR(wsFormat));

You should not use the "open dialog" to change the value. Instead use the input configuration "Write Variable" to change a variable value in the visualization. in the setting of this input command, you can choose the Input type (select dialog).

Not sure, but maybe before you enter step 5, set i, lineindex and charIndex to 0. And the buffer variable should have a size bigger than 1 line. Additionally I think you should set bufferstart to 0 before you enter step 5. And in the OSCAT function you always point to the buffer address, but shouldn't this be (buffer + bufferstart)?

If you want to use the Test Manager, I prefer to start all the tests through the scripts of this manager. So open from there the projects, load it and run it. If you also want to use Python scripts to access CODESYS functionality, while executing a Test Manager script, then also start them from the Test Manager commands.