8,153
edits
Changes
no edit summary
''Main Article: [[RunScribe]]''
[[RunScribe]] is a small pair of [[Footpod]]'s that provide a wide variety of [[Foot Strike]] metrics. These include things like Impact G's, GCT, Braking G's, [[Pronation]], and more. I love the detailed metrics that are provided, and the insight into my running form, and possible imbalances. The main disadvantage with the RunScribe approach is that the data is not available during the run, and has to be analyzed afterward. RunScribe is rather more sophisticated than most Footpods as it not only has a 3-axis accelerometer, it also has a 3-axis gyroscope and a 3-axis magnetometer allowing it to sense far more movement. You can read about my testing at [[RunScribe]].
[[File:RunScribe.jpg|none|thumb|500px|An overview of the data from RunScribe]]
=MilestonePod=
''Main Article: [[MilestonePod]]''
[[MilestonePod]] is a vastly cheaper alternative to RunScribe, and while it doesn't provide the detailed analytics, it's a great value for money. It's also a cheap and effective way of keeping track of the mileage of your shoes, and is worth its price for that feature alone. Like [[RunScribe]] the MilestonePod doesn't provide real-time metrics, and you have to analyze the results post run. You can read about my testing at [[MilestonePod]].
{| class="wikitable"
|- valign="top"
RPM<sup>2</sup> (Remote Performance Measurement/Monitoring) is a pair of insoles that fit into your normal running shoes. These insoles measure pressure and use accelerometers to measure movement (a little like Sensoria). The details are not entirely clear from the web site, but they claim to measure [[Cadence]], Ground Contact Time, [[Foot Strike]], and "acceleration power". The system also claims to measure running power, though I'm not sure of the methodology. The RPM<sup>2</sup> system measure pressure in four areas (Sensoria has three), giving a [[Pronation]] measurement. There are notes that RPM<sup>2</sup> insoles are not waterproof, which is rather disconcerting, and if you run in different shaped shoes the fitment is likely to be problematic. The sizing of the insoles needs to take into account the position of the ball of the foot to ensure the sensor is in the right place. The system supports both Ant+ and Bluetooth so there is both a phone app and some information that can be displayed on a watch (it's not clear if this is more than just power). The system can also be used as a power meter for cycling.
=SHFT=
The SHFT system uses two pods, one on the chest and one on the foot, rather like the Zoi. The SHFT system includes some unusual metrics such as toe off angle and body angle, as well as Cadence, GCT, Vertical Osculation, Impact, Braking, and Foot Strike. They also claim to measure power for running, something I'd need to see demonstrated in a lab to believe it's accurate and even then I'm not sure it's useful due to the impact of [[Running Economy]]. The system requires you to carry your phone, and it appears that your only feedback is via audio through the headphones which I generally find rather ineffective. It looks like there are some good post run analytics available via the app, but no sign of data export. The price of the two SHFT sensors is $300 which is a little high compared with other systems. =Proportional Audio Feedback =Many running sensors will provide information on your biomechanics using an audio message. Typically, this is a spoken message such as "you're landing on your heel" or "your braking is 1.31 feet per second." I generally find these audio messages far more annoying than they are useful. The messages tend to occur too infrequently for me to get a sense of how any modifications in my form are changing the metric being measured. The spoken word means it's a little tricky to combine this with music or radio. A better approach is to have a simple signal like a beep when your metric is outside the desired level. For example, [[TgForce]] will beep when your impact is too high, and you can combine this simple audio signal with music for the spoken word from a in audiobook or the radio. I believe that a superior approach is to have a variable audio signal that indicates how well you're doing. So instead of having a simple threshold such as 7g you'd have a range such as 5-9g. Then, when your impact is above the lower threshold you would get an audio signal, but the audio signal would vary in one or more of volume/pitch/duration depending on where you are in the range. So a 5g impact would produce a quiet, short, deep beep, and 89G impact would produce a loud, longer, high-pitched beep. This way you'd get quantitive feedback on how well you're doing against your chosen metric.