Data Studio Basketball: How to verify LiveStats IAU settings for NCAA communication?

Topic

  • How to verify LiveStats IAU settings for NCAA Basketball communication?
  • Do this if the XML File is NOT appearing in the specified folder or the file is not named correctly.

Environment

  • Product: 
  • Component: Data Studio Basketball, COM file, NCAA LiveStats for Basketball (NLS for Basketball), Genius Sports
  • Control System: Show Control System (SCS)
my apps_ds basketball 3.jpg
Note: The following information and configuration is just an example. Your setup may be different. For instance, the following is expecting both the interface and data provider XML file to be on the same machine. If that is not the case, the folder on our Data Studio computer will need to be shared so that Genius can be configured to output the XML file to the shared folder.
Do not run DSTI and Data Studio at the same time.  This will cause inconsistencies with data.  
 

Steps

Reference this KB for Methods:
Genius Live Stats / IAU (In-Arena-Utility) File Delivery Best Practices for Data Studio or Data Server

Verify Data Studio Configuration.

  1. With LiveStats and the In-Arena Utility (IAU) tool up and running, navigate to C:\[Sport], or example:  C:\Basketball.  
  2. Verify if LiveStats is currently writing an XML file to the desired location. The default file name is bbgame.xml.  However, IAU can be configured to output a different name and Data Studio Basketball can be configured to read a file with a different name.  The important item is the name IAU is outputting matches the name Data Studio is reading. 
  3. If a XML file is available, log into Data Studio Basketball and go to the Data Providers Page

Click on the NCAA XML.

  1. Under the Game File Location, verify the exact path to the file. 
    1. This should match the predetermined LiveStats file location.  
    2. This should be a local or hosted file. 
      1. **Note** If the file is Hosted, the Daktronics Data Basketball Service should be set to Log On as This account: ".\V7000" OR ".\User" and the password for the account. See Data Studio Basketball or Volleyball unable to access the hosted Genius NCAA LiveStats file, however, can be viewed in Windows Explorer
      2. May also need to input a Username and Password if needed to access the FTP site.
        NCAA XML Provider Configuration1.png
  2. Under Read Interval, enter a time (in seconds) of how often the file should be read; leaving this set to "0" will update every time the file changes.  The 0 for on change only works if the XML file is on the same computer as the Data Studio software.
    1. This value (in seconds) will need to be saved as something between 0 and 120. 
    2. For local files, 2-5 seconds is recommended.
    3. For internet based files, 6-10 seconds is recommended.
    4. Be careful not to set the interval faster than the file can be delivered, or a queue of unprocessed files could cause data to lag. The more reliable the internet connection, the more frequent the Read Interval may be.
  3. Data should be populating on the Stats Dashboard in Data Studio Basketball if the configured LiveStats folder is updating.  

Note: For pregame, the Team Names should populate.  Player Names will populate when they get a stat.  

NCAA XML Provider Configuration3.png

Verify the LiveStats IAU Settings.

If a XML file is NOT appearing in the specified folder, or the file is not named correctly, do the following:
  1. Close the game open in Live Stats and close that program.
  2. Open Live Stats IAU and in the Live Stats IAU tool, select basketball as your sport.
  3. In the IAU tool ensure the IP address is set to localhost and the port is set to 7677.
NCAA XML Provider Configuration5.png

Select connections and verify there is a connection set up to output to Daktronics and verify the settings with the image below.


NCAA XML Provider Configuration6.png

If there is not an output configured, configure one based on these settings.
  1. Format: Stat Crew XML
  2. File Name Mode: Use Default File name (or use Custom but the file names must match)
  3. Filename: bbgame.xml (or use another name as but the file names must match)
  4. The location needs to be sent to the mapped network folder on the Data Studio machine that the customer has created. NCAA XML Provider Configuration2.png
 
  1. After saving the setting, open the Live Stats Basketball interface, open a game and enter a play to generate a new xml file.
  2. The XML file should now be available in C:\LiveStats\Basketball
    1. Check to see if Data Studio Basketball is reading the file by viewing the Stats Dashboard. The Team Names should match the XML file. The Player Names will not populate until they have a stat.  
    2. If data is present, verify that stats can be sent to the display by playing stat related content.

KB ID: DD4551554


DISCLAIMER: Use of this content may void the equipment warranty, please read the disclaimer prior to performing any service of the equipment.

DAKTRONICS DOES NOT PROMISE THAT THE CONTENT PROVIDED HEREIN IS ERROR-FREE OR THAT ANY DEFECTS WILL BE CORRECTED, OR THAT YOUR USE OF THE CONTENT WILL PROVIDE SPECIFIC RESULTS. THE CONTENT IS DELIVERED ON AN "AS-IS" AND "AS-AVAILABLE" BASIS. ALL INFORMATION PROVIDED IN THIS ARTICLE IS SUBJECT TO CHANGE WITHOUT NOTICE. DAKTRONICS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTIES OF ACCURACY, NON-INFRINGEMENT, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. DAKTRONICS DISCLAIMS ANY AND ALL LIABILITY FOR THE ACTS, OMISSIONS AND CONDUCT OF YOU OR ANY THIRD PARTIES IN CONNECTION WITH OR RELATED TO YOUR USE OF THE CONTENT. ADJUSTMENT, REPAIR, OR SERVICE OF THE EQUIPMENT BY ANYONE OTHER THAN DAKTRONICS OR ITS AUTHORIZED REPAIR AGENTS MAY VOID THE EQUIPMENT WARRANTY. YOU ASSUME TOTAL RESPONSIBILITY FOR YOUR USE OF THE CONTENT AND ANY LINKED CONTENT. YOUR SOLE REMEDY AGAINST DAKTRONICS FOR DISSATISFACTION WITH THE CONTENT IS TO STOP USING THE CONTENT. THIS LIMITATION OF RELIEF IS A PART OF THE BARGAIN BETWEEN THE PARTIES.

The above disclaimer applies to any property damage, equipment failure, liability, infringement, or personal injury claim arising out of or in any way related to your use or application of the content, whether such claim is for breach of contract, tort, negligence or any other cause of action.