beautypg.com

General instrument operation, State changes – Micromod MOD: 1800P - MOD 30ML Identity Module (Version 2) System, I/O and Communications Functions User Manual

Page 20

background image

Logic Functions - Book 1

DATABASE DESCRIPTION

2-8

2.4

GENERAL INSTRUMENT OPERATION

2.4.1 State

Changes

Instrument States
The instrument may be in one of the following states:

UPLOAD

Instrument was powered up with memory module switch in the
upload position and will do nothing beyond copying the main
database (if it is ’complete’ and its checksums verify) into the
memory module.

POR

Power up restart in process.

DEFAULT

The instrument does not have a valid user generated database
and is therefore running a default database to sustain
communications, etc.

BEING_CONFIGURED

An external device has configuration control and is authorized to
download. The instrument is running the default database in
expectation of downloads to the main.

HOLD

The instrument has a valid user database, but is running only
overhead blocks. (No loops).

LOCAL_HOLD

The instrument has a valid user database and would be in RUN;
but, the Run/Service switch is in Service (hold) and only
overhead blocks are running.

RUN

Instrument has a valid user database and is running all blocks.

Loop or Block States
Loops and blocks may be in one of the following states:

RUN

A normal operation state that is the only state in which a loop or
block is executed. This state runs algorithms, sets qualities per
inputs and algorithm results, and manages diagnostics.

HOLD

A non-executing run state that is provided to save execution
time when a particular loop or block is not required continuously.
Attributes can be read and written and quality remains as it was
in the previous state. When a value with bad quality is written,
the quality changes to good if the associated loop is also in run
or hold.

OFF

A non-executing state where attributes can be read and written
and quality is set bad. If you switch a loop to OFF and then to
HOLD or DEBUG, all output qualities will be BAD.

DEBUG

A non-executing state where attributes can be read and written
and quality remains as it was in the previous state. When a
value with bad quality is written, the quality changes to good.

Loop or block state transition actions are described in Table 2-2.