Programming the audio messenger interface (ami), Programming cautions – GAI-Tronics Sonic Alarm Sonic Alarm System Software Programming and User Manual User Manual

Page 44

Advertising
background image

Pub. 42004-410A

Sonic Alarm™ System Programming and User Manual

Page: 41 of 98

f:\standard ioms - current release\42004 instr. manuals\42004-410a.doc
03/09

Programming the Audio Messenger Interface (AMI)

The AMI configuration file, which may include tones and messages, is stored on a memory card and
inserted into the AMI. The memory card is removable and can be re-programmed from a PC equipped
with a card reader/writer device and associated software. The AMI Configuration Tool (ACT) software is
provided with the AMI.

Programming Cautions

When creating the Sonic system configuration file (.mio file) and the AMI configuration it is important to
consider the alarm and message priorities. It is very easy to create priority conflicts if one is not careful.
It is suggested that a priority list be generated prior to creating the configurations.
The Sonic System prioritizes alarm events from 1 to 10 (1 = lowest, 10 = highest).
The AMI prioritizes messages from 0 to 40 (40 = lowest, 0 = highest).

It is suggested that all AMI messages be set to the default priority of 3 in the AMI configuration. This
will ensure that all message prioritization is handled by the Sonic System configuration and not the AMI.
Since the AMI messages are assigned to Alarm Events in the Sonic configuration, the Alarm Event will
determine the priority. Priorities are set on the Event screen of the Sonic Console program.

In addition, when programming the number of times an alarm message should play, always set the AMI
configuration to play the message one time. Set the actual play time on the Alarm Event screen in the
Sonic Console program.

Advertising