Interface Input Tags

Indicates whether the 432ES-IG3 network interface device is in Run mode or a faulted state.

0 = Not in Run mode, or in a fault state (includes recoverable and nonrecoverable faults). When 0, all three SIL 3 channel status bits report as in the safe state.

1 = Run mode

Indicates whether the 432ES-IG3 network interface device has a connection to a controller. The controller sets this bit.

0 = No connection

1 = Connection OK

Indicates whether the 432ES-IG3 network interface device has one or more diagnostics bits set.

0 = No diagnostics active

1 = One or more diagnostics codes are present

Indicates whether the 432ES-IG3 network interface device is synchronized with a 1588 Grandmaster clock.

0 = Not synchronized

1 = Synchronized

Indicates whether the 432ES-IG3 network interface module was once synchronized with a 1588 Grandmaster clock but is not now synchronized.

0 = No timeout

1 = Timeout has occurred

Increments each time a distinct diagnostic condition is detected and each time a distinct diagnostic condition transitions from detected to not detected. Set to zero by a power cycle. Wraps from 255 (-1) through 1 and 0 is skipped.

For example, if the 24V supply drops momentarily to 16V and returns to 24V. The diagnostic sequence count increments by 2 (by 1 for the transition to 16V and again by 1 for the transition back to 24V).

Indicates whether the device power voltage supply is too low, below 20.3V. Increase the voltage to at least 20.4V to clear the warning.

0 = Voltage not too low

1 = Voltage too low

Indicates that the supply voltage level to the interface is too high. The trip point occurs from 27V through 28.3V. The voltage must be reduced to a level between the specified range from 20.4V through 26.4V.

0 = Voltage not too high

1 = Voltage too high

0 = No internal fault present

1 = An internal fault is present

Indicates whether the device or port pair is in DLR mode.

0 = Device is not in DLR mode

1 = Device is in DLR mode

0 = No devices have demand on safety function

1 = At least one device has demand on safety function

Indicates whether the GuardLink channel detects a fault. If the channel is disabled, the fault bit sets to 1.

0 = Channel fault is not detected; channel has normal data.

1 = Channel fault detected

This tag is a roll-up of all diagnostic conditions for this channel. This Fault member triggers both the DiagnosticActive member and increments/decrements the Diagnostic Sequence Count.

Indicates whether the data on the channel is uncertain.

0 = Data is valid

1 = Data validity is questionable

Indicates whether the GuardLink channel is operational.

This tag is the SIL3/PLe safety bit.

0 = The channel is in a safe state.

1 = The channel is in an operational state; the safety conditions for each node on the channel are valid.

Indicates whether a faulted terminator is detected at the end of the GuardLink circuit. This fault does not indicate a missing terminator.

0 = The terminator is present and functions properly

1 = The terminator does not function properly

Indicates whether more than 32 devices are detected on the channel. A missing terminator sets this tag to 1. A break anywhere in the channel Link (trunk) cable sets this tag to 1.

0 = Number of devices is no more than 32

1 = Too many devices found on the channel (greater than 32)

Indicates that there are client devices that keying did not verify. A missing terminator will set this tag to 1. This fault can require you to cycle power to the channel to clear the fault.

0 = All devices have been verified

1 = Unverified devices present

Indicates the number of client devices (hardware) detected on the channel.

Indicates the client device or event that caused the last transition from the operational to the safe state.

-1 = After power up.

-2 = Shows if the device that caused the trip is not known or if the channel is running protocol 1.0. Examples include an open link cable and a node that cannot respond due to a fault.

-3 = Shows that you sent an unlock command to one or multiple devices while the channel is in operational mode. FW 3.001 (with Output Data set to Safety Data in the Device Definition) shows that you set the LockUnlockEn channel output tag to 1.

-4 = The channel is set to Not Used on the Channels page of the device properties.

0 through 31 = The non-locking client device that caused the transition. If Node 0 caused the transition, the value is 0. If Node 17 caused the transition, the value is 17. After the first node causes the trip, subsequent device trips do not change the DeviceTripAddress, because the subsequent trips did not cause the Status to transition from 1 to 0.

Indicates the time stamp of the last transition from an operational to a safe state. The time stamp is updated for all causes, whether the cause was due to a device, an inhibit command, a connection fault, or other cause. In the list of Controller Tags, change the Style to Date/Time to show the value as a date and time.

A decimal value of 0, shown as a Date/Time, is DT#1969-12-31-19:00:00.000 (UTC-5:00) - adjusted for your time zone.

See descriptions in Ch0.

See descriptions in Ch0.

0 = No fault

1 = Fault present on port, or the port is used but not connected

Indicates whether the data on the port is uncertain.

0 = Data is valid

1 = Data validity is questionable

0 = The port is not connected

1 = The port is connected to a network

0 = Half-duplex

1 = Full-duplex

Indicates the status of link auto-negotiation.

0 = Auto-negotiation in progress.

1 = Auto-negotiation and speed detection failed. Using default values for speed and duplex. Default values are product-dependent; recommended defaults are 10 Mbps and half-duplex.

2 = Auto negotiation has failed but detected speed. Duplex was defaulted. Default value is product-dependent; recommended default is half-duplex.

3 = Successfully negotiated speed and duplex.

4 = Auto-negotiation not attempted. Forced speed and duplex.

Network speed.

10 = 10 Mbps

100 = 100 Mbps

1000 = 1000 Mbps (not supported by the 432ES-IG3 network interface device)

See descriptions in Port1.

The number of TCP/IP connections currently open to the adapter. This number will change over time, as connections are opened and then closed automatically.

The number of CIP™ connections currently open to and through the adapter. This tag consists of 1 safety connection plus one connection for each used channel. In addition, a channel with over 24 devices use an additional connection. The max number of expected CIP connections is 7.

A running sum of the number of Sequenced Address Item Sequence Numbers that are skipped in Class 0 and Class 1 connections that the adapter and its children consume.

A running count of the number of connections that time out, both originated and targeted, both to and through the adapter.

The number of Class 3 packets and unconnected packets that the device sends and receives in the previous second.

The number of class 0 and class 1 packets that the adapter transmits and receives in the previous second.

The sum over all ports of the following Ethernet Link object values: In Discards, In Errors, In Unknown Protos, Out Discards, Out Errors, Alignment Errors, FCS Errors, Single Collisions, Multiple Collisions, SQE Test Errors, Deferred Transmissions, Late Collisions, Excessive Collisions, MAC Transmit Errors, Carrier Sense Errors, Frame Too Long, and MAC Receive Errors.

The percentage of the capacity of the compute engine of the product (whether that is a CPU, a core of a CPU, or a thread) most important to the performance of communication of packets by the product. Due to the variations in communication architectures of various products, each product must define this value that is based on its design.

The current value of the Network Status instance attribute of the DLR object for devices with multiple Ethernet ports that support DLR. Values:

0 = Normal

1 = Ring Fault

2 = Unexpected Loop Detected

3 = Partial Network Fault

4 = Rapid Fault/Restore Cycle

Reports as a DLS supervisor.

0 = Not a supervisor

1 = Supervisor

The offset in nanoseconds from the local clock to the system time. This value is useful for the detection of steps in time. This value updates when a PTP update is received.

The time when the Local Clock Offset was most recently sampled. This value is zero and the first-time stamp occurs when the device synchronizes with the Grandmaster clock.

The EUI-64 Identity of the CIP Sync™ Grandmaster clock to which the device is synced.