Dear Valued Customers,
Thank you for your business and continued interest in Mircom’s Fire Alarm Systems.
The FX-400 Series Contact ID (CID) dialer reporting has been updated from Firmware SO-434 V2.1.8 and Configurator MSW-045 V2.1.2 onwards.
Background:
All Contact ID messages have the following format: ACCT MT QXYZ GG CCC
Historical treatment of zone identification GG CCC:
Historically on the FX-400/FX-401, the portion of the contact ID message which yields zone identification were assigned based upon the entry order within the configurator for both input and output zones. There was no relationship to the physical location of the device, such as loop, address, and sub-address.
Current treatment of zone identification GG CCC:
In the currently released firmware, Mircom has updated the identification method of the device. The GG CCC portion of contact ID message is now used to provide direct linkage to the loop number, address number and sub-address number (if applicable). With this update, the FX-400/FX-401 treats the CCC as a representation of the device address and the GG as both the loop number and the sub-address number as follows:
| G | G | Loop | Subaddress | G | G | Loop | Subaddress | G | G | Loop | Subaddress | G | G | Loop | Subaddress | |||
| 0 | 1 | 0 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 2 | 1 | 3 | 1 | 3 | 1 | |||
| 0 | 2 | 0 | 2 | 1 | 2 | 1 | 2 | 2 | 2 | 2 | 2 | 3 | 2 | 3 | 2 | |||
| 0 | 3 | 0 | 3 | 1 | 3 | 1 | 3 | 2 | 3 | 2 | 3 | 3 | 3 | 3 | 3 | |||
| 0 | 4 | 0 | 4 | 1 | 4 | 1 | 4 | 2 | 4 | 2 | 4 | 3 | 4 | 3 | 4 | |||
| 0 | 5 | 0 | 5 | 1 | 5 | 1 | 5 | 2 | 5 | 2 | 5 | 3 | 5 | 3 | 5 | |||
| 0 | 6 | 0 | 6 | 1 | 6 | 1 | 6 | 2 | 6 | 2 | 6 | 3 | 6 | 3 | 6 | |||
| 0 | 7 | 0 | 7 | 1 | 7 | 1 | 7 | 2 | 7 | 2 | 7 | 3 | 7 | 3 | 7 | |||
| 0 | 8 | 0 | 8 | 1 | 8 | 1 | 8 | 2 | 8 | 2 | 8 | 3 | 8 | 3 | 8 | |||
| 0 | 9 | 0 | 9 | 1 | 9 | 1 | 9 | 2 | 9 | 2 | 9 | 3 | 9 | 3 | 9 | |||
| 4 | 0 | 0 | 10 | 5 | 0 | 1 | 10 | 6 | 0 | 2 | 10 | 7 | 0 | 3 | 10 | |||
| 4 | 1 | 0 | 11 | 5 | 1 | 1 | 11 | 6 | 1 | 2 | 11 | 7 | 1 | 3 | 11 | |||
| 4 | 2 | 0 | 12 | 5 | 2 | 1 | 12 | 6 | 2 | 2 | 12 | 7 | 2 | 3 | 12 | |||
| 4 | 3 | 0 | 13 | 5 | 3 | 1 | 13 | 6 | 3 | 2 | 13 | 7 | 3 | 3 | 13 | |||
| 4 | 4 | 0 | 14 | 5 | 4 | 1 | 14 | 6 | 4 | 2 | 14 | 7 | 4 | 3 | 14 | |||
| 4 | 5 | 0 | 15 | 5 | 5 | 1 | 15 | 6 | 5 | 2 | 15 | 7 | 5 | 3 | 15 | |||
| 4 | 6 | 0 | 16 | 5 | 6 | 1 | 16 | 6 | 6 | 2 | 16 | 7 | 6 | 3 | 16 | |||
| 4 | 7 | 0 | 17 | 5 | 7 | 1 | 17 | 6 | 7 | 2 | 17 | 7 | 7 | 3 | 17 | |||
| 4 | 8 | 0 | 18 | 5 | 8 | 1 | 18 | 6 | 8 | 2 | 18 | 7 | 8 | 3 | 18 | |||
| 4 | 9 | 0 | 19 | 5 | 9 | 1 | 19 | 6 | 9 | 2 | 19 | 7 | 9 | 3 | 19 |
Example:
The GG CCC portion of the contact ID in this updated dialer operation for a device on loop 2, with address 4 and sub-address 1 would be sent as 21 004.
Summary:
With this latest approach, not only can the received message at the Central Station be uniquely decoded to determine the location of the event down to the physical location but each even now has a unique GG CCC.
We thank you for your continued support.
If you have any questions or comments, please contact us directly at: [email protected]
Sincerely,
Mircom Group of Companies
