GE Mark VIe IS220PAICH1B Analog Input/Output

Mark VIeS SIF configurations are created and maintained in the ToolboxST application,

along with the basic process control configurations. This environment provides all the facilities to create, download, and maintain these configurations. 

Mark VIeS Safety controllers have two operating modes that are used for application execution: Locked and Unlocked. 

When in Unlocked mode, full access to the controller is granted, 

including the ability to download code, set constants, force points, and all other configuration and diagnostic operations.

When in Locked mode, all changes to the controller operation are prevented to ensure the integrity of the safety functions. 

Within the Mark VIeS Safety controller, branding is used to support Locked mode and integrity checks.

When the controller is unlocked, and the operator is satisfied with system operation, 

the system configuration is branded so that it can be uniquely identified. 

Once branded, a diagnostic alarm is generated if there are any changes to application code, constants, hardware integrity, or network connectivity.

The diagnostics based on branding include all communications through the IONet to provide 100% network diagnostic coverage (DC) independent of the network hardware selected.

Variable Health

Inside the Mark VIeS Safety controller, every variable is associated with a set of qualities that provide additional information,

or support advanced features such as forcing, simulation, or alarms. Some of these qualities are visible to users through

ToolboxST application, and others are made available to application code through blockware.

Variable health measures the validity of the data stored in the variable. When the ToolboxST application collects variable data

from the controller, it also scans the health information and displays a U (for Unhealthy) beside each live data value if the

corresponding health quality is FALSE. The Variable Health block (VAR_HEALTH) allows application code to access

variable health. The Prevote block (PREVOTE) allows application code to access prevote values and health.

The health of a variable with no connection to I/O is always TRUE, and therefore uninteresting. Also, output health is always

TRUE. The health of variables associated with I/O is calculated from point and link health. Point health originates from

software close to the hardware. Link health is calculated by the controller. These two values are passed through a logical AND

gate to form variable health.

Each I/O server defines the non user-configurable point and group health. For example, the point health of an analog input

may be declared unhealthy if its value exceeds some limit, and the point health of all inputs on an I/O pack may be declared

unhealthy if a problem is detected in the signal acquisition hardware. It may not be practical for an I/O server to provide a

health indication for each individual point and so this component of variable health is optional.

Bently 3500/65 145988-02  

ABB  PF900-NR 3BDH000357 

ABB  HS810 3BDH000305R0101 

ABB  VIPA972-0DP01 

YASKAWA CACR-SR07BE12M  

ABB S-073N 3BHB009884R0021 

ABB 3BHL000986P0006  

ABB 5SDF1045H0002 

ABB 5SDF0860H0003 

ABB 5SHY3545L0010 3BHB013088R0001 3BHE009681R0101 GVC750BE101  

XP POWER  F8B6D4A3G3  

Triconex 8310  

TRICONEX 4351B 

TRICONEX 3721 

TRICONEX 3700A 

TRICONEX 4351A 

TRICONEX 4351B 

TRICONEX 3503E 

TRICONEX 3008 

TRICONEX 3664 

TRICONEX 8310N2  

ABB XUD194 XUD194A 3BHC018137R0001   

ABB PCD530A102 3BHE041343R0102  

TRICONEX MP3009  

YOKOGAWA AAI141-H50 S2  

TRICONEX 3625