GCQuad with TGC up and running

[jrock000]

I listed the steps I took to get this thing going. I just got done playing a round at a famous course down South where a big tourney was supposed to be held this weekend.

Step 1: Buy this: https://golfsimulatorstore.com/colle...13246583636067 - this part is a pain because you need to install protee and TGC and wait for all your licenses to come via email.

Step 2: Configure protee as instructed in other posts. Basically - you need to just change 1 setting to configure it to external data

Step 3: Install GQSX.com - pm me if you need this

Step 4: Connect the Quad to the computer via wifi

Step 5: Connect to internet either via ethernet cable or another wifi card and bridge connections - this allows to connect to internet and qcquad at the same time

Step 6: Launch Protee then GQSX (click on connect) then start TGC

It should now work. No needing all that other stuff like you do for the GC2.

[intrinsic]

Just as a follow-up -

Still no joy unfortunately, but seems to be a communication issue between the GC Quad and Pro Tee Interface.

I've got the GC2 and GC Quad set up next to each other for comparison, so basically...

1) I connect the GC Quad to Wifi on my PC. I have a wired ethernet internet connection, so all good on that score.
2) Startup Protee Golf Interface (v 3.16) - as per using it with my GC2, my settings are:
- Use game: The Golf Club
- Use external data: On

When I start up GQSX I get a 'green' status on Direct WIFI connection and on Protee Program
When I click on Connect in GQSX I get a 'green' status on GCQ Online

All feels like we should be good to go! However, TGC 2019 just doesn't pick anything up.

Reason I'm suspecting a communication issue is that the Pro Tee Interface is not picking up any 'Last Shot Data' from the GC Quad (irrespective of whether TGC is doing anything).

If I start up my GC2 (same PC etc), then run GSX, when I hit a ball the Last Shot Data updates with info from the GC2 - so would then be reflected in TGC 2019.

I'm struggling to work out why GQSX isn't talking to ProTee Golf Interface, given I get a green status on all 3 elements.

Could I please ask anyone who has this up and running on GC Quad, could you let me know if ProTee Golf Interface updates the Last Shot Data from your Quad? I'm guessing it does, and that's the culprit here. A bit stuck now!

Thanks.

I don't have this working just yet but I've had it work usually when I'm done for the night and just giving up (2am three nights in a row). I also was not getting ProTee Golf Interface to register the shots. The log is showing it interacts with TGC2019. If you change clubs, Protee knows the club changes. It simply isn't grabbing the data from GCQuad.

Once I get a break today, I'll go back to the garage and run through my theory of the steps to see if it works.

Hopefully, someone else on this forum who has this working can chime in because this WAS working at one point for me predictably using ONLY the steps jrock outlined initially. It stopped magically 3 days ago.

[phgolf]

Thanks for the info here Intrinsic - really appreciate it.

I'll give it a go and let you know if I make any progress my side!

[phgolf]

Right, gone through those steps again - no joy unfortunately.

With the Pings I'm not seeing any dropouts at all, but no communication between the Quad and PTGI that I can see. Really puzzling.

