States

ABB Field Information Manager Learning Center

The Loop Check Status of each node is indicated by one of the below described states.

The Status section provides an overview about the number of nodes with a certain status.
Clicking on a status filters the detailed grid for all nodes with the selected status.

Results from previous Loop Check View are indicated by a history icon.

Are you looking for support or purchase information?

Passed

All test points of the selected Loop Check Scope are passed.

This indicates that the compete signal loop from system down to field device and back is working appropriately and that the configuration is correct.

Failed

One or more test points of the selected Loop Check Scope are failed.

Additional status information in failed test group provides the possible cause and suggested actions to pass Loop Check.

This indicates communication problems in the signal loop from system down to field device and back or mismatches in the configuration between system, field device and used Loop Check settings in FIM.

Not available

Node or connected field device is not reachable or does not support required functionality.

Additional status information in failed test group provides the possible cause and suggested actions to pass Loop Check.

This indicates general communication problems in the signal loop from system down to field device and back because the Loop Check in FIM cannot be started correctly.

Not used

Node is not used (can only be documented in manual Loop Check).

This Loop Check state can be applied to all nodes which are not in use, e.g. because they are empty and not wired to any device.

In Execution

Loop Check is currently in execution.

The overall progress of the executed Loop Check for all selected nodes is indicated in the Info Center. Once finished for a node, the node state changes to one of the above mentioned states (e.g. Passed or Failed).

In Queue

Loop Check is currently in queue and will be executed soon.

FIM performs as many automatic Loop Checks in parallel as possible, but all nodes that cannot be executed immediately are put into queue until resources are free for execution.

Untested

Node is untested without any existing Loop Check result.

Loop Check

Navigation

Select region / language