GCQuad with TGC up and running

[intrinsic]

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.

At this point, I'm not ruling anything out thanks for the heads up. I didn't know it was related but you're right, it could be.

[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).

Yes, it does help but not in a good way. So it seems that QCQuad isn't sending the data through the interface into protee. So if protee interface can't see it, TGC won't either.

Bummer. I hope someone can find out who built the GSQX app so I can look at the source code to see if Foresight changed the code with an update.

[phgolf]

Sorry, I only saw the first part (the GC2 audit trail via GCX), here's the Quad version - following the same steps suggested
1) Fire up PTGI
2) Connect the Quad via WIFI
3) Connect via GSQX app (all green)
4) Open up TGC 2019
5) Driving Range - Hit a ball.

--
PTGI Messages:

6) 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"}}

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

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

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

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

SDK connected
1) protocol: PTSDK

--

So basically all looks good until you get to Driving Range, then nothing.

I pinged MTHunt on here, and they may know who owns the source code. It could be a simply change driven by either a change in TGC 2019 (unlikely) or GCQuad (more likely).

Interestingly, I shut TGC 2019 down, disconnected then reconnected GSQX and got the JSON errors you saw in your original post, so also got those 'non valid data' errors too.

[Scottnorm]

Yes, it does help but not in a good way. So it seems that QCQuad isn't sending the data through the interface into protee. So if protee interface can't see it, TGC won't either.

Bummer. I hope someone can find out who built the GSQX app so I can look at the source code to see if Foresight changed the code with an update.

The thing that confuses me is that after struggling for hours yesterday, at one point it worked. Everything on TGC2019 was working. Then I logged off and couldn't get back on. So, what caused it to stop?

[Scottnorm]

I just gave control of my machine to protee support. They went through and tested/reviewed everything. They say everything is functioning fine. Issue is GSQX. Not sure where to go from here.

[johnnybogey]

Curious, who owns GSQX?

[phgolf]

I think a chap on here wrote it as a favour to his friends? From what I can see!

So a couple of schools of thought (that may be wrong):
- Foresight have changed / blocked / encrypted the messages from GC Quad (hence GSQX isn't plumbing the data into the Pro Tee Golf Interface any more)
- A Microsoft Windows update has blocked messages from the GC Quad into the Pro Tee Golf Interface
- Something else totally random!

I've never had it working, though I've only had my Quad a few days - but a few on here have had it working previously (even in the last day or so).

I've pinged a chap on here to see how they built it (if they're the right person). However, I've got a super geeky friend who's going to help me track the messages from the GC Quad to see what it spits out, and see if we can work out how to create a new version. No promises, but we'll give it a go!

If anyone wants a crack at explaining what GSQX does in terms of messaging then feel free to ping me a note!

[Scottnorm]

I think a chap on here wrote it as a favour to his friends? From what I can see!

So a couple of schools of thought (that may be wrong):
- Foresight have changed / blocked / encrypted the messages from GC Quad (hence GSQX isn't plumbing the data into the Pro Tee Golf Interface any more)
- A Microsoft Windows update has blocked messages from the GC Quad into the Pro Tee Golf Interface
- Something else totally random!

I've never had it working, though I've only had my Quad a few days - but a few on here have had it working previously (even in the last day or so).

I've pinged a chap on here to see how they built it (if they're the right person). However, I've got a super geeky friend who's going to help me track the messages from the GC Quad to see what it spits out, and see if we can work out how to create a new version. No promises, but we'll give it a go!

If anyone wants a crack at explaining what GSQX does in terms of messaging then feel free to ping me a note!

Thanks. The only thing I cannot explain is that it worked for me yesterday for a short time. I logged off and could never get it back. Just so damn strange.

[johnnybogey]

Thanks. The only thing I cannot explain is that it worked for me yesterday for a short time. I logged off and could never get it back. Just so damn strange.

Possible GC Quad update took place in the background?

[Scottnorm]

