How to Troubleshoot "Burnt" Looking Digits on the Scoreboard

Modified on Tue, 10 Sep at 7:33 PM

Friendly Reminder: For the most up-to-date information regarding this article, please use the following link: https://confluence.sportradar.ag/pages/viewpage.action?pageId=506711169

This is a very specific situation that may happen from time-to-time due environmental conditions.

The problem: Right after installation you may see “burnt” looking-like digits, as the one displayed in the image above.

Friendly Reminder: Please, make sure there is not an actual burnt digit before contacting the customer a potential problem.

To verify if this information , you must access the Vivotek configuration by typing the following commands within terminal or a command prompt:

ssh keeadmin@arena-gw.keemotion.com -L XXXX:localhost:XXXX
ssh KS-[servername] -L XXXX:[camera_IDnumber]:80

Next, you must access the web interface by opening a web browser and use the following information http://localhost:XXXX/ and change the syntax that shows "XXXX" to the port number you are using. This will allow you to check and see if the digits are flickering. If yes, this means that their scoreboard has no burnt digits. Also, you may realize it by the “halo” effect around the digits.

Pro Tip: The camera ID number can simply be typed using the following command on the server:

kee camera detect

Steps to Solve this issue: In order to fix this, you need to disable the Wide Dynamic Range (WDR) feature in the Vivotek image settings.

Open the following link using your XXXX: http://localhost:XXXX/setup/media/imaging.html and disable WDR under image settings >> exposure.

Pro Tip: Changing the exposure mode to “Manual” and adjusting the exposure time slider can also help in similar type of situations.

This should resolve the problem. If it does not, then it means the scoreboard has actual burnt digits and its calibration may not be successful, making it impossible to read properly.

Any question about this matter, please contact the Quality Experts or assign this problem in a ticket to them within Zendesk.