GCQuad and GCHawk Problems: A Symptom-First Fix List

A GCQuad or GCHawk that stops reading shots is usually suffering from one of a small number of problems. The quickest route to a fix is to match the symptom to its likely cause before you start changing settings. Most faults trace back to three things: power interruptions, a firmware mismatch between the unit and the software, or a tracking mode or license that doesn't match what you expect the system to do.

This guide is organized by symptom rather than by product. Start with the fault finder table, which points you to the right section. Each section then runs the checks in the order they are worth doing, from the quickest and cheapest to the ones that end in a support ticket.

Foresight's own support documentation and the manual that shipped with your unit are the final word on menu names, LED patterns and firmware steps. Where this guide describes a menu path or a light pattern, treat it as a pointer. Sources disagree on some of those details, and firmware changes them over time.

How we put this together: we compared Foresight's published specs, its setup guidance and owner reports, then ordered the checks from quickest to slowest. We don't accept free gear, and links may earn us a commission.

Which unit, which connection: get this straight before you fix anything

The GCQuad and the GCHawk belong to the same product family, but they sit in different places and connect differently. Before you go through any fix, work out which one you own, since many steps that work for one don't apply to the other. If you're still comparing options, our GCQuad overview and the GCHawk overhead launch monitor overview lay out the differences in more detail, and Foresight's QuadMAX is the next step up in that line.

The GCQuad is a floor unit that sits beside the ball. It has four high-speed cameras, a rechargeable battery and an onboard screen that can show a LOCKED message. It connects to the PC by USB or through its own Wi-Fi link. The full list of connection options depends on your firmware, so the manual is the reference for that.

The GCHawk is a ceiling-mounted overhead unit. It is mains powered and typically wired, and it tracks the ball and club from above. The connection method and the supported ceiling-height range are both listed in the manual, and they matter for the fixes later in this guide.

Both units run through Foresight's FSX software, either FSX Pro or FSX Play, or through supported third-party software. Here is the short version of what separates them:

Unit	Mounting position	Power	Connection options	Club data requirements
GCQuad	Floor, beside the ball	Rechargeable battery	USB or Wi-Fi link to the PC	Club markers on the face, active Club Analysis license
GCHawk	Ceiling, overhead	Mains	Typically wired	Club markers on the face, active Club Analysis license

One point trips up a lot of owners. The Wi-Fi link between the PC and the launch monitor is a device link, not an internet connection. The PC can talk to the unit over that link and still have no internet at all. Online features such as FSX Play multiplayer and cloud features need a second route to the internet, either Ethernet or a second Wi-Fi adapter. Keep that in mind through the rest of this guide, because it explains one of the most common "it's broken" reports that turns out to be a network design issue.

Fault finder: symptom, likely cause, first move

Find the row that matches what you're seeing, go to the section listed, and run the checks there. If more than one row fits, start with the power cycle and then work down the list.

Symptom	Most likely cause	First move	Section
PC can't find the unit	Power state, USB cable or port, or a stale connection	Power cycle in order, then check the cable and port	When the PC cannot find the launch monitor
Unit's Wi-Fi connects, but the PC has no internet	The unit's Wi-Fi link does not carry internet	Add Ethernet or a second Wi-Fi adapter for the PC	When the PC cannot find the launch monitor
Online features in FSX Play drop or lag	Network speed, weak Wi-Fi, or devices switching networks	Check speed, turn off mobile data on the app device, pause streaming	When the PC cannot find the launch monitor
Unit on, but shots not registering	Placement, lenses, ball, mat or speed range	Check placement and clean the lenses	When the unit is on but shots are not registering
Phantom shots with no ball	Something in view is moving or reflecting light	Run the swing-without-a-ball test	When the unit is on but shots are not registering
Ball data fine, no club data	Tracking mode, license, markers or firmware	Check the tracking mode and license in FSX	Ball numbers fine, club numbers missing or wrong
Club data patchy or inconsistent	Peeling, dirty or worn markers, or light and glare	Clean and refit the markers, then check the lighting	Ball numbers fine, club numbers missing or wrong
LED shows an error state	Unit not level, lens obstruction, or low battery	Check level, clear the lenses, charge the battery	Status lights and the LOCKED message on the GCQuad
LOCKED on the GCQuad screen	Licensing or authorization problem, often after a failed update	Restart, update firmware, verify the license, then contact support	Status lights and the LOCKED message on the GCQuad

