Barco DP2K SLP Series, Руководство по обслуживанию

Страница: 380 / 410

R5906848 /04 DP2K SLP Series 380
→ Command messages also indicate originator.
Apr 6 14:09:07 localhost local0.info dp60[233]: system - load fcb file "lamp-on“
→ on fan controller board, lamp-on state is set.
External commands received by the Barco controller are preceded with the command (port = xxx)
string
Where xxx can be :
•
/dev/ttyS0:0
= Command comes from the serial connection labeled ( “ RS232 IN"). That can be from a
touch panel which is connected through a RS232 cable, or from a communicator which is connected
serially.
•
/dev/ttyS2:0
= Command comes from a touch panel attached with a dedicated cable to the back of the
projector (touch panel input).
•
/dev/ttyS3:0
= Command comes from the TI board. This is typically a command that is part of a macro
stored on that board.
•
10.36.62.17:43680
= Command comes from a remote machine with indicated IP address, followed by
the local of the remote machine that send this command internal. The command is initiated internally, due
to an internal reason.
•
button
= button is triggered from the keypad, attached to the projector.
Some examples :
•
command (port = /dev/ttyS2:0) - set network ip-address to 10.140.162.141 (dhcp off)
=
From the touch panel, the IP address of the projector was set to 10.140.162.141
•
command (port = 10.36.62.17:43680) - set network ip-address to 10.36.62.62 (dhcp
off)
= From a device with IP address 10.36.63.17, the IP address of the projector was changed to
10.36.63.17
•
command (port = /dev/ttyS0:0) - set dowser open
. = From a touch panel or PC, connected
serially (connector labeled "Touch panel"), the dowser was set to open.
•
command (port = /dev/ttyS0:0) - set lamp off
= From a touch panel or PC, connected serially
(connector labeled "Touch panel"), the lamp was powered off.
•
command (port = internal) - set lamp off
= For an internal reason the state of the lamp was set to
off.
•
command (port = button) - set dowser closed
= The dowser was closed from the keypad.
The error messages are explained in the troubleshooting list - code 5831
ICP log files
Example of log file content :
2010/04/06 09:02:40.964797 I ICP application 1.2(126) init Shows the ICP package
2010/04/06 09:02:40.980964 I successfully initialized the LoginLevelProtection mutex
2010/04/06 09:02:41.039022 I Autotiming initialized
2010/04/06 09:02:41.049829 I Autotiming using VSyncs
2010/04/06 09:02:41.051245 I Started Autotiming Port threads
2010/04/06 09:02:41.051755 I Autotiming started
2010/04/06 09:02:41.052149 I Port thread running
2010/04/06 09:02:41.052897 I Port thread running
2010/04/06 09:02:43.632304 I Started Autotiming Main thread
2010/04/06 09:02:43.633017 D Autotiming thread running
2010/04/06 09:02:43.633476 D Autotiming: blank the image
2010/04/06 09:02:43.792939 D Autotiming: unblank the image
...
Format
‘Date Time’ ‘Severity’ ‘message’
Where :
•
‘Date Time'
= the time when the event occurred.
•
‘Severity’
= One character severity indication can be : 'D ” (Debug) – “ E ” (Error) – “ I ” (Informational) -
“ U ” (User).
•
‘message’
= The actual error message.
Example :
Troubleshooting