Manitou is designed to allow for easy to understand and consistent event codes and descriptions, therefore, the event maps point incoming event codes to SIA-like codes, such as BA for Burg, FA for Fire, etc. There are additional event codes that are not "SIA-like" that exist in Manitou. The following descriptions explain the different types of codes and their purpose and use.
Events preceded with an asterisk (*) - Such as *A, *LC, *LT, etc...
These events are reserved for the Manitou Signal Handler and are used to redirect or indicate changes or violations.
For example, when Manitou receives an Open event (OP or the like) the Manitou Signal Handler checks to see if the account is monitoring an Open/Close schedule and if the Open is in violation of that schedule. If it is in violation it will take that Open event and change it to the violation event code such as an Unscheduled Open (*OU).
Events preceded with a percentage sign (%) - Such as (%! )
These events codes are reserved for RECEIVER generated events. These are items like Printer failures, Communications failures and restores from the Receiver itself. These should not be used in signal translations for events coming from the monitored site.
SIA-Like event codes.
These are the codes used in the event maps and are set to make understanding of the events clear and intuitive.
For Example: BA, BA1, BA2,... All point to Burglary alarms as do their restores. The Contact ID Event Map maps E130 to BA, E131 to BA1, etc... that way if you require a specific override based on the Contact ID code you DO NOT need a raw override to manage any changes based on the Contact ID codes.
In the event that you have a number of E140 and/or E150 Events programmed, these would need to be zone programmed either on the Transmitter or Customer as they often emulate non-intelligent events for technologies like AES.