Home ^{Object Oriented Programming (Extended) home (WikiPage)}
Download project Object Oriented Programming (Extended) Product description More information System requirements and restrictions Object Oriented Programming (Extended) This example demonstrates how object orientation is used to realize a building which has different rooms with different functionalities. The included visualization illustrates the implementation. Product description This example demonstrates an object oriented programming approach. Therefore a building with different rooms and functionalities was implemented. At daytime, all the light bulbs are switched off and the air condition is set to 21. At nighttime, all light bulbs are switched on and the temperature is set to 15. With the manual mode, the light can be switched on and off separately. The "cellar room" has one light but no service is provided. The "cheap room" also has one light, but additionally a service is provided which changes the light bulb when the end of its lifetime is reached. The "better room" has a duo light with the doubled lifetime of a normal room and the "climate better room" additionally has an air conditioner, where the filter has to be changed after a certain amount of temperature changes. More information Main: Creates all the four rooms and calls the necessary functions, depending on the mode (daytime, nighttime, manual). clsRoom: Base function block for a room. The necessary functions which are needed for every room are provided here. All four rooms inherit from this function block. clsCellarRoom: Extends the base room and has an instance of the clsLight function block to implement the light bulb. clsCheapRoom: Extends the base room and includes an instance of the clsLight1min, which implements a light bulb with a lifetime of one minute. It also includes the service function. clsBetterRoom: Extends the base room and includes an instance of clsDuoLight1min, which has the doubled lifetime and it also includes the service function. clsClimateBetterRoom: Extends the clsBetterRoom and adds an air condition. FB_AirCondition: The temperature for the day- and nighttime is regulated with the help of this function block. clsLight: Base function block which recognizes whether the light is switched on or off. clsLight1min: Extends the clsLight and implements the IService interface. With this function the lifetime of the light bulb is monitored. clsDuoLight1min: Extends the clsLight1min with a second timer to double its lifetime. FB_LifeTimer: Counts down the lifetime of a switched on light bulb. Visualization: The main visualization includes different rooms. Each consists of a light bulb, a service message, a service display that shows whether a service is needed and two buttons, one to toggle the light on or off and one to reset the service. The topmost room additionally shows the temperature. With the "OpMode" slider the mode can be set to daytime with light, night time without light or manual to switch the lights on and off separately. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Screenshot of Visualization
Last updated: 2020-09-28

Home ^{Object Oriented Programming home (WikiPage)}
Download project Object Oriented Programming Product description More information System requirements and restrictions Object Oriented Programming This example shows how object oriented programming can be used. It shows the implementation of a building with different rooms. The visualization is used for a better demonstration. Product description This example displays a building with three different types of rooms. The first type has only one light. The second one has an additional light, the third has two lights and additionally shows the temperature. At daytime, all the lights are turned on and the temperature is set to 25. At nighttime all lights are turned off and the temperature is set to 15. To show the conversion from an interface to a function block, the temperature of room six is always set to 35. More information ILight: Interface for setting and getting the light value. IRoom: Interface for doing some operations, when the daytime or nighttime comes up. ITemp: Interface for setting and getting the temperature. RoomType1: This function block implements the ILight and IRoom Interface. Therefore all Interface methods need to be implemented. The function "Operation_Daytime" switches the lights on and "Operation_Nighttime" switches the lights off. RoomType2: This function block extends RoomType1 and inherits all methods. The method "SetLight" is overridden, and extended for the additional light. RoomType3: This function block extends RoomType2 and additionally implements the ITemp interface. The methods "Operation_Daytime" and "Operation_Nighttime" are overridden and extended with the temperature. CheckFB: Checks the time of the day. Each time period lasts five seconds. BuildingManager: Depending on the time of day, the corresponding operations are done. Additionally a conversion from the ITemp interface to the function block of RoomType3 is done with the function "__QUERYINTERFACE". Visualization: Displays eight rooms of three different types. The light bulbs are switched on at daytime and switched off at nighttime. Two rooms also show the temperature. This value determines the size and color of the bar. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Screenshot of Visualization
Last updated: 2020-09-28

