Constants (GVL) ¶ Attributes: qualified_only InOut: Scope Name Type Initial Comment Constant NOTIFY_TAG_PAINTDATA_AVAILABLE DWORD 1 This tag can be sent to a targetvisualization instance to signal that new information is available that can be drawn from now on. This tag does not use the parameters at the moment.

EventParameter ¶ EVTPARAM_Application (Struct)

EVTPARAM_Application (STRUCT) ¶ TYPE EVTPARAM_Application : STRUCT <category>Event parameter</category> <element name=”pszApplication” type=”IN”>The name of the application that started the target visu window</element> InOut: Name Type pszApplication POINTER TO STRING

TargetVisuCyclic (FUN) ¶ FUNCTION TargetVisuCyclic : UDINT This function will be called cylically by the generic visualization libraries for active targetvisualization clients when it is supported by these libraries. The call is used for implementing a targetvisualization without the need for multitasking systems. InOut: Scope Name Type Comment Return TargetVisuCyclic UDINT Input dwTargetVisuHandle XWORD The handle of the targetvisualization instance that should be called.

TargetVisuFindById (FUN) ¶ FUNCTION TargetVisuFindById : SysTypes.RTS_IEC_RESULT This function can be used to find out the handle of the targetvisualization when having the according identification InOut: Scope Name Type Comment Return TargetVisuFindById SysTypes.RTS_IEC_RESULT Input dwExternId DWORD The identification used by the visualization to manage their different clients. Output hTargetVisu SysTypes.RTS_IEC_HANDLE

TargetVisuNotify (FUN) ¶ FUNCTION TargetVisuNotify : SysTypes.RTS_IEC_RESULT This function can be used to send notifications to a targetvisualization instance. As those notifications are usually sent in an asynchronous way, do not expect immediate effects when this function returned! InOut: Scope Name Type Comment Return TargetVisuNotify SysTypes.RTS_IEC_RESULT Input hTargetVisu SysTypes.RTS_IEC_HANDLE The handle of the targetvisualization dwTag DWORD The tag that signals which kind of information should be sent to the targetvisualization pParam POINTER TO BYTE This parameter can hold data that is related to the tag. The interpretation of this data depends on dwTag. It can as well be interpreted as a numeric (and thus non pointer) value

File and Project Information ¶ Scope Name Type Content FileHeader creationDateTime date 02.03.2023, 11:02:32 companyName string 3S-Smart Software Solutions GmbH libraryFile CmpTargetVisu.library primaryProject True productName CODESYS productProfile CODESYS V3.5 SP16 Patch 3 contentFile CmpTargetVisu.clean.json version version 2.0.0.0 ProjectInformation Released bool True LastModificationDateTime date 02.03.2023, 11:02:30 LibraryCategories library-category-list System|SysLibs Author string 3S-Smart Software Solutions GmbH Company System CompiledLibraryCompatibilityVersion CODESYS V3.5 SP15 Description See: Description Placeholder CmpTargetVisu Project CmpTargetVisu Title CmpTargetVisu Version version 3.5.19.0

Library Reference ¶ This is a dictionary of all referenced libraries and their name spaces. CmpEventMgr ¶ Library Identification ¶ Placeholder: CmpEventMgr Default Resolution: CmpEventMgr, * (System) Namespace: CmpEventMgr Library Properties ¶ LinkAllContent: False Optional: False QualifiedOnly: False SystemLibrary: False Key: CmpEventMgr SysTypes2 Interfaces ¶ Library Identification ¶ Name: SysTypes2 Interfaces Version: newest Company: System Namespace: SysTypes Library Properties ¶ LinkAllContent: False Optional: False QualifiedOnly: False SystemLibrary: False Key: SysTypes2 Interfaces, * (System)

CmpTls Implementation Library Documentation ¶ Company System Title CmpTls Implementation Version 3.5.17.0 Categories System|SysLibs Author CODESYS Development GmbH Placeholder CmpTls Implementation Description 1 ¶ This library provies access to the TLS Implementaiton of the runtime system. The CmpTlsCreateContext and CmpTlsCreateContext2 functions are used to setup a TLS specific object which may be used in other libraries such as SysSocket2. The ohter functions provied access to an TLS implementation on static buffers. This can be used to implement the TLS protocol on some third party protocol. The classical implementation with sockets is provied within the SysSocket2 library. Contents: ¶ CmpTlsAccept (Function) CmpTlsBufferDataReceived (Function) CmpTlsBufferDataSent (Function) CmpTlsBufferDataToSendAvailable (Function) CmpTlsBufferOpen (Function) CmpTlsClose (Function) CmpTlsConnect (Function) CmpTlsCreateContext (Function) CmpTlsCreateContext2 (Function) CmpTlsFreeContext (Function) CmpTlsRead (Function) CmpTlsShutdown (Function) CmpTlsWrite (Function) Indices and tables ¶ 1 Based on CmpTls Implementation.library, last modified 20.04.2021, 15:57:07. LibDoc 4.4.0.0-b.27 The content file CmpTls Implementation.clean.json was generated with CODESYS V3.5 SP16 Patch 3 on 20.04.2021, 15:57:07.

CmpTlsAccept (FUN) ¶ FUNCTION CmpTlsAccept : RTS_IEC_RESULT Starts handshaking on the server side. The client has to initiate the handshaking. This is the first function call on the serverside after establishing the unterlaying connection. Data has to be received first. This function will is likley to read and write data. InOut: Scope Name Type Comment Return CmpTlsAccept RTS_IEC_RESULT Result of this operation. May be one of these values: ERR_OK: No error. Everything worked as expected. ERR_NOTINITIALIZED: The TLS component was not initialized proberly. ERR_TLS_CONNECTION_CLOSED: The TLS connection is closed. Use TlsShutdown to shutdown locally. ERR_TLS_WANT_READ: The operation needs TO read data FROM the IO system. There is no data available. ERR_TLS_WANT_WRITE: The operation needs to write data to the IO system. This is not possible. ERR_TLS_RETRY_OPERATION: Something went wrong. Try the same function call again ERR_TLS_IO_SYSTEM: An error in the unterlaying IO system. ERR_TLS_INTERNAL: An internal Error of the TLS Component ERR_FAILED: Unknown error. Input hTlsConn RTS_IEC_HANDLE Handle of the TLS connection, created with one of the TLSxxxOpen functions