Possible GC Quad update took place in the background?

I guess if it happened in the hour that I was away, its possible - but doubtful. I normally have to download fxf updates.

[JR757]

I thought i would chime in, i have used the guad with GSQX for around 6 months. I have never had an issue until i updated the firmware on the quad 2 weeks ago. Right after i did it TGC stopped working with the quad. I attempted to rollback, to two different previous firmware version, and they both caused the quad to go to boot error. Because of this, i think Foresight has blocked (encrypted) something, and prevented a firmware rollback. I could be wrong. I was told the firmware was not the issue and have tried many different things to get it to connect. I am sorry to hear others are now having this same issue. Hopefully there is a solution out there.

[intrinsic]

I think a chap on here wrote it as a favour to his friends? From what I can see!

So a couple of schools of thought (that may be wrong):
- Foresight have changed / blocked / encrypted the messages from GC Quad (hence GSQX isn't plumbing the data into the Pro Tee Golf Interface any more)
- A Microsoft Windows update has blocked messages from the GC Quad into the Pro Tee Golf Interface
- Something else totally random!

I've never had it working, though I've only had my Quad a few days - but a few on here have had it working previously (even in the last day or so).

I've pinged a chap on here to see how they built it (if they're the right person). However, I've got a super geeky friend who's going to help me track the messages from the GC Quad to see what it spits out, and see if we can work out how to create a new version. No promises, but we'll give it a go!

If anyone wants a crack at explaining what GSQX does in terms of messaging then feel free to ping me a note!

I think something is certainly awry. GSQX was working fine for many of us until a few days ago. I made no pre-emptive decision to upgrade the firmware on the GCQuad nor worried about upgrading Windows. My problems began with the GCQuad disconnecting from WiFi and this problem existed with FSX as well. Once it was clear that I couldn't get a single shot read by TGC did I decide to investigate upgrading the firmware.

It was only after much troubleshooting on FSX, TGC and PTGI that I decided to upgrade the firmware.

Just like JR757 , I was unable to get the older firmware installed. I would get boor error M1. Not sure if anyone else has a better idea.

[mthunt]

Does anyone have a quad working or all of them not reading in TGC?

[Hubbahub32]

My TGC still runs. I don't believe I have updated the firmware or plugged in my quad all of July though. Maybe that is the difference.

[mthunt]

I’ll be impressed if Foresight did this. Are you using Windows 10?

[Hubbahub32]

Yes. Windows 10 and everything is updated. Knock on wood, hope it keeps working.

[LEO MODE]

Someone said if you upgrade to Foresight firmware 3.x, you cannot roll back to 2.x version. Is that true?

[intrinsic]

Someone said if you upgrade to Foresight firmware 3.x, you cannot roll back to 2.x version. Is that true?

I wasn't able to roll back. I got a boot error "M1" on the physical device after trying. I had to upgrade it back to FW 3.x to get it working again.

[LEO MODE]

interesting. we would need more sample size to see if this is universal across the board.

[JR757]

I am unable to rollback, I get the same boot error.

[intrinsic]

All, anyone who has TGC2019 for GCQuad is pretty much fubr'd I looked at the log files on the GCQuad and found this lovely logged item associated with v3.x of the firmware

07162020 20:57:51.010: Error Q12 - !!! Error - Rs9113Comm::Receive; expecting rsp for 0x4e, rcvd 0x0
07162020 20:57:51.047: Error N80 - !!! Error - Enable Ball Data Msg no longer supported over Ethernet/WiFi

If anyone is interested, hook up the USB-C cable to your PC and then navigate to your drives. You'll see one for the GCQuad and a .log file which has the details in there. This means GSQX will not be able to grab ball data from the GCQuad which means it can't pass it to Protee.

My hunch is that E6 is behind this. This essentially will try to force TGC users to consider buying more FSX courses or switch to E6.

[LEO MODE]

Can you play iPad app? iPad app also uses wifi so not sure if they will break their own app using wifi.