When sending an IEDnet Announcement request (0x1000/0x0001) message to a 510ACS or 520ACS, it is possible that the request will be rejected. The reason for the rejection will be indicated in the non-zero acknowledgement or NACK code returned via an IEDnet response. Possible values for this code are listed in the table below.
|
Constant Name |
Value |
Meaning |
|
NACK_ANNOUNCE_LOCKED |
0x10 |
Announcements below a certain priority are currently blocked due to an emergency condition. |
|
NACK_NO_ANNOUNCE |
0x11 |
Cannot create a new announcement due to an internal condition like all slots full. |
|
NACK_ANN_ACTIVATION |
0x12 |
Announcement failed to go active for any of a number of reasons, some internal errors. |
|
NACK_NO_ACG |
0x13 |
There is no Announcement Code Group for the request. This can only happen if the announcement type definitions in Enterprise have been messed with in a bad way. |
|
NACK_NO_ZONES |
0x14 |
No (defined) zones in the announcement request. Either the request was empty of zones or contained zone numbers that are not defined. |
|
NACK_BAD_MS_NUMBER |
0x15 |
Invalid (undefined) mic/source number in the announcement request. |
|
NACK_MS_IN_USE |
0x16 |
The requested mic/source is currently in use on another announcement. |
|
NACK_NO_TAKES |
0x17 |
A pre-recorded message request did not contain any (defined) Takes (digital audio files IDs). |
