GSX interface stopped working

[SwingHarder]

Had anyone had issues with their GSX interface where it went from working fine to no longer being able to get the Status Input to be connected?

Some background, I've had my sim and been playing TGC with a GC2 since February. No issues so I have some familiarity with navigating the various interfaces (ie I've made sure I have the right com port selected, tried both incoming and outgoing to be sure).

I recently took my sim down for a few weeks while I drywalled and painted the room. Nothing complex, just unplugged computer and took down screen. However after getting everything back up, I can't get the GC2 to connect. I have FR1 software as well and have had no issues playing that over bluetooth, so I'm ruling out the bluetooth connection.

Things I've tried, unpairing and re-pairing GC2, uninstalling and reinstalling both interfaces, and forcing GC2 com ports to lower numbers (they were originally 12 and 13, I've changed them to 3 and 4).

I have GSX interface 0.6.7 and Protee interface 3.0.7e. I've opened a ticket with Protee but am hoping someone here has had this issue before. I'd like to not start the spring tour with a goose egg.

[mthunt]

This is almost always a bluetooth issue. Click onto the paired gc2 and delete it then connect it. The ports should be com 3 and 4. If you're still stuck, open a ticket.

[SwingHarder]

Tried that, no luck. I know my bluetooth is working because I've been using the FR1 range via bluetooth the last couple days. Ticket is open, just hoping to get it fixed in time for Hilton Head

[mthunt]

I've seen the exact same thing happen my pros set up. Every time he added the gc2 the com ports went up. He wasn't deleting. FSX still worked. Once I deleted it properly, the com ports went back to 3 and 4. If yours aren't 3 and 4 it won't work.

[SwingHarder]

Hmmm, I deleted it and paired it again, com ports went up. This is what I've seen before but had no issue until I got above com port 15. I had to manually force it to com 3 and 4, maybe I'm not deleting it the same way

[Mxwoodman]

I had an issue that it worked fine then it quit I tried everything but it ended up being the Bluetooth board went out in the GC2.
Get the FS Apple app and try and pair to it if you can then it's something to do with the PC

[SwingHarder]

Using FR1 via bluetooth so I know it's connecting.

[mthunt]

Win 8&10
Bluetooth, show devices, remove device on GC2

Then Bluetooth, add device

Then Bluetooth settings. Coms 3&4

[mthunt]

If coms went up it didn't delete.

[SwingHarder]

Thanks all for the suggestions. I gave up and reset Windows. Apparently this changes your machine ID, now back to square 1 and waiting on Protee for new interface license key.

[SwingHarder]

Figured I'd update this in case anybody has this issue in the future. I reset Windows 10 and redownloaded everything. Machine ID for TGC stayed the same so I put in my previous license code and it worked. Machine ID for Protee interface changed so I had to wait a few hours for a new license key. Everything is working now. Tomorrow should be fun, tournament in the morning followed by 2 rounds at Hilton Head in the evening. Good thing the GF is out of town.

[Jbryant016]

Had similar issue, but restarting my comp and opening / closing GSX program multiple times ended up working. I also noticed TGC machine ID stayed the same last time I performed a complete reinstall of my OS

[Jbryant016]

So I said earlier that opening / closing the GSX app ending up working... Not so much!

Here's my background: I recently built a custom computer just for TGC Sim. The only bluetooth device connected has been the GC2 and I was successful with connecting everything to play the game. My only problem was when there would be unusually long delays in processing the data from my GC2 to the GSX program (I would watch how long it took the numbers register on the GSX program). It really bothered me and I figured the issue was from having the computer about 5 feet away. I had experience prior to the TGC sim with the foresight ipad app... the ipad had to be very close in order to successfully connect to the GC2.

