Skytrak Unregistered Shots

[jrz]

It is officially time for this topic to get its own thread. Enough people have mentioned it in various other conversations on this board and it has been glaringly ignored by SkyTrak_Seth.

Many of us have been experiencing a significantly higher number of unregistered shots in both the Skytrak app and TGC. It is difficult to define exactly when this problem started, but it seems that the consensus is that it began around when the version 2.3 applications were released and, as a result, firmware version 1.5 was installed on the Skytrak device.

While I can't speak for everyone else on this forum I can say the following for certain:

1) The number of unregistered shots has dramatically increased since the timeframe mentioned above.

2) Unregistered shots do not seem to be shot type dependent. For example, I will often hit a slightly thin or fat shot which registers as expected and follow this with a perfectly hit shot which is not registered (this sucks, btw - it never fails to pick up shanks but does fail to pick up shots that are seemingly perfectly struck).

3) The unregistered shots are not due to ball position or the height of the Skytrak unit. I have tried every standard suggestion and am very good at placing the ball a bit behind the laser dot for drives, a bit in front of the laser dot and closer to the unit for pitches, etc. I have tried raising and lowering the height of my Skytrak unit. SkyTrak_Seth - please do not come back and suggest playing with ball position to remedy unregistered shots. We have all tried this and the problem persists.

4) The dramatic increase in unregistered shots has made play in the Skytrak app and TGC much less enjoyable. Every time the Skytrak fails to pick up a shot in TGC it is almost comical because of how frequently this happens during a "live" TGC round.

5) The dramatic increase in unregistered shots has made playing with friends (locally) a nightmare. I have had to apologize to them for how often it occurs, deliver instructions on the "ball position fixes" to my fellow players, etc. Often another unregistered shot occurs right after my vehement defense of Skytrak and it just makes me look like an ass.

SkyTrak_Seth - please officially address this issue. When I first purchased my Skytrak unit I thought that the shot delay would be so frustrating that it might be the Achilles heel of the device and cause me to return it and spend the extra money for a GC2. The shot delay turned out to be fine (about 2 seconds for me in both the Skytrak app and TGC). Every time another shot is not registered, however, I have to take a deep breath and my mind inevitably starts thinking about how the extra cost of the GC2 would be worth it because of the minimal delay and it's proven reliability to register shots. I am now on the fence about keeping the Skytrak and have begun the process of figuring out how I would explain to my girlfriend if I were to spend the extra funds for a GC2 (even though we are not married yet she is still the boss.... ;-) )

[dsailer]

Sorry to year this. Must be really frustrating especially now that you have TGC. I just wanted to add two things: one, I haven't had this happen much at all since the last release. (iOS, iPhone for me) If anything, I've had fewer no reads. Two, I wonder if it is related, or even the same problem, as the increased connection issues:

http://golfsimulatorforum.com/forum/skytrak/66167-skytrak-connection-problems-since-lastest-update

I'm wondering if the no read, is really just the connection problem that occurred when a shot was hit. Is there any correlation between users experiencing these two issues?

The interesting thing is that I used to have connection problems BEFORE the last release, not they are all but fixed for me.

Hopefully Skytrak will address this and also add a few more beta testers next time.

[N54TT]

I only use my iPad and haven't had any issues with unread shots. As the poster above said....maybe it's connection related? Does the top light on the Skytrak turn red then green after the shots that don't register?

[jrz]

Yes, the unit will usually think for a moment (the laser light goes off, the top light goes red) and then it goes back to all green and laser light on without a shot being recorded.

[GmanJeff]

This is my experience, too. The laser dot goes out, the top green light goes out, but the shot fails to register and after a pause the unit resets by itself to three green dots and the laser active. No particular delay in resetting. I experience this with perhaps 10% of my shots. I'm on Windows, connected via USB.

[wbond]

Is there any chance you may be taking a practice swing near the ball and the top green light would go off and not come back on before you actually hit? I have been lucky because i don't have any of these issues, but i have noticed this before.

[jrz]

No, this isn't the problem. The light does sometimes go off when a ball is placed in front of the unit or it detects rapid club movement, but I never hit the ball before the laser light comes back on and all lights are green.

[TeaPeg]

Really sorry to read about this issue cropping up again in the forum. jrz, I would start with a simple test. 200 shots on the ST range and 200 shots in TGC. Are the number of misreads the same for both? While you have assumed that the issue lies with ST your testing may reveal something entirely different. I would suggest that there will be a greater number of misreads in TGC than the ST app. If/when you can confirm this through testing then you will know which avenue to pursue.

[SkyTrak_Seth]

jrz , I do apologize for being away from the board for ~ a week, but this is the first I've read of this issue. I'm happy to officially respond. As you can see, the first 4 responses to your post indicate that this is not an across-the-board issue. So here's a few things I need to ask:

1) Has your unit ever been hit with a ball?

2) Do you use the shield? If so, is the unit height still as if it were sitting on the mat?