Home ^{Network Variables home (WikiPage)}
Download project Network Variables Product description More information System requirements and restrictions Network Variables This example demonstrates how to share variables within a network. It consists of two applications. One is sending the variables and the other one receives them. Product description This example shows how variables can be exchanged between different systems within a network. One device is sending a variables and the other one receives them. To run the example, the applications need to run on different systems, due to the fact that a port can only be used once on each system. More information GVL_Send: Is a global variable list, which also includes the network settings in the global variables properties (see screenshot). Port 1202 and the broadcast address can remain default. With this setting everyone can receive the variables. Within a project it is possible that the devices communicate either directly or via a file. If the sender and receiver are located in two separate projects it is only possible to communicate via a file. This example uses a file for communication. Right click the GVL_Send and set in the "Link to File" property the file that should be used. NVL: Is a global network variable list. The sender application or the imported file is set here. Main_Receive: To check the result the values of the network variables are assigned to local variables. Additionally some diagnostic information is retrieved. In order to work correctly the sender application must be started before the receive app. In this way the file which will be imported by the receiver can be created first. If several senders on one system are used, different ports have to be defined for correct communication. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Screenshot
Last updated: 2020-09-28

Home ^{Recipe Management home (WikiPage)}
Download project Recipe Management Product description More information System requirements and restrictions Recipe Management This example demonstrates the use of the Recipe Manger. A recipe in CODESYS is a value set for a user-defined variable list (recipe definitions). Recipes can be used for setting and monitoring values for a specific set of variables on the PLC. Product description The example demonstrates how recipes can be easily read and written and how the programming interface of the library RecipeManagement can be used for extended requirements. More information The example project contains the applications RecipeManCommands and SimpleRecipeManagement. The application SimpleRecipeManagement shows how recipes can be easily stored and read in files. The RecipeManCommands application demonstrates the programming interface of the RecipeManagement library using an ST example. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Screenshot of Visualization
Last updated: 2020-09-28

Recipe Management SVN repository ^{Recipe Management code (SVN Repository)}
Last updated: 2020-09-28

Home ^{RPC Example home (WikiPage)}
Download project RPC Example Product description More information System requirements and restrictions RPC Example An example project for "Remote Procedure Calls". Two applications demonstrate the implementation of server and client RPC applications. Product description The example is based on the library RPC which is part of the CODESYS Development System. The library contains all required components for building RPC applications. The example project RPCExample.project shows the usage of this library on the basis of a simple client and server application. More information The project RPCExample.project includes the applications RPClient and RPCServer. Both applications must run on separate devices. RPC Client The program PROG executes four remote procedure calls on the server: HelloServerRequest GetTargetId GetTargetNodeName GetTargetVersion Each call is handled by the function block RPCRequest which uses the function block RPC.CLClient to send an RPC request to the server. The results of the request are copied to the corresponding variables in the method InvokeCallback of the function block RPCClientCallback. The request status and the result of the request are displayed in visualization. Visualization At first, the IP address of the server must be entered in the field "Server IP". After that the RPC request can be started via the button "RPC Request". RPC Server The program PLC_PRG initializes the function block RPC.CLServer and registers the interface IRPCProvider. A procedure is described by objectId, interfaceId and operationnumber. The request and the callback function are handled by operationnumber in the method Request. The callback function can also be executed asynchronously in the next cycle. The server component of the RPC library includes three standard procedures with device information by default (Target Name, Target ID, Target Version). System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Screenshot of Visualization
Last updated: 2020-09-28

Home ^{Serial COM mit Visualisierung home (WikiPage)}
Download project Serial COM with Visualization Product description More information System requirements and restrictions Serial COM with Visualization This example shows the use of three COM Ports. One port is for reading, another for writing and one can do both. The included visualization shows the reading and writing result together with the used parameters. The user can switch between the three different ports. Product description This example includes the communication with a serial COM port. In the visualization can be decided if one port should be used for both reading and writing or if two ports, one for reading and one for writing should be used. More information The correct port numbers needs to be adapted. The use of devices requires the adaption of the several parameters. PLC_PRG: The main program is responsible for activating the chosen serial ports and set the specific parameter values for each port, like port number or baud rate. By changing the ports in the visualization, the unused ports will be closed. SERIAL_LINE: Initially the given communication parameters are set. Afterwards the port is opened with this parameter list. Depending on the mode, the reading or writing process will be started. After reading, the buffer will be saved into a variable. Before the writing process can start, the string which should be written to the COM port is moved to a buffer variable. Visualization: The SERIAL_LINE_VISU is the visualization module which shows the used parameters, occurred errors and the reading or writing result. The main visualization references this module for the different ports. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Screenshot of Visualization
Last updated: 2020-09-28