Three root causes account for most of these rows. Power interruptions, where the unit or PC drops out mid-session or the battery runs low, produce connection drops and gaps in the data. A firmware mismatch between the unit and FSX causes odd behavior, and missing club data is a common symptom of it. A wrong tracking mode or a missing license makes the system report less than you expect, which looks like a fault but is really a setting.

When the PC cannot find the launch monitor

Work through the power cycle before you touch drivers or network settings. Most "can't find the unit" problems clear up after a clean restart, and the cost of trying is a couple of minutes.

Restart in the right order

Follow this sequence in order. The reasoning is simple: FSX looks for the unit when it opens, so the unit should already be ready when the software starts.

Turn the unit off and unplug its power adapter for about 30 seconds.
Close FSX on the PC.
Start the launch monitor first and let it finish starting up.
Reopen FSX.
If it still fails, restart the PC as well. Owners often skip this step and go straight to reinstalling software, which is the slowest route.

A clean restart fixes more than it should, and that is the reason it belongs at the top of the list. Power and software states can get stuck in a half-connected condition that a restart clears, while a driver reinstall changes things that were never the problem.

USB checks for the GCQuad

USB is the simplest connection to test, and a cable or port fault is the most common reason it fails. Use the original cable, plugged straight into a USB 3.0 port. On most PCs the USB 3.0 port is blue inside, though you should check the port itself rather than rely on the color. Avoid hubs and extension cables, since they are a frequent cause of intermittent drops that come and go during a session.

When the GCQuad is connected by USB, it should appear as a mass storage device in File Explorer on Windows or Finder on macOS. Confirm that against the current firmware, because the behavior can change between releases. If it doesn't appear:

Try another USB 3.0 port on the PC.
Test the cable on a different device to see whether it still shows up.
Reinstall the USB drivers from the support page on Foresight's website.

A missing mass storage device usually points to the cable or the driver rather than to the unit itself. That distinction tells you which of the three fixes to try first, and it saves you from reinstalling software when a different port would have solved the problem.

Wi-Fi, mesh networks and the lost internet problem

Wi-Fi problems show up in two forms. Either the connection to the unit fails, or the PC loses its internet when it joins the unit's network. The first is usually signal strength or settings. The second comes from the design of the link, which we covered earlier.

The network guidance quoted in the sources we compared asks for the 5 GHz band to be enabled and broadcast, a network name without spaces or special characters, and a connection to the main router rather than a mesh satellite node. Mesh systems can hand the PC off between nodes in ways that break a session, so the main router is the more reliable target. Check each of these against Foresight's current guidance, because firmware and documentation both change.

Joining the GCQuad's own Wi-Fi means the PC is on a network with no internet. For internet, you need Ethernet or a second dual-band USB Wi-Fi adapter. Position that adapter away from the unit and away from the PC's own casing, and use a short USB extension cable if that's what it takes to get it clear. A nearby adapter can pick up enough interference from the unit's signal to slow down or drop out.

The figure quoted for online features in FSX Play is 25 Mbps down and 5 Mbps up. Compare your connection against it before you assume the software is at fault, and confirm the number against Foresight's current requirements before you spend money on a faster plan.

Two habits cause a lot of lag in online play, and both are easy to fix:

On a tablet or phone running the app, turn off mobile data so the device doesn't switch networks in the middle of a session.
Pause video streaming on the same network during a session. Streams compete for bandwidth and add latency that you'll notice in online play.

Mismatched IP settings are a less common cause, and they show up when the PC has a fixed address that doesn't fit the network the unit is on. Setting the PC to obtain its address automatically is the usual starting point. Weak Wi-Fi through thick walls and loose or damaged USB cables are the other two causes that come up most, and both can be checked in a few minutes. The Wi-Fi drops and lag guide goes deeper on the network side if the steps here don't clear it.

When the unit is on but shots are not registering

The unit has power and the software is connected, but shots don't show up. That points at the setup around the unit more than at the unit itself. Work through the checklist in order, and run the phantom-shot test only after you've ruled out placement.

