ClientRequestReadHoldingRegistersWide (FB) ¶ FUNCTION_BLOCK ClientRequestReadHoldingRegistersWide EXTENDS ClientRequestReadWideRegisters ReadHoldingRegisters client request (FC03) for registers > 16bit. For details about client request see |ClientRequest| . For details about “wide registers” and endianess see ServerTCP_extended or ServerSerial_extended . Please visit https://forge.codesys.com/prj/codesys-example/modbus/home to find examples. InOut: Scope Name Type Initial Comment Inherited from Input xExecute BOOL Rising edge: Starts defined operation FALSE : Resets the defined operation after ready condition was reached ETrigTo udiTimeOut UDINT Max. operating time for executing [µs], 0: No operating time limit ETrigTo Output xDone BOOL Ready condition reached ETrigTo xBusy BOOL Operation is running ETrigTo xError BOOL Error condition reached ETrigTo Inout rClient Client Reference to |Client| . ClientRequest Input uiUnitId UINT 0 Unit-Id to send the request to. ClientRequest udiReplyTimeout UDINT (50 * 1000) 50 ms ClientRequest uiMaxRetries UINT 0 Maximum number of request retries in case of “reply timeout”. ClientRequest Output eErrorID Error Error status ClientRequest eException ExceptionCodes Request exception code. ClientRequest uiRetryCnt UINT 0 Number of request retries in case of “reply timeout”. ClientRequest Input uiStartItem UINT 0 First “data item” to read. ClientRequestRead uiQuantity UINT 1 Number of “data items” to read. ReadCoils / ReadDiscreteInputs: 1 to 2000 ReadHoldingRegisters / ReadInputRegisters: 1 to 125 ClientRequestRead pData POINTER TO BYTE 0 Pointer to result data, memory has to be provided by caller. ClientRequestReadWideRegisters uiDataItemSize UINT “data item” size / register width (in bytes). The ClientRequest has to know about the “data item” size a-priori to provide memory for result data. In case the server unexpectedly does have a different “data item” size than assumed, the ClientRequest can not succeed. ClientRequestReadWideRegisters
ClientRequestReadInputRegistersWide (FB) ¶ FUNCTION_BLOCK ClientRequestReadInputRegistersWide EXTENDS ClientRequestReadWideRegisters ReadInputRegisters client request (FC04) for registers > 16bit. For details about client request see |ClientRequest| . For details about “wide registers” and endianess see ServerTCP_extended or ServerSerial_extended . Please visit https://forge.codesys.com/prj/codesys-example/modbus/home to find examples. InOut: Scope Name Type Initial Comment Inherited from Input xExecute BOOL Rising edge: Starts defined operation FALSE : Resets the defined operation after ready condition was reached ETrigTo udiTimeOut UDINT Max. operating time for executing [µs], 0: No operating time limit ETrigTo Output xDone BOOL Ready condition reached ETrigTo xBusy BOOL Operation is running ETrigTo xError BOOL Error condition reached ETrigTo Inout rClient Client Reference to |Client| . ClientRequest Input uiUnitId UINT 0 Unit-Id to send the request to. ClientRequest udiReplyTimeout UDINT (50 * 1000) 50 ms ClientRequest uiMaxRetries UINT 0 Maximum number of request retries in case of “reply timeout”. ClientRequest Output eErrorID Error Error status ClientRequest eException ExceptionCodes Request exception code. ClientRequest uiRetryCnt UINT 0 Number of request retries in case of “reply timeout”. ClientRequest Input uiStartItem UINT 0 First “data item” to read. ClientRequestRead uiQuantity UINT 1 Number of “data items” to read. ReadCoils / ReadDiscreteInputs: 1 to 2000 ReadHoldingRegisters / ReadInputRegisters: 1 to 125 ClientRequestRead pData POINTER TO BYTE 0 Pointer to result data, memory has to be provided by caller. ClientRequestReadWideRegisters uiDataItemSize UINT “data item” size / register width (in bytes). The ClientRequest has to know about the “data item” size a-priori to provide memory for result data. In case the server unexpectedly does have a different “data item” size than assumed, the ClientRequest can not succeed. ClientRequestReadWideRegisters
ClientRequestReadWideRegisters (FB) ¶ FUNCTION_BLOCK ABSTRACT ClientRequestReadWideRegisters EXTENDS ModbusFB.ClientRequestRead Read client request base class for ReadHoldingRegistersWide and ReadInputRegistersWide InOut: Scope Name Type Initial Comment Inherited from Input xExecute BOOL Rising edge: Starts defined operation FALSE : Resets the defined operation after ready condition was reached ETrigTo udiTimeOut UDINT Max. operating time for executing [µs], 0: No operating time limit ETrigTo Output xDone BOOL Ready condition reached ETrigTo xBusy BOOL Operation is running ETrigTo xError BOOL Error condition reached ETrigTo Inout rClient Client Reference to |Client| . ClientRequest Input uiUnitId UINT 0 Unit-Id to send the request to. ClientRequest udiReplyTimeout UDINT (50 * 1000) 50 ms ClientRequest uiMaxRetries UINT 0 Maximum number of request retries in case of “reply timeout”. ClientRequest Output eErrorID Error Error status ClientRequest eException ExceptionCodes Request exception code. ClientRequest uiRetryCnt UINT 0 Number of request retries in case of “reply timeout”. ClientRequest Input uiStartItem UINT 0 First “data item” to read. ClientRequestRead uiQuantity UINT 1 Number of “data items” to read. ReadCoils / ReadDiscreteInputs: 1 to 2000 ReadHoldingRegisters / ReadInputRegisters: 1 to 125 ClientRequestRead pData POINTER TO BYTE 0 Pointer to result data, memory has to be provided by caller. uiDataItemSize UINT “data item” size / register width (in bytes). The ClientRequest has to know about the “data item” size a-priori to provide memory for result data. In case the server unexpectedly does have a different “data item” size than assumed, the ClientRequest can not succeed.
MemoryBarrier Library Documentation ¶ Company 3S - Smart Software Solutions GmbH Title MemoryBarrier Version 3.5.17.0 Categories Intern|MultiCore Namespace MemoryBarrier Author 3S - Smart Software Solutions GmbH Placeholder MemoryBarrier Description 1 ¶ Library that contains a function that calls the memory-barrier-operator. By means of this library, it is possible to create compiler-version-dependent functionality dealing with different tasks on different cores. One simply has to use an optional placeholder “MemoryBarrier” and a statement like {IF defined (pou: MemoryBarrier.MemoryBarrier)} MemoryBarrier.MemoryBarrier(); {END_IF}. Contents: ¶ MemoryBarrier (Function) Indices and tables ¶ 1 Based on MemoryBarrier.library, last modified 20.04.2021, 15:08:20. LibDoc 4.4.0.0-b.27 The content file MemoryBarrier.clean.json was generated with CODESYS V3.5 SP16 Patch 3 on 20.04.2021, 15:08:21.
MemoryBarrier (FUN) ¶ FUNCTION MemoryBarrier : BOOL InOut: Scope Name Type Return MemoryBarrier BOOL
File and Project Information ¶ Scope Name Type Content FileHeader creationDateTime date 20.04.2021, 15:08:21 companyName string 3S-Smart Software Solutions GmbH libraryFile MemoryBarrier.library primaryProject True productName CODESYS productProfile CODESYS V3.5 SP16 Patch 3 contentFile MemoryBarrier.clean.json version version 2.0.0.0 ProjectInformation IsEndUserLibrary bool False Released True LastModificationDateTime date 20.04.2021, 15:08:20 LibraryCategories library-category-list Intern|MultiCore Author string 3S - Smart Software Solutions GmbH Company 3S - Smart Software Solutions GmbH CompiledLibraryCompatibilityVersion CODESYS V3.5 SP15 DefaultNamespace MemoryBarrier Description See: Description DocFormat reStructuredText LanguageModelAttribute qualified-access-only Placeholder MemoryBarrier Project MemoryBarrier Title MemoryBarrier Version version 3.5.17.0
Library Reference ¶ This is a dictionary of all referenced libraries and their name spaces.
CoDeSys Memory Manager Library Documentation ¶ Company 3S - Smart Software Solutions GmbH Title CoDeSys Memory Manager Version 3.5.12.0 Categories Intern Namespace CMM Author Bernhard Werner Placeholder MemoryManagement Description 1 ¶ Library for Memory Management. The memory to manage has a fixed size and is used by __NEW and __DELETE. For synchronization syssem is needed. Contents: ¶ MemoryManager GVL (GVL) IMemoryManager (Interface) LMMBlock (Struct) LinearMemoryManager (FunctionBlock) Indices and tables ¶ 1 Based on MemoryManagement.library, last modified 15.12.2017, 11:45:38. LibDoc 4.4.0.0-b.27 The content file MemoryManagement.clean.json was generated with CODESYS V3.5 SP12 on 15.12.2017, 11:45:38.
MemoryManager ¶ GVL (GVL) IMemoryManager (Interface) Alloc (Method) Free (Method) LMMBlock (Struct) LinearMemoryManager (FunctionBlock) Alloc (Method) FB_Exit (Method) FB_Init (Method) FindFirstFreeBlock (Method) Free (Method) GetBlockFromBuffer (Method) GetNextBlock (Method) GetNextFreeBlock (Method) GetPreviousBlock (Method) Initialize (Method) MergeBlockWithNextBlock (Method) Reset (Method) prvAssert (Method) prvInitBuffer (Method)
GVL (GVL) ¶ InOut: Scope Name Type Initial Constant NULL POINTER TO BYTE 0
