UMP (Unified Media Platform)

14.4 Troubleshooting

 

No Display

 

Below is an excerpt from the technical documentation of the Intel mainboard used in this UMP. If the device does not show an image on any display device, but the LEDs on the front of the device light up, you can diagnose the problems with the overview of blink patterns:

 

Front-panel Power LED Blink Codes

 

 

Type

Pattern

Processor initialization complete

On when system powers up, then off for 0.5 seconds

 

 

POST complete

On when system powers up, then off for 0.5 second

 

 

BIOS update in progress

Off when update begins, then on for 0.5 second, then off for 0.5 second; pattern repeats until BIOS update

is complete

 

 

Video error

On-off (0.5 second each) two times, then 3.0 second

pause (off) between on-off blink pattern; repeat entire

pattern (two on-off blinks and pause) until system is

powered off

 

 

Memory error

On-off (0.5 second each) three times, then 3.0 second

pause (off) between on-off blink pattern; repeat entire

pattern (three on-off blinks and 3-second pause) until

system is powered off

 

 

Thermal warning

On-off (0.5 second each) four times, then 3.0 second

pause (off) between on-off blink pattern; repeat entire

 pattern (four on-off blinks and 3-second pause) until

16th on blink, then end

 

If you determine that a thermal warning is preventing the system startup in a normal operating environment (=< 25° Celsius), unplug the device and wait approximately 20 – 30 minutes before powering it on again.


 

14.4 Troubleshooting (continued)

 

BIOS Errors

 

Due to varying temperature, power conditions and simply normal wear, the BIOS (Basic Input/Output System) may display an error which prevents it from booting. In such cases you will generally need a keyboard (UMP-R-3XX) to rectify the situation, though in some cases a reboot may be sufficient. Below is an excerpt from the technical documentation of the Intel mainboard used in this UMP:

 

 

Error Message Explanation

 

CMOS Battery Low

The battery may be losing power or deteriorating.

CMOS Checksum Bad

The CMOS checksum is incorrect. The CMOS memory may have been corrupted. Run Setup to reset values.

 

 

Memory Size Decreased

Memory size has decreased since the last boot. If no memory was removed, then memory may be faulty.

 

 

No Boot Device Available

System did not find a device to boot. Insert the recovery CD or key and follow instructions.

 

 

 

If you receive a CMOS Battery Low warning at boot time, you may need to replace the lithium/manganese dioxide cell (CR2032) battery on the device’s mainboard. If the device is still covered by warranty, contact UMP support for a replacement battery.

 

If you receive the No Boot Device Available error at boot time, enter the system BIOS and reload the default settings. Next make sure all USB peripherals except for the HIDs are disconnected, and attempt to start the device again. If this fails, contact UMP support.

 


 

14.4 Troubleshooting (continued)

 

UMP/OS and UMP-OSD Errors

 

Errors in the UMP-OSD are logged in the regular log directory. Any errors that impair the OSD’s functionality in a directly or indirectly undocumented manor may be reported to UMP support.

 

It is recommended to make a backup of your settings before changing any parameters! Please see chapter 1, section 8 for more information on creating a backup.

 

 

If you encounter errors in the device’s logfiles or in the OSD, you can attempt to diagnose the problem by checking the device’s log in the Web Interface. Advanced users may wish to enable debugging options in the OSD configuration to enable a more detailed output from the various responsible files. The following debugging and logging parameters can be configured under Settings -> All -> Debug in the Web Interface:

 

 

DEBUG = True 

 

Here you can specify the general verbosity of the ‘main-103.log’ logfile. Possible values: True = 1, False = 0 or 2 (full).

 

DEBUG_CHILDAPP = True

 

Here you can specify whether to provide verbose syntaxes to applications launched from the OSD. Possible values: True or False.

 

DEBUG_SKIN = False

 

Here you can specify whether to log skin specific errors. It is intended to provide additional debugging information when creating or modifying skins. Possible values: True or False).

 

DEBUG_IDLEBAR  = False

 

Here you can specify whether to show verbose logging information for the IdleBar in the OSD. Possible values: true = 1, false = 0 or 2 (full).


 

14.4 Troubleshooting (continued)

 

Below is the continuation of the parameter listing presented on the previous page:

 

DEBUG_IDLEBAR_FONT = 'tiny0'

 

Here you can specify the font to be used for IdleBar debug information on the OSD.

 

DEBUG_TIME = False

 

Here you can specify whether to log timing statistics. Possible values: True or False.

 

DEBUG_BENCHMARKING = False

 

Here you can specify whether to provide benchmarking debug statistics. Possible values: True or False.

 

DEBUG_BENCHMARKCALL = False

 

Here you can specify whether to provide function call benchmark statistics. Possible values: True or False.

 

DEBUG_STDOUT = True

 

Here you can specify whether to log additional output from commands and external applications launched from the OSD. Possible values: True or False.

 

DEBUG_RECORDSERVER = True # can be true = 1, false = 0 or 2 (full)

 

Here you can specify whether to provide verbose logging information for the Record server process. Possible values: True = 1, False = 0 or 2 (full).

 

DEBUG_ENCODINGSERVER = False

 

Here you can specify whether to provide verbose logging information for the Encoding server process. Possible values: True or False.

 

DEBUG_WEBSERVER = False # can be true = 1, false = 0 or 2 (full)

 

Here you can specify whether to provide verbose logging in formation for the Web server process. Possible values: True = 1, False = 0 or 2 (full).