Friendly Reminder: For the most up-to-date information regarding this article, please use the following link: https://confluence.sportradar.ag/display/SK/Scorebot+-+ScoreLink+or+ScoreHub+by+Sportzcast
What is a Scorebot?
A Scorebot is a device that is used to receive game score/time data from an arena scoreboard when using an OCR camera is not possible. The bot receives data from the arena’s scoreboard controller and uploads the data to Sportzcast, the vendor for the bots. The Keemotion system grabs the score/time data from Sportzcast’s servers and applies it on the stream overlay.
An Example of a Scoreboard Controller from Daktronics is show in the image below (There are many manufacturers of scoreboard controllers). The grey headphone jack converts to a DB9 cable on the ScoreLink to gather the necessary scoreboard data. (Sometimes with an older scorebot there is a DB25 cable that will connect to the scoreboard controller).
Scorebots need to be connected by an Ethernet cable to a network at the arena. It does not need to be on the same network as the arena server. Friendly Reminder: Ports 1402 and 1403 must be open on the network(s).
Below is a diagram illustrating the hardware setup for a scorebot:
There are two types of Scorebots currently being used which are shown within the images below:
The second model on the far right (“ScoreLink”) can get power through the Ethernet cable (PoE). Not every unit will have a separate power cable. If it does, the cable will go into the USB port on the device. According to Sportzcast the best method to use for power is PoE.
Scorebot Settings
To check a Scorebot configuration for an arena, use the following steps:
1.) Go to the Arena in WebAdmin
2.) Go to Settings
3.) Go to the director.conf file within WebAdmin
An arena that has a Scorebot installed must have the following code in the image below within the director.conf file. The ScoreBotNumber
property within the image below should have a unique number for the scorebot that is assigned to the arena. Make sure this is added to the code below with the correct scorebot number.
//ScoreBot Config
#define SKIP_READER1
#define SKIP_READER2
#define SKIP_READER3
#define SCOREBOARDLINK SBL_MODE_SCOREBOT
#ifdef SCOREBOARDLINK
<ConfigureFilter Name="sbl">
<Property Name="Configuration">scorebot.sportzcast.net:1402</Property>
<Property Name="ScoreBotNumber">50440</Property>
<Property Name="LicenseKeyScorebot">GT keemotion1 2ABAFCA5E61065515D5A320168EECD6B</Property>
<Property Name="Channel">0</Property>
<Property Name="Delay">00000</Property>
</ConfigureFilter>
#endif
Basic Scorebot Troubleshooting
If a client who uses a Scorebot reports that they are not seeing the score show on their production overlay, follow the steps below.
1.) Confirm the bot number is correct from the client. It is a 3-5 digit ID number on the device. Make sure this number is the same as the ScoreBotNumber
property in director.conf in Webadmin.
2.) Confirm if the bot is correctly plugged into power, internet, and the scoreboard controller. Ask for a picture of the bot while it is connected. Also ask for a picture of where the bot is plugged into on the scoreboard controller.
3.) Ask the client to unplug the Ethernet cable from the bot and plug it into a laptop. Can they access the internet? If not, go to next step.
4.) Ask the client to check the other end of the Ethernet cable. Is it correctly plugged into a network router or wall socket? If possible, ask the client to switch the cable into a different port on the router/panel and try to access internet again.
If the client is able to access the internet, they should then plug the cable back into the Scorebot. Check the production (or start one if there is none) for score/time/game clock/quarter and restart it if there is no information that shows up automatically.
Advanced Troubleshooting
Sportzcast Support Web GUI
Sportzcast has an admin program that allows you to see the individual bots in their organization and their online/offline status. You can access the program using the following link: http://psa.sportzcast.net/
Next, you will be asked for a username and password. Use the email [email protected] and for the password, ask a senior member of your team.
Next, you will see the main page which is similar to the below image listing all the bots under the Keemotion Franchise. From here, you can also search for specific bots by entering the Scorebot # in the Value field.
To see the list of currently online and functioning bots, select Online Bots in the dashboard at the top of the page.
Click on the button that states "View JSON" on the far right of the list of bots to view the XML live data.
By selecting View Bot, you will be brought to the specified Bot's configuration page. Here will be all the information regarding the device (This is similar to the data in the old BOTServer Client).
We are also able to change the Vendor Sport Code through the new GUI.
To see a bot’s XML view from this screen, scroll down to the Sportzbot Live Data section and select JSON.
How this helps troubleshooting
If you are able to connect to a bot and view it’s data but there are issues with showing the score/time on the Keemotion side, we can assume there is some sort of issue with the Keemotion system’s configuration. Checking the configuration in the
director.conf
within WebAdmin. This is a good first step for troubleshooting purposes.If you cannot connect to the bot or the data is not accurate, we can assume the issue is with the way the bot is being plugged in, it’s network connection or possibly the bot itself. (In this case follow the hardware troubleshooting steps below)
Hardware Troubleshooting
If a client has already tested the Ethernet cable connected to the Scorebot and they are unable to access the internet on a laptop, try the following steps below:
1.) The client should switch out the cable for a different one and then test the laptop internet again. If there’s still no connection, they should contact their IT staff to check their network equipment.
2.) If the client is able to access the internet on their laptop after swapping the cables, they should re-plug the cable back into the Scorebot. Check the bot’s status on the Sportzcast Support Web GUI or BOTServer Client. If the bot does not come back online within 1 minute, go to step
3.) Tell the client that they will need their IT department to check and see if their network has ports TCP 1402 and UDP 1403 open for outbound traffic.
4.) If a bot is online and visible on the Tester software and there isn't information showing on the data output, then there is an issue with the way the data is being processed by the bot. Check to see if the Scorebot’s data cable is good. Ask the client to unplug the cable that’s on the scoreboard controller and plug it into a different data port. Most controllers have more than 1 output port. An example of this is within the below image.
ScoreLink Light Indicator Definitions are show below
Scoreboard - this light should be blinking which shows that the data is transmitting with the scoreboard controller.
In-range - this light is for wireless setups of scoreboard controllers
Power - this light should always be solid green.
Server - this light should be blinking green when looking for an IP address and blinking blue when it is communicating properly.
USB - this light is for a direct connection with a computer to the ScoreLink device, in order to read scoreboard information. This is an optional setup.
SportzCast Operating Hours
If you find that a license has expired or is about to expire, please use the following contact information below in regards to the subscription/invoice renewal for the scorebot.
Primary Contact: Megan Gustafson - [email protected]
Secondary Contact: Samuel Provencher - [email protected]
Sportzcast Support Team
Email: [email protected] or [email protected]
Website: geniussports.com
Telephone #: 321-888-3800
Missing Scorebots?
If you find a scorebot for an arena is missing from the BOTServer Client, email Sportzcast Support with the bot number and name of the client and request to have the scorebot added to the Keemotion franchise account
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article