Records not executing

If an Application Calculation Engine (ACE) Configuration (aceconfig) record is not executing, it could be because of one of these reasons:

• The aceconfig record is disabled. Check the Enable column on the ACE Summary display in the easy eXtended Operator Station (ezXOS) to determine if this is the cause.

• The aceconfig record is not being triggered. Check the Trigger Configuration tab on the aceconfig Row Edit form in the Advanced Database Editor (ADE).

• A PubSub input has no publishers. Check to see a Stale icon on the ACE Summary display in the ezXOS. Use the Multisubscriber to verify whether or not the topic has a value by subscribing to it.

• A Path input is not available. The ACE retries twenty times in case ab ACE routine is running before the RealTime database (RTDB) table points are available.

• The aceconfig record is missing a dataset field.

  Note: When you create the aceconfig record with an output point, the record will inherit its dataset from the output point. However, it is important to remember that you will have to set the aceconfig record's dataset manually, if you create an aceconfig record without an output point.

  Refer to The Application Calculation Engine (ACE) code (acecode) aborts without warning for another potential cause.