Features I would like to see?
Features I would like to see?
I am new to the ibike, but already there are some features that I would like to see.
1. I use the Flight Deck, (gear selection/Distance), the Blackburn Delphi 6.0 (heart rate/cadance/Speed/Time) and the ibike for (watts/cal/slope sometimes wind). I like to see this information as I ride, and I don't want to be scrolling through windows while I am riding. If ibike could add this information to its unit and screen, my handlebar would be less cumbersome. (at the moment I have no room for a bell or front light)
2. I woud like to be able to set up my own screen on the ibike to show the information that I select is important. This could be done when connected to the ibike software, or while out on the bike. Perhaps to use provide 3 or 4 specific data at a larger font while other pieces of data are on the screen in smaller font to one side/top/or bottom.
3. I would like to see a gear analysis in ibike - where it takes over from my Flight Deck, and its virtual cadence. I could enter my gear ratio into the unit and ibike could analyse which gear I am in and display as such. It should also be able to analyse the best selection where I achieve the most watts power. This way I could get maximum power and cadence working for me at the same time. I would expect this (sweet spot) would change as I improved my riding ability.
4. I would like to see the Profiles easier to create, switch around, save and apply in the ibike software. I don't find the software easy to apply Profiles to the data. Perhaps this is me, but I am usually quite good with software. I know there will be different clothing as I head out to ride, jacket, just a shirt, shell, rain gear, helmet that can affect my wind resistance. I would like to select my profile quickly before heading out the door.
5. Calibration - the ibike software should suggest which coast calibrations to drop so that the results are more realistic. At the moment I remove the highest and lowest numbers, but they might not be the correct values to discard, or it may not be enough.
6. When I do a 4 mile return ride, the software could provide an error rating or ratio. It should point out if the elevations don't match from the turnaround point. It could supply possible suggestions for tweaks that would help direct me to achieve a correct adjustment. The most likely candidate would the level calibration, or poor wind reset, temperature when I started vs. 20 minutes later, or identify inconsistent movement/vibration in the unit mount.
Please add more
1. I use the Flight Deck, (gear selection/Distance), the Blackburn Delphi 6.0 (heart rate/cadance/Speed/Time) and the ibike for (watts/cal/slope sometimes wind). I like to see this information as I ride, and I don't want to be scrolling through windows while I am riding. If ibike could add this information to its unit and screen, my handlebar would be less cumbersome. (at the moment I have no room for a bell or front light)
2. I woud like to be able to set up my own screen on the ibike to show the information that I select is important. This could be done when connected to the ibike software, or while out on the bike. Perhaps to use provide 3 or 4 specific data at a larger font while other pieces of data are on the screen in smaller font to one side/top/or bottom.
3. I would like to see a gear analysis in ibike - where it takes over from my Flight Deck, and its virtual cadence. I could enter my gear ratio into the unit and ibike could analyse which gear I am in and display as such. It should also be able to analyse the best selection where I achieve the most watts power. This way I could get maximum power and cadence working for me at the same time. I would expect this (sweet spot) would change as I improved my riding ability.
4. I would like to see the Profiles easier to create, switch around, save and apply in the ibike software. I don't find the software easy to apply Profiles to the data. Perhaps this is me, but I am usually quite good with software. I know there will be different clothing as I head out to ride, jacket, just a shirt, shell, rain gear, helmet that can affect my wind resistance. I would like to select my profile quickly before heading out the door.
5. Calibration - the ibike software should suggest which coast calibrations to drop so that the results are more realistic. At the moment I remove the highest and lowest numbers, but they might not be the correct values to discard, or it may not be enough.
6. When I do a 4 mile return ride, the software could provide an error rating or ratio. It should point out if the elevations don't match from the turnaround point. It could supply possible suggestions for tweaks that would help direct me to achieve a correct adjustment. The most likely candidate would the level calibration, or poor wind reset, temperature when I started vs. 20 minutes later, or identify inconsistent movement/vibration in the unit mount.
Please add more
Re: Features I would like to see?
I agree with you on the user configurable screens, the rest of your suggestions, I could do without
Re: Features I would like to see?
Live TSS and NP as in TraingPeaks and Ergomo would be good.
-
- Site Admin
- Posts: 392
- Joined: Fri Jan 11, 2008 8:52 am
- Location: Durham, NC
Re: Features I would like to see?
The menu item "Profiles->Send Profile to iBike..." was intended to be the quick and easy way to change profiles. Just give the profile a descriptive name so you can find it quickly. Also, note that you can drag your profiles into the order that you want them to appear in the "Edit Profiles..." window. The order that you select will be the same order you see when you select "Profiles->Send Profile to iBike...". And if you ever get too many profiles to deal with, you can export an archive and delete them in iBike2.alback wrote:4. I would like to see the Profiles easier to create, switch around, save and apply in the ibike software. I don't find the software easy to apply Profiles to the data. Perhaps this is me, but I am usually quite good with software. I know there will be different clothing as I head out to ride, jacket, just a shirt, shell, rain gear, helmet that can affect my wind resistance. I would like to select my profile quickly before heading out the door.
You shouldn't have to remove any of your coastdowns--behind the scenes iBike2 weights the better profiles more so you don't have to figure it out. The feature for removing coastdowns is mostly to allow you to do more than one set of coastdowns in one outting. For example, if you want to calibrate 2 different sets of wheels, you can do both without going back to the computer in between. Do your coastdowns & 4 mi ride with one set, change the wheels, and then do a new set of coastdowns & 4 mi ride. Later at the computer, use the timestamp information to select which coastdowns to remove from the processing of each profile.alback wrote:5. Calibration - the ibike software should suggest which coast calibrations to drop so that the results are more realistic. At the moment I remove the highest and lowest numbers, but they might not be the correct values to discard, or it may not be enough.
Also, feel free to remove any coastdowns if there was a known problem with them and you can remember which ones they were. Maybe you had to touch the brakes, or you accidentally pedaled too soon, or some such problem.
Hmm, there are some opportunies to provide some more feedback on how well the profile came out. As it stands, the program checks for gross errors and prevents creating bad profiles.alback wrote:6. When I do a 4 mile return ride, the software could provide an error rating or ratio. It should point out if the elevations don't match from the turnaround point. It could supply possible suggestions for tweaks that would help direct me to achieve a correct adjustment. The most likely candidate would the level calibration, or poor wind reset, temperature when I started vs. 20 minutes later, or identify inconsistent movement/vibration in the unit mount.
There are some good comments in 1-3 also, but they are a matter for future hardware.
Travis
Re: Features I would like to see?
Thank you for the reply Travis, I found the coasts results vary rather widely. When I have about 6- 10 to work with, I delete the extreme values. This could be because I do not have cadence on my bike so unless I spot the change from 'fast' to coast immediately, or I accelerated too quickly to 32km and the momentum carries me through a crest in speed. For me, the only time I the ibike indicated a 'bad coast' I was on a rather bumpy paved road.You shouldn't have to remove any of your coastdowns--behind the scenes iBike2 weights the better profiles more so you don't have to figure it out. The feature for removing coastdowns is mostly to allow you to do more than one set of coastdowns in one outting. For example, if you want to calibrate 2 different sets of wheels, you can do both without going back to the computer in between. Do your coastdowns & 4 mi ride with one set, change the wheels, and then do a new set of coastdowns & 4 mi ride. Later at the computer, use the timestamp information to select which coastdowns to remove from the processing of each profile.
Also, feel free to remove any coastdowns if there was a known problem with them and you can remember which ones they were. Maybe you had to touch the brakes, or you accidentally pedaled too soon, or some such problem.
I hope you are able to implement some of the suggestions, I will try some of your suggestions on using my Profiles.
thanks for reading and responding,
Alan
Re: Features I would like to see?
I would like to see a sound signal added to the iBike, something like a watch tone. This sound signal could be used when doing coast downs to indicate you have reached coast speed. Your coasts would probably be more consistant and you can concentrate on rider position and the road rather than watching the road and the iBike for the coast to flash.
It could also be used for other settings of the iBike re-sets, wind, + alt and new ride.
Also to signal a transition uphill to downhill or minimum watts, heart zone, cadence zone etc. - Interval timer - pre set ride time etc.
Ofcourse this would need to be selectable (on or off) by the rider
AR
It could also be used for other settings of the iBike re-sets, wind, + alt and new ride.
Also to signal a transition uphill to downhill or minimum watts, heart zone, cadence zone etc. - Interval timer - pre set ride time etc.
Ofcourse this would need to be selectable (on or off) by the rider
AR
-
- Site Admin
- Posts: 392
- Joined: Fri Jan 11, 2008 8:52 am
- Location: Durham, NC
Re: Features I would like to see?
Not to argue that the sound signal wouldn't be useful, but I just wanted to point out that you don't have to worry about looking down at the iBike when starting coast-downs. After you get the "coast" instruction, you still have a couple of moments to get set in your position before the iBike starts recording coast-down data.alback wrote:I would like to see a sound signal added to the iBike, something like a watch tone. This sound signal could be used when doing coast downs to indicate you have reached coast speed. Your coasts would probably be more consistant and you can concentrate on rider position and the road rather than watching the road and the iBike for the coast to flash.
I would actually like a beep at the end of the coast-down. I hate it when I look down 1/2 m/hr too soon.
Re: Features I would like to see?
After two whole rides with the iBike, the thing I'd most like to see is a firmware upgrade that does a realtime temperature compensation on the wind offset. It seems to change quite a lot during a ride... and unlike the tilt there is really no good check on the wind. Even on an out-back or loop ride the actual avg wind can easily be non-zero. Mine was reading 4mph today when I finished the ride... in zero wind... which I guess means it got warmer... which makes sense, since that is what happened.
Travis... do you know if this is possible? Might not be exact (ie different units might have slightly different curves), but at least it should be better than nothing.
Travis... do you know if this is possible? Might not be exact (ie different units might have slightly different curves), but at least it should be better than nothing.
-
- Site Admin
- Posts: 392
- Joined: Fri Jan 11, 2008 8:52 am
- Location: Durham, NC
Re: Features I would like to see?
This is on our radar and has been for a long time. It is a matter of time, resources, and picking the battles. Another thing that factors in is that the 4 parties that have to coordinate in doing this live & work in MT, NC, and NY. No promises, but it is on the radar.rruff wrote:After two whole rides with the iBike, the thing I'd most like to see is a firmware upgrade that does a realtime temperature compensation on the wind offset. It seems to change quite a lot during a ride... and unlike the tilt there is really no good check on the wind. Even on an out-back or loop ride the actual avg wind can easily be non-zero. Mine was reading 4mph today when I finished the ride... in zero wind... which I guess means it got warmer... which makes sense, since that is what happened.
Travis... do you know if this is possible? Might not be exact (ie different units might have slightly different curves), but at least it should be better than nothing.
Re: Features I would like to see?
I don't know exactly what kind of temperature detector they have, but temperature detectors are typically the slowest of all detectors to react, slowest by, at times, an order of magnitude or two. Given this, it's likely any compensation of wind offset via feedback from the temp signal, or summat, will lag quite a bit behind the real changes.rruff wrote:After two whole rides with the iBike, the thing I'd most like to see is a firmware upgrade that does a realtime temperature compensation on the wind offset. It seems to change quite a lot during a ride... and unlike the tilt there is really no good check on the wind. Even on an out-back or loop ride the actual avg wind can easily be non-zero. Mine was reading 4mph today when I finished the ride... in zero wind... which I guess means it got warmer... which makes sense, since that is what happened.
Travis... do you know if this is possible? Might not be exact (ie different units might have slightly different curves), but at least it should be better than nothing.
Be an organ donor. When you're dead, you won't need 'em.
Re: Features I would like to see?
Since the temperture change rates we are looking at are typically a few degrees per hour, I'm not worried the that temperature sensor can't respond accurately within a second (like the other sensors can).alienator wrote:I don't know exactly what kind of temperature detector they have, but temperature detectors are typically the slowest of all detectors to react, slowest by, at times, an order of magnitude or two. Given this, it's likely any compensation of wind offset via feedback from the temp signal, or summat, will lag quite a bit behind the real changes.
Thanks for the info Travis! I know there is a lot to do, but I'm very impressed with how you guys have continuously improved the firmware, and the software for post processing. One of the early issues... the vibration sensitivity... seems to have been completely "solved" also. I did a long ride yesterday on some pretty rough roads, and there were zero spikes or dropouts.
Re: Features I would like to see?
One other thing I'd like to see. There is a place in the software for using a 2nd CdA. I'd like to see this be a part of the iBike's processing in realtime. With say three CdA regimes (normal, tucked, and climbing) the overall accuracy would be improved.
Re: Features I would like to see?
Along the lines of rrufs comment, I'd like to be able to use the results from a calibration in the other position(s), perhaps actually specify the profile to use below x speed (and y speed if multiple allowed) instead of just a 2nd CDA which in itself is very nice, btw!
I used the snapshot to determine that my drops position is about 1.25 times CDA of my Pro Design aero-bar position (normal) and it seems to work well. I think the tilt changes enough with each position that my setup would improve accuracy with using the actual profile.
Great features, any way we can get em!!!
Thanks,
Russ
I used the snapshot to determine that my drops position is about 1.25 times CDA of my Pro Design aero-bar position (normal) and it seems to work well. I think the tilt changes enough with each position that my setup would improve accuracy with using the actual profile.
Great features, any way we can get em!!!
Thanks,
Russ
Re: Features I would like to see?
I would like to be able to download all calibration and coast data to my computer and store it in a folder where I can retrieve it in iBike2 to review. Currently we can compare profiles and review each 4 mile ride, but not the coasts themselves. Perhaps this data is held in the "ibcd4m" files, I am not sure how complete they are as I cannot open them.
I would also like to be able to retrieve each coast and visualise it in a graph. This would help me understand more about my coasts and perhaps improve my consistency. I could review the 'fast' mode, the 'coast' mode and how I may have affected the result - acceleration, speed, elevation, slope, wind etc.
In IBike 2, we can save export profile files 'ibp' and calibrations are saved as "080601_cal_data.ibcd4m" but we can't review. Once the coasts are cleared from the iBike memory - the data from that calibration session is gone.
I read in another thread that the battery will last longer if data is cleared from the iBike unit? Not sure if this is correct. However it makes sense to upload every piece of data to the computer (and access it) rather than store it on the iBike.
I would also like to be able to retrieve each coast and visualise it in a graph. This would help me understand more about my coasts and perhaps improve my consistency. I could review the 'fast' mode, the 'coast' mode and how I may have affected the result - acceleration, speed, elevation, slope, wind etc.
In IBike 2, we can save export profile files 'ibp' and calibrations are saved as "080601_cal_data.ibcd4m" but we can't review. Once the coasts are cleared from the iBike memory - the data from that calibration session is gone.
I read in another thread that the battery will last longer if data is cleared from the iBike unit? Not sure if this is correct. However it makes sense to upload every piece of data to the computer (and access it) rather than store it on the iBike.
Re: Features I would like to see?
I was wondering why we couldn't access the coast-downs also. I guess they don't want us to see those files for some reason. So...
I decided to do my own coast-down rides and reduce the data. In other words I do the coast-downs with the iBike reading normally, then go into the csv file later and do a curve fit of each run to get CdA and Crr. I use Excel to do this. One thing I will say is that it is not so easy to get consistent CdA and Crr numbers from coast-downs. You can always adjust one variable up and the other down and still get a pretty good fit. What seems to work best is to do some high speed runs for CdA (from ~30 down to 15 mph) and some low speed runs for Crr (~10 down to 3 mph). Once I get a good Crr, I peg this for the CdA calc (ie it is not a variable), then go back and peg this new CdA in the Crr calc. Calm conditions are a really good idea, since gusts of any magnitude will cause inconsistencies... even though these are measured by the iBike and are accounted for. Also you must make sure that the wind offset stays close to zero... or track it and account for it later.
When I get some more practice at this I'll post more info...
I decided to do my own coast-down rides and reduce the data. In other words I do the coast-downs with the iBike reading normally, then go into the csv file later and do a curve fit of each run to get CdA and Crr. I use Excel to do this. One thing I will say is that it is not so easy to get consistent CdA and Crr numbers from coast-downs. You can always adjust one variable up and the other down and still get a pretty good fit. What seems to work best is to do some high speed runs for CdA (from ~30 down to 15 mph) and some low speed runs for Crr (~10 down to 3 mph). Once I get a good Crr, I peg this for the CdA calc (ie it is not a variable), then go back and peg this new CdA in the Crr calc. Calm conditions are a really good idea, since gusts of any magnitude will cause inconsistencies... even though these are measured by the iBike and are accounted for. Also you must make sure that the wind offset stays close to zero... or track it and account for it later.
When I get some more practice at this I'll post more info...
Re: Features I would like to see?
What is a curve fit and how is this done? Do you eliminate the profile from the iBike first?rruff wrote:I was wondering why we couldn't access the coast-downs also. I guess they don't want us to see those files for some reason. So...
I decided to do my own coast-down rides and reduce the data. In other words I do the coast-downs with the iBike reading normally, then go into the csv file later and do a curve fit of each run to get CdA and Crr. I use Excel to do this. One thing I will say is that it is not so easy to get consistent CdA and Crr numbers from coast-downs. You can always adjust one variable up and the other down and still get a pretty good fit. What seems to work best is to do some high speed runs for CdA (from ~30 down to 15 mph) and some low speed runs for Crr (~10 down to 3 mph). Once I get a good Crr, I peg this for the CdA calc (ie it is not a variable), then go back and peg this new CdA in the Crr calc. Calm conditions are a really good idea, since gusts of any magnitude will cause inconsistencies... even though these are measured by the iBike and are accounted for. Also you must make sure that the wind offset stays close to zero... or track it and account for it later.
When I get some more practice at this I'll post more info...
After doing coast downs on a good flat and smooth road, then the 4 mile on the same road, I thought I had the perfect calibration. However when I reviewed the results using these profiles, they weren't what I expected. The first problem I saw was the elevation was significantly different from start to finish when it should be identical. It was a clear day, so the barometer should not have changed much.
I did 2 sets of coasts and 4 mile runs immediately following each other, one in the drops, the other on the hoods. I found the Riding tilt at -.0343 in the hoods - the 'riding tilt' in the drops is a positive number 0.010. I can't understand why the numbers are so different unless the iBike moves with the carbon handlebars.
I also notice when I ride that as soon as I change to the drops, my watts rise although I know I am not putting forth any increased effort. You would think the watts should drop as I am more aero or speed will increase. Therefore I concluded that my handlebar mount must be twisting skyward ever so slightly as I change from hoods to drops. I checked this also by watching the slope as I make the change and it does change slightly, every time.
I have ordered a new IAero, and a Stem mount which should overcome this issue.
Both sets had lower Fric numbers than before probably due to the smooth surface. The problem when I applied these Profiles is the Watts average drops significantly from my other calibrations taken on road surface that is typical to my daily rides.
I look forward to your post using Excel to evaluate my calibration.
Alan
Re: Features I would like to see?
No, that is correct. The Iaero does not know that you are in a more aerodynamic position (unless you are using an ANT+ Sport power meter in conjunction). So, if you put out a constant wattage, and get more aero, your speed will go up. The Iaero only sees the increase in speed and thinks you must be pushing more wattage to reach that speed.alback wrote:
I also notice when I ride that as soon as I change to the drops, my watts rise although I know I am not putting forth any increased effort. You would think the watts should drop as I am more aero or speed will increase.
Alan
Boyd Johnson
http://www.boydcycling.com - high performance carbon wheels and accessories
http://www.boydcycling.com - high performance carbon wheels and accessories
Re: Features I would like to see?
No... I just do the runs with the iBike reading normally, then take the exported .csv file and paste the relevant data into a spreadsheet... where I perform a least-squares fit on the data using the equations of motion. I get the values of CdA and Crr that fit the data the best. I assume this is the same way the iBike evaluates the CDs, but it gives me more options on how I do the CDs. I can do both higher and lower speed ones for instance. CdA is totally dominant at high speeds, but you need low-speed data to get Crr.alback wrote:What is a curve fit and how is this done? Do you eliminate the profile from the iBike first?
100 ft of elevation change on a 4hr ride isn't unusual.After doing coast downs on a good flat and smooth road, then the 4 mile on the same road, I thought I had the perfect calibration. However when I reviewed the results using these profiles, they weren't what I expected. The first problem I saw was the elevation was significantly different from start to finish when it should be identical. It was a clear day, so the barometer should not have changed much.
The iBike certainly does change tilt depending on what you do to the bars. It will pivot with whatever it is attached to. If you push forward on the drops I can see this causing the iBike to tilt upward slightly, though I haven't tried that one. I guess everybody see a negative tilt on the hoods. Last time I got -.6% on the hoods.I did 2 sets of coasts and 4 mile runs immediately following each other, one in the drops, the other on the hoods. I found the Riding tilt at -.0343 in the hoods - the 'riding tilt' in the drops is a positive number 0.010. I can't understand why the numbers are so different unless the iBike moves with the carbon handlebars.
As coachboyd mentioned would be totally normal even if the tilt stayed the same, since the iBike assumes that your CdA is fixed.I also notice when I ride that as soon as I change to the drops, my watts rise although I know I am not putting forth any increased effort. You would think the watts should drop as I am more aero or speed will increase. Therefore I concluded that my handlebar mount must be twisting skyward ever so slightly as I change from hoods to drops. I checked this also by watching the slope as I make the change and it does change slightly, every time.
*If* the stem is the major source of flex, then a stem mount will be less effected if you put it close to the steerer... but not if it is close to the bars. I wouldn't expect a big difference anyway.I have ordered a new IAero, and a Stem mount which should overcome this issue.
Re: Features I would like to see?
Ooops on my above post....
My 1.25x CDA for 2nd position was hoods not drops, compared to Pro Design aero-bars... shows you how much
I ride in the 2nd position .
Russ
My 1.25x CDA for 2nd position was hoods not drops, compared to Pro Design aero-bars... shows you how much
I ride in the 2nd position .
Russ
Re: Features I would like to see?
Not to argue with you, I am new to the aero numbers and certainly relent to your experience. However from my coasts, my aero numbers are .331 on the hoods and .327 while riding in the drops. If I plug these aero numbers into other rides, the watts hardly change.coachboyd wrote:No, that is correct. The Iaero does not know that you are in a more aerodynamic position (unless you are using an ANT+ Sport power meter in conjunction). So, if you put out a constant wattage, and get more aero, your speed will go up. The Iaero only sees the increase in speed and thinks you must be pushing more wattage to reach that speed.alback wrote:
I also notice when I ride that as soon as I change to the drops, my watts rise although I know I am not putting forth any increased effort. You would think the watts should drop as I am more aero or speed will increase.
Alan
I really don't notice a speed increase yet the iBike increases watts by about 10%. If I refer to my Kinetic watts tables a 10% increase in watts is greater than 1 mph. I would see that kind of speed difference.
I believe the iBike determines higher watts from tilt increase, where it perceives I am travelling at the same speed and sloping up slightly. I see a change in tilt every time I change from hoods to drops or back. I say this since a couple of times, I would change only the right hand from the hood to the drops and the watts would change, if I changed the left there wasn't a change (ibike is mounted to the right of my stem).
The mount must be rock solid, but it also needs to be in a position where it has the least influences from the rider. The stem mount should be an improvement.
Re: Features I would like to see?
I have been a happy owner of the iBike for almost 2 months now (and upgraded to the IAero), but there are more features and tweaks that I would like to see.
IBike unit:
1. Show true watts during the ride as determined by iBike2 software.
2. Illuminated screen /switchable.
3. Screen up front, buttons at back and over the mount to reduce risk of throwing tilt off.
4. Switch profiles between bike 1 and bike 2 (sensors etc)
5. Selectable auto off vs always on so when I stop for a bar, the wireless or unit doesn't shut down. Or an selectable auto off so I can say stay up for 30 minutes before shutting down.
6. Selectable information on each screen.
7. Higher resolution screen, selectable fonts.
8. Sound alert - coasts, wireless drop, unit shutting off, excessive moisture etc.
9. USB mount for connection to the computer, as the iBike is always laying on its side etc. using the current handlebar mount style.
10. Stem mount has an opening for a plastic tie, unfortunately it interferes with the contact of the mount as it passes over the top of the stem between the mount and the stem. This raises the mount on the stem (by the thickness of the plastic tie) and causes it to rock at that point. An adjustment of design of the mount would correct this. Possibly a shoulder front and back of the mount where 2 straps would be more effective and not interfere with the contact of the mount to the stem.
Or make the mount with 2 screw down straps rather than the single it now uses. The increased length would also minimize any tendancy to rest slightly askew of centerline.
11. Adjustable angle to stem mount, rather than guessing low vs high, and to set the IBike at the best level/viewing angle.
12. O ring Gasket on mount, to reduce loosening of bayonnet from constant on/off the bike, and improve the seal against rain.
13. GPS option - not only for mapping, but as second power meter and improved calibration to elevation/tilt.
IBike2 Software:
1. Open more than one ride at a time on the screen, (vertical, tile, horizontal, select window etc)
2. Drag and drop to overlay one graph over another.
3. Use arrow keys to move incrementally along the graph, mouse is too jumpy.
4. Ability for user to select if ride was a loop, so elevation is adjusted to zero for improved tilt and power calibration.
5. Zoom in where the lineal cursor is left, current zoom always resets to start of the ride.
6. More training information from the ride information, similar to intensity factor, endurance, power peaks, cadence, heart etc. Optimum cadence to power.
7. Collective total, average, maximum of ride information. (graphs of same).
8. Download all ride data including calibration rides to save on the hard drive.
9. Improved Profile calibration where the software detects those coasts that are out of range.
10 Profile naming saving etc.
11. Abiiity to personalize all features on the iBike/iAero and those that cannot be adjusted due to the 18 window limit. ie Auto on off, Auto hill, LCD intensity, Selectable screens etc.
Umm, I might have repeated some from before.
Alan
IBike unit:
1. Show true watts during the ride as determined by iBike2 software.
2. Illuminated screen /switchable.
3. Screen up front, buttons at back and over the mount to reduce risk of throwing tilt off.
4. Switch profiles between bike 1 and bike 2 (sensors etc)
5. Selectable auto off vs always on so when I stop for a bar, the wireless or unit doesn't shut down. Or an selectable auto off so I can say stay up for 30 minutes before shutting down.
6. Selectable information on each screen.
7. Higher resolution screen, selectable fonts.
8. Sound alert - coasts, wireless drop, unit shutting off, excessive moisture etc.
9. USB mount for connection to the computer, as the iBike is always laying on its side etc. using the current handlebar mount style.
10. Stem mount has an opening for a plastic tie, unfortunately it interferes with the contact of the mount as it passes over the top of the stem between the mount and the stem. This raises the mount on the stem (by the thickness of the plastic tie) and causes it to rock at that point. An adjustment of design of the mount would correct this. Possibly a shoulder front and back of the mount where 2 straps would be more effective and not interfere with the contact of the mount to the stem.
Or make the mount with 2 screw down straps rather than the single it now uses. The increased length would also minimize any tendancy to rest slightly askew of centerline.
11. Adjustable angle to stem mount, rather than guessing low vs high, and to set the IBike at the best level/viewing angle.
12. O ring Gasket on mount, to reduce loosening of bayonnet from constant on/off the bike, and improve the seal against rain.
13. GPS option - not only for mapping, but as second power meter and improved calibration to elevation/tilt.
IBike2 Software:
1. Open more than one ride at a time on the screen, (vertical, tile, horizontal, select window etc)
2. Drag and drop to overlay one graph over another.
3. Use arrow keys to move incrementally along the graph, mouse is too jumpy.
4. Ability for user to select if ride was a loop, so elevation is adjusted to zero for improved tilt and power calibration.
5. Zoom in where the lineal cursor is left, current zoom always resets to start of the ride.
6. More training information from the ride information, similar to intensity factor, endurance, power peaks, cadence, heart etc. Optimum cadence to power.
7. Collective total, average, maximum of ride information. (graphs of same).
8. Download all ride data including calibration rides to save on the hard drive.
9. Improved Profile calibration where the software detects those coasts that are out of range.
10 Profile naming saving etc.
11. Abiiity to personalize all features on the iBike/iAero and those that cannot be adjusted due to the 18 window limit. ie Auto on off, Auto hill, LCD intensity, Selectable screens etc.
Umm, I might have repeated some from before.
Alan
Re: Features I would like to see?
A feature or change I would like to see on the ibike forum site is a change to the search engine. When you do a search for a word such as sensor, wireless, cadence, battery etc. it refuses to search as these are too commonly used words.
Ofcouse these words are commonly used, however the search engine should still provide a list of posts that contain typical subjects within the scope of iBike use.
Alan
Ofcouse these words are commonly used, however the search engine should still provide a list of posts that contain typical subjects within the scope of iBike use.
Alan
Re: Features I would like to see?
I agree with alback's iBike2 for Windows' suggestions 3, 4 & 5 (above).
In addition to those, I add...
GH1. There is a quirky behavior with window scroll bars. When you're scrolling the window (in zoomed-in mode), if your mouse strays too far from the scroll bar, you start selecting a region on screen (rather than moving the scroll bar).
GH2. Unless I'm all wet, it doesn't appear that annotations get stored with the ride. This is unfortunate. I've tried annotating a ride thinking it was storing the annotations in the ride. When I load up a new ride, the annotations stay with their location on the ride (and not with the ride). That detracts somewhat from the value of the annotations. I'd love to be able to add annotations, but if they don't get stored with the ride, it doesn't make much sense to take the time to draw them. I could see where a coach would annotate a ride and send a rider back comments from a screen shot, but that's not my usage. I'd like to annotate the rides for archive. I'd love to put in comments like "here's where I started the sprint -- and beat the guys to the edge of town" or (not so much fun) "this is the point where I ran out of gas and fell off the pack in shame."
At some level these feel like they might best be elevated each to their own post, but unless they gain traction, I'll leave the laundry list here.
My thanks to Travis for his hard work updating the tool.
In addition to those, I add...
GH1. There is a quirky behavior with window scroll bars. When you're scrolling the window (in zoomed-in mode), if your mouse strays too far from the scroll bar, you start selecting a region on screen (rather than moving the scroll bar).
GH2. Unless I'm all wet, it doesn't appear that annotations get stored with the ride. This is unfortunate. I've tried annotating a ride thinking it was storing the annotations in the ride. When I load up a new ride, the annotations stay with their location on the ride (and not with the ride). That detracts somewhat from the value of the annotations. I'd love to be able to add annotations, but if they don't get stored with the ride, it doesn't make much sense to take the time to draw them. I could see where a coach would annotate a ride and send a rider back comments from a screen shot, but that's not my usage. I'd like to annotate the rides for archive. I'd love to put in comments like "here's where I started the sprint -- and beat the guys to the edge of town" or (not so much fun) "this is the point where I ran out of gas and fell off the pack in shame."
At some level these feel like they might best be elevated each to their own post, but unless they gain traction, I'll leave the laundry list here.
My thanks to Travis for his hard work updating the tool.