Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Understanding Enbase Run Status Functions

Learn how Enbase Run Status Functions use controller state and fault information to determine a consistent equipment running status.

Enbase includes several Run Status Functions that interpret status and fault information from connected equipment controllers. These Functions help convert controller specific state information into a usable Enbase Run Status value.

Run Status Functions in the Library

  • Centurion Run Status
  • DE-3000 Run Status, including support for DE-3000 and DE-4000 controller types
  • EMIT Run Status
  • Equipment Run Status for more general equipment state and fault codes
  • TTD/TDXM Run Status
  • Consolidated Run Status for selecting status across multiple device sources

What Information Is Used?

The exact inputs depend on the Function, but Run Status logic can use state registers, fault registers, ready to start codes, shutdown codes, running codes, test mode status, and other controller specific values.

Why Run Status Functions Matter

Different controllers represent operating states differently. A Run Status Function provides a structured way for Enbase to interpret those controller specific values for monitoring, alarms, and other logic.

Configuration Assistance

Run Status Functions depend on the correct source Tags and controller specific codes. Contact Enbase Support if a Run Status value does not match the actual equipment state or if you need help configuring a controller integration.