Placement. Check that the GCQuad is neither too close nor too far from the hitting zone, and that it sits level with the mat. Use the unit's own ball-position guidance rather than a fixed rule of thumb. One source describes the ball as sitting within about an inch of a reference point, but confirm that figure in the manual before you rely on it.
Lenses. Wipe the lenses with a microfiber cloth. A thin layer of dust is enough to cause misses, and it can build up without you noticing.
Ball. Badly scuffed, non-conforming or unusual balls can fail to trigger a read. Use balls that Foresight lists as compatible, and check its support material for where that list lives.
Mat. A thick or uneven mat raises the ball and changes its position relative to the cameras. Use a mat made for launch monitor use. SwingTurf is one mat the sources cite as launch-monitor-friendly.
Speed range. Shots outside the detection range, such as very slow chips, may not register at all. Check the stated range in the manual so you know what to expect.
Firmware. Some firmware versions carry tracking bugs that cause missed or inconsistent reads. Update to the current release, then test again.
Phantom-shot test. Swing without a ball. If the unit registers a shot, something in view is moving or reflecting light. Remove it and test again, and keep doing this until the phantom reads stop.

The phantom-shot test is worth doing on its own because it separates two problems that look identical from the software side. A missed real shot points at placement, lenses or the ball. A registered shot with no ball points at the room, and the lighting and room setup section below covers that case.

Ball numbers fine, club numbers missing or wrong

Club data depends on four things, in this order: the tracking mode, the license, the markers and the light. Check the mode first, because a correct setup in the wrong mode still gives you ball numbers only. This is the most confusing category for owners, and the fix is usually a setting rather than a repair.

Check the tracking mode and the license first

Open the tracking mode setting in FSX. The sources we compared describe two modes. In the one called 1-Dot, the system reports ball flight only, with no markers or license needed. In 4-Dot, it reports ball data plus club data such as club speed, angle of attack and face angle, and it needs markers plus an active Club Analysis license. Confirm what your firmware and FSX version provide in each mode, since the names and options vary. One source gives the path as Settings, then Tracking Mode, but check the menu on your own version.
Confirm the Club Analysis license is active. One source gives the path as Account, then Licenses. Find the license entry in your FSX account settings and check its status.
Restart FSX after any activation. If the license shows as active and club data still fails, log out and back in to refresh the status.

Seeing only ball data usually means one of two things: the system is in the ball-only mode, or the license is not active. Check both before you move on to the markers, because the markers can't help if the mode isn't set to read them. Once the mode and license are right, the club data problem is almost always in the markers or the light.

Fit the markers the way Foresight's template shows

Use the markers Foresight supplies rather than third-party stickers. Club data depends on the system recognizing the marker pattern, and stickers from other sources may not match the pattern the software expects. A marker that's the wrong shape or size can look fine on the face and still fail to read.

Clean the club face first with a damp cloth, then dry it fully. Markers that go on a dirty or oily face peel mid-swing, and that peeling shows up as patchy club data.
Apply the markers exactly as the template in the manual shows. Placement advice varies between sources. One says near the heel of the face and another says centered, so trust the template over any single guide.
Start with a mid-iron, such as a 7-iron. Its flat face holds markers easily, which makes it a sensible first test club before you try the rest of the set.
Replace markers that are peeling, dirty or faded. One source estimates a replacement every 10–15 rounds, but judge your own set by how it looks and how it reads, since wear depends on how often you play and how you store them.

Markers aren't the only cause of patchy club data. Mats and turf can interfere, and glare or shadows on the club face can stop the system from picking up the markers. On a GCHawk, the overhead camera's alignment also matters, and a bumped mount can misalign the view enough to cause intermittent misses on the club. The lighting and room setup section covers the environmental side in detail.

Update firmware so club data reaches FSX

Old GCHawk firmware can stop club data from importing into FSX or into third-party apps. If the mode, license and markers all check out and the club data still doesn't arrive, the firmware is the next thing to check.

Power the unit and connect it to the network so it can reach the update service.
In FSX, open the device settings and find the firmware section. Menu names vary between versions, so look for the equivalent section on yours.
Choose the option to check for updates, and follow the prompts that appear.
Leave the unit alone for about 5 to 10 minutes. Never power it off during the update, since an interrupted update is one of the causes behind the LOCKED message covered below.
When the update finishes, restart the unit, then restart FSX.

