GC2 Bluetooth Windows 10 issues

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Drmuzoid
    Junior Member
    • Dec 2015
    • 12
    #1

    GC2 Bluetooth Windows 10 issues

    Hey guys,
    Finally got the TGC 2019 to use with my GC2. I had my doubts about the Bluetooth but it has worked in the past with Foresight FR1 and the Perfect Parallel interface and ***. Then after some updates a year or so ago it had issues. It does pair with Windows and shows in the Device Manager Bluetooth list and it tries to connect in FR1 but doesn’t. Trying to use TGC 2019 but the input in the GSX fails to connect.

    I have had remote sessions with Par2Pro and a long one with the team at ProTee and spoken with Foresight support. No one can pinpoint the problem. I am willing to send it back to Foresight for a new BT chip but I just want to be sure the problem is not with my Windows system first. I have read a lot of your conversations on the forum but nothing has worked so far.

    I’m using Windows 10 Pro (exact version below). Completed updates including chip sets etc, as far as I can tell. I have tried the Asus Bt400 and IOGEAR GBU521 adaptors. But here are the signs I don’t understand:

    In Device Manager, Bluetooth>Foresight Gc2 >Properties >Events says:

    Device not migrated due to partial or ambiguous match

    Also same for RFCOMM Protocol TDI and
    Standard Serial over Bluetooth Link says “requires further installation”…

    Result is apparently that nothing from GC2 gets through the chain. Screen shots below. If ANYBODY has an answer or suggestion it would be most appreciated. Thanks.
    Click image for larger version Name: Windows 10 Ver.jpg Views: 832 Size: 15.7 KB ID: 330306Click image for larger version Name: GC2 Standard Serial ov BT Migrated but reqires further installation.jpg Views: 641 Size: 84.9 KB ID: 330307Click image for larger version Name: GC2 2681 BT info.jpg Views: 641 Size: 132.3 KB ID: 330308
    Tags: None
    • mthunt
      Ultimate Member
      • Aug 2014
      • 4746
      #2
      You can try the non com or USB interface instead of GSX.

      https://www.dropbox.com/s/lpgdo6mz0x...1_0_1.zip?dl=0
      My Courses:
      World Par 3's by mthunt
      Toronto GC (L) mthunt
      Burlington G&CC by mthunt
      Weston G&CC by mthunt
      London Hunt Club L mthunt
      Park CC Lidar mthunt
      Sunningdale GC Robinson L
      Sunningdale GC Thompson L
      Muirfield Village (liDAR) First Ever Lidar course
      Country Club of Castle Pines (liDAR)
      The Sanctuary GC ProTee L
      The National GC L mthunt
      Mississaugua GC L mthunt
      Shaughnessy G&CC L mthunt
      Markland Woods CC mthunt
      Hidden Lake Old L mthunt
      Magna GC L mthunt
      Barrie CC L mthunt
      mthunt Range

        Comment

        • Celeras
          Senior Member
          • Jan 2019
          • 199
          #3
          mthunt often has the inside track on these things so feel free to try what he suggested as a workaround, but usually "Device migrated" problems in windows 10 are a result of the device driver. Typically after a Windows update screws up and automatically installs something with a compatibility issue... which seems to track with what you said in your first sentence.

          My recommendation would be to right click the bluetooth in Device Manager and rollback and/or reinstall the driver. If you want to let windows do it you can just uninstall the device and reboot the computer, or grab it from appropriate source. For example here is the page for the BT400 (make sure that matches what you have Im just going by your post): https://www.asus.com/us/Networking-I...Desk_Download/

            Comment

            • Drmuzoid
              Junior Member
              • Dec 2015
              • 12
              #4
              Thanks for the replies. mthunt For the USB interface for TGC do I need to install both files - UsbDk and gc2_to_TGC or is UsbDk only for FSX?

                Comment

                • mthunt
                  #4.1
                  mthunt commented
                  04-18-2021, 02:06 PM
                  Editing a comment
                  The MSI is a driver shield for FSX. Install it and the GSX alternative or fix the driver like Celeras said or both.
                • Drmuzoid
                  Junior Member
                  • Dec 2015
                  • 12
                  #5
                  Wow, thanks so much for the USB interface! Until I get the bluetooth sorted out, this seems to work well. Should have asked here first : )
                  Uninstalling/installing driver didn't work and we did that many times with Protee and Par2Pro support as well. Still baffled with that...

                    Comment

                    Previous template Next
                    Working...