Issue: GPS Receiver not detected by GPSports Console

Symptoms:

• Unable to see 'Seaweed' flowing on the GPSports Console (top right hand corner) when the Receiver is connected to the PC, this indicates the Receiver is not detected by GPSports
  
  
  

Expected Behaviour:

• When the GPS Receiver is detected by GPSports, 'Seaweed' will flow intermittently (if no devices detected), or fully (if one or more devices are actively being received)
  
  
  • No Devices detected by the Receiver, but GPS Receiver detected by GPSports:
    
    
    
  • Device(s) detected by the Receiver, and GPS Receiver detected by GPSports:
    
    

Troubleshooting Steps:

• Try connecting the Receiver to other USB ports
  
  
• Try connecting the Receiver through a USB hub
  
  
• Try connecting the Receiver to another PC that has GPSports installed, and check if it is detected
  
  
• Open the Windows Device Manager:
  
  
  • Check if the Receiver is seen under "Ports (COM &LPT)"
    A Receiver detected by the PC will appear as a 'Minimax TRX' device:
    
    
    
    
• If there is a device recognized but it has an error, or it is not seen as a 'Minimax TRX', attempt to update the Device Driver:
  
  
  • Right click the device in Device Manager
    
    
  • 'Update Driver'
    
    
  • 'Browse my computer'
    
    
  • Find path "C:\Program Files\GPSports Console Release\Drivers"
    
    
  • 'Next' > 'Close'
    
    
• If there is no device under "Ports (COM &LPT)"
  
  
  • Check if the receiver shows up in "Universal Serial Bus Controllers"
    It may display as a "Generic USB Hub"
    
    
  • Unplug the Receiver and check if the controller disappears and re-plug the Receiver to confirm that that controller is the receiver
    
    
    
    
• If no Devices appear/disappear whatsoever when connecting/disconnecting the Receiver:
  
  
  • Reboot the PC
    
    
  • Check to see if other USB Devices are able to be detected by the PC
• Please Contact Support if your Receiver appears as a Generic USB Hub, does not appear at all in Windows Device Manager, or all other Troubleshooting steps have been exhausted