Check for updates roughly once a month. Keeping the firmware current means you're less likely to hit a bug that's already been fixed, and you won't be caught out by a mismatch between the unit and the software after an FSX update.

Status lights and the LOCKED message on the GCQuad

The unit's own lights and screen are the quickest diagnostic you have, and they're also the part of this guide most likely to mislead you. Sources disagree on what some of the lights mean, and the meaning can shift between firmware releases. Treat the general pattern below as a starting point, and check the light legend in your manual before you act on it.

The general pattern owners describe is green for ready or ball detected, and red for an error or a unit that isn't tracking. A blue indicator relates to club tracking status. The sources differ on the finer detail. One describes solid green as tracking active and blinking green as a shot recorded, with solid red meaning an error and blinking red meaning low battery or a firmware issue. Another says a steady blue light means club tracking is active, a flickering one means partial detection, and no light means the unit needs repositioning or cleaning. Your manual's legend is the authority, and it overrides any pattern you read here.

If the light shows an error, work through these checks:

Level. Confirm the unit is level with the mat. A tilted unit can throw off detection.
Obstructions. Clear the lenses of any tee, debris or dust. A tee left in front of the lens is the sort of obstruction that's easy to miss.
Battery. Charge the GCQuad. A low battery can show up as an error light, and it can look like a hardware fault when it's only a power issue.

What the LOCKED message is tied to

The LOCKED screen is linked to licensing or authorization. The sources we compared associate it with an unauthorized software version or licensing issue, a failed firmware update, a change in ownership or subscription, and corrupted system files. Which one applies to your unit is something Foresight support can work out faster than you can by guessing. The steps below rule out the easy causes first, so that if you do need support, you've already cleared the simple ones.

The fix order runs as follows:

Restart the unit and FSX.
Check for firmware updates and install any that are available, letting the update finish fully before you power down.
Confirm the license is active in your FSX account.
If the message stays, contact Foresight support, with the details listed later in this guide.

Stick to firmware that Foresight publishes. Unofficial firmware can void the warranty, and an unofficial install is the kind of change that can leave a unit in the authorization state that LOCKED reflects. If you've made any change to the unit's software before the message appeared, mention it to support, since it's one of the first things they will want to know.

Room setup that keeps the cameras locked on

Lighting, reflections and the space around the ball cause a lot of erratic data that looks like a hardware fault. Work through the checklist below, then look at the camera feed in the software or app. The feed shows you what the cameras see, which is often more useful than guessing at the cause.

Sunlight. Direct sunlight overpowers the cameras. Close the blinds or move the unit away from windows before you blame the hardware.
Light type. Use steady artificial light in the range of about 3000K to 5000K color temperature. Steady LED or halogen fixtures both fit that range. Avoid flickering or dimmable lights, since they strobe and can make the cameras lose the ball between frames.
Shadows and glare. Remove shadows on the ball and mat. More light isn't always better, because too much causes glare that hides ball and club face detail. Aim for even light over the hitting area.
Camera feed. Check the camera view in the software or app. A grainy or washed-out picture tells you to adjust the lighting before anything else.
Clear zone. Keep objects out of roughly 3 ft around the ball. Loose items, bags and tees left close to the hitting area can all end up in the camera's view.
Reflective surfaces. Cover or move mirrors, metal and glossy paint that bounce light back toward the cameras. A glossy wall behind the hitting area is a common culprit, and it's easy to overlook because it looks harmless to the eye.
Wireless gear. Keep routers, phones and other wireless devices a few feet away from the unit. One source gives 6 ft as the distance, so check that figure against your manual.
People and motion. Fans, pets and people moving behind the hitting area can confuse the cameras. Keep that area still during a session, and turn fans away from the unit if you can.

The GCHawk has its own version of this problem. Its overhead view depends on the ceiling height and on the mount staying put, so read the ceiling height guide before you blame lighting or software for a fault that might be geometry. If lighting is the more likely suspect, the lighting interference guide walks through the light sources that cause the most trouble in a bay. Lens cleaning and the calibration routine are covered in the sensor cleaning and calibration guide, which is worth checking after any move or bump.

