Associated with: PSTN outstations; direct outstations for which the communications availability is ‘Incoming Only’ or ‘Periodic’; direct outstations with PSTN fallback enabled; output points on advanced drivers; pulse actions on advanced drivers
With some types of outstation, ClearSCADA queues certain pick action requests automatically if it is not in communications with the outstation when the request is triggered. With some other types of outstation, your system may be configured to provide the option to queue such requests if required (see Optionally Queue Pick Action Requests on PSTN and ‘On Demand’Outstations).
The Queued Request status attribute is displayed whenever a pick action request is queued and awaiting execution.
One Queued Request status attribute entry is displayed per queued request.
On a point or pulse action’s Status display, the attribute indicates the type of pick action that is queued and the value of that requested action (if applicable). The attribute also indicates the user that requested the pick action and the time and date that the request was made.
Control to 45.00 requested by RJones (Mar/17/2010 09:53:54.704)
(Indicating that the queued request is for a ‘Control’ pick action, which is being used to change a point’s value to 45.00.)
An outstation’s Status display lists requests that are currently queued on any of the outstation’s ‘dependants’ (such as points and pulse actions) as well as any queued outstation requests. For dependants, the entry includes the full path and name of the item to which the queued request relates.
"NW.Region 1.Analog Output Point 2" - Control to 45.00 requested by RJones (Mar/17/2010 09:53:54.704)
"NW.Region 1.Digital Output Point 3" - Control Start requested by CGrosso (Mar/17/2010 11:26:10.018)
"NW.Region 1.Pulse 1" - Pulse Close requested by AVandaal (Mar/17/2010 10:14:59.393)
(Indicating that two point controls and one pulse action are waiting to be executed when ClearSCADA is next in communications with the outstation. The first queued request is that for the same ‘Control’ pick action shown in the previous example. For dependants, each entry includes the full path of the database item to which the queued request relates.)
ClearSCADA executes any queued requests when it is next in communication with the outstation. The exceptions to this are any requests that are superseded by another request, or canceled using the Cancel Queued Request pick action.