3) I assume you are using clean white golf balls?

[SkyTrak_Seth]

You know, I've seen many a SkyTrak units take their fair share of beatings and keep on ticking, but any time there is an issue such as this especially if it differs from the majority of the field, I would always err on the side of caution and have the unit checked out. Just FYI, I've pulled a brand new unit first thing this morning, downloaded a fresh v2.3 app from the app store and have hit well over 100 shots over the course of 4 hours with not a single disconnect or missed shot.

[jrz]

SkyTrak_Seth, what's the process for sending my device in to be checked? I have a two week international trip coming up and it would be perfect timing to part ways with my Skytrak for a bit.

[SkyTrak_Seth]

Their live chat should be able to set that up no problem. Just tell them you want it checked out. If you come up short, just PM me and let me know and I'll get it going in the right direction.

[Vincent_Vega]

jrz , I do apologize for being away from the board for ~ a week, but this is the first I've read of this issue. I'm happy to officially respond. As you can see, the first 4 responses to your post indicate that this is not an across-the-board issue. So here's a few things I need to ask:

1) Has your unit ever been hit with a ball?

2) Do you use the shield? If so, is the unit height still as if it were sitting on the mat?

3) I assume you are using clean white golf balls?

Seth,

First of all, I appreciate your presence on this board and all the info you provide. I know this isn't part of your official job duties. But this can't be the first time you guys have heard of this issue. I myself messaged you about it a month ago. I fully agree that this isn't an across the board issue, but there are quite a few who have brought it up on the forums. I have this happen maybe 4-5 times a round on average. I can live with that no problem. It does however get to be more of a problem when 3 or 4 people locally are playing and that number is obviously multiplied 4 or 5 times. Unlike jrz, I was able to remedy my problem quite a bit by learning where to place the ball with each club relative to how high/low that club launches. So like I said, I'm content with my current results.

But can you possibly shed some light on what might be causing this? I'm referring to the following light sequence following a shot... Red, Green, Green. This seems to say that the cameras are picking up the ball, but there's some interruption in the connection during the processing of said shot. As the previous 4 responses state, I believe they're all using iOS. Maybe this issues only pertains to PC users? When I was using my iPhone and the Skytrak app, I very rarely had a no read. Maybe I should try connecting via WIFI instead of USB?

Like I said, 4 times a round is really not hindering my enjoyment. But it would be great to get that number down. So you can confirm that you guys don't have any "no-reads" at the Skygolf offices?

[st_golfer]

I am going to try switching to wifi tonight and see if it gets better. Using PC and USB I got 10 No Reads (R-G-G) in 49 swings. It's seemingly getting worse.

[Mickey]

Happened 5 or 6 times over 14 holes on harbour town yesterday. Is it enough to really tick me off - not really. But it is enough to keep me from inviting friends and family over for a round. As for when this started happening - almost certainly with the latest update.

[m3w]

My thoughts exactly! It's super embarrassing when you're explaining to someone on the range that you paid $3,500 for it, then proceed to hit a dozen shots that don't register.

[SkyTrak_Seth]

Seth,

First of all, I appreciate your presence on this board and all the info you provide. I know this isn't part of your official job duties. But this can't be the first time you guys have heard of this issue. I myself messaged you about it a month ago. I fully agree that this isn't an across the board issue, but there are quite a few who have brought it up on the forums. I have this happen maybe 4-5 times a round on average. I can live with that no problem. It does however get to be more of a problem when 3 or 4 people locally are playing and that number is obviously multiplied 4 or 5 times. Unlike jrz, I was able to remedy my problem quite a bit by learning where to place the ball with each club relative to how high/low that club launches. So like I said, I'm content with my current results.

But can you possibly shed some light on what might be causing this? I'm referring to the following light sequence following a shot... Red, Green, Green. This seems to say that the cameras are picking up the ball, but there's some interruption in the connection during the processing of said shot. As the previous 4 responses state, I believe they're all using iOS. Maybe this issues only pertains to PC users? When I was using my iPhone and the Skytrak app, I very rarely had a no read. Maybe I should try connecting via WIFI instead of USB?

Like I said, 4 times a round is really not hindering my enjoyment. But it would be great to get that number down. So you can confirm that you guys don't have any "no-reads" at the Skygolf offices?

Oh for sure, I know I've addressed several different issues with capture before, but was pointing out that #1 this is not a blanket issue with any new software or firmware update, and #2 I'm certainly not ignoring anything. I always try to help out here, but last week was spring break with the kids. RED/GREEN/GREEN is the normal light sequence when the unit captures a shot. The top light is called the 'armed' light - if it's green, that means you can hit a shot. If it's red, it is disarmed. We disarm it from the time it triggers until the shot has finished it's roll and the data is displayed. You'll notice that if you 'false-trigger' the unit by waiving a club in front, it returns to the armed state much faster because it's clear that it has nothing to process. On the other hand, you'll notice that it sometimes takes longer than usual to process (start to fly the ball) on bad or out of the ordinary shots because the software wants to make double-sure that it's really that shot.