Home ^{Serial COM Example home (WikiPage)}
Download project Serial COM Example Product description More information System requirements and restrictions Serial COM Example This example shows how to use the serial port. Therefore the communication of two ports with each other is implemented. The first one writes a string of characters, which is read by the second one. Product description This example demonstrates how serial communication can be implemented, how ports are opened, closed and information is read and send. A second example shows the usage of the library SysCom. More information Application 'CAASerialComExample': At the beginning the necessary parameters for the ports are set in an array of PARAMETER structs. The first value is the used parameter and the second one is the value of the parameter. The correct port numbers need to be adapted in the aCom1Params and aCom2Params variables. In the following example the parameter is the port and the value is 1. So the COM1 port is used. aCom1Params[1].udiParameterId:=COM.CAA_Parameter_Constants.udiPort; aCom1Params[1].udiValue := 1; If the ports are open and no error occurred one port starts writing. After this port finished writing, the other port will be used for reading. At the end both ports will be closed and the used "Handles" will be released. Application 'SysComExample': This application shows how to use the library SysCom for serial communication. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories -
Last updated: 2020-09-28

Home ^{Shared Memory Communication home (WikiPage)}
Download SharedMemoryExample.zip Shared Memory Communication Product description More information System requirements and restrictions Shared Memory Communication This example shows how data can be exchanged between a CODESYS controller and other processes by means of shared memory. Product description In the sample project, data from a CODESYS controller is shared with other processes by means of shared memory. The CODESYS package includes additional implementation examples in C (Linux), C# (Windows), and C++ (Windows). More information The CODESYS package includes the following examples: SharedMemoryExampleExt.project The project uses shared memory to read and write data with the SysShm library. The DataExchange structure is used for data exchange. Values from shared memory is read to the variable deInstRead. The variable deInstWrite is used for writing values to shared memory. The values of deInstWrite are changed in each cycle. The values of both variables are displayed in the visualization. The following examples read the value of deInstWrite and write to the variable deInstRead: SharedMemoryCLinux C program for Linux to read and write data be means of shared memory SharedMemoryWinCpp C++ program for Windows to read and write data be means of shared memory SharedMemoryWinCSharp C# program for Windows to read and write data be means of shared memory SharedMemoryExampleExt.project/SyncExample: The application SyncExample shows how data can be read and written synchronously via shared memory. SynchronizationExample: C++ program for Windows for synchronized reading and writing of data via shared memory. In this example the data exchange is done by the application SyncExample. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System V3.5.16.1 or higher Runtime System CODESYS Control V3.5.16.1 Required Accessories - Screenshot of Visualization
Last updated: 2020-09-28

Home ^{Task Manager home (WikiPage)}
Download project Task Manager Product description More information System requirements and restrictions Task Manager This example shows how task information can be read. Product description The example shows how task information can be read with the help of the system library CmplecTask. More information AllTaskInfo: This function stores information of all available tasks in an array. CurrentTaskInfo: This function returns information about the current task. PLC_PRG: This program calls the functions AllTaskinfo and CurrentTaskInfo. Second_PRG: This program is called by the task SecondTask. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories -
Last updated: 2020-09-28

