Review and Suggestions
Posted: Thu Apr 23, 2020 2:00 am
Overall Impression: I am loving it and would definitely buy this again. There are limitations to this but for my purposes and at the price I paid, I think this was a great purchase.
The good things:
1. Your response and support on the forum is honestly phenomenal. You were very attentive to my questions and responsive to my almost nonstop posts so I really appreciated it and it made me happy to have bought the device from a company that obviously cared.
2. It works. After a lot of tweaking, I have gotten to the point were I can tell that the power values consistently reflect my HR trends, and my subjective effort regardless of whether I am on a slow climb, or a fast descent and regardless of wind conditions.
3. For someone nerdy like me it is really nice to go through the data, and also to tweak the settings to get the machine to work just right.
4. There is a lot of potential data to mine through
The bad:
1. The calibration. Honestly I thought this part was horrible. Calibration rides never got it right for me and I think its partly because I am in a windy area. On a short calibration ride, one wind gust would probably screw things up? Then I never knew how to start another calibration ride if I wasn't happy with the one that was finished and was far from a computer. Regardless of what I did or what the true reason was, the calibration rides just didn't work. It seems many on the forum had similar experiences but I quickly learned that I didn't need it to work. I got my settings right by changing them manually when looking at lap data from a park loop and looking at out and back rides.
2. The mount: There are way too many possible positions on the mount and even placing it as far forward as possible still didn't ensure reproducibility. I eventually used your advise of just keeping the device on my bike and never taking it off. I wash my bike with the device in place now.
3. The manual/ instruction paperwork provided were very limited. They did not address important things such as for example the ability to click the button several times to shut the powerpod off. There are other things as well that aren't even included in isaac. For example, when I started off I thought that the average wind speed was an average over time. So I was expecting that unless there were disproportionately bigger climbs when the wind was a tailwind, I would spend more time in the wind and should adjust parameters so that the average wind for an out and back or lap is positive. Then I find out from you that average wind is over distance ==> it will be 0 in a lap or out and back when the wind speed doesn't change.
4. Fixing angles when the device moves using check calibration. Often times, I had the device move around from its prior position. Powerpod somehow compensated for htis quickly in my ride and from several minutes onwards the power values returned to normal. however when I would go back, use the check calibration it would predict parameters that were out of range and could not be sent back to powerpod. I think this is a problem because if I do a calibration in that position I get parameters that work. Its not clear to me why the powerpod somehow comes up with parameters to fix the issue within minutes of my ride, but those parameters can't be saved after going through the check calibration?
5. Rapid changes give weird numbers. When changing from decent to flat, or decent to climb, or climb to decent etc the numbers are crazy for one or two readings. not sure if this has to do with different sensors having different sensing times? ( slope is still considered something different when acceleration is already updated or vice-versa?). This also happened to an extreme with some wind gusts and was annoying.
6. Combining with data from a cycling computer is hard and didn't work. My cycling computer usually started recording earlier than powerpod because I always checked that my sensors were working before turning powerpod on. The problem was that the data could be shifted. My cycling computer file may be a few seconds earlier than powerpod. And these things can change if when I pause my ride it pauses on one of the machines earlier than the other. A solution could be to manually move the data, or to have isaac match the timing based on heart rate or cadence etc ( since both are getting this info from the same source). It didn't seem to be doing that matching and so combining with my cycling computer data was useless.
Suggestions:
1. For calibration:
- Give specific instructions in your manual and guidance about good practices to manually tweek calibration after a ride. The stuff I used and mention here helped me but I am sure you have other tools or principles you use and it would be nice to see those written in the manual. I used laps around a park and out and back rides with tweeking values to get my gravity 0, and wind 0 for most laps. I liked laps because the short time meant that wind conditions weren't likely to change much and because it almost gave you multiple samples to test and confirm on. I also manually looked at out and back rides but paid much more attention to the end of the out and the first part of the back since the timing was so close that the wind conditions were much more likely to be similar. I found this worked better for me than the check calibration button.
- Use coasting instead of or in combination with the out and back: Coasting would be great to use because it is the gold standard. Even calibrating against a DFPM is only as good as the DFPM but when coasting there is no question that the power is 0. I saw that there was a coasting section in isaac but not much explanation is given in the manual and I did not know how to use it.
- Option to see the calculated power during coasting instead of the forced 0 output from powerpod. I think this would be super helpful to do manual calibrations when I know that I did not use the brakes on a decent. So when my cadence meter goes to 0, the powermeter is forced to show a power of 0. It would be nice to instead see what power wouldve been calculated in order to get a sense of how good my parameters are. So for example if my calculated power for coasting down the hill and having x acceleration is + 10 or -10 .... Im not worried... if its -50, maybe I was on the breaks a bit ..... but if my parameters calculate a power of 70 when coasting then obviously regardless of what i thought my calibration needs adjustment and is way off.
- Have ISAAC highlight areas of similar stable heart rate: So gravity was much more quickly and easily calibrated than wind. I got to a point where I really trusted my power values on a slow climb but wasn't sure about similar power values on a flat. If ISAAC could see my average heart rate and power on a climb and identify flats or descents with similar heart rate, I would be able to see if the power values were similar to those of a climb with similar heart rate.
2. Allow for adjustment of CdA: An option that adjusts CdA to a drops position on all decents > slope x would be nice. It would be optional but may help many of us. Even nicer, you can have certain sensors that can be worn/ attached to bike in order to estimate when your position is changed to drops ( perhaps sensing distance between chest and the powerpod for example... when its smaller then you are on drops and you switch to the lower CdA).
3. Print more detailed instructions, and the isaac manual or a reference to it in the package. I didn't even know there was an ISAAC manual. A lot of questions I asked you on the forum couldve been avoided if I saw the isaac manual first. ( Maybe you provide more detailed manuals but my package was limited because I got a refurbished product?)
4. Design a mount with very specific limited possible positions. It would only allow positioning at angles a, b, and c. Then I would keep the mount in place, remove powerpod, and be able to return it and mount in angle a consistently.
5. Show what gears I was in: Knowing cadence and speed should make it easy for you to figure out what gearing ratio the rider is in. Then if the rider puts in information about their cassette and chainrings you can provide the exact gears they were in based on their gearing ratio and the next gearing ratio they shifted into etc. Also, you would be able to tweak the settings for the wheel circumference to a more exact number based on their cassette and true gearing ratio.
The good things:
1. Your response and support on the forum is honestly phenomenal. You were very attentive to my questions and responsive to my almost nonstop posts so I really appreciated it and it made me happy to have bought the device from a company that obviously cared.
2. It works. After a lot of tweaking, I have gotten to the point were I can tell that the power values consistently reflect my HR trends, and my subjective effort regardless of whether I am on a slow climb, or a fast descent and regardless of wind conditions.
3. For someone nerdy like me it is really nice to go through the data, and also to tweak the settings to get the machine to work just right.
4. There is a lot of potential data to mine through
The bad:
1. The calibration. Honestly I thought this part was horrible. Calibration rides never got it right for me and I think its partly because I am in a windy area. On a short calibration ride, one wind gust would probably screw things up? Then I never knew how to start another calibration ride if I wasn't happy with the one that was finished and was far from a computer. Regardless of what I did or what the true reason was, the calibration rides just didn't work. It seems many on the forum had similar experiences but I quickly learned that I didn't need it to work. I got my settings right by changing them manually when looking at lap data from a park loop and looking at out and back rides.
2. The mount: There are way too many possible positions on the mount and even placing it as far forward as possible still didn't ensure reproducibility. I eventually used your advise of just keeping the device on my bike and never taking it off. I wash my bike with the device in place now.
3. The manual/ instruction paperwork provided were very limited. They did not address important things such as for example the ability to click the button several times to shut the powerpod off. There are other things as well that aren't even included in isaac. For example, when I started off I thought that the average wind speed was an average over time. So I was expecting that unless there were disproportionately bigger climbs when the wind was a tailwind, I would spend more time in the wind and should adjust parameters so that the average wind for an out and back or lap is positive. Then I find out from you that average wind is over distance ==> it will be 0 in a lap or out and back when the wind speed doesn't change.
4. Fixing angles when the device moves using check calibration. Often times, I had the device move around from its prior position. Powerpod somehow compensated for htis quickly in my ride and from several minutes onwards the power values returned to normal. however when I would go back, use the check calibration it would predict parameters that were out of range and could not be sent back to powerpod. I think this is a problem because if I do a calibration in that position I get parameters that work. Its not clear to me why the powerpod somehow comes up with parameters to fix the issue within minutes of my ride, but those parameters can't be saved after going through the check calibration?
5. Rapid changes give weird numbers. When changing from decent to flat, or decent to climb, or climb to decent etc the numbers are crazy for one or two readings. not sure if this has to do with different sensors having different sensing times? ( slope is still considered something different when acceleration is already updated or vice-versa?). This also happened to an extreme with some wind gusts and was annoying.
6. Combining with data from a cycling computer is hard and didn't work. My cycling computer usually started recording earlier than powerpod because I always checked that my sensors were working before turning powerpod on. The problem was that the data could be shifted. My cycling computer file may be a few seconds earlier than powerpod. And these things can change if when I pause my ride it pauses on one of the machines earlier than the other. A solution could be to manually move the data, or to have isaac match the timing based on heart rate or cadence etc ( since both are getting this info from the same source). It didn't seem to be doing that matching and so combining with my cycling computer data was useless.
Suggestions:
1. For calibration:
- Give specific instructions in your manual and guidance about good practices to manually tweek calibration after a ride. The stuff I used and mention here helped me but I am sure you have other tools or principles you use and it would be nice to see those written in the manual. I used laps around a park and out and back rides with tweeking values to get my gravity 0, and wind 0 for most laps. I liked laps because the short time meant that wind conditions weren't likely to change much and because it almost gave you multiple samples to test and confirm on. I also manually looked at out and back rides but paid much more attention to the end of the out and the first part of the back since the timing was so close that the wind conditions were much more likely to be similar. I found this worked better for me than the check calibration button.
- Use coasting instead of or in combination with the out and back: Coasting would be great to use because it is the gold standard. Even calibrating against a DFPM is only as good as the DFPM but when coasting there is no question that the power is 0. I saw that there was a coasting section in isaac but not much explanation is given in the manual and I did not know how to use it.
- Option to see the calculated power during coasting instead of the forced 0 output from powerpod. I think this would be super helpful to do manual calibrations when I know that I did not use the brakes on a decent. So when my cadence meter goes to 0, the powermeter is forced to show a power of 0. It would be nice to instead see what power wouldve been calculated in order to get a sense of how good my parameters are. So for example if my calculated power for coasting down the hill and having x acceleration is + 10 or -10 .... Im not worried... if its -50, maybe I was on the breaks a bit ..... but if my parameters calculate a power of 70 when coasting then obviously regardless of what i thought my calibration needs adjustment and is way off.
- Have ISAAC highlight areas of similar stable heart rate: So gravity was much more quickly and easily calibrated than wind. I got to a point where I really trusted my power values on a slow climb but wasn't sure about similar power values on a flat. If ISAAC could see my average heart rate and power on a climb and identify flats or descents with similar heart rate, I would be able to see if the power values were similar to those of a climb with similar heart rate.
2. Allow for adjustment of CdA: An option that adjusts CdA to a drops position on all decents > slope x would be nice. It would be optional but may help many of us. Even nicer, you can have certain sensors that can be worn/ attached to bike in order to estimate when your position is changed to drops ( perhaps sensing distance between chest and the powerpod for example... when its smaller then you are on drops and you switch to the lower CdA).
3. Print more detailed instructions, and the isaac manual or a reference to it in the package. I didn't even know there was an ISAAC manual. A lot of questions I asked you on the forum couldve been avoided if I saw the isaac manual first. ( Maybe you provide more detailed manuals but my package was limited because I got a refurbished product?)
4. Design a mount with very specific limited possible positions. It would only allow positioning at angles a, b, and c. Then I would keep the mount in place, remove powerpod, and be able to return it and mount in angle a consistently.
5. Show what gears I was in: Knowing cadence and speed should make it easy for you to figure out what gearing ratio the rider is in. Then if the rider puts in information about their cassette and chainrings you can provide the exact gears they were in based on their gearing ratio and the next gearing ratio they shifted into etc. Also, you would be able to tweak the settings for the wheel circumference to a more exact number based on their cassette and true gearing ratio.