[Smudge_si]

Seth,

First of all, I appreciate your presence on this board and all the info you provide. I know this isn't part of your official job duties. But this can't be the first time you guys have heard of this issue. I myself messaged you about it a month ago. I fully agree that this isn't an across the board issue, but there are quite a few who have brought it up on the forums. I have this happen maybe 4-5 times a round on average. I can live with that no problem. It does however get to be more of a problem when 3 or 4 people locally are playing and that number is obviously multiplied 4 or 5 times. Unlike jrz, I was able to remedy my problem quite a bit by learning where to place the ball with each club relative to how high/low that club launches. So like I said, I'm content with my current results.

But can you possibly shed some light on what might be causing this? I'm referring to the following light sequence following a shot... Red, Green, Green. This seems to say that the cameras are picking up the ball, but there's some interruption in the connection during the processing of said shot. As the previous 4 responses state, I believe they're all using iOS. Maybe this issues only pertains to PC users? When I was using my iPhone and the Skytrak app, I very rarely had a no read. Maybe I should try connecting via WIFI instead of USB?

Like I said, 4 times a round is really not hindering my enjoyment. But it would be great to get that number down. So you can confirm that you guys don't have any "no-reads" at the Skygolf offices?

Very similar for me as Vincent said , doesn't bother me too much on my own its usually 4-5 times a round , it doesn't seem specific to a certain shot type , can happen with driver / iron / wedge but when I have friends over it becomes almost embarrassing having to explain the miss reads.

[Jimsol]

I have been having this issue quite a bit. I do have the latest firmware and software on both my PC and Ipad. Seems as if for the first dozen shots or so it works fine then I'll hit a shot and it will not register. the laser would come on I would hit and nothing. I'll wait the laser would come back I would hit and it would register. its like after a dozen or so it would only register every other one.. very frustrating. I did call tech and sent it in to get checked. I just got it back last night and hope to see if the problem was fixed. I'll let you know how it goes.
.

[SkyTrak_Seth]

Yes, please do!

[Jimsol]

I have been attempting to use my Skytrak since I got it back from supposedly being repaired. It now connects to my network fine but it still after a dozen shots or so starts to only register every other shot. It cycles and the laser comes on like its ready, I hit the laser goes off but doesnt show the shot. the laser come back on I hit and it may or may not register again. it continues on a every other or so cycle until I turn it off and start all over.. It has been very frustrating and Skytrak said they fixed it?... something is wrong.. please help..

[Vincent_Vega]

Oh for sure, I know I've addressed several different issues with capture before, but was pointing out that #1 this is not a blanket issue with any new software or firmware update, and #2 I'm certainly not ignoring anything. I always try to help out here, but last week was spring break with the kids. RED/GREEN/GREEN is the normal light sequence when the unit captures a shot. The top light is called the 'armed' light - if it's green, that means you can hit a shot. If it's red, it is disarmed. We disarm it from the time it triggers until the shot has finished it's roll and the data is displayed. You'll notice that if you 'false-trigger' the unit by waiving a club in front, it returns to the armed state much faster because it's clear that it has nothing to process. On the other hand, you'll notice that it sometimes takes longer than usual to process (start to fly the ball) on bad or out of the ordinary shots because the software wants to make double-sure that it's really that shot.

Sorry, wasn't insinuating that you were ignoring. Yeah, I understand the difference in the false trigger and when it stays red after a normal shot. I've had well struck shots not register just as much as poorly struck shots (which is the only time I get annoyed because like any amateur I don't hit my next shot near as well of course). If this is a hardware limitation, then so be it. But that doesn't appear to be the case because some are claiming to have never even had this issue. So that leaves either quality control or user error. A few times per round isn't a big deal for me, but sounds like some are having more frequent issues. I'm sure most of them have done extensive experimenting with unit height, making sure it's level, lighting, golf ball quality, etc. But it seems like there is one universal factor that some are doing that is giving them better results than others. Just seeing if we can openly discuss what that might be so those having major issues can try those methods.

[SkyTrak_Seth]

No worries, that was to the OP. While a few missed shots per round isn't ideal at all, it really could be a multitude of factors which makes it very hard to chase down. However, I will continue to look into the issue to make sure it's nothing in the software.

[ernie18]

Jrz i would like to point you to my skytrak tips and tricks thread to further help your skytrak experience. I think you might note some of the tips and tricks will help you in your future endeavors. it can be found via the search feature in this forum.

[jrz]

Thank you for the suggestion. I have read just about every Skytrak post and have seen all of the tips and tricks and have tried just about everything possible.

[goodmatt78]

SkyTrak_Seth You mentioned sending in the unit to get checked out. Did you ever decide on the fee to do so? I know this was discussed last summer, but you kept saying that a type of service plan was being put together....then nothing.

Any update on how this works?

[SkyTrak_Seth]

Sending an email now.

[goodmatt78]

Never received anything.