Technical Questions on ProTee 2.0 + Base + 3rd Party LM

[wizardofodds]

I have a couple technical questions about the collective operation of ProTee 2.0 + Base + 3rd Party LM. I may need to create some scenarios or clarify with follow-ups. Technical responses are welcome. Setup: Open API/SDK directs JSON data streams into ProTee 2.0 which allows you to specifiy if the data being sent is club data and/or ball data. 1) Is there an option to send both club and ball data at the same time? (e.g. GC2 ball + HMT club) 2) How does ProTee 2.0 choose to model ball flight if I'm sending it 3rd Party ball data only but I have the Base Sensors connected as usual? (e.g. GC2 ball + Base club)

[Maverick]

Great question!

1: Yes, you can send both club and ball data to ProTee 2.0.

You can use ProTee base+2 cameras, GC2+HMT, or ProTee base+3rd party LM, assuming one is integrated.

2: ProTee 2.0 only uses ball data to model the ball flight.

The Protee Interface accepts club data from the main sensor and ball data from the ball track(ball speed), H-cam(ball path), and V-cam(ball LA). When putting, the putting sensor measures ball speed and ball path.

Using club data, back spin and spin axis is calculated. Both calculated spin data along with ball path, ball speed, and ball LA are all sent to ProTee 2.0 via the ProTee Interface program. It also sends the club data. But only ball data is used to model the ball flight. The club data is only used in the shot analysis screen for display purposes.

If a 3rd party LM is integrated, all ball data from the LM will be sent to ProTee 2.0 via the ProTee Interface program(or possibly something else)and used to model the ball flight. The club data will still be sent to ProTee 2.0 for display purposes only.

When a 3rd party LM is integrated, you would no longer need the two machine vision cameras.

Btw, all the comments above also applies to TGC simulator version.

[Cklguy2013]

[QUOTE=Zmax;n14394]Great question!


Using club data, back spin and spin axis is calculated. Both calculated spin data along with ball path, ball speed, and ball LA are all sent to ProTee 2.0 via the ProTee Interface program. It also sends the club data. But only ball data is used to model the ball flight. The club data is only used in the shot analysis screen for display purposes.

Hi Zmax,

I'm a bit confused here, if "spin data" is used in modeling ball flight, doesn't that mean that club data is used, as spin data is calculated based on club data. Or, are you saying that ball flight is modeled on ball speed, LA and path only, ignoring calculated spin data?

[Maverick]

No, I'm not saying that at all.

ProTee 2,0 uses only ball data to model the ball flight. But at the moment, ProTee does not measure ball spin or spin axis. So, club data is used by the ProTee interface program to calculated spin and spin axis. Which is then sent to ProTee 2.0 in addition to ball speed, path , and LA, which is all used to model the ball flight.

You might be confusing ProTee interface program with ProTee 2.0 the simulation software.

[Cklguy2013]

Thanks I understand, at the current time, the club data is used to calculate spin data, which is used in modeling ball flight. Of course,when and if we ever have a 3rd party LM, this unit will calculate ball spin etc, so I would assume that the club data would then be for information purposes only. The trick then I believe will be to match up the club data and ball data via orientation of the units. Personally I love having club data, as I believe it is very useful for instructional purposes.