Unfortunately I made the decision to get the Quad without FSX2020 as I'd not read particularly good things about it - but maybe that's a problem of itself? (Though I can't see any references on here to needed FSX to use GQSX or TGC 2019).

I've still got this thing in my head about it trying to connect to an External Data IP of 127.0.0.1 (and External Data Port of 9090) because that was required for the GC2. It's in the settings file for PTGI, which is why I keep wondering if that's causing it some inner conflict!

Not proving to be straight forward! But we'll get there I'm sure - if you've had it working, and others have on here, there's presumably just something I've not quite got right.

I'm lucky my garage is a nice room temperature, so not quite as challenging as yours! Fair play for those 2am problem solving efforts though

[intrinsic]

Right, gone through those steps again - no joy unfortunately.

With the Pings I'm not seeing any dropouts at all, but no communication between the Quad and PTGI that I can see. Really puzzling.

Unfortunately I made the decision to get the Quad without FSX2020 as I'd not read particularly good things about it - but maybe that's a problem of itself? (Though I can't see any references on here to needed FSX to use GQSX or TGC 2019).

I've still got this thing in my head about it trying to connect to an External Data IP of 127.0.0.1 (and External Data Port of 9090) because that was required for the GC2. It's in the settings file for PTGI, which is why I keep wondering if that's causing it some inner conflict!

Not proving to be straight forward! But we'll get there I'm sure - if you've had it working, and others have on here, there's presumably just something I've not quite got right.

I'm lucky my garage is a nice room temperature, so not quite as challenging as yours! Fair play for those 2am problem solving efforts though

Just tried a quick test and FSX2020 did nothing to help. It just validated one thing which is that FSX2020 and GSQX cannot both have a lock on the GCQuad. It's one or the other. The GCQuad links up perfectly fine with FSX2020 now and the WiFi connection is stable. Hitting shots on GCQuad get picked up by FSX2020 so there isn't a communication issue.

I'm going to look at the firewall options to see how the communication between the apps work to see if the ports are getting blocked.

To your question about the External Data Port being 9090, I can confirm GQSX.exe is using port 9090 (you can use the ResourceMonitor windows tool to verify this). 127.0.0.1 is just a loopback IP address (means, that it knows to communicate with itself).

I'll post back when I get another chance.

[phgolf]

Ah that makes sense - the 127.0.0.1 thing is a red herring then!

Is there a way of monitoring (a log file on Quad, for example) to see what it's actually trying to share with PTGI? I guess that's what you're trying to do with the firewall / port thing.

No problem, no rush - and appreciate all your help!

[Scottnorm]

Strange. I just clicked it and it worked for me.

Thanks, guys. I got it. I also have the protee interface downloaded now and TGC software installed. I "connect" with GSQX after selecting "club" and they all show green below. On the Protee interface, I have it configured to TGC and "external data". I open up TGC software and have the golf range in front of me. I hit a ball and nothing happens. GCQuad is showing that it has the shot, but nothing transmits to TGC. Wifi on GCQuad is connected. Any ideas? Thanks.

[phgolf]

Sadly having the exact same issue!

[Scottnorm]

Thanks, guys. I got it. I also have the protee interface downloaded now and TGC software installed. I "connect" with GSQX after selecting "club" and they all show green below. On the Protee interface, I have it configured to TGC and "external data". I open up TGC software and have the golf range in front of me. I hit a ball and nothing happens. GCQuad is showing that it has the shot, but nothing transmits to TGC. Wifi on GCQuad is connected. Any ideas? Thanks.

Well, I've emailed customer support at protee. they've been helpful in the past. So far, this has been a very time consuming and expensive experiment. Hope I can get money back if I can't get it working.

[phgolf]

Sorry to hear that! Please let us know how you get on. I know they don't 'officially' support GC2 / Quad, but people have clearly had it working in the past, so there's something a bit amiss.

I've got GC2 working happily with TGC 2019, and upgraded hoping it was something that I could get the best out of the Quad too. Ultimately they will sort it (and there's some really helpful people on here too, which is great!) so it's a patience game I think!

[Scottnorm]

I can't explain it. I shut down everything and restarted. All of the sudden it is working. I think the key was to shut down and restart the protee interface after selecting TGC and external data. Will keep this forum posted.

[intrinsic]

I can't explain it. I shut down everything and restarted. All of the sudden it is working. I think the key was to shut down and restart the protee interface after selecting TGC and external data. Will keep this forum posted.

Good luck. Don't reboot!

[phgolf]

Lucky man!

[Scottnorm]

Good luck. Don't reboot!

Couldn't help myself. Logged off to try and download a couple of more courses, and now I can't get it to work again. Everything is showing connected. Just no ball data.

Honestly, if you own a GCQuad and are considering this, I wouldn't do it until there is more clarity/certainty that it will work. The process is extraordinarily convoluted and not user friendly and the outcome is dubious at best. I've already dropped my money on TGC, and unless they will give me a refund, will continue to tinker away to see if I can getting working on a consistent basis. Will update this forum if I am able to get it to work in a reliable manner.

[LanceMan]

Having the same issue. Worked great for 5-6 weeks ... now its dead. Thank you all for posting your ideas/fixes/progress. Hoping there's a fix!

[soupy]

could it be the new GCquad F/w?

[Scottnorm]

My GCQuad is three years old, though its been updated with most recent software.

[soupy]

Can you downgrade to the level just below it to see if it works? Not sure if downgrading is allowed

[Scottnorm]

No. I have putting analysis on my quad and cannot change software.

[intrinsic]

So a bit more investigative work done. The ports are good for the most part. The GSQX app is indeed getting a lock on the GCQuad to read the dataset (or else FSX wouldn't have issues connecting). I've narrowed it down to Protee based on my understanding.

Earlier posts pointed to a python script that can launch random shots into the Protee interface. Running this showed the data coming from an 'external data' source so that much is now confirmed. Looking at the debugging line further though, it seems there's a data transmit issue.

When Protee Interface is launched:
Non valid data received from remote device:
{"protocol":"PTSDK", "INFO":{"status":"202", "message":"SDK connected"}}
{"protocol":"PTSDK", "INFO":{"status":"204", "message":"TGC not connected"}}

Error filling data from Json data:
var: ; value:
Error converting Json data:
protocol:PTSDK#status:202#message:SDK connectedprotocol:PTSDK#status:204#message:TGC not connected

After launching GQSX.exe:
Client Connected. IP (external data): 127.0.0.1

Pressing on the "Connect" button in GQSX creates no errors

Launching the TGC2019 console:
Non valid data TGC received from remote device.

Non valid data received from remote device:
TCPServer {"protocol":"PTSDK", "INFO":{"status":"200", "message":"Nickname updated to : Intrinsic"}}

Error filling data from Json data:
var: ; value:
Error converting Json data:
TCPServer protocol:PTSDK#status:200#message:Nickname updated to : Intrinsic
Non valid data received from remote device:
{"protocol":"PTSDK", "INFO":{"status":"200", "message":"Valid license"}}

3) protocol: PTSDK



My suspicion is that the error filling data issue is causing the crux of the problem and it may not have anything to do with the GCQuad firmware version. I'll send this information to Protee and see what I hear back. Stay tuned...

p.s. phgolf if you can confirm what you see when you connect the GC2 with the Protee Interface, it will help to confirm what I'm seeing on my end (and the same for GCQuad too, if you wouldn't mind).

