-
Last edited by Maverick; 09-27-2014, 03:29 PM. -
For what it is worth, I do see higher speeds on the ES 12 outside. But I am measuring the exact same swings and getting the difference. ES 12 is supposed to be pretty darn accurate as well. I'd sure like to believe the higher number is correct but that would mean the skytrak is off. It's a no win for me. Based on post #1435 I'm thinking skytrak is correct. If sebmour sees the same vs CG2. I'll accept the skytrak is correct and hit the weight room. -
Guys I'm seeing the same issue with ballspeed when comparing my Skytrak and ES12. I get about a 7 MPH difference or so. Skytrak will give me mid 160s and ES12 will give me low 170s and the only plausible explanation I can think of is the way the Skytrak is measuring the ballspeed. I haven't done the math but I'm guessing that the ES12 is measuring the ballspeed moving directly away from the unit and the skytrak is measuring the horizontal speed. A little bit of trigonometry and the pythagorean theorem would clarify this.Comment
-
Until Ver. 1.9 comes out i'm not taking anything for granted on the numbers. If they are wrong at one part of the ball flight they can be exhibiting issues somewhere else too. They've been silent so far on release to App Store dates, so something is up. Which is a shame as I'm getting tired of hitting 210Y 6 Irons into nowhere.
From what i've read - ES is a pretty known quantity (since 2011 i believe) and has proven 1-2 mph inline with FS and TM readings consistently. We don't yet have that large a sample size for ST.Comment
-
I get a much higher BS on driver on my ES12 against Flightscope but it is pretty much bang on for 4 iron downwards. I do find I don't strike it as well outdoors hence my ballspeds are down than when in the net and less fearful and target conscious.Last edited by Skedaddle; 02-17-2015, 08:13 PM.Comment
-
One other thing. Indoors : does your ES12 agree to Skytrak on ballpseed? You should see the same disparity inside and outComment
-
interesting theory but the math shows it would get worse for irons (higher launch=cosine of the launch angle is less), so I don't believe this is the culprit since most everyone thinks the iron ball speeds are spot on.Originally posted by Nicknku View PostComment
-
Inside : Hit 6 balls with a 6 IRON (driver can be wrong on ES12) and log the ballspeeds on both Skytrak and ES12
Outside : Hit 6 balls with a 6 IRON and log the ballspeeds on both Skytrak and ES12
I did this when I got my new Flightscope and was querying the ballspeed numbers. As I have said when I went outside I hit it worse and my ballspeed went down. Doing the above drill verified the Fscope was correct as the numbers were within 1 mph both inside and outComment
-
I realize the math would show that if the ballspeed calculation is the same for all launch angles.... there is obviously something up with ballspeed at lower launch.Originally posted by TorchRedRob View PostComment
-
Do you think it would process images differently based on launch angle? I wouldn't think so. But it's all speculation, so I'm gonna drop it. At this point I'm sure in my case it was me and not the launch monitor. Plus, the driver test data on the skytrak website matches to within 1mph of trackman ball speeds.Originally posted by Nicknku View PostComment
-
I have a very small sample size but on 4 shots (3 I have posted earlier in this thread) I have taken with Skytrak, ball speed on average was very close +/- 2 MPH and not always the same direction. Vertical launch angle was also very close. Spin was off by an almost constant 500 RPM and I think that may be that I am not comparing apples to apples. Total spin versus back spin and side spin and axis - I want to understand these better and also understand what Skytrak is giving me. If you change SkyTrak fom side spin rpm to axis with a shot showing, it recalculates the spin - so there's a correlation that I don't understand. I can see that mis-interpreting data would cause bad decisions in picking or setting-up a club. Back on point: Based on my experience, ball speed measured by ST is accurate as is vertical launch angle. I am starting to figure out that getting this unit lined-up to target line properly can have a profound effect on horizontal launch angle and side spin. Having the unit on a mat that moves around a little makes it more challenging.Comment
-
I find that Ball Speed, LA and BS are all measure really well and close with GC2. Side angle and Sidespin are not always close but I think that comes from the fact the Skytrak might not have been align properly. It's pain to align to target.Last edited by sebmour; 02-22-2015, 02:19 AM.Comment
-
That is amazingly close. With more iterations of the code in software it's going to get better and better.
Wow.Comment
-
You happen to get any driver comparisons. I feel the problem might be with lower launching and higher ball speeds.Comment
-
Mike Z,
Regarding total spin and side spin:
Back spin = total spin * cos (spin axis)
Side spin = total spin * sin (spin axis)
Spin axis = atan (side spin / back spin)
Conceptually, all that's going on here is breaking the spin vector into its components based on the spin axis.Comment
- Golf Simulator Forum is the center point for discussion on golf simulator products, brands, manufacturers, launch monitors and everything else related to golf simulation.
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.
Tweet
Comment