
Let’s have a look the time axis of a complete stroke (figure above). It starts with the Catch, defined here as the point where the handle is closest to the chain gate. I assume that a stroke is not a single stroke, so the flywheel is still running at the catch. The axis that is rotated by the chain and the flywheel are connected by a clutch. This is a device similar to the freewheel of a bicycle. We can only add power to the flywheel when the speed of the handle matches the current speed of the flywheel. At the catch our arms are fully stretched, so in order to move the handle we have to move our body. To get the handle up to the speed the speed of the flywheel we have to bring our body up to speed. This takes time and a lot of power. This is phase-I in the figure. In phase-1 the PM cannot sense what we do because it only senses the rotation of the flywheel. In phase-II in which apply power to the flywheel, the PM can measure our force and the speed of the handle. A short time before the finish of the drive, the handle movement slows down and the PM is again disconnected from the handle movement (Phase-III). This is also the case for the recovery (phase-IV). Clearly, the PM is blind for movements during a big part of the stroke, viz. phases I,III and IV. What the PM or ErgData shows as Drive Length and Drive Time applies to a part of the drive, viz. phase-II.
Let's see how the handle speed is related to the flywheel speed. The chain of the C2 erg is 1/4 inch. That means that each link is 2.54/4 = 0.635 cm long. The chains runs over a 14-sprocket wheel, so one rotation of the axis on which the flywheel is mounted corresponds to a handle displacement of 14 x 0.635 = 8.89 cm. Typical drive speeds are 1.5-2 m/sec. This corresponds to about 17 - 22.5 rotations per second.
One of the options to measure handle speed is to measure the rotations of the sprocket axis. For this, we have to look to the side opposite of the flywheel. Behind a plastic cap (picture below) we find the axis capped with a hexagonal nut. I have read several academic studies where a rotary encoder was connected to the axis. This is an instrument that gives multiple pulses over each rotation. However, at a rotation rate of about 20/sec this would overwhelm my data collecting capabilities. So I looked for simpler means, preferably contactless,.

One option is optical. However, the available photoresistor was rather slow (typically 30 msec rise and 30 ms decay). Another sensor is magnetic. This is used in the flywheel (3 magnets with Hall effect sensor). I had a lot of experience with reed-switch sensors which are commonly used for measuring the speed of a bicycle. I thought to give it a try, although the rotations per second of a bicycle wheel are much slower (30 km/h = 10 m/sec ; typical wheel circumference = 2m, hence 5 rps).
I was long pondering about how to make a small wheel that was driven by the hexagonal nut, before I hit upon a simple solution : a DVD disc. It turned out that I only needed to carve 6 edges in the central hole of a DVD to match the geometry of the hexagonal nut. The next step was to screw 2 spoke magnets on the DVD and find a way of mounting the wheel sensor (reed switch) close to the circular path of the magnets. The use of 2 magnets means that each passage of a magnet corresponds to a handle displacement of 8.89/2 = 4.445 cm. This is the maximum resolution of this setup.



The sampling of the sensor was done with an available DATAQ DI-145 data acquisition kit that has a maximum rate of 240 samples/sec. The DI-145 is connected to an old laptop with a Windows-XP operating systems (this DATAQ has no drivers for later Windows systems). The raw data were then transferred to a desktop that has more advanced data processing software.
The first question was, of course, whether the reed-switch sensor could cope with the high rotation speed of the magnets. Fortunately, this turned out to be the case as shown in the next figure. The information is in the number of peaks and in the time-spacing of the peaks. The height of the peaks is not important. Each successive peak corresponds to a handle displacement of 4.445 cm. The drive has 34 peaks, which implies a drive distance of 151 cm. The recovery has 35 peaks. There are no peaks missing.

The information in the spacing of the peaks can be converted in a speed graph (speed=0.04445/(time gap)).

This graph shows several interesting features. The drive starts with a huge speed ramp, almost linear. This is the initial acceleration of the body (phase-I). The acceleration is much bigger than I expected : from 0.3 m/sec to 1.5 m/sec in about 0.15 sec amounts to an acceleration of 8 m/sec². Note that the acceleration for a vertical jump in the air is 10 m/sec². At an estimated body mass of 50 kg (lower legs don't move) this implies a power of some 350W! Note that there are 4 data points in the initial ramp, so a displacement of about 13 cm. All this happens before the flywheel sensor takes note. At 1.5 m/s I hit the speed of the flywheel and started the power input for the flywheel.


The reason I share these first results, which are provisional, is that I like to challenge other readers to come up with alternatives or better ways to measure handle speed. Maybe there are readers who have experience with Arduino or Raspberry-Pi computers, or have friends playing with such systems, which might do faster and better sampling. I am happy to share more detail. Send me a personal mail if you are interested.
(to be finished soon ; more text will be added)