Indicates the specific absolute time (in UTC) that the client wants to wait for the Server to process a response by either returning whatever data it might have or confirm that there was some error condition which prevents a successful response. Data for items, which is not available by that time, should be returned as errors. If the RequestDeadline is earlier than the current time of the server (RcvTime) then the whole request fails.
If (RequestDeadline - RcvTime) <= 0 Then E_TIMEDOUT fault
If (RequestDeadline - current time) <= 0 Then E_TIMEDOUT errors for unprocessed items
The request may timeout independently of RequestDeadline based on other system parameters. In the case of the system based timeout, the whole request will fail. The client can thus expect that the request will come to some closure based on the lesser of the RequestDeadline and the system based timeout.
If omitted then the server will use some server specific period to process the response.
The expectation is that the client and server are reasonably time synched which is necessary for this service to work properly. The client may gain some insight in calculating this attribute by reviewing RcvTime, and ReplyTime in the ReplyBase for responses.
The server specific timeout might be determined by something equivalent to a TCP/IP timeout or perhaps by the time required to make a connection to a remote RTU. It is expected that the server specific maximum time will generally be no more than a minute or two although this depends on the details of the underlying system.

Syntax

Requirements

See Also