Home ^{Trace Example home (WikiPage)}
Download project Trace Example Product description More information System requirements and restrictions Trace Example The example "Trace Example" contains two applications concerning trace recording and trace configuration in IEC 61131-3 via the Trace Manager. Product description The example project "TraceExample.project" shows how to record and store values of variables via the Trace Object and the Visu Trace Element. Another application demonstrates the configuration of a Trace Object in Structured Text. More information on the Trace Object and the Visu Trace Element can be found in the CODESYS help: CODESYS Development System > Reference, User Interface > Objects > Object 'Trace' and CODESYS Visualization > Visualization Elements > 'Special Controls' > Element 'Trace' and its Dialogs More information Application TraceRecordingExample The application TraceRecordingExample demonstrates how to record and store values of variables via the Trace Object and Visu Trace Element. Steps to save and load recordings via the Visu Trace Element: Configure the trace element Start the trace Start the trigger Store the trace Load the trace (Restriction: Works only if the trace was saved with the currently running application) Steps to save and load recordings via the Trace Object: Configure the trace element Download the trace (trace menu) Start the trace via trigger or recording condition Store the trace (trace menu) Load the trace (trace menu) Application IECTraceConfiguration The application IECTraceConfiguration configures a Trace Element directly via Structured Text. The corresponding functions of the Trace Manager are implemented in the library CmpTraceMgr. Trace objects receive their data from a Packet. A Packet can hold one or more Records. The variable to record is assigned to a Record. The program PLC_PRG creates and configures a Packet and a corresponding Record. The function block FBTracMgr encapsulates the functions and handles of the Trace Manager CmpTraceMgr. The programmatically configured Trace can be loaded into a Trace Object with the function "Upload Trace" in the trace menu. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Application TraceRecordingExample Trace of the application IECTraceConfiguration
Last updated: 2020-09-28

Home ^{Trend Example home (WikiPage)}
Download project Trend Example Product description More information System requirements and restrictions Trend Example The example project shows how to visualize and record values with the "Trend" element. Product description The example project "TrendExample" contains three applications with different "Trend" configurations. Following features are described in the example: Conditional recording of values Long term recording of values Multiple recording of values More information on the "Trend Element" and its configuration can be found in the CODESYS Help: CODESYS Visualization > Visualization Elements > 'Special Controls' > 'Trend' More information Application ConditionalRecording The recording of values can be triggered by a recording condition. The example generates a sine signal with amplitude of 500. The signal is recorded, if the amplitude is greater or equal 200. The recording condition can be set in the section "Recording Settings" of Trend Recording Manager. Application LongTermRecording This example shows how to configure the trend element for long term recordings. The example simulates the power of a solar station. The power rCurrentPower will be recorded every 20 seconds and will be stored in the database every minute. You can set the recording interval via the dialog "Advanced Trace Settings" and the field "Measure in every n-th cycle". The storage interval can be set by the field "Store every N milliseconds" in the dialog "Trend Storage". Application SimpleTrendExample The example application generates three signals which are recorded and visualized by the trend element. The recording can be started with the Record button. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Application ConditionalRecording Application LongTermRecording Application SimpleTrendExample
Last updated: 2020-09-28

Home ^{Visu Dialog ST home (WikiPage)}
Download project Visu Dialog ST More information System requirements and restrictions Visu Dialog ST This project contains three example applications relating to the visualization of dialogs with the language "Structured Text (ST)". More information Application DialogVarInOut This example shows how dialogs can be opened and how input values can be read and checked by an event handler. The event handler IEditBoxInputHandler is set in the main program PLC_PRG. The method VariableWritten is called after an input value is set. The range of the input value is checked by the method CheckValue of the function block ControlFB. The OK-Button is active if the variable pVar is less than 100. Notice that the function block ControlFB is passed to the frame by the attribute VAR_IN_OUT_AS_POINTER. Application FileDialog This example shows how file dialogs can be opened by program (ST) via the DialogManager. The file filter and an instance of the function block Visu_FbFileListProvider is created in the program PLC_PRG. The function block Visu_FbFileListProvider is used by the dialog to list and filter files. The function OpenFileDialog sets theVisu_FbFileListProvider and opens the dialog. After selecting a file, the name of the file is displayed in the visualization. Application IECOpenDialog The example shows how to open dialogs via the library Visu Utils. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System V3.5.16.1 or higher Runtime System CODESYS Control V3.5.16.1 Required Accessories -
Last updated: 2020-09-28

