Analysis

Module Input Data State Change

Motion Group execution

Axis Watch

Axis Registrations 1 or 2

Consumed Tag

EVENT instruction

Controller fault handlers can be used for handling controller faults or errors. Controller fault handlers are executed when a controller major fault occurs, or a program fault is not handled by a fault routine.

PowerUp handlers can be used to execute logic relating to the power up sequence of the controller. PowerUp handlers perform startup execution after an abnormal loss of power in Run Mode.

Encrypted — Source protection has been applied to the routine. These routines cannot be analyzed.

Ladder Diagrams — Routine is written using ladder elements.

Function Block Diagrams — Routine is written using a series of sheets that represent different functions.

Structured Text — Routine is written using structured text syntax to make a series of conditional logic statements to evaluate.

Sequential Function Charts — Routine is written using a flowchart that uses steps and transitions to perform specific operations or actions.

Safety-Lock — Displays whether the project is safety-locked. A safety-locked project is protected from unauthorized changes by a safety signature.

Safety Level — For GuardLogix 5580 Safety controllers, determines whether the project is at a safety level SIL2/PLd or SIL3/PLe. For all other types of controllers, it’s the current SIL level of the controller.

Safety Signature ID — Displays the unique ID corresponding to the validation of the Safety controller project. The date and time values correspond to when the signature was generated. The ID is a unique value calculated by the controller over the memory contents at the time that the signature is generated.

Signature Run Mode Protect — If

Yes

then the safety signature cannot be deleted while the controller is in Run Mode, regardless of the Safety application state.

When Replacing Safety I/O — Displays the setting for the project that determines whether the controller sets the safety network number (SNN) of a safety I/O module that is connected to and has configuration data, either

Configure Only When No Safety Signature Exists

or

Configure Always

.

Safety Network Number — Displays the port and the 6-byte hexadecimal safety network number (SNN) assigned to the port. If the controller has more than one port that supports a CIP Safety connection, the SNN for each port is displayed.

Safety Tag Mapping — Displays how tags are mapped between standard classes and safety classes in the project.

Motion Group Name — The name used to refer to a consolidated set of the axes that provide coordinated motion.

General Fault Type — The fault type that is used for the motion control group.

Assigned axes — Identifies how many axes are in the motion group.

Unassigned axes — Any axes present in the project that are not assigned to a motion group.

Virtual axes — An imaginary axis (see glossary) with full motion planner operation, but not associated with any physical device.

Physical axes — Axes that exist in a piece of equipment.

Coarse update rate — A type of rate that selects the periodic rate (at which the motion task executes) to compute the servo commanded position, velocity, and accelerations to be sent to the output modules when executing motion instructions. If the coarse update rate is too small, the processor may not have time to execute non-motion related logic. As a rule, a motion task requires one millisecond per axis to allow the processor a reasonable execution time.

Tag scope percentage: Controller-scoped tags versus local tags

Tag data type percentage Atomic alias, and structures.

Array Type as string or atomic

User defined: Structures defined during the development of the application by the customer or solution provider.

Strings. Structure used to define variable string data.

Add-On Defined. Structures defined by an Add-On Instruction

Pre-defined. Predefined data type defined by the controller, for example Counter, Timer, and PID.

Module defined. Data type defined b a module to store input, output, and configure data for the module

Produced tags broadcast information from the local controller to the rest of the system for consumption.

Consumed tags are information received by the local controller from tags produced by other controllers in the system.

Message tags transfer (send or receive) data between controllers by executing a message (MSG) instruction.