[phgolf]

Hi, thanks for continuing to look into this!

So, here's the steps when connecting to the GC2 via GSX.

A) Fire up Pro Tee Golf Interface
- Messages (in PTGI):
Initialise TGC Connection

--

B) Open up GSX and click 'Connect'
Messages:
Client Connected. IP (external data): 127.0.0.1

--

C) Hit a ball (TGC is not open at this point!)
Messages:
1) protocol: PROTEE

The last shot data on PTGI is now populated with data from my GC2

--

D) Start up TGC 2019
Messages:

Non valid data received from remote device:
{"protocol":"PTSDK", "INFO":{"status":"200", "message":"Valid license"}}

4) protocol: PTSDK
TGC data received: {"protocol":"PTSDK", "INFO":{"status":"204", "message":"TGC not connected"}}

TGC not connected
3) protocol: PTSDK
TGC data received: {"protocol":"PTSDK", "INFO":{"status":"202", "message":"SDK connected"}}

SDK connected
2) protocol: PTSDK

-

Then as TGC 2019 gets to the main menu it adds -
TGC data received: {"protocol":"PTSDK", "INFO":{"status":"203", "message":"TGC connected"}}

TGC connected
5) protocol: PTSDK

--

E) Go to Practice Range on TGC 2019
Messages:
TGC data received: {"protocol":"PTSDK", "INFO":{"status":"150", "playerName":"My Name", "courseName":"Practice Facility", "tourName":"", "playerClub":"DR", "playerHand":"RH", "playerDistanceToFlag":"590.32", "playerSurface":"TEE"}}

6) protocol: PTSDK
TGC data received: {"protocol":"PTSDK", "INFO":{"status":"203", "message":"TGC connected"}}

TGC connected

--

F) Hit a ball on TGC 2019
Messages:
TGC data received: {"protocol":"PTSDK", "INFO":{"status":"102", "message":"Ball launched"}}

Ball launched
8) protocol: PTSDK
7) protocol: PROTEE

--

G) When ball / club data is shown on screen
Messages:
TGC data received: {"protocol":"PTSDK", "INFO":{"status":"150", "playerName":"My Name", "courseName":"Practice Facility", "tourName":"", "playerClub":"DR", "playerHand":"RH", "playerDistanceToFlag":"590.32", "playerSurface":"TEE"}}

10) protocol: PTSDK
TGC data received: {"protocol":"PTSDK", "INFO":{"status":"150", "playerName":"My Name", "courseName":"Practice Facility", "tourName":"", "playerClub":"DR", "playerHand":"RH", "playerDistanceToFlag":"590.32", "playerSurface":"TEE"}}

9) protocol: PTSDK
TGC data received: {"protocol":"PTSDK", "INFO":{"status":"102", "message":"Ball launched"}}

--

Hope that's useful!

[simmb]

I don’t own a Quad and not sure exactly how the Protee interface works but could any of this be related to the recent changes of the tournament website? There is some form of link between the SDK and that site as shot recording uses that website. Just seems a bit coincidental that the site changed a few days ago and some of you say this issue started happening a few days ago. Maybe nothing but thought I would mention it.