Home ^{Visu Event Handler home (WikiPage)}
Download Visu_Event_Handler.zip Visu Event Handler Product description More information System requirements and restrictions Visu Event Handler Three example projects show how events of visualizations can be handled by a program and how to implement the necessary interfaces. Product description This example package shows how events of visualizations can be caught in a program. Three example projects demonstrate the usage of the Key Event Handler, the Mouse Event Handler and the Editbox Event Handler. More information 'EditboxHandler.project': This example implements the interface VisuElems.IEditBoxInputHandler. The method VariableWritten is called by the event handler if a value is written in a textbox. 'KeyEventHandler.project': This example implements the interface VisuElems.IEditBoxInputHandler. The method HandleKeyEvent is called by the event handler if a key is pressed. 'MouseHandler.project': This example implements the interface VisuElems.VisuElemBase.IMouseEventHandler . The method HandleMouseBtnEvent is called by the event handler if a mouse button is pressed or released. The method HandleMouseMoveEvent is called by the event handler if the mouse is moved. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Screenshot of Visualization
Last updated: 2020-09-28

Home ^{Visu Element XY Chart Example home (WikiPage)}
Download Visu_Element_XY_Chart_Example.zip Visu Element XY Chart Example Product description More information Application XYChartCurvesOverlapping Application XYChartProgrammingMode Application XYChartZoomingPanning System requirements and restrictions Visu Element XY Chart Example This sample project demonstrates how to use the 'XY Chart' visualization element. Product description The sample project 'XYChartExamples' includes three applications for the 'XY Chart' visualization element. This 'XY Chart' visualization element displays the curve of array values graphically as a line or bar chart in the Cartesian coordinate system. The sample project includes applications covering the following topics: Curve overlapping Curve programming Zooming and panning More information Application XYChartCurvesOverlapping The application demonstrates how to use the overlapping mode. Application XYChartProgrammingMode The application demonstrates how to use the programming mode. Application XYChartZoomingPanning The application demonstrates how to use the zoom and pan function. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Application XYChartCurvesOverlapping Application XYChartProgrammingMode Application XYChartZoomingPanning
Last updated: 2020-09-28

Home ^{Visu File Transfer Example home (WikiPage)}
Download project Visu File Transfer Example Product description More information Transfer type File Transfer type Streaming System requirements and restrictions Visu File Transfer Example This sample project demonstrates how to transfer files between a CODESYS PLC and the CODESYS web visualization. Product description The sample project "Visu File Transfer Example" provides two options for exchanging a file between a CODESYS PLC and a web visualization client. • Transfer type File • Transfer type Streaming More information Transfer type File Fast implementation by means of configuration within the element properties Transfer type Streaming The project provides example implementation for a VisuStreamReader and VisuStreamWriter. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Input configuration - File transfer Class diagram VisuStreamReader / VisuStreamWriter Visualization: Operating panel
Last updated: 2020-09-28

Home ^{Visu Value Change Handler Example home (WikiPage)}
Download project Visu Value Change Handler Example Product description System requirements and restrictions Visu Value Change Handler Example The sample project records variable value changes that were triggered by user input within the visualization. Product description All visualization elements that change the value of a variable by user input call the IValueChangedListener interface. With this interface, the value changes can be recorded and then processed programmatically. Sample project "VisuValueChangeHandler.project": The function block FB_ValueChangedListener implements the interface IValueChangedListener. In the PLC_PRG program, the function block is registered at ValueChangedListenerManager. When the value of a visualization element changes, the ValueChanged method of the FB_ValueChangedListener function block is called. In the sample project, all user inputs are written via the visualization to the log file of the device. The corresponding visualization element can be selected using the input assistant. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories -
Last updated: 2020-09-28

home Discussion ^{Visu Value Change Handler Example home (Discussion)}
Forum for home comments
Last updated: 2020-09-28

code Discussion ^{Visu Value Change Handler Example code (Discussion)}
Forum for code comments
Last updated: 2020-09-28

Visu Value Change Handler Example SVN repository ^{Visu Value Change Handler Example code (SVN Repository)}
Last updated: 2020-09-28

(no subject) ^{Visu Value Change Handler Example home (Thread)}
Last updated: 2020-09-28

