Actions

Difference between revisions of "PA Failure State System"

From Zenitel Wiki

(PA Failure State System)
(PA Failure State System)
Line 6: Line 6:
  
 
The various IP-ARIO PA faults and states are reported as sub events on the [[Faulty_Station_Line_(Event_Type) | 13-Faulty Station Line]].<br>
 
The various IP-ARIO PA faults and states are reported as sub events on the [[Faulty_Station_Line_(Event_Type) | 13-Faulty Station Line]].<br>
When fault state is reported OFF from IP-ARIO the fault state in AMCD will still be active until acknowledge and cleared by the user. <br>
+
When a fault state is reported OFF from IP-ARIO, the fault state in AlphaCom will stay active until acknowledged and cleared by the user. <br>
 +
 
 
Subevent 10-18 will only be reported once. The error will stay active in the system, even if the error has been removed, until one have performed an [[PA_Failure_State_System#Fault_ACK.2FCLEAR_on_DAK_keys|ACK/CLEAR sequence]].
 
Subevent 10-18 will only be reported once. The error will stay active in the system, even if the error has been removed, until one have performed an [[PA_Failure_State_System#Fault_ACK.2FCLEAR_on_DAK_keys|ACK/CLEAR sequence]].
  

Revision as of 09:16, 1 December 2015

PA Failure State System

When used as PA interface some of the IP-ARIO inputs are used for reporting failure state of 1 or 2 amplifiers.


The various IP-ARIO PA faults and states are reported as sub events on the 13-Faulty Station Line.
When a fault state is reported OFF from IP-ARIO, the fault state in AlphaCom will stay active until acknowledged and cleared by the user.

Subevent 10-18 will only be reported once. The error will stay active in the system, even if the error has been removed, until one have performed an ACK/CLEAR sequence.

A NVRAM structure is used for additional configurable elements.
Configurable elements are:

  • Default description text intended for use in fault mail to PA panels. The text are sent to event handler as %2.nam
  • Default placement of status indication in the "DAK block" related to the PA interface. ( DAK block)
  • Default priority used for fault mails. (Unique priority make it easy to remove specific fault from mail queues)
Event Handler IP-ARIO failure states
Event text (%2.nam) SUB event (%sev) DAK block index (%pai) Priority (%pap) Comment
FAULT ACK 2 7 50 Event text for debugging
FAULT CLEAR 3 10 50 Event text for debugging
ZONE BLINK 4 1 50 Event text for debugging
ZONE STEADY 5 1 50 Event text for debugging
IPA DOWN 10 4 140
RELAY 1 11 2 100
POWER 1 12 5 101
LINE MON 1 13 8 102
XLR MON 1 14 11 103
RELAY 2 15 3 104
POWER 2 16 6 105
LINE MON 2 17 9 106
XLR MON 2 18 12 107
- 20 - - "Live" State of Line Mon. 1
- 21 - - "Live" State of Line Mon. 2
- 22 - - "Live" State of Amp 1 Discon.
- 23 - - "Live" State of Amp 2 Discon.
- 24 - - "Live" State of 20KHZ Mon. 1
- 25 - - "Live" State of 20KHZ Mon. 2
- 26 - - "Live" State of Level Detect. 1
- 27 - - "Live" State of Level Detect. 2

Updated Event Handler Macros and $DP messages

wudd        (Added label and string variables)
%udd        (Added label and string variables)
gind        (NEW  group version of ind)
%paf        (NEW, PA fault in UDP group check)
%pai        (NEW, PA fault indicator in DAK block)
%pap        (NEW, PA fault mail priority)
%prci       (NEW, Current Physical RCI state)
%prco       (NEW, Current Physical RCO state)
$PA_CMD     (NEW, PA command, ACK/CLEAR)
$SET_IPRCO  (NEW, Set physical RCO on IP station/IP-ARIO)
$CANCEL_MAIL(Added option for delete mail with specific priority, Mail-id = 253)


Default Grouping of fault state on CRM DAK

The status of faults of one IP-ARIO are grouped to one CRM DAK block of 3 * 4 DAK keys.

Fault Indication On DAK panel
ZONE FAULT RELAY 1 RELAY 2
IPA DOWN POWER 1 POWER 2
FAULT ACK LINE MON 1 LINE MON 2
FAULT CLEAR XLR DISCON 1 XLR DISCON 2

PA fault Example Configuration

Fault Handeling on a CRM with DAK pannels

The status of faults of one IP-ARIO are grouped to one CRM DAK block of 3 * 4 DAK keys.
DAK block

The block number used for each IP-ARIO is configured in AlphaPro->Station-> "used defined parameter" (%EXP).
Block number 1 to 8.

Example system:

  • Three IP-ARIO in UDP group 1, DAK block 1,2 and 3 programmed in EXP.
  • Two CRM with DAK modules in station group 2 and UDP 2.
  • RCO 1 used for fault indication of fault state in UDP group 1 (ON or OFF)

Event for fault indication and fault mail

The following event will do: (in this order)

  • Set fault indicators on CRM DAK panels in CRM group 2 in the DAK block position.
  • Send Mail and Cancel Mail to CRM group 2, with related fault priority.
  • Set Zone fault indicator on CRM DAK blinking/steady/off
  • Set fault indicator led on IP-ARIO
  • Set global fault indicator (RCO) related to fault in UDP group 1 (Do we need blinking?)
  • Control ACK and CLEAR status led for the related DAK Block leds.
Owner:        UDP 1
Event Type    13-Faulty station line
Sub Event     255
When Change   ON/OFF
Action:
if %op(%sev,>=,10)
  gind 2 %pai(%1.exp) 1 1
  if %chg(1,0)
    $STM %1.ref L85 U%pap '(%1.dir) %2.nam'
    stop
  endif
  $CANM %1.ref L85 NM253 U%pap
  stop
endif
$SLRC W1 U%paf(1)
if %op(%sev,=,4)
  gind 2 %pai(%1.exp) 1 2
  ind %1.phy 1 1 2
  stop
endif
gind 2 %pai(%1.exp) 1 1

Fault ACK/CLEAR on DAK keys

  • One common ACK event for all CRM stations in UDP 2 for each IP-ARIO.
Owner:        UDP 2
Event Type    30-DAK AS RCI
Sub Event     CRM DAK key used for Ack
When Change   ON
Action:
$PA_CMD L(IP-ARIO) U01
  • One common Clear event for all CRM stations in UDP 2 for each IP-ARIO.
Owner:        UDP 2
Event Type    30-DAK AS RCI
Sub Event     CRM DAK key used for Clear
When Change   ON
Action:
$PA_CMD L(IP-ARIO) U02