What do misreads look like?

[ldsfunaz]

I just got my Skytrak about a month ago and have been loving it. Just been in the ST range so far and for the first two weeks all was perfect. Only hitting irons but 99% of shots were read correctly. Lately I have been seeing some crazy flights that I would call misreads. Each one of these takes about 30 seconds to complete. Its happening about 5% of the time.

I see a lot of people bringing the term up but not much info on what the misread looks like. Is this what people are experiencing too?

[calebm1001]

Woah!! Never seen that happen on mine. I dont think this would fall under your typical “misread” category. This looks like a glitch or a bug in the software. If it happens more and more I would contact skytrak.

[Lynchdpm]

I experienced that in the beginning as well, just a handful of times. When this occurred I was playing around with the altitude settings. Not sure if this is your issue, but just check. I usually have my ST set at 200 altitude, the "glitch" occurred when I cranked the altitude up to 8000. Since I returned ST setting to 200 altitude, no more glitch

[Fantastish]

I have never seen anything like that. That does not look like a misread. It looks like a bug in the Skytrak driving range software.

[Dan McWhirter]

There was a bug about September 2016, that was subsequently fixed. I'm pretty sure it happened with a firmware update. Are you sure your new SkyTrak has the current firmware?

[dg_1983]

Misreads are normally very low spin. I don't really suffer from other misreads. As others have said make sure you are running the latest version of the application

[chriscwhite]

I have been hitting on my SkyTrak for a year now, and I have never had a single reading like the pics you posted. My misreads are usually not reading the ball at all. My next most common misread is reading way too much spin like 11,000 or higher.

[pcascio]

Looks like you're gripping the club too tight.

[skytrakali]

This is classic numerical instability. There are other posts that have examples like this. This is not a misread - it's a miscalculation by the extrapolation algorithm

[ldsfunaz]

Thanks everyone for the feedback. I am using the android app, software 3.3.2 (25) and firmware version 1.7 which I think are both up to date.
I am using foam balls (Orange Callaway HX Practice balls) so I have the elevation cranked up pretty high, 8000-10000, to get more realistic carry/total distances. The distances were getting spot on but I guess the software can't really handle it. I'll drop it back down to see if it helps and I will report back.

[jut111]

Probably should have mentioned foam balls in the OP. Thats definitely the issue

[SkyTrak_Jordan]

Using foam balls will give you misreads. We recommend using normal golf balls for hitting and testing purposes.

[Llamma]

Foam balls could well be the issue here

[trhuke]

I just got my Skytrak about a month ago and have been loving it. Just been in the ST range so far and for the first two weeks all was perfect. Only hitting irons but 99% of shots were read correctly. Lately I have been seeing some crazy flights that I would call misreads. Each one of these takes about 30 seconds to complete. Its happening about 5% of the time.

I see a lot of people bringing the term up but not much info on what the misread looks like. Is this what people are experiencing too?

YEAH, but look at the distance on those drives!!! ;-)
I have had this happen occasionally too, usually when I had the altitude settings goosed.

[SkyTrak_Seth]

Yeah, we did run into issues on this a few years ago and put in a fix for it. But I think you've stumbled across a way to stress the algorithms to the point of breaking again by using foam balls at Colorado Rockies altitude I'll look into addressing it further, but for now, back the altitude down and use real balls.

[a4chet]

Here's another misread, there's no way I hit the ball like this

[SkyTrak_Seth]

Are you lining up a black mark toward the cameras prior to hitting? White headed driver?