Home ^{IO Mapping Tool home (WikiPage)}
Download IO_Mapping_Tool.zip IO Mapping Tool Product description More information System requirements and restrictions IO Mapping Tool With the IEC library "IO Mapping Tool", the inputs and outputs of a program can be remapped via a visualization in runtime mode. Product description The inputs and outputs are mapped via function blocks and the corresponding visualizations. In doing so, the function blocks are simply activated between the desired inputs our outputs. The library contains the following function blocks. Function blocks with eight inputs and outputs: Basic function block Function block for BOOL inputs and outputs Function block for BYTE inputs and outputs Function block for WORD inputs and outputs Function blocks with a variable number of inputs and outputs: Basic function block Function block for BOOL inputs and outputs Function block for BYTE inputs and outputs Function block for WORD inputs and outputs Function blocks with eight inputs and outputs In the function blocks IOMappingBool, IOMappingByte, and IOMappingWord, eight variables each of the corresponding type are used for the inputs and outputs. Function blocks with variable inputs and outputs In the function blocks VarIOMappingBool, VarIOMappingByte, and VarIOMappingWord, the inputs and outputs are mapped via arrays of length g_iMaxIOs. The parameter g_iMaxIOs can be edited via the parameter list Param and it can be maximum 256. Basic function blocks In the function blocks IOMappingBaseFB and VarIOMappingBaseFB, an array of integer values is created for each. The indices of the array represent the inputs and the values at the corresponding positions represent the outputs for these inputs. Only one input can ever point to an output. When changing the mapping of inputs and outputs, it is checked if the output has already been mapped to an input. If this is the case, then the value of the earlier input is set to -1. The array that saves the mapping of inputs to outputs is stored with the PersistenceManager. More information The package contains the library "IO Mapping Tool" and the sample project "IOMappingExample.project". Visualization Two visualizations are included in the library. One is for the fixed number of inputs and outputs and the other is for the variable number of inputs and outputs. The eight inputs and outputs in the visualization IOMappingVisu are each represented by eight radio buttons. When a radio button is selected on the left side, the corresponding output is selected automatically on the right side. By default, the outputs are ordered according to the inputs. After changing the mapping, the new mapping is saved by clicking the "Set" button. Clicking the "Reset" button discards all changes after the last save. In the visualization VarIOMappingVisu, the mapping is represented and editable by means of combo boxes. The left box represents the inputs and the right box represents the outputs. The current mapping is displayed clearly in the adjacent table. The "Set" and "Reset" buttons function in the same way as for IOMappingVisu. Sample project The sample project "IOMappingExample" demonstrates how to use the function blocks IOMappingBoolFB and VarIOMappingBoolFB. the mapping of values is saved by means of the PersistenceManager. For this purpose, the library AC_Persistence has to be linked in the POU pool and added as a module instance (see also: "Persistence Manager" in the CODESYS help). System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Visualization with eight inputs and outputs Visualization for a variable number of inputs and outputs
Last updated: 2020-09-28

Home ^{MultiTouch Example home (WikiPage)}
Download project MultiTouch Example Product description More information System requirements and restrictions MultiTouch Example This visualization example shows how to evaluate and handle touch events of MultiTouch displays in CODESYS. Product description This visualization example shows how to evaluate and handle touch events of MultiTouch displays in CODESYS. If visualization is used on a MultiTouch display, then an additional control concept is available to the user. Apart from the usual mouse and keyboard events, gestures and touch events are evaluated and processed. Supported gestures Pan gesture: pressing, shifting and releasing with a finger moves the contents of a window or a tab Flick gesture: fast shifting of a finger in an area, i.e. "flicking", leads to switching between different visualization screens Multi touch events: operating with several fingers at a time Several elements in a visualization screen can be actuated at the same time with several fingers. Thus it is possible to develop a two-hand control or a virtual mixer in which several sliders can be actuated at the same time. The IGestureEventHandler interface of the VisuElems.VisuElemBase library enables IEC 61131-3 code to be implemented in order to react to gestures. A gesture event can be intercepted and consequential actions can be implemented. The following clients can execute visualization on a MultiTouch device CODESYS TargetVisu on a device with Windows operating system CODESYS TargetVisu on a device with Linux operating system More information The project MultiTouchExample.project shows the usage of the interface IGestureEventHandler2. The function block GesturesHandler implements the interface IGestureEventHandler2. At first the event handler must be registered at the event manager. This is done in the method FB_Init of the function block GesturesHandler. The methods HandleFlickGesture, HandlePanGesture and HandleTouchEvent will be called if a corresponding event occurs. The example contains following functions: Scrolling: Scrolling inside of frames and tab controls Multiple inputs: Simultaneous control of input elements Two-hand inputs: The example demonstrates the input handling with two hands Handling in IEC: Event handling of touch events in IEC 61131-3; the example displays the current touch points at the screen Flick detection: Counts the horizontal and vertical flick events System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Screenshot of Visualization Screenshot of Visualization Screenshot of Visualization
Last updated: 2020-09-28

