Why %A trip characters return error “CONDITION NOT ACTIVE” when using sub-condition trip sequences
Problem
When using a sub-condition trip sequence, %A trip characters return error #CONDITION NOT ACTIVE# and it cannot be found in the diagnostic message from the troubleshooting guide as it can be seen below.
Solution
The %ASubCondName%, %ASubCondDef%, and %ASubCondDesc% trip sequences are not suitable for use with a “cleared” redirection trigger since the alarm is not active. Therefore, the #CONDITION NOT ACTIVE# diagnostic message appears.
For instance, the %ASubCondDesc% trip sequence gives a description of the alarm’s current active sub-condition. If the alarm is cleared, there is no active sub-condition, so it gives the #CONDITION NOT ACTIVE# message.
When using a sub-condition trip sequence, %A trip characters return error #CONDITION NOT ACTIVE# and it cannot be found in the diagnostic message from the troubleshooting guide as it can be seen below.
Solution
The %ASubCondName%, %ASubCondDef%, and %ASubCondDesc% trip sequences are not suitable for use with a “cleared” redirection trigger since the alarm is not active. Therefore, the #CONDITION NOT ACTIVE# diagnostic message appears.
For instance, the %ASubCondDesc% trip sequence gives a description of the alarm’s current active sub-condition. If the alarm is cleared, there is no active sub-condition, so it gives the #CONDITION NOT ACTIVE# message.
Released for: Schneider Electric UK
Need help?
Product Selector
Quickly and easily find the right products and accessories for your applications.
Get a Quote
Start your sales inquiry online and an expert will connect with you.
Where to buy?
Easily find the nearest Schneider Electric distributor in your location.
Help Centre
Find support resources for all your needs, in one place.