Barco DP2K-12C, Руководство по обслуживанию

Страница: 79 / 359

4. Troubleshooting
Where :
•
‘
Time’
= the time when the event occurred
•
‘facility code’
= component level that generates a log message
•
’severity code’
= the severity can be : info – debug – warning – alert – err.
•
‘component name’
= component name that generates a log message.
-
dp60
= main process
-
kernel
= Linux kernel
-
router
= component which manages the router
-
TI_marriage
= component which handles the marriage
-
clo
= component which handles Light Sensor logic
-
license-manager
= internal license manager
-
crypto memory
= process which handles communication with crypto memory module (ID card)
•
‘pid’
= Process identi fi er. The internal process identi fi er, of the component generating the log message.
•
‘message’
= The actual error message.
The Barco controller inserts every hour an unique entry in the Barco log fi le and in the TI log fi le. This is done to be able to synchronize
events in both log fi les, when the clocks are not aligned. It will also be used for a tool, that is still to be implemented, that will merge
both log fi les, to make better analysis.
Example of such an entry :
Feb 3 02:41:16 localhost local0.info dp60[233]: log mark - 0000003c1b84 - 8
Each Barco entry into a TI log is proceeded with a B.
What does the id means (as in the example) :
•
0000003c
- the fi rst 4 bytes give a hex interpretation of how many time the system has been booted.
- 3c hex is 60 in decimal. It means that this system has been booted 60 times. Every boot cycle increases the timer with 1.
•
1b84
= the last two bytes, are random unique 2 bytes.
•
8
= the last digit indicates the number of hours passed in this boot cycle (in a decimal value). Every boot cycle resets this
number to 0.
Ethernet connection messages in log fi le (some examples).
Apr 6 14:05:19 localhost local0.info dp60[233]: main - closing connection of
150.158.197.64:43680 (keep-alive time expired)
→ after 15 minutes of inactivity projector will close connection.
Apr 6 14:08:55 localhost local0.info dp60[233]: main - accepted connection from
150.158.192.133:43680
→ connection from communicator, from pc with ip address 150.158.192.133
Apr 6 14:08:58 localhost local0.info dp60[233]: log (port = 150.158.192.133:43680:1e) - lo-
gon-phmt-barco-default
→ communicator inserts in log fi le, who logged on to projector
Apr 6 14:09:07 localhost local0.info dp60[233]: command (port = 150.158.192.133:43680:1e) - set
lamp on
→ 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 :
R5905043 DP2K-12C/11CX 19/02/2018 75