Home ^{PLC Chat home (WikiPage)}
Download project PLC Chat Product description More information System requirements and restrictions PLC Chat The PLC Chat includes a chat server which can handle up to 16 PLC clients and the client program. The chat UI is displayed on a CODESYS TargetVisu and can be accessed by the CODESYS Web Visualization. Product description The PLC Chat includes a chat server which can handle up to 16 PLC clients and the client program. The chat UI is displayed on a CODESYS TargetVisu and can be accessed by the CODESYS WebVisu. This example demonstrates the usage of the library NetBaseServices. Server: Download the server application to a PLC and execute the program. Enter the IP address for the server in the visualization configuration. Choose a free port for the connection. Give the chat a name (optional) Now click the "Go Online" button. The status bar changes from "not connected" to "waiting for clients". Client: Download the client to another PLC and run the application (up to 16 PLCs can participate) Change to the configuration tab Choose your nick name. Enter the IP address and port of the server Click the "Go Online" button. The status bar now displays "connection established". More information Server and client use the library NetBaseServices for their connections. TCP_Server (PRG): The server is initialized with the IP address and the port number of the configuration in the visualization. All incoming connections are stored in the array "a_tcp_connections". Up to 16 clients can be handled by the server. When the program reaches the state STATE.WAITE_FOR_MESSAGE all connections are checked for incoming messages. A received message will be stored in an instance of MessageBuffer(FB). The server passes all received messages to the connected clients. Sent messages are marked by setting a flag in "axSentFlags". If a client goes offline the server will then close all open connections to that client. In case of a server reset all clients are removed and their connections closed. MessageBuffer (FB): The MessageBuffer is a FIFO buffer. Incoming messages are stored here by the server and loaded when they get distributed to the connected clients. TCP_Client (PRG): The client will be initialized with the data entered in the configuration of the visualization. When a connection to a server was established the client waits for incoming messages. If there is a message it will be saved in the clients MessageQueue instance. If the user enters a message in the visualization the client sends the text with the users nick name to the server. In case of a log out the connection to the server will be closed. MessageQueue(FB): The MessageQueue stores all incoming messages. The last 10 messages will be displayed in the chat client visualization. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories -
Last updated: 2020-09-28

Home ^{Visualization Elements home (WikiPage)}
Download project Visualization Elements Product description More information System requirements and restrictions Visualization Elements This example shows the use of some visualization elements and events, e.g. working with external pictures or rotating objects with mouse events. Product description To include an external image, an Image Pool object must be added. The included images must use the ID from the Image Pool for the Static ID property. Some mouse events are directly supported from the visualization (OnMouseClick, OnMouseDown, OnMouseLeave, OnMouseEnter, OnMouseUp and OnMouseMove). Additional ones (double click, dragging) were implemented in the "MouseEvents" program. This example changes the color of an object when an event occurs. Another function is the rotation. This function can distinguish between interior and normal rotation. In both cases the element rotates around the center point of the element. With the interior rotation, the element additionally rotates itself, whereas with the normal rotation it does not. More information Main: Calls the following programs. MouseEvents: This program implements the double click and dragging for object. A timer is used for the double click to wait for the second mouse click. To implement the dragging, a new position for the object is calculated when the mouse is pressed and moving. Node: This program is responsible for expanding and collapsing the node by a double click. This is also realized with a timer for the double click. Rotation: For each degree of a circle the position is calculated. Visualization: It is important that the time interval for the visualization task is short in order to get fast feedback from the user interface. System requirements and restrictions System requirements and restrictions Info Programming System CODESYS Development System Version 3.5.14.0 or higher Runtime System CODESYS Control Version 3.5.14.0 Required Accessories - Screenshot of Visualization
Last updated: 2020-09-28

Sort by relevance or date