I rearranged my setup to comfortably fit my computer next to the GC2 (about 3-4 feet away - had not purchased a USB extension at this point). Everything was going pretty good, but then started having unusually long delays (sometimes around 15-20 seconds) before the ball would move. Naturally, I disconnected the GC2, restarted the computer, restarted all applications, etc. This caused the COM port to change to a higher number (just how Windows 10 handles connecting to the GC2). Some say this is an issue, but if I changed the GSX program to match the Bluetooth COM port settings (e.g., COM 5), it would successfully connect, but still occasionally experience an annoying delay. This time around, I figured the delay was caused by the wrong COM port that's recommended (COM 3 & 4). The prior COM ports were listed as "in use" when I tried to change, so I figured something happened beyond my knowledge of Windows 10, so I started doing research on google and youtube. Read multiple ways to clear old COM ports to get back to 3 & 4 (meanwhile still thinking I may need a USB extension cable to place directly next to the GC2, but was still caught up on figuring out the COM issue). Anyway, I messed up some settings in the Device Manager and screwed something up because when I tried reinstalling my Bluetooth, the installation could not be completed (from the CD it came with). I have the recommended ASUS device. Ultimately caused me to reinstall Windows to get everything back to normal. As mentioned above this causes the ProTee machine ID to change, so I have to wait on that. I purchased the USB extension cable so it is sitting next to the GC2. I hoping this does the trick. The GC2 is at COM 3 & 4, so I'm confident it will be good.

If not, my only question from this long post is: what on earth is causing this delay sometimes? It ruins my experience!

[Jbryant016]

For those that experience the issue of reconnecting the GC2 which assigns a new COM port (assigns a higher number), please see the instructions in the link I provided to successfully clear all COM ports to start fresh. When I would reconnect my GC2, it would move the outgoing COM port to #5 or higher the more times I disconnected / reconnected. Each time it leaves the prior COM ports as "in use" if you try to change the COM ports back to the original one. Not sure why Windows does this, but follow the instructions and you should clear it up. I will try my best to avoid this by never disconnecting the Bluetooth pairing. I only did this because I was trying to find a solution to the long delay I would sometimes get (but this will mostly likely due to not having an USB extension cable).

Edit Windows Registry to clear "in use" COM ports: http://blog.cognitioninfotech.com/20...-com-port.html

[mthunt]

So I said earlier that opening / closing the GSX app ending up working... Not so much!

Here's my background: I recently built a custom computer just for TGC Sim. The only bluetooth device connected has been the GC2 and I was successful with connecting everything to play the game. My only problem was when there would be unusually long delays in processing the data from my GC2 to the GSX program (I would watch how long it took the numbers register on the GSX program). It really bothered me and I figured the issue was from having the computer about 5 feet away. I had experience prior to the TGC sim with the foresight ipad app... the ipad had to be very close in order to successfully connect to the GC2.

I rearranged my setup to comfortably fit my computer next to the GC2 (about 3-4 feet away - had not purchased a USB extension at this point). Everything was going pretty good, but then started having unusually long delays (sometimes around 15-20 seconds) before the ball would move. Naturally, I disconnected the GC2, restarted the computer, restarted all applications, etc. This caused the COM port to change to a higher number (just how Windows 10 handles connecting to the GC2). Some say this is an issue, but if I changed the GSX program to match the Bluetooth COM port settings (e.g., COM 5), it would successfully connect, but still occasionally experience an annoying delay. This time around, I figured the delay was caused by the wrong COM port that's recommended (COM 3 & 4). The prior COM ports were listed as "in use" when I tried to change, so I figured something happened beyond my knowledge of Windows 10, so I started doing research on google and youtube. Read multiple ways to clear old COM ports to get back to 3 & 4 (meanwhile still thinking I may need a USB extension cable to place directly next to the GC2, but was still caught up on figuring out the COM issue). Anyway, I messed up some settings in the Device Manager and screwed something up because when I tried reinstalling my Bluetooth, the installation could not be completed (from the CD it came with). I have the recommended ASUS device. Ultimately caused me to reinstall Windows to get everything back to normal. As mentioned above this causes the ProTee machine ID to change, so I have to wait on that. I purchased the USB extension cable so it is sitting next to the GC2. I hoping this does the trick. The GC2 is at COM 3 & 4, so I'm confident it will be good.

If not, my only question from this long post is: what on earth is causing this delay sometimes? It ruins my experience!

In my experience the long delay is usually Bluetooth. The closer the Bluetooth and the better the adapter, the shorter the delay. I have an extended range Trednet Bluetooth. It worked a lot better than the old one.

[Jbryant016]

I got it up and running. Getting a steady 1.5 - 2 second delay which is good enough for me!