How to set up DakStats Rodeo with Omni Sport 2000 to a Galaxy via serial connection

Topic

  • Rodeo Timing with Galaxy via RS-422.

Environment

  • Product: DakStats Rodeo, AF-3400
  • Component: RS-232 to RS-422 Signal converter
  • Control System: Venus 1500 Version 3, Venus 1500 RT, Omni Sport 2000

Steps

  • When setting up a direct serial connection to a Galaxy it is necessary to run Clock data from the Omni Sport Directly to the Galaxy to prevent time delay.  The Omni then needs to be connected to the Computer so that DakStats Rodeo also gets time information.  Since DakStats Rodeo is located on the same computer as Venus 1500 it will communicate through the 1500 RT program to send data to the board.  The Venus 1500 RT program puts a 5000 offset on the signal for the Rodeo information so DakStat will have a Zero offset. 
     
    1. Connect cabling between quick connect on Galaxy and RS-232 to RS-422 signal converter.
    2. Connect serial cable or USB to serial converter between the computer and the signal converter.
    3. Connect a 9 pin serial between the computer and the Omni Sport 2000 Results port.
    4. Connect the RTD 9 pin port of the Omni Sport 2000 to the 1/4inch Phone connector on the Galaxy for RTD clock information to show on the board.
 
  • Setting up Venus communications:
    1. Check Device Manager to determine what comport is being used to talk to the Galaxy.
    2. If Venus has previously talked to the Galaxy confirm in Administrator that the comport is correct and test communications to the board.
 
  • Setting up DakStats Rodeo:
    1. Open DakStats Rodeo.
    2. Click Configure INPUT/OUTPUT.
    3. Under configure Ports double click the empty field under name to open DLStream Configuration Wizard.
    4. Set the Type to Comport, name to Timer, and click Apply.
    5. Click Com Settings select the Port that the Omni Sport 2000 is connected to, Baud 19200, 8, None, and click Apply.
    6. Click Protocol List and select Standard/Enhanced RTD then click Apply and Finish.
    7. Under INPUT: Timer name the connection, then select the port drop down and select Timer.
    8. Under configure Ports double click the empty field under Timer to open DLStream Configuration Wizard.
    9. Set the Type to UDP/IP, name to Results, and click Apply.
    10. Click UDP Settings select the Port 17000, Broadcast, and click Apply.
    11. Click Protocol List and select Standard/Enhanced RTD then click Apply and Finish.
    12. Under OUTPUT: Rodeo In Progress name the connection, then select the port drop down and select Results, Type is serial, Offset is 0.
    13. Use the above to setup a Announcer Monitor if needed.
 
  • For more information, see: 
     
    • Setting up Venus 1500 RT:
      1. Plug in the RT Key.
      2. If Venus 1500 shell is opened prior to installing the RT key close the shell and reopen to get the 5th button which is RT.
      3. Click the far right button on Venus 1500 shell to open RT.
      4. Double Click on 1.
      5. Click configure.
      6. Click UDP Port then OK.
      7. Type in port 17000 to match DakStats Rodeo click OK.
      8. Click ITF…
      9. Select Browse in the selection bar.
      10. Select Rodeo in Progress (Serial).itf. Click Open then OK.
      11. Click Select Display.
      12. Displays that are getting RT data need to be selected then added to the Authorized for RTD Input: using the >>.
      13. Click Close then Close again.
      14. RT program can be minimized but needs to be running to send data to the board.
 
  • Setting up a network Loopback connection this is only need if the computer has no network connection:
    1. Open Control Panel.
    2. Double click Add Hardware.
    3. Click Next.
    4. Select Yes, I have already connected the hardware then Next.
    5. Go to the bottom of the list and highlight Add a new hardware device then click next.
    6. Select Install the hardware that I manually select from a list then Next.
    7. Highlight Network adapters then click Next.
    8. Highlight Microsoft then select Microsoft Loopback Adapter then click Next/.
    9. Click Next to install then click Finish/.
    10. Depending on the computer this connection may be bridged when active to the local area connection.  Local area connection would need to be unbridged to get internet access/.
 
  • Due to DakStats broadcasting the stats through UDP and nothing is connected to the local area connection (Ethernet) on the computer a Loop back adapter will need to be configured.  The Loop Back connection will also be bridged to the local area connection.  A Loop back connection fakes out the computer in allowing it to send UDP broadcasts to itself with out having a device connected to the network port.
 
  • Venus 1500 RT must be running for data to go to the display.
 

KB ID: 000025722


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.