Failure to record data
Posted: Tue Dec 25, 2018 9:51 pm
I was playing around with a couple of pieces of equipment today and decided to make a quick comparison between the estimated CdA for one and the estimated CdA for the other. I didn't do the full testing protocol because (1) this was not intended to be a careful measurement that would be comparable with results on a different day (a project for another day) and (2) I was running out of time.
At the time I THOUGHT that the bike I was riding was the one that was most recently set up in Profile 4.
After I woke up my sensors and my computer I pressed the button on the Aeropod. It blinked green a couple of times then turned to a steady green. I was far enough away from my other bikes that their sensors were irrelevant even if they had been on and I'm pretty sure none of the other sensors was active.
During the ride I pressed the Aeropod button occasionally if I had to stop for more than a few seconds for any reason and was always greeted by a steady green light.
When I returned home and loaded the ride file in Isaac I discovered that there were no DFPM data and no cadence data. The bike has both a C1 DFPM and a separate cadence sensor. I thought that was odd so I extracted the bike profile from the ride file and discovered that the wireless IDs for speed and power corresponded to a different bike, not the one I was riding. I didn't use Tracker so there was no GPS data.
There was something else puzzling as well. Although there were no DFPM data there were Aeropod power and also speed data.
All of which raises several questions:
(1) How in the world did the Aeropod get speed data if it was not paired to the correct sensor? Obviously it is possible in principle to calculate speed from acceleration ... but are the Aeropod's sensors that good?
(2) Why did I consistently see the green indicator light that (unless I have misunderstood) is supposed to indicate that sensors did pair correctly?
(3) Why is there no viable, user-friendly way to determine which sensors are actually paired with the Aeropod?
I decided to see if I could still recover useful information by merging the power and other data from my Garmin's FIT file and discovered that although Isaac offers to import that data from FIT files it is not in fact able to do so. Fortunately the Fit File Repair Tool CAN read FIT files and then export them as TCX and Isaac can import the data from that format.
Which raises another question:
(4) Why does Isaac offer to merge data from FIT files if it cannot in fact do so?
In the end I was able to generate data of uncertain reliability by merging Power information from the Garmin. I'm not convinced that my shiny new wheel covers did in fact reduce CdA by 10% but I HOPE that's correct.
I intend to do more formal testing in the future and maybe things will go more smoothly then... but today's difficulties certainly emphasize the NECESSITY of having a user interface that can communicate actual information.
At the time I THOUGHT that the bike I was riding was the one that was most recently set up in Profile 4.
After I woke up my sensors and my computer I pressed the button on the Aeropod. It blinked green a couple of times then turned to a steady green. I was far enough away from my other bikes that their sensors were irrelevant even if they had been on and I'm pretty sure none of the other sensors was active.
During the ride I pressed the Aeropod button occasionally if I had to stop for more than a few seconds for any reason and was always greeted by a steady green light.
When I returned home and loaded the ride file in Isaac I discovered that there were no DFPM data and no cadence data. The bike has both a C1 DFPM and a separate cadence sensor. I thought that was odd so I extracted the bike profile from the ride file and discovered that the wireless IDs for speed and power corresponded to a different bike, not the one I was riding. I didn't use Tracker so there was no GPS data.
There was something else puzzling as well. Although there were no DFPM data there were Aeropod power and also speed data.
All of which raises several questions:
(1) How in the world did the Aeropod get speed data if it was not paired to the correct sensor? Obviously it is possible in principle to calculate speed from acceleration ... but are the Aeropod's sensors that good?
(2) Why did I consistently see the green indicator light that (unless I have misunderstood) is supposed to indicate that sensors did pair correctly?
(3) Why is there no viable, user-friendly way to determine which sensors are actually paired with the Aeropod?
I decided to see if I could still recover useful information by merging the power and other data from my Garmin's FIT file and discovered that although Isaac offers to import that data from FIT files it is not in fact able to do so. Fortunately the Fit File Repair Tool CAN read FIT files and then export them as TCX and Isaac can import the data from that format.
Which raises another question:
(4) Why does Isaac offer to merge data from FIT files if it cannot in fact do so?
In the end I was able to generate data of uncertain reliability by merging Power information from the Garmin. I'm not convinced that my shiny new wheel covers did in fact reduce CdA by 10% but I HOPE that's correct.
I intend to do more formal testing in the future and maybe things will go more smoothly then... but today's difficulties certainly emphasize the NECESSITY of having a user interface that can communicate actual information.