Activity for TimvH
-
TimvH posted a comment on discussion Engineering 🇬🇧
Really not clear what you are trying to do, but isn't a Struct enough? So add an object of the type DUT to the Application. Then create a structure TYPE ST_Sensor : STRUCT sName : STRING; uiNumber : UINT; END_STRUCT END_TYPE Then in you application add an instance of this Structure stSensor1 : ST_Sensor := (sName := 'my sensor', uiNumber := 1); or use it like this stSensor1.sName := 'my sensor';
-
IF you create an ENUM {attribute 'qualified_only'} {attribute 'strict'} TYPE E_IO : ( FIRST := 0, SECOND := 1 ); END_TYPE You should be able to access the array items like: IOCard_OUTPUT[E_IO.FIRST]
-
IF you create an ENUM {attribute 'qualified_only'} {attribute 'strict'} TYPE E_IO : ( FIRST := 0, SECDOND := 1 ); END_TYPE You should be able to access the array items like: IOCard_OUTPUT[E_IO.FIRST]
-
IF you create an ENUM {attribute 'qualified_only'} {attribute 'strict'} TYPE E_IO : ( FIRST := 0, SECDOND := 1 ); END_TYPE You should be able to access the array items like: IOCard_OUTPUT[E_IO.FIRST]
-
If you have a Windows system (RTE), then why not run the CODESYS HMI as separate controller. This could easily be moved to another PC if required. In the HMI you could also still use the Symbolic Var access as part of the Data Source Manager, although maybe OPC is the preferred way to make it more future proof. Or what about the Remote Target Visu. Then you can reduce the load of the main controller, while still only having to create one application including Visualization. This is now also supported...
-
You could create a DUT of the Type Union and add an array of 2 bytes + an Int. Then write the byte values in the array of the Union and read the Int. Or VAR iInt : INT; byHigh : BYTE := 2#1111_1111; byLow : BYTE := 2#1111_1111; END_VAR iInt := TO_INT(byHigh*16#100 + byLow);
-
If you are not using any specific Raspberry Pi functionality, then probably the "universal" Control Linux ARM SL is the approriate runtime to run on the Pi. For the license it doesn't matter which runtime version you choose, because this is not hardware based anymore, but application based. Best is to use the latest version of CODESYS. To determine which license you need, double click on your device, go to the tab License metrics.... Generate the code for your application and see which license you...
-
You have declared the function block in a function and call the instance also from a function. This is not correct, because a function is initialised with every call. The http client function block should be declared as Global Variable if you want to cal it from a Function, but probably it is better to declare it in a Program and also call the instance of the http function block from the same Program.... The variables of a Program are not initialised with each call.
-
If your Control Win is the Modbus "Master" then your configuration should be something like: Modbus_COM (Serial port) - Modbus Master (this is the Control Win SoftPLC actively setting up the communication) - Modbus Slave (this is then your WAGO 750-315) You need to add channels to the Modbus Slave configuration to inform the master which variables to read/write from the Wago module. The way you configured it now, the Control Win is also a slave. PS, don't forget to put the PLC (Control Win) in R...
-
You cannot create an array of Programs. Create a Function Block for this purpose instead of a program. You can create an array of FB instances and call each instance in a loop.
-
First of all you need to enable "Use unicodestrings" in the Visualization Manager. This function returns a pointer to a WSTRING (not STRING). To get this wstring value, do something like this: VAR myWstringVariable : WSTRING(255); END_VAR myWstringVariable := myResult^; // this is dereferencing the pointer to the WSTRING.
-
https://content.helpme-codesys.com/en/CODESYS%20Git/_git_using_scripting.html
-
With new runtimes, the access outside the runtime folder is protected. See: https://forge.codesys.com/forge/talk/Engineering/thread/3da9ded84e/
-
I think, that if you set the timebase to T#0s, that it will be reset. But you can also make your own ramp down with a Timer (make sure the PT time is not T#0s):
-
I think, that if you set the timebase to T#0s, that it will be reset. But you can also make your own ramp down with a Timer:
-
The string_Util_Intern is not the library I referred to. With a CONCAT function (also with the string util library) a search is done for the NULL character. If you concatenate 20000 characters to one string, then the longer the string, the longer it takes to find this NULL character.
-
Create a (global) array of Messages: aMessage : ARRAY[0..NR_OF_MESSAGES-1] OF CAN.RxMESSAGE; Then add each received message to the array. IF UserVarGlobal.g_countMsg_RPMset < NR_OF_MESSAGES THEN aMessage[UserVarGlobal.g_countMsg_RPMset] := Message; UserVarGlobal.g_countMsg_RPMset := UserVarGlobal.g_countMsg_RPMset + 1; END_IF
-
See: https://forge.codesys.com/prj/codesys-example/element-collect/home/Home/ This contains an application "OnlineChangeSafeLinkedListExample". What you should do is create a new interface which has your "Priority" property. Then your FB should extend the base element function block and implement your own interface: E.g. FUNCTION_BLOCK MyElement EXTENDS COL.LinkedListElementBase IMPLEMENTS I_MyInterface Then the __QUERYINTERFACE does the magic to check if your "element" also implements your interface....
-
The new (UTF8) string library is faster and can handle large strings. https://content.helpme-codesys.com/en/CODESYS%20String%20Libraries/_strlib_start_page.html PS, in CODESYS, the maximum string length is not 255 characters. The String functions of the standard library are limited to strings of 255 characters. But you can use other (memory) functions to handle strings larger than 255 characters.
-
https://forge.codesys.com/prj/codesys-example/file-utilities/home/Home/
-
Their is quite a detailed explanation in the help: https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_codesys_modularization.html
-
See: https://content.helpme-codesys.com/en/CODESYS%20FAQ/_faq_start_page.html
-
The message means that you (CODESYS) tries to open the function block, but this is not possible because the library which contains the FB is compiled. You either get this when you try to manually open the function block (while editing the application), but it could also happen that an exception occurs in the running application and CODESYS tries to show the location where it occured. If it happened in an FB of the compiled library, it cannot show this and you could get this message too.
-
See: https://content.helpme-codesys.com/en/CODESYS%20Examples/_ex_canopen_canopen.html SDO example: SegmentedAndBlockWriteExample: Writing if an object of any length via SDO (segmented transfer or block transfer) by means of CiA405.SDO_WRITE_DATA This help page also contains a link to a demo project.
-
You could use the Modulo function to get the minute part from the total minutes: Minutes := TotalMinutes MOD 60;
-
Your function block instance is not called, so the code is not executed to set the light on when the button is pressed.
-
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.
-
Most likely related to the Device Diagnostics functionality. Double click on your device (PLC), go to the tab "PLC settings". Enable the advanced option "Enable diagnosis for devices". Build your application again.
-
You should only open de COM port once and then leave it open. This hCom should not keep on incrementing. (off course when you are done communicating, you need to close the COM port)
-
In your project you selected the "CODESYS Control Win V3" as device, but the device you want to connect to is a "CODESYS Control Win V3 x64". Those are not the same. If you double click on the device during the network scan, you will get information that these are not the same, but that you can change the type in your project to the x64 bit type. Another option is to "right-click" on the device in the device tree of your project and select "update device" then select the x64 type.
-
See the attached pdf with some notes (screenshots) which I prepared for one of our customers to help them get going. Hopefully this helps for you too.
-
Add the object "POU for Implicit Checks" to your application, then select "Bounds check". This will create a function which is automatically called each time an array is write accessed. In the function you can handle "out of bounds" situations. By default it will be limited to its lower or upper bound.
-
Use e.g. the condition: TCP_Connection_0.xActive AND NOT(TCP_Write_0.xDone)
-
I don't know the root cause... But what could help to continue when it seems to hang, is stop the CODESYS (communication) Gateway. Go to the Windows SysTray, find the icon for the Gateway and then stop it and start it again. This will interrupt the connection between CODESYS and your controller.
-
You should ask IFM to provide you with the correct version of their controller packages. Then after you have installed this, you can select the correct version of the controller by right clicking on it in the device tree, update device, enable the option "Display all versions" and then select the version which matches your controller. Alternatively you can ask IFM to provide an update package which can update the runtime version on your controller to 3.2.0.0.
-
Are you 100% sure you created a boot application?
-
Not sure, but maybe it related to the style. Go to the Visualization Manager in your project and see if a style is selected, or choose another style to see if this helps.
-
Are you using the Control Win SL (installed together with the development environment of CODESYS)? If yes, you might want to consider using the CODESYS RTE instead. This has real-time capabilities (running on separate core(s)). But to be able to use this, you have to install the CODESYS Ethernet driver for your network interface to be able to let the RTE access the network port also in realtime. See: https://store.codesys.com/en/codesys-control-rte-sl-bundle.html https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_windows_rts_v3.html...
-
Are you using the Control Win SL (installed together with the development environment of CODESYS)? If yes, you might want to consider using the CODESYS RTE instead. This has real-time capabilities (running on separate core(s)). But to be able to use this, you have to install the CODESYS Ethernet driver for your network interface to be able to let the RTE access the network port also in realtime. See: https://store.codesys.com/en/codesys-control-rte-sl-bundle.html https://content.helpme-codesys.com/en/CODESYS%20Control/_rtsl_windows_rts_v3.html...
-
This is almost always related to previously working with an additonal monitor. If you have placed CODESYS on that monitor, later start your laptop again and open CODESYS without that monitor, then Windows still places it in the previous position, but then it is not visible. So the solution by cehermanstad can be used to move it to the main screen to make it visible again. PS, another way to move it, is by pressing SHIFT and then right-click on the icon in the task bar, then select move. You can then...
-
I'm not sure, but maybe you have to configure the 750-652 first with the WAGO-IO-CHECK software to set it in RS485 mode?
-
You have selected the new Ladder editor. This only has these items in the toolbox.
-
The IoT library contains a Web Socket library. Maybe this provides your required functionality. See https://store.codesys.com/en/codesys-iiot-libraries-sl.html
-
It is part of the IoT library. See: https://store.codesys.com/en/codesys-iiot-libraries-sl.html
-
if you just want to show the currently logged in user in the visualization, then just create a field with text %s and as text variable VisuElems.CurrentUserName
-
Yes, it is possible to set breakpoints and use step into / step over (also in Ladder diagram). Yes, the PLC will actually stop, so be carefull with this. How a PLC works is that at the start of the execution of the Task, the Inputs are read, then the code is being executed and then the outputs are written. So if you set a breakpoint, you will not see your analog inputs changing, because the task cycle is interrupted and the inputs and outputs are not refreshed. For detailed information, see: htt...
-
It depends on your application which CPU speed and RAM size you need. If you think the Control Standard S license is sufficient then my guess is that your selected PC has no problem running your application. There are no more "hardware" based single licenses available anymore, only application based licenses. So this "Raspberry Pi" restriction for home automation is not applicable anymore. For more information see: https://store.codesys.com/en/howto_applicationbasedlicenses
-
The Epis controller should support the CodeMeter driver to be able to access the license containers on the CODESYS Key.
-
To prevent ambiguous use of this enumeration value. Let's say another ENUM is available in your project or in another library which has an enumeration value AM_WRITE, then it is not clear which AM_WRITE you want to assign. By this qualified access to the SysFile.AM_WRITE, it is completely clear for the compiler.
-
Maybe the CODESYS HMI is a good solution. https://store.codesys.com/en/codesys-hmi-sl-bundle.html Run this on the remote main control station. In the HMI application you can add the data source manager and to this manager you can add Data sources. A data source has a reference to the PLC you want to connect to and can get access to the variables of the PLC application. You can then use these variables in the visualization of the HMI application.
-
I had a similar error "Invalid ERR Ack input". What you need to do is link an variable from the "non-safe" PLC to the Group IOs of the POU in the Safety app. * Add a POU to the SafetyApp (probably already done, otherwise you don't get this error) * Right click on this POU - select properties * Go to the Group IOs tab * Link a variable to the Err.Ackn. input I don't know about the Size of zero, I didn't get this error. Were you able to fix this?
-
I'm not sure what you are trying to do, but getting the CurrentUserGroupID like this will not work, because there could be multiple Visualization Clients and each can have a different user that is logged in. Also when you go online with CODESYS and open an Visualization, this is counted as a client. Probably this is the reason you see it changing. What you can to is "iterate" over all clients and then see which user is logged in on which visualization Client. For this you need to add the Visu Utils...
-
You can use the (open source) FTP client in Forge. This works on 64 bit systems. See: https://forge.codesys.com/prj/ftp-client/code/HEAD/tree/ As this is open, the idea is that when you use it and make improvements to the source code, that you also commit this in a branch so others can also benefit from it.
-
copy paste?
-
I think you want to implement client side scripting? Maybe creating HTML5 objects is an option, because the JavaScript is executed on the client side. See html5
-
What maybe helps is the Visu Dialog ST demo project: https://store.codesys.com/en/visu-dialog-st.html This has an application IECOpenDialog where dialogs are opened using the VU.FbOpenDialogExtended function blocks. The fbOpenConfigurationDialog call has a reference (interface) to the "close listener" FB of which it's method is automatically called when the dialog is closed. This way you can create specific function blocks for each dialog when it is closed and do what you want with the data that...
-
I'm not really sure what you are trying to do, but maybe you are referring to using the CmpCharDevice library? When you "open" the connection to a device, you can pass flags. What helped me is to set the non-blocking flag. I'm not sure if this is what you are referring to, but maybe it helps: dFlags: DINT := CmpCharDevice.ACCESS_MODE.O_RDONLY + DINT#4000; // see details for flags: http://linux.die.net/man/2/open, + DINT#4000 is for non-blocking hDevice := CmpCharDevice.CDOpen(szFilename, dFlags,...
-
https://en.wikipedia.org/wiki/Modbus
-
Maybe there is a better way, but a long time ago I created a test application that worked like this: With a button I opened the dialog and I added a "Input configuration - OnDialogClosed" "Execute ST-Code" action to this same button which called the following Function when the dialog was closed: F_OnFileDialogClosed(pClientData); Below this Function which handled the result: // This function is called from the visualization when the dialog is closed. FUNCTION F_OnFileDialogClosed : BOOL VAR_INPUT...
-
In the example project, you can see that a CAN.CANAreaReceiver is used which has an VAR_IN_OUT reference to a RECEIVER_AREA structure. This structure has a dwIdStart and dwIdEnd to filter a range of ID's and process them through the referenced msgProcessor.
-
In the example project, you can see that a CAN.CANAreaReceiver is used which has an VAR_IN_OUT reference to a RECEIVER_AREA structure. This structure has a dwIdStart and dwIdEnd to filter a range of ID's and process them throught the reference msgProcessor.
-
On a PC with the Control Win, this is probably related to the fact that the CAN drivers are not loaded. Go to the folder where your Control Win Configuration file is: - E.g. C:\ProgramData\CODESYS\CODESYSControlWinV3x64\E1FA7ABE - Open the CODESYSControl.cfg - Remove the semi-colon in front of the CAN driver you want to use (section ComponentManager). - Set the component ID to the next number in the list (e.g. Component.8) - Save this file and restart the Control Win.
-
For a demo application related to date/time, see: https://forge.codesys.com/prj/codesys-example/date-and-time/home/Home/
-
You will need a USB to RS485 converter to connect the PC to the Modbus RTU Slave Device. In Windows this converter will be recognized as Serial COM poort (e.g. COM2, or COM3, see the windows device manager to find this out). Select this port in your CODESYS application. On the PC you need to use the CODESYS Control Win (SoftPLC) to run your application. It will not work in simulation mode, because then the Modbus Communication will not be activated.
-
Maybe select the local gateway instead of the gateway on the remote device?
-
You need to start the application, see the "start" option at the top left (next to close simulation).
-
Maybe the following helps: https://forge.codesys.com/prj/codesys-example/modbus/home/Home/
-
Look all the way at the end of the link below. This provides a way to use arrays with various lengths: https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_datatype_array.html
-
You are trying to make something very simple really complex, but my best guess is that the order of execution is: - initialize FB (x becomes 1) - Load persistent (x is 1) - start application (x remains 1) PS, It could also be that your "persistent" variables are not stored correctly and that, at startup, the value is always 0. Did you add this variable to the Persistent Variable list? And did you make sure that this works correctly on the device you are using? So maybe the execution order is: - load...
-
It is a naming convention. Nothing else. Most often you see this being used for the local (private) variables of a Function Block. It comes mainly from C++ / C# to not mix them up with (public) properties. Probably best is to search for C++ naming conventions to get more information.
-
go to the library manager of your project click on Add Library (top left corner) type in CAA Memory - you will see it in the list. If not, and you don't have the latest version, maybe you have to select Advanced first. then double click it to add it to the library manager of your project. Then you can use the functions from it in your project.
-
Maybe you should not use SIZEOF, but LEN. Because SIZEOF means you will get the memory size of your string variable (e.g. maximum 80 characters), but LEN will give the actual length of the string.
-
Maybe you could use the "CAA Memory" library for this. This library contains a function MemMove. Here you can specify the pointer to memory of your source and target and set the number of bytes to "move". To get the pointer to your array of 18 Words, use ADR(nameOfYourArray) to get the pointer to it's memory location.
-
See https://faq.codesys.com/pages/viewpage.action?pageId=1310825
-
In recent CODESYS versions you can go to the device settings (similar location where you scan the network for your communication settings with your controller). Here is an additional entry (tab) called "Licensed software metrics". This will give you all information you need. See also: https://content.helpme-codesys.com/en/CODESYS%20Development%20System/_cds_f_obj_device.html and https://store.codesys.com/en/howto_applicationbasedlicenses
-
Most likely you use a Runtime of SP19 or higher, because starting from this version the default setting is that only access to files in the PLC folder are allowed. This is for security reasons. You can allow the runtime to access files outside of this folder, but you have to modify the CODESYSControl_User.cfg. For the exact file name and it's location, see: https://faq.codesys.com/display/CDSFAQ/Location+of+the+configuration+file Or ask the vendor of your PLC. One option is to set the IecFilePath,...
-
I'm not sure, but I guess it has the attribute 'no_assign'. Probably it is better to use a reference: VAR_INPUT slave : REFERENCE TO IoDrvModbus.ModbusSlaveComPort; END_VAR
-
Added projectarchive 3.5 SP18 P3
-
The example project, which is included in the package, shows an example with CFC program (CFC_PRG). This calls the FB MsgProcessor_EchoCFC. This FB calls a method ProcessMessage, which calls the FB CAN.CANSender. This has a reference to the interface of the CANDriver and a reference to the Message you want to send. So you could use this FB to send any CAN message. The Message is a struct: TYPE MESSAGE : STRUCT udiCanID : UDINT; (* CAN-ID (Communication Object Identifier) is the bitId of a CAN-frame...
-
Hi Ben, you are right, I answered too quickly. You need to send a message with own defined COB ID. Probably the CAN Level2 communication is your best option. There is an example project available which contains a library that encapsulates this communication method to access it in an OOP way. See the store: https://store.codesys.com/en/canbus-example.html In the package is a library and an example project. Hopefully this helps.
-
CSV is short for comma separated value. So add comma's between your values. Probably you want to open it in Excel, then it depends on your country settings what your default delimiter is. In some cases a semi-colon could be better/easier than a comma, but this has nothing to do with CODESYS.
-
I think you just installed the library in the repository and then used it, but the idea is that you can open the library in CODESYS and edit it. And yes, you can then change the layout, use other characters, so you then make your own dialog. You can then change the library information (menu: Project - Project Information - Summary). Enter you Company name, Title of the library and Version, then install it in the library repository and use it.
-
I'm not sure you want to go in this direction, because the example below contains code which is marked as obsolete, but the library mentions that if no other option is possible, then it could be an escape... so be warned 😬 Add the following code to your "HandleClient" method xChangePage : BOOL; itfVisuClientRawData : VU.IVisualizationClientRaw; xQueryOK := __QUERYINTERFACE(itfClient, itfVisuClientRawData); IF xQueryOK AND xChangePage THEN VisuElems.g_VisuManager.SetMainVisu(pClientData := itfVisuClientRawData.ClientDataPointer,...
-
I'm not sure you want to go in this direction, because the example below contains code which is marked as obsolete, but the library mentions that if no other option is possible, then it could be an escape... so be warned 😬 Add the following code in you "HandleClient" method xChangePage : BOOL; itfVisuClientRawData : VU.IVisualizationClientRaw; xQueryOK := __QUERYINTERFACE(itfClient, itfVisuClientRawData); IF xQueryOK AND xChangePage THEN VisuElems.g_VisuManager.SetMainVisu(pClientData := itfVisuClientRawData.ClientDataPointer,...
-
Maybe this helps: https://forge.codesys.com/prj/codesys-example/visudialogs/home/Home/ ?
-
https://forge.codesys.com/forge/talk/Engineering/thread/ea23226bbe/
-
Unused inputs/outputs (not used anywhere in your application) are not updated by default by CODESYS. See: https://faq.codesys.com/pages/viewpage.action?pageId=106889249 for more information. PS, putting the PLC in RUN could also help :-).
-
It is not clear what you want to do, because a DWORD contains 32 bits. If you just want to get a certain bit out of the DWORD, you could use e.g.: xBool := dwDword.0; If this is not what you want, then please specify which 4 bits you would like to have as output of the function.
-
Ask the company which sold you the PLC.
-
Probably you have to delete the cmact_license folder first and then reboot. See the FAQ about this (is for RaspPi, but similar for PFC): https://faq.codesys.com/pages/viewpage.action?pageId=1310825
-
I'm not sure if I understand it correctly, but on an Android device you could install the CODESYS Web View. But your controller should then support the WebVisu to show the visualization in this "web app". See: https://play.google.com/store/apps/details?id=com.codesys.webview&hl=nl&gl=US
-
You can read the status of the license from your application through the CmpCodeMeter library. See https://forge.codesys.com/forge/talk/Runtime/thread/1c1b00cfc7/ So the code could be something like (change the numbers according to the licenses you are searching for): VAR // add CmpCodeMeter library xCheckLicense: BOOL; xFound: BOOL; Handle: CmpCodeMeter.RTS_IEC_HANDLE; Result: CmpCodeMeter.RTS_IEC_RESULT; END_VAR // check for valid Raspberry Pi license IF xCheckLicense THEN xCheckLicense := FALSE;...
-
As I understood it, the benefit of using the functions from the VisuUtils library are: - not required to call these functions from the Visu Task - end-user friendly call of function blocks (follows the common behaviour model) - future proof (backward compatible) - ... So you are motivated to use the function blocks from the VisuUtils library. Off course these are function blocks and you have to call them over multiple cycles until xDone is TRUE, because internally it has to wait until the visualization...