Table 61 specifies the AnalyserStateMachine’s State Objects. These State Objects are instances of the StateType defined in [OPC 10000-5]. Each State is assigned a unique StateNumber value. Subtypes of the AnalyserDeviceStateMachineType can add References from any state to a subordinate or nested StateMachine Object to extend the FiniteStateMachine.

See Table 62 for a description of the states.

Table 61 – AnalyserDeviceStateMachineType States

BrowseName

References

Target BrowseName

Value

Target Type Definition

Notes

States

Powerup

HasProperty

StateNumber

100

PropertyType

ToTransition

PowerupToOperatingTransition

TransitionType

Operating

HasProperty

StateNumber

200

PropertyType

FromTransition

PowerupToOperatingTransition

TransitionType

FromTransition

MaintenanceToOperatingTransition

TransitionType

FromTransition

LocalToOperatingTransition

TransitionType

ToTransition

OperatingToLocalTransition

TransitionType

ToTransition

OperatingToMaintenanceTransition

TransitionType

ToTransition

OperatingToShutdownTransition

TransitionType

Local

HasProperty

StateNumber

300

PropertyType

FromTransition

OperatingToLocalTransition

TransitionType

FromTransition

MaintenanceToLocalTransition

TransitionType

ToTransition

LocalToOperatingTransition

TransitionType

ToTransition

LocalToMaintenanceTransition

TransitionType

ToTransition

LocalToShutdownTransition

TransitionType

Maintenance

HasProperty

StateNumber

400

PropertyType

FromTransition

OperatingToMaintenanceTransition

TransitionType

FromTransition

LocalToMaintenanceTransition

TransitionType

ToTransition

MaintenanceToOperatingTransition

TransitionType

ToTransition

MaintenanceToLocalTransition

TransitionType

ToTransition

MaintenanceToShutdownTransition

TransitionType

Shutdown

HasProperty

StateNumber

500

PropertyType

FromTransition

OperatingToShutdownTransition

TransitionType

FromTransition

LocalToShutdownTransition

TransitionType

FromTransition

MaintenanceToShutdownTransition

TransitionType

A standard set of states are defined for analyser devices. These states represent the operational condition of the device. All devices that contain an AnalyserDeviceStateMachineType must support this base set. A device may or may not require a Client action to cause the state to change, as defined in the state descriptions below.

Table 62 – AnalyserDeviceStateMachineType State Description

StateName

Description

Powerup

The AnalyserDevice is in its power-up sequence and cannot perform any other task.

Operating

The AnalyserDevice is in the Operating mode.

The ADI Client uses this mode for normal operation: configuration, control and data collection.

In this mode, each child AnalyserChannels are free to accept commands from the ADI Client and the Parameter values published in the address space values are expected to be valid.

When entering this state, all AnalyserChannels of this AnalyserDevice automatically leave the SlaveMode state and enter their Operating state.

Local

The AnalyserDevice is in the Local mode. This mode is normally used to perform local physical maintenance on the analyser.

To enter the Local mode, the operator shall push a button, on the analyser itself. This may be a physical button or a graphical control on the local console screen. To quit the Local mode, the operator shall press the same or another button on the analyser itself.

When the analyser is in Local mode, all child AnalyserChannels sit in the SlaveMode state of the AnalyserChannelStateMachine.

In this mode, no commands are accepted from the ADI interface and no guarantee is given on the values in the address space.

Maintenance

The AnalyserDevice is in the Maintenance mode. This mode is used to perform remote maintenance on the analyser like firmware upgrade.

To enter in Maintenance mode, the operator shall call the GotoMaintenance Method from the ADI Client. To return to the Operating mode, the operator shall call the GotoOperating Method from the ADI Client.

When the analyser is in the Maintenance mode, all child AnalyserChannels sit in the SlaveMode state of the AnalyserChannelStateMachine.

In this mode, no commands are accepted from the ADI interface for the AnalyserChannels and no guarantee is given on the values in the address space.

Shutdown

The AnalyserDevice is in its power-down sequence and cannot perform any other task.

The set of states defined to describe an AnalyserDevice can be expanded. Sub-states can be defined for the base states to provide more resolution to the process and to describe the cause and effects of additional stimuli and transitions.