OVERVIEW
Notification codes are used as a short hand indicator for the meaning of alarms and log entries. They are a 64 bit integer that are predefined within the architecture of Limelight XE™. Note, there is a range (0x00000001 to 0x0000FFFF) allocated for users to define custom messages. These can also be incorporated into the alarm system to trigger procedures when the log entry meets the user criteria. Unless specified below, all other codes are reserved for future use.
NOTIFICATION CODES
Code Revision - Version 2.2
| Code (hex) | Code (dec) | Description |
|---|---|---|
| 0x00000000 | 0 | Null or unknown reason for entry |
| Core - User Defined Codes | ||
| 0x00000001 | 1 | Start of user defined notification codes |
| 0x0000FFFF | 65535 | End of user defined notification codes |
| Core - Account Manager Codes | ||
| 0x00010000 | 65536 | Account Manager - Account successfully created |
| 0x00010010 | 65552 | Account Manager - Account successfully updated |
| 0x00010020 | 65568 | Account Manager - Account successfully deleted |
| 0x00010028 | 65576 | Account Manager - Account successfully recovered |
| 0x00010030 | 65584 | Account Manager - Deleted accounts purged from system |
| 0x00010040 | 65600 | Account Manager - Account binding successfully updated |
| 0x00010050 | 65616 | Account Manager - Binding made available to account |
| 0x00010060 | 65632 | Account Manager - Binding removed from account |
| 0x00010070 | 65648 | Account Manager - Token added to system |
| 0x00010080 | 65664 | Account Manager - Token updated in system |
| 0x00010090 | 65680 | Account Manager - Token deleted |
| 0x000100A0 | 65696 | Account Manager - Deleted tokens purged from system |
| 0x000100B0 | 65712 | Account Manager - Account invalid (not found) |
| 0x000100C0 | 65728 | Account Manager - Account has insufficient rights |
| 0x000100D0 | 65744 | Account Manager - Account store to DB failed |
| 0x000100E0 | 65760 | Account Manager - Token store to DB failed |
| 0x000100F0 | 65776 | Account Manager - Token timestamp failed |
| Core - License Server Codes | ||
| 0x00010100 | 65792 | License Server - Connection lost with management server |
| 0x00010110 | 65808 | License Server - Server on-line |
| 0x00010120 | 65824 | License Server - Engine attempting to access remote server |
| 0x00010130 | 65840 | License Server - Error in reporting status |
| Core - Database Manager Codes | ||
| 0x00010200 | 66048 | Database Manager - Database connection successfully created |
| 0x00010210 | 66064 | Database Manager - Database connection successfully deleted |
| 0x00010220 | 66080 | Database Manager - Database connected |
| 0x00010230 | 66096 | Database Manager - Database disconnected |
| 0x00010240 | 66112 | Database Manager - Database connection restored |
| 0x00010250 | 66128 | Database Manager - Database clean up completed |
| 0x00010280 | 66176 | Database Manager - Database failed to connect |
| 0x00010290 | 66192 | Database Manager - Connection creation failure |
| 0x000102A0 | 66208 | Database Manager - Connection open failure |
| 0x000102B0 | 66224 | Database Manager - Connection failed (DB engine went away) |
| 0x000102C0 | 66240 | Database Manager - Connection close failure |
| 0x000102D0 | 66256 | Database Manager - Failed to clean up database |
| 0x000102E0 | 66272 | Database Manager - Migration process failed |
| Core - Driver Manager Codes | ||
| 0x00010300 | 66304 | Driver Module - Driver loaded successfully |
| 0x00010310 | 66320 | Driver Module - All drivers loaded |
| 0x00010320 | 66336 | Driver Module - Driver started successfully |
| 0x00010330 | 66352 | Driver Module - All drivers started |
| 0x00010340 | 66368 | Driver Module - Driver paused successfully |
| 0x00010350 | 66384 | Driver Module - Driver resumed successfully |
| 0x00010360 | 66400 | Driver Module - Driver stopped successfully |
| 0x00010370 | 66416 | Driver Module - Driver reset successfully |
| 0x00010380 | 66432 | Driver Module - Module disabled, drivers unloaded |
| 0x00010390 | 66448 | Driver Module - Driver unexpectedly terminated |
| 0x000103A0 | 66464 | Driver Module - Driver failed to start |
| 0x000103B0 | 66480 | Driver Module - Driver failed to stop |
| Core - HTTP Server Codes | ||
| 0x00010500 | 66816 | HTTP Server - Session has started |
| 0x00010510 | 66832 | HTTP Server - Session has ended (timed out / logged off) |
| 0x00010520 | 66848 | HTTP Server - Failed to start |
| 0x00010530 | 66864 | HTTP Server - Document load has failed (file corrupt or not found) |
| 0x00010540 | 66880 | HTTP Server - Document parser has failed (invalid syntax) |
| 0x00010550 | 66896 | HTTP Server - General failure |
| 0x00010560 | 66912 | HTTP Server - SSL failed to connect |
| Core - Log Manager Codes | ||
| 0x00010600 | 67072 | Log Manager - Log cleared |
| 0x00010610 | 67088 | Log Manager - Log event code added |
| 0x00010612 | 67090 | Log Manager - Log event code deleted |
| 0x00010614 | 67092 | Log Manager - Log event code restored |
| Core - Schedule Manager Codes | ||
| 0x00010618 | 67096 | Schedules - Schedule item is active |
| 0x0001061A | 67098 | Schedules - Schedule item is inactive |
| 0x00010620 | 67104 | Schedules - Schedule class master binding registered |
| 0x00010630 | 67120 | Schedules - Schedule class master binding un-registered |
| 0x00010640 | 67136 | Schedules - Schedule class added |
| 0x00010650 | 67152 | Schedules - Schedule class updated |
| 0x00010660 | 67168 | Schedules - Schedule class deleted |
| 0x00010670 | 67184 | Schedules - Schedule class recovered |
| 0x00010680 | 67200 | Schedules - Master binding registration failed |
| 0x00010685 | 67205 | Schedules - Master binding un-registration failed |
| 0x00010690 | 67216 | Schedules - Class add function failed |
| 0x000106A0 | 67232 | Schedules - Class update function failed |
| 0x000106B0 | 67248 | Schedules - Item add function failed |
| 0x000106C0 | 67264 | Schedules - Item update function failed |
| 0x000106D0 | 67280 | Schedules - Item delete function failed |
| 0x000106E0 | 67296 | Schedules - Item failed to execute state change |
| 0x000106F0 | 67312 | Schedules - Token timestamp addition to database failed |
| Core - Security Codes | ||
| 0x00010700 | 67328 | Security - Blocked IP address attempted access |
| 0x00010710 | 67344 | Security - Login failed - Invalid credentials |
| 0x00010720 | 67360 | Security - Login failed - Maximum simultaneous user limit reached |
| 0x00010730 | 67376 | Security - Login failed - Account is disabled |
| 0x00010740 | 67392 | Security - Server connection accepted |
| 0x00010750 | 67408 | Security - Login successful |
| 0x00010760 | 67424 | Security - Logout successful |
| 0x00010770 | 67440 | Security - Administrator forced user logout |
| 0x00010780 | 67456 | Security - License invalid |
| 0x00010790 | 67472 | Security - License maximum instantiations exceeded |
| Core - IP Security Codes | ||
| 0x000107A0 | 67488 | Security - IP address added to security database |
| 0x000107B0 | 67504 | Security - IP address updated in security database |
| 0x000107C0 | 67520 | Security - IP address deleted from security database |
| 0x000107D0 | 67536 | Security - IP security type changed |
| 0x000107E0 | 67552 | Security - IP addresses imported into security database |
| Core - SMTP Client Codes | ||
| 0x00010800 | 67584 | SMTP Client - Failed to send message |
| Core - System Codes | ||
| 0x00010900 | System - Module started | |
| 0x00010910 | System - Module stopped | |
| 0x00010920 | System - Module paused | |
| 0x00010930 | System - Module resumed | |
| 0x00010940 | System - Object created | |
| 0x00010950 | System - Object updated | |
| 0x00010960 | System - Object deleted | |
| 0x00010970 | System - Property updated | |
| 0x00010980 | System - Timer started | |
| 0x00010990 | System - Sunrise | |
| 0x000109A0 | System - Sunset | |
| 0x000109B0 | System - User Action | |
| 0x000109C0 | System - Socket communications listening | |
| 0x000109C2 | System - Socket communications connecting | |
| 0x000109C4 | System - Socket communications connected | |
| 0x000109C6 | System - Socket communications disconnecting | |
| 0x000109C8 | System - Socket communications disconnected | |
| 0x000109CA | System - Socket communications error | |
| 0x000109D0 | System - UDP Broadcast - IP Check | |
| 0x000109D1 | System - UDP Broadcast - UDP attack (DOS, etc) | |
| 0x000109D2 | System - UDP Broadcast - Command from client or other server | |
| 0x000109E0 | System - Remote Server Manager - Running | |
| 0x000109E1 | System - Remote Server Manager - Failure | |
| 0x000109E2 | System - Remote Server Manager - No remote server specified | |
| 0x000109E3 | System - Remote Server Manager - Remote server failure | |
| Core - System Error Codes | ||
| 0x00010A00 | System - General failure | |
| 0x00010A10 | System - Failure to start module | |
| 0x00010A20 | System - Failed to create object | |
| 0x00010A30 | System - Failed to delete object | |
| 0x00010A40 | System - Failed to save settings to database | |
| 0x00010A50 | System - Failed to load settings from database | |
| 0x00010A60 | System - Failure in system timer (timed events will not occur) | |
| 0x00010A70 | System - Failed to handle message | |
| 0x00010A80 | System - Failure in driver hardware | |
| 0x00010A90 | System - Failure power supply | |
| 0x00010A91 | System - Failure power supply - Restored | |
| 0x00010AA0 | System - Failure battery backup | |
| 0x00010AA1 | System - Failure battery backup - Restored | |
| 0x00010AF0 | System - Hardware tampering detected | |
| 0x00010AF1 | System - Hardware tampering cleared | |
| Core - Procedure Manager Codes | ||
| 0x00010E00 | Procedure Manager - Alarm binding added | |
| 0x00010E10 | Procedure Manager - Alarm binding deleted | |
| 0x00010E20 | Procedure Manager - Event binding added | |
| 0x00010E30 | Procedure Manager - Event binding deleted | |
| Core - Driver Manager Codes | ||
| 0x00011000 | Driver Hardware - Initialized | |
| 0x00011010 | Driver Hardware - Ready | |
| 0x00011020 | Driver Hardware - Failure | |
| Driver - Access Control Codes | ||
| 0x00081100 | Access Control - Invalid (bad) token | |
| 0x00081101 | Access Control - Token valid but unassigned to account | |
| 0x00081102 | Access Control - Token valid but disabled | |
| 0x00081103 | Access Control - Token was passed back | |
| 0x00081105 | Access Control - Account has no privileges to asset | |
| 0x00081106 | Access Control - Account privileges to asset are out of schedule | |
| 0x00081108 | Access Control - Account privileges are in schedule but no assets assigned | |
| 0x00081109 | Access Control - Account privileges are in schedule but denied for asset | |
| 0x0008110A | Access Control - Account privileges are in schedule - access granted for asset (pass code only) | |
| 0x0008110B | Access Control - Account privileges are in schedule - access granted for asset (token only) | |
| 0x0008110C | Access Control - Account privileges are in schedule - access granted for asset (token or pass code) | |
| 0x0008110D | Access Control - Account privileges are in schedule - access granted for asset (token and pass code) | |
| 0x0008110E | Access Control - Account privileges are in schedule - access granted for asset (token and two factor pass code) | |
| 0x00081119 | Access Control - Account privileges override schedule - access denied for asset | |
| 0x0008111A | Access Control - Account privileges override schedule - access granted for asset (pass code only) | |
| 0x0008111B | Access Control - Account privileges override schedule - access granted for asset (token only) | |
| 0x0008111C | Access Control - Account privileges override schedule - access granted for asset (token or pass code only) | |
| 0x0008111D | Access Control - Account privileges override schedule - access granted for asset (token and pass code) | |
| 0x0008111E | Access Control - Account privileges override schedule - access granted for asset (token and two factor pass code) | |
| 0x00081120 | Access Control - Command not authorized for account | |
| 0x00081121 | Access Control - Command invalid | |
| 0x00081122 | Access Control - Command executed | |
| 0x0008112F | Access Control - System in lock down | |
| 0x00081130 | Access Control - Token not assigned to any user | |
| 0x00081131 | Access Control - Token inactive | |
| 0x00081132 | Access Control - Token active | |
| 0x00081133 | Access Control - Attempt to use suspended token to gain access | |
| 0x00081138 | Access Control - Attempt to use lost token to gain access | |
| 0x0008113C | Access Control - Attempt to use retired token to gain access | |
| 0x0008113E | Access Control - Attempt to use deleted token to gain access | |
| 0x000811F0 | Access Control - Access control request from reader | |
| 0x000811F1 | Access Control - Access control response to reader | |
| Driver - Video Codes | ||
| 0x00081200 | Video - Stream failure | |
| 0x00081210 | Video - Loss of video signal | |
| 0x00081220 | Video - Motion detected | |
| 0x00081230 | Video - Object detected | |
| Driver - Modbus Codes | ||
| 0x00081300 | Modbus - Unknown Error | |
| 0x00081310 | Modbus - Server Connected | |
| 0x00081320 | Modbus - Server Disconnected | |
| 0x00081330 | Modbus - Server Connection Restored | |
| 0x00081340 | Modbus - Server Connection Lost | |
| Driver - HID Global VertX / EDGE Codes | ||
| 0x00081400 | HID Global - Door forced | |
| 0x00081410 | HID Global - Door held or blocked open | |
| 0x00081420 | HID Global - Door obstruction cleared | |
| 0x00081480 | HID Global - Access control message | |
| Driver - ADS-B Ground Station Codes | ||
| 0x00081500 | ADS-B Station - Unknown Error | |
| 0x00081510 | ADS-B Station - Connected | |
| 0x00081520 | ADS-B Station - Disconnected | |
| 0x00081530 | ADS-B Station - Connection Restored | |
| 0x00081540 | ADS-B Station - Connection Lost | |
| 0x00081550 | ADS-B Station - Reconnecting |