1. An Orbbec Femto Mega camera, to be placed in the front of the rider. This might be your 3rd Femto Mega camera if you already have 2 for bilateral capture.
   
2. A network cable connecting the camera to the PoE Network Switch (assuming you already have a network switch for your other cameras.)
   
3. A sync adaptor and second network cable to connect the camera to the Orbbec Sync Hub (assuming you have a sync hub for your other 2 cameras)
   
4. Tripod or other camera mounting option
5. A subscription to Velogic Studio Pro (the Aero module is a Pro-only feature)
   
6. A PC meeting our System Requirements.
   

Positioning the camera

1. Place the camera mounted vertically (so rotated 90degrees from the “natural” orientation; the camera sensors are wider than they are high, so by rotating, we can use the longest axis to match the height of the rider)
   
2. Optimal distance for the camera is 1200mm (measured from the front of the camera to the leading surface of basebar for Tri, TT and road). It’s OK to go further back, but not too much closer than that. 
   
3. Optimal height of the camera is at the same height as the base bar or handlebars.

Installing Velogic software on the camera

Configuring the camera in Velogic Studio's Step 1

1. "Color view" is the view from the color sensor in the Femto Mega camera. You should ensure that this rectangle is positioned to capture the rider, with some margin.
   
2. "Wind view" is the view from the depth sensor in the Femto Mega. It has been "flattened" so that objects further away from the camera don't look smaller than objects closer to the camera, so it may look strange.
   This is the view that's actually used to generate the Frontal Area metric, so it's important that you correctly position the selection rectangle to cover the rider, but exclude things like the platform that the bike is sitting on.
   Note that this is a messy and imperfect-looking view, because Velogic Studio's algorithm is compensating for parts of the rider it can't actually see (e.g. the rider's chest obscured by their hands). Our algorithm accounts for this, and the overall Frontal Area metric that you see is a statistical combination from many frames.
3. "Depth view" is also from the depth camera, but as if viewed from the side of the rider. You can adjust this rectangle to control the "front" and "back" cutoff distances, to ensure that you capture all of the bike+rider, and nothing else (such as a platform or rear trainer). Make sure that the rectangle is positioned far enough backwards to get the rider's whole ankle at its rearmost point, i.e. halfway up the recovery phase of the stroke.
   

Adding Aero Baseline Details in Step 1

When you have an Aero camera active, you will see an "Aero Baseline Details" panel on the right-hand side of step 1:

1. Course Distance and Baseline Time give Velogic Studio an idea of how far and how fast your rider is travelling. This is used when estimating the effects of changing position, see "Aero MotionMetriq's" below.

Aero liveview and metrics in Step 2

1. Cd (coefficient of drag, which you have entered)
2. A (frontal area, which Velogic Studio has measured)
   
3. CdA (Cd x A, the product of the two terms, which should correlate to what you would measure in a wind tunnel)
   

Aero MotionMetriq's

1. Frontal Area is Velogic Studio's measurement of the frontal area of the rider + bike, in m²
   
2. Cd is Velogic Studio's estimate of the Coefficient of Drag of the rider. The estimation method is proprietary, but is based on the torso angle and the position of the rider. If you aren't using a lateral camera, this number will be blank.
   
3. CdA is simply Coefficient of Drag x Frontal Area. This is what a wind tunnel measures.
   

1. Aero Drag Power is an estimate of the power (watts) produced by the rider that is going solely towards overcoming Aero drag force.
   This is calculated from the current CdA, the average speed (Course Distance / Baseline Time) and a number of assumptions. It's not intended to be accurate (and there are too many assumptions for it to be accurate) but it will give a good indication of the difference in power required in different positions through the fit.
   
2. Course Time (mins) is the time it would take to complete the course distance entered in step 1 at the current CdA.
   For the Initial capture, this will be set to the Course Time set in Step 1, assuming that the initial position is the baseline position.
   For subsequent captures, this will be adjusted based on the difference in CdA; if the CdA goes down, the course time should also go down.
   Again, this won't be accurate because of the number of assumptions involved, but when compared against other captures it gives a good indication of how different Aero positions impact speed and therefore course outcomes.