A small kit worth keeping next to the bay

Most of the downtime covered in this guide can be shortened with a few spares kept together. Test each one once, when nothing is wrong, so that you know it works before you need it in the middle of a session.

Spare USB cable. Keep a spare certified USB 3.0 cable for the GCQuad. The sources describe a USB 3.0 Type-A to Type-B cable, so match that connector type when you buy.
Ethernet cable. Keep a Cat 6 Ethernet cable, or better, for a wired connection between the PC and the router.
USB-to-Ethernet adapter. Keep one for a laptop without an Ethernet port. Test it before you need it, since a new adapter sometimes needs its driver installed first.
Dual-band USB Wi-Fi adapter. Keep one for internet access when the PC is joined to the GCQuad's Wi-Fi.
Club markers. Keep a pack of genuine Foresight club markers so that a peeling set doesn't stop a session.
Microfiber cloth. Use it for the lenses and for the club faces before you apply markers.
Bubble level. A small level makes it quick to confirm the unit sits level with the mat.
Compatible balls. Keep a few clean balls that Foresight lists as compatible, so you can rule the ball in or out in seconds.

If you move the unit between locations, the GCQuad cases and accessories guide covers the carry options and what to look for in a case. A case also protects the lenses on the road, which removes one of the more common causes of missed reads on arrival.

Shop GCQuad and GCHawk accessories

What to have ready before you contact Foresight support

If the steps in this guide don't clear the fault, a support ticket gets resolved faster when it arrives with the details already gathered. Foresight support can diagnose licensing and hardware issues remotely, so the information you send up front decides how quickly they can start. Collect the following before you write to them.

Unit details. The unit model and its serial number.
Versions. The firmware version on the unit, the FSX version on the PC, and the operating system.
Connection. The connection type in use: USB, Wi-Fi or Ethernet.
Symptom. The exact symptom, when it started, and whether it happens on every shot or only some of them.
Screen or lights. A photo of the screen or the LED state, including any LOCKED message.
Steps tried. The list of steps you've already run from this guide, with the order you ran them in.

Write down what changed just before the fault started. A firmware update, a move of the unit, a new router, or a change to the network are the sort of changes support will ask about first, and having them in the ticket narrows the search. Include the date and time of the first failure if you can recall them, since logs from the software can be matched against it.

Questions GCQuad and GCHawk owners ask

The questions below cover the points that come up most often in the sources we compared. Each answer points back to the section that covers the topic in more detail, and the answers are the same ones that appear in this page's structured data.

Can I use the GCQuad's Wi-Fi and still play online in FSX Play?

Yes, but not through the same link. The GCQuad's Wi-Fi connects the unit to the PC and does not carry internet, so the PC needs Ethernet or a second Wi-Fi adapter for its own connection. The sources we compared quote 25 Mbps down and 5 Mbps up for online play, and that figure is worth checking against Foresight's current requirements. The section on Wi-Fi and the lost internet problem covers the setup in more detail.

Why does the GCHawk give ball data but nothing for the club?

The usual causes are the tracking mode, the Club Analysis license, the markers or the firmware. Check that FSX is set to the mode that includes club data, confirm the license is active, and log out and back in to refresh the status. Apply the markers as Foresight's template shows, and update firmware, since older versions can block club data from importing.

Do I need to recalibrate a GCHawk after a firmware update?

Restart the unit and FSX after any update. If readings shift afterwards, run the calibration or alignment routine in the software, and do the same after the mount has been moved or bumped. Foresight's manual has the current recommendation, so follow it where it differs from this answer.

Will any golf ball work with a GCQuad?

Not all balls track equally. Clean, conforming balls in good condition are the safest choice, while badly scuffed or unusual balls can cause misses or odd spin readings. Foresight publishes compatibility guidance, and that list is the one to rely on.

Is it safe to move a GCQuad between the range and an indoor bay?

Yes, the GCQuad is a portable unit with a built-in battery, and carry cases exist for it. Before each move, charge the battery, clean the lenses, and level the unit, then reconfirm ball position. Direct sunlight into the cameras can still cause misses, so keep the unit out of it on the range.

Your Foresight Unit Stopped Cooperating: How to Get the GCQuad or GCHawk Reading Again