Frequently Asked Question
Monitoring of Walk In DMS sign
Last Updated 5 years ago
Walk in DMS can be monitoring using:
I. NTCIP MAINBOARD (SNMP)
DMS sign has the main board 9246 with an NTCIP FW. You can use regular SNMP commands in order to monitor the health of the system. Attached please review the MIB files. This can be done by:
1. Downloading and install net-snmp executables from:
https://sourceforge.net/projects/net-snmp/files/net-snmp%20binaries/5.5-binaries/
2. Execute following command from the folder where snmp executables are installed (usually c:/usr/bin/). This commands give you 16 bits of possible errors
snmpget -v1 -c public udp:IP:161 .1.3.6.1.4.1.1206.4.2.3.9.7.1.0,
where IP is the IP of the DMS sign
Name/OID: shortErrorStatus.0; Value (Integer): 24576
A bitmap of summary errors. When a bit is set, the error is presently active. When a bit is clear the error is not currently active. If no sensor is present or supported (for a corresponding bit), the bit shall not be set.
The bits are defined as follows:
Bit 0 - reserved (lowest bid)
--The definition contained in Version 1 stated 'other'. However, 'other' is no longer allowed as a value.
Bit 1- communications error - this bit shall be set if any error associated with the communications between the central computer and the device occurs.
Bit 2- power error - this bit shall be set if any error associated with the power supply to any component occurs (see the objects dmsPowerFailureStatusMap and lowFuelThreshold).
Bit 3- attached device error - this bit shall be set if any error associated with attached (supported, and enabled) external devices occurs.
Bit 4- lamp error - this bit shall be set if any errors associated with any lamp occurs (see the objects lampFailureStuckOn and lampFailureStuckOff). This bit is only applicable to devices that support lamps such as fiber optic signs or front-illuminated reflective signs. This bit is not applicable to lamps or fluorescent lights illuminating the housing or cabinet.
Bit 5- pixel error - this bit shall be set if any errors associated with anypixel occurs (see the objects pixelFailureTableNumRows for NTCIP 1203v1 deployments, and pixelFailureTableNumRows, and/or dmsPixelFailureTestRows and dmsPixelFailureMessageRows for NTCIP 1203v2 deployments.). This bit is only applicable to devices that support illumination of individual pixels, but not to drum signs. Note that certain sign technologies such as flip disk only sign may not be able to determine pixel errors.
Bit 6- photocell error - this bit shall be set if any errors associated withthe supported light sensors occurs (see the object dmsLightSensorStatusMap).
Bit 7- message error - this bit shall be set if any errors associated withactivating and/or displaying a message occurs (see the object dmsActivateMsgError).
Bit 8- controller error - this bit shall be set if any errors associated with the controller occurs (see the controllerErrorStatus object)
Bit 9- temperature warning - this bit shall be set if any of thetemperature values detected by the device exceed non-standardized temperature values (see the object tempSensorWarningMap). This bit is included to allow vendors or agencies to define vendor- or agency-specific threshold objects that indicate temperature changes that are of interest but not dangerous to the life-expectancy of the device (see also the 'critical temperature' bit)
Bit 10- climate-control system error - this bit shall be set if any errors associated with the climate control systems such as fans and/or heaters occurs (see the object dmsClimateCtrlStatusMap).
Bit 11- critical temperature error - this bit shall be set if the critical temperature as defined by the value of the critical temperature objects have been exceeded. (see the object dmsTempSensorHighCriticalTemperature and dmsTempSensorLowCriticalTemperature).
Bit 12- Drum-sign Rotor error - This bit shall be set if any errors associated with the rotor of a drum sign occurs.
Bit 13- This bit shall be set if any door to any DMS field component (cabinet or housing) is open(see the object dmsStatDoorOpen).
Bit 14- Humidity warning - This bit shall be set if any humidity sensorsensor is reporting a humidity warning (see the object dmsHumiditySensorStatusMap). To track a history of transient error conditions utilize the event logging table located in the Global Objects Definitions NTCIP 1201 v03.
Bit 15 - reserved (highest bit) DMS.shortErrorStatus:code Data Element
3. You should receive a reply similar to that:
SNMPv2-SMI::enterprises.1206.4.2.3.9.7.1.0 = INTEGER: 24576
In this example Bit 13 =1 which shows open door.
24576 - 6000H or 1010000000000000 shows door open (Bit 13 set to 1)
16384 - 4000H or 1000000000000000 shows everything is OK. No errors
4. Once you have the main error you can run additional commands to see details as per the bit description above. For example if you are getting error for the temperature you can run following commands for further information:
dmsTempSensorHighCriticalTemperature and dmsTempSensorLowCriticalTemperature).
5. You can run following command to get a list of all NTCIP commands available:
snmpwalk -v1 -c public udp:IP:161 .1.3.6.1.4.1.1206.4.2.3
where IP is the IP address of your DMS sign
You can see a sample report as an output of the command in the attached file snmpwalkreport.txt
6. You can use the output of the SNMP command with SolarWind monitoring software. See information how to setup here:
https://support.solarwinds.com/Success_Center/Network_Configuration_Manager_(NCM)/Download_configuration_through_SNMP
7. You can use the output of the SNMP command with Nagios monitoring software. See information how to setup here:
https://assets.nagios.com/downloads/nagiosxi/docs/Using-The-SNMP-Walk-Wizard.pdf#_ga=2.254094472.1600150165.1528125893-561842929.1527708903
II. NON NTCIP MAINBOARD
1. Using API. You can us the attached Windows OS executable to automate the execution of the program and generate the log files which can be the parsed and integrated with monitoring Software such as Nagios or SolarWinds (For more information and examples please see http://www.webinject.org/plugin.html ) to send emails out in the event of errors or warning. Additionally error and warning report for particular LEDs that are experiencing problems can be downloaded. The reports contains information about the individual LED and additional information such as time stamps etc.
2. You can use VMS controller or Sigma software to look at information for main board, run test on the sign such as pixel tests etc..
I. NTCIP MAINBOARD (SNMP)
DMS sign has the main board 9246 with an NTCIP FW. You can use regular SNMP commands in order to monitor the health of the system. Attached please review the MIB files. This can be done by:
1. Downloading and install net-snmp executables from:
https://sourceforge.net/projects/net-snmp/files/net-snmp%20binaries/5.5-binaries/
2. Execute following command from the folder where snmp executables are installed (usually c:/usr/bin/). This commands give you 16 bits of possible errors
snmpget -v1 -c public udp:IP:161 .1.3.6.1.4.1.1206.4.2.3.9.7.1.0,
where IP is the IP of the DMS sign
Name/OID: shortErrorStatus.0; Value (Integer): 24576
A bitmap of summary errors. When a bit is set, the error is presently active. When a bit is clear the error is not currently active. If no sensor is present or supported (for a corresponding bit), the bit shall not be set.
The bits are defined as follows:
Bit 0 - reserved (lowest bid)
--The definition contained in Version 1 stated 'other'. However, 'other' is no longer allowed as a value.
Bit 1- communications error - this bit shall be set if any error associated with the communications between the central computer and the device occurs.
Bit 2- power error - this bit shall be set if any error associated with the power supply to any component occurs (see the objects dmsPowerFailureStatusMap and lowFuelThreshold).
Bit 3- attached device error - this bit shall be set if any error associated with attached (supported, and enabled) external devices occurs.
Bit 4- lamp error - this bit shall be set if any errors associated with any lamp occurs (see the objects lampFailureStuckOn and lampFailureStuckOff). This bit is only applicable to devices that support lamps such as fiber optic signs or front-illuminated reflective signs. This bit is not applicable to lamps or fluorescent lights illuminating the housing or cabinet.
Bit 5- pixel error - this bit shall be set if any errors associated with anypixel occurs (see the objects pixelFailureTableNumRows for NTCIP 1203v1 deployments, and pixelFailureTableNumRows, and/or dmsPixelFailureTestRows and dmsPixelFailureMessageRows for NTCIP 1203v2 deployments.). This bit is only applicable to devices that support illumination of individual pixels, but not to drum signs. Note that certain sign technologies such as flip disk only sign may not be able to determine pixel errors.
Bit 6- photocell error - this bit shall be set if any errors associated withthe supported light sensors occurs (see the object dmsLightSensorStatusMap).
Bit 7- message error - this bit shall be set if any errors associated withactivating and/or displaying a message occurs (see the object dmsActivateMsgError).
Bit 8- controller error - this bit shall be set if any errors associated with the controller occurs (see the controllerErrorStatus object)
Bit 9- temperature warning - this bit shall be set if any of thetemperature values detected by the device exceed non-standardized temperature values (see the object tempSensorWarningMap). This bit is included to allow vendors or agencies to define vendor- or agency-specific threshold objects that indicate temperature changes that are of interest but not dangerous to the life-expectancy of the device (see also the 'critical temperature' bit)
Bit 10- climate-control system error - this bit shall be set if any errors associated with the climate control systems such as fans and/or heaters occurs (see the object dmsClimateCtrlStatusMap).
Bit 11- critical temperature error - this bit shall be set if the critical temperature as defined by the value of the critical temperature objects have been exceeded. (see the object dmsTempSensorHighCriticalTemperature and dmsTempSensorLowCriticalTemperature).
Bit 12- Drum-sign Rotor error - This bit shall be set if any errors associated with the rotor of a drum sign occurs.
Bit 13- This bit shall be set if any door to any DMS field component (cabinet or housing) is open(see the object dmsStatDoorOpen).
Bit 14- Humidity warning - This bit shall be set if any humidity sensorsensor is reporting a humidity warning (see the object dmsHumiditySensorStatusMap). To track a history of transient error conditions utilize the event logging table located in the Global Objects Definitions NTCIP 1201 v03.
Bit 15 - reserved (highest bit) DMS.shortErrorStatus:code Data Element
3. You should receive a reply similar to that:
SNMPv2-SMI::enterprises.1206.4.2.3.9.7.1.0 = INTEGER: 24576
In this example Bit 13 =1 which shows open door.
24576 - 6000H or 1010000000000000 shows door open (Bit 13 set to 1)
16384 - 4000H or 1000000000000000 shows everything is OK. No errors
4. Once you have the main error you can run additional commands to see details as per the bit description above. For example if you are getting error for the temperature you can run following commands for further information:
dmsTempSensorHighCriticalTemperature and dmsTempSensorLowCriticalTemperature).
5. You can run following command to get a list of all NTCIP commands available:
snmpwalk -v1 -c public udp:IP:161 .1.3.6.1.4.1.1206.4.2.3
where IP is the IP address of your DMS sign
You can see a sample report as an output of the command in the attached file snmpwalkreport.txt
6. You can use the output of the SNMP command with SolarWind monitoring software. See information how to setup here:
https://support.solarwinds.com/Success_Center/Network_Configuration_Manager_(NCM)/Download_configuration_through_SNMP
7. You can use the output of the SNMP command with Nagios monitoring software. See information how to setup here:
https://assets.nagios.com/downloads/nagiosxi/docs/Using-The-SNMP-Walk-Wizard.pdf#_ga=2.254094472.1600150165.1528125893-561842929.1527708903
II. NON NTCIP MAINBOARD
1. Using API. You can us the attached Windows OS executable to automate the execution of the program and generate the log files which can be the parsed and integrated with monitoring Software such as Nagios or SolarWinds (For more information and examples please see http://www.webinject.org/plugin.html ) to send emails out in the event of errors or warning. Additionally error and warning report for particular LEDs that are experiencing problems can be downloaded. The reports contains information about the individual LED and additional information such as time stamps etc.
2. You can use VMS controller or Sigma software to look at information for main board, run test on the sign such as pixel tests etc..
