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.