iBike Software Update 6.1.0

[mwirwin]

Hi to everyone at iBike

Happy Holidays! Hope everyone got what they wanted.

I just updated to 6.1.0 and found some glitches and then a I have a request/suggestion:

1. It erased all my training interval sets. I've recreated them and now have backed them. Is there an .INT folder some place, or is it just imbedded in the software until I export it? Can you create a dedicated folder to alleviated the export process (currently, I have to export them one at a time or import them one at a time).

2. While I was re-creating my training interval sets, I noticed that when I copied an interval and then dragged and dropped the new interval, the new interval loses the number sequence - no number is assigned to the dragged interval. So if I drag a new interval and drop it between interval 3 and 4, it ends up as interval 3, an interval with a blank sequence cell, and then interval 4.

3. I notice that the iBike ride files have switched from .csv format to a .ibr format. I actually like the .csv format because if something goes terribly wrong (Ex, cold weather or moisture may cause glitches for a short portion of my ride, for example), I can open up the .csv file and average out the numbers from surrounding data (as long as everything else remains relatively equal). So my question is: can you give the user the option of using .csv or .ibr formats?

Thanks for your help!

Mike

[Ute]

It appears that the new iBike file format (ibr) is not compatible with WKO+ software. I tried importing a file tonight without success. I imported the standard csv format for months without a problem. Does anyone else have this issue? Is there a work around?

[Ute]

OK. I jumped the gun a bit. I read the release notes. I exported the ibr file as a csv file. It imports into WKO+ just fine. One extra step now.

[texmurphy]

I am finding two issues with 6.1.0:

When merging with a .fit, sometimes the gps coordinates are invalid and 6.1.0 will Export the coordinates as NaN (for any output format: csv, tcx, gpx). This may be a failure of the device recording the .fit (Garmin Edge 500 v.260), however a NaN will result in conversion to Lat/Long=0,0 which will totally mess the route. Instead the trackpoint data output should not include the gps coordinates.
If i merge with a tcx converted by Garmin Training Center, GTC will not output the invalid coordinates (the <Position></Position> is not output to the tcx), and so there is not problem.

Example below from 6.1.0 csv output loaded to OpenOffice. First piece is a .fit merge example, 2nd is from merge with GTC output tcx from the same .fit, 3rd is the tcx output by GTC the same activity. It would appear the tcx merge just continues to use the last <Position> group found until a new coordinate group is encountered:

Code: Select all

39.42318	-76.65355	2011-12-28T09:39:10
39.42323	-76.65358	2011-12-28T09:39:11
39.42329	-76.6536	2011-12-28T09:39:12
39.42334	-76.65364	2011-12-28T09:39:13
NaN	NaN	2011-12-28T09:39:14
NaN	NaN	2011-12-28T09:39:15
NaN	NaN	2011-12-28T09:39:16
NaN	NaN	2011-12-28T09:39:17
39.42361	-76.65379	2011-12-28T09:39:18
39.42366	-76.65382	2011-12-28T09:39:19
39.42372	-76.65385	2011-12-28T09:39:20
39.42378	-76.65388	2011-12-28T09:39:21

Code: Select all

39.42273	-76.65321	2011-12-28T09:39:10
39.42277	-76.65326	2011-12-28T09:39:11
39.42282	-76.65331	2011-12-28T09:39:12
39.42286	-76.65336	2011-12-28T09:39:13
39.42291	-76.65341	2011-12-28T09:39:14
39.42296	-76.65345	2011-12-28T09:39:15
39.42302	-76.65348	2011-12-28T09:39:16
39.42307	-76.65351	2011-12-28T09:39:17
39.42313	-76.65354	2011-12-28T09:39:18
39.42318	-76.65356	2011-12-28T09:39:19
39.42324	-76.65358	2011-12-28T09:39:20
39.42329	-76.65361	2011-12-28T09:39:21
39.42335	-76.65364	2011-12-28T09:39:22
39.4234	-76.65367	2011-12-28T09:39:23
39.42345	-76.6537	2011-12-28T09:39:24
39.42351	-76.65373	2011-12-28T09:39:25
39.42356	-76.65376	2011-12-28T09:39:26
39.42361	-76.65379	2011-12-28T09:39:27
39.42367	-76.65382	2011-12-28T09:39:28
39.42373	-76.65385	2011-12-28T09:39:29
39.42378	-76.65388	2011-12-28T09:39:30

Code: Select all

         <Trackpoint>
            <Time>2011-12-28T14:39:24Z</Time>
            <Position>
              <LatitudeDegrees>39.4234264</LatitudeDegrees>
              <LongitudeDegrees>-76.6536843</LongitudeDegrees>
            </Position>
            <AltitudeMeters>92.0000000</AltitudeMeters>
            <DistanceMeters>6533.5698242</DistanceMeters>
            <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t">
              <Value>139</Value>
            </HeartRateBpm>
            <Cadence>74</Cadence>
            <Extensions>
              <TPX xmlns="http://www.garmin.com/xmlschemas/ActivityExtension/v2" CadenceSensor="Bike">
                <Speed>6.5630002</Speed>
                <Watts>173</Watts>
              </TPX>
            </Extensions>
          </Trackpoint>
          <Trackpoint>
            <Time>2011-12-28T14:39:25Z</Time>
            <AltitudeMeters>92.0000000</AltitudeMeters>
            <DistanceMeters>6544.8896484</DistanceMeters>
            <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t">
              <Value>139</Value>
            </HeartRateBpm>
            <Cadence>74</Cadence>
            <Extensions>
              <TPX xmlns="http://www.garmin.com/xmlschemas/ActivityExtension/v2" CadenceSensor="Bike">
                <Speed>6.6040001</Speed>
                <Watts>157</Watts>
              </TPX>
            </Extensions>
          </Trackpoint>
          <Trackpoint>
            <Time>2011-12-28T14:39:26Z</Time>
            <AltitudeMeters>92.2000000</AltitudeMeters>
            <DistanceMeters>6546.6997070</DistanceMeters>
            <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t">
              <Value>139</Value>
            </HeartRateBpm>
            <Cadence>74</Cadence>
            <Extensions>
              <TPX xmlns="http://www.garmin.com/xmlschemas/ActivityExtension/v2" CadenceSensor="Bike">
                <Speed>6.6040001</Speed>
                <Watts>157</Watts>
              </TPX>
            </Extensions>
          </Trackpoint>
          <Trackpoint>
            <Time>2011-12-28T14:39:27Z</Time>
            <Position>
              <LatitudeDegrees>39.4235849</LatitudeDegrees>
              <LongitudeDegrees>-76.6537784</LongitudeDegrees>
            </Position>
            <AltitudeMeters>92.2000000</AltitudeMeters>
            <DistanceMeters>6553.3198242</DistanceMeters>
            <HeartRateBpm xsi:type="HeartRateInBeatsPerMinute_t">
              <Value>139</Value>
            </HeartRateBpm>
            <Cadence>75</Cadence>
            <Extensions>
              <TPX xmlns="http://www.garmin.com/xmlschemas/ActivityExtension/v2" CadenceSensor="Bike">
                <Speed>6.6240005</Speed>
                <Watts>169</Watts>
              </TPX>
            </Extensions>
          </Trackpoint>

The above two sections, the first merged with a .fit and the second merged with the .fit converted to a tcx highlight another apparent issue. This is the same activity, yet the gps tracks show different trackpoints. Either 6.1.0 is interpolating the gps location in the .fit to match timing with my iAero (both devices set for 1 second recording) or else 6.1.0 is converting or rounding the binary .fit coordinates differently.
Loading of the .fit to SportTracks and Garmin result in identical gps trackpoints.

[racerfern]

WRT the above comments, I also see some NaN or 0,0 points once in a while with TCX files from a Garmin 705, although not nearly as many as some FIT files are recording. I manually remove them in Excel, however that is no longer possible in 6.1.0 because the invalid points get reinserted when you open the file in 6.1.0 again.

[travispape]

I am out of town this week in the mountains with only sporadic contact with the outside world and without a computer. I will take a look at these issues next week when I am back in the office. I already know that I will need to build a new release for the NaN issue with gps coordinates.

Also, keep in mind that when you merge data with you iBike data, the time base for the merged data must be synchronized to the iBike's. This does involve interpolating the merged data.

Travis

[lorduintah]

Travis -

I have not installed 6.1 based on these entries - but I thought this could be related or at least worth noting.

While using the TRAINER mode - after I have downloaded a ride into the software (in my case 6.0.2) - if I adjust the barometric pressure - then the power goes to NaN.

I realize that I have not gone anywhere and the altitude should not play a role in any values, but there seems to be some calculation cross-over from this. Ideally, the change to barometric pressure should still work without trashing the power values.

Tom

[mwirwin]

Thanks for additional info on other issues. Here are a couple more:

1. 6.1.0 erased my profiles in the iBike Software - luckily one of my profiles survived on the iBike Pro Unit.
2. The update also wiped out my trainer set up in the software. BTW - There is no way to get the trainer set up from the iBike. Many of the trainers have the same name - is there a way to track this on the iBike unit or download it from the unit?

[travispape]

Thanks for additional info on other issues. Here are a couple more:

1. 6.1.0 erased my profiles in the iBike Software - luckily one of my profiles survived on the iBike Pro Unit.
2. The update also wiped out my trainer set up in the software. BTW - There is no way to get the trainer set up from the iBike. Many of the trainers have the same name - is there a way to track this on the iBike unit or download it from the unit?

All of that information should be preserved, so it would be good to sort this out. And it might still be possible to recover the information. I'll email you.

[travispape]

OK. I jumped the gun a bit. I read the release notes. I exported the ibr file as a csv file. It imports into WKO+ just fine. One extra step now.

Hey guys, note that there is a keyboard shortcut for generating the CSV export: Control-E on Windows and Command-E on Mac. I know it's an extra step but at least it is a quick one.

By the way, iBike CSV and IBR files both contain all of the information contained in the other. In other words, if you export a ride file as an iBike CSV and then reopen it in the SW, it will not be missing anything compared to saving it as an IBR file. This might not always be the case, but we will give ample warning if it ever needs to change. In the mean time, it would be good to get used to using the IBR files and let us know if any issues come up with them.

Travis

[racerfern]

Here's the biggest issue I have:

I export a CSV file in order to make if available for uploading to Strava or SportTracks. Let's say there's a problem with a GPS point or a wind spike that didn't get fixed. I open the file in Excel, fix the error and save it then exit Excel. Now I have to open the file again in iBike because an iBike CSV export is not EXACTLY the same as an Excel version. Until now that hasn't been a problem, simply save as csv from iBike and all is well.

However with the release of 6.1.0 the csv file ends up getting the NaN put back in. So exporting as a csv just reintroduces the error. Catch 22 all over again...

[texmurphy]

Will the ibr format or toolkit be made available to outside developers?

[Morocco Mole]

OK. I jumped the gun a bit. I read the release notes. I exported the ibr file as a csv file. It imports into WKO+ just fine. One extra step now.

Hey guys, note that there is a keyboard shortcut for generating the CSV export: Control-E on Windows and Command-E on Mac. I know it's an extra step but at least it is a quick one.

By the way, iBike CSV and IBR files both contain all of the information contained in the other. In other words, if you export a ride file as an iBike CSV and then reopen it in the SW, it will not be missing anything compared to saving it as an IBR file. This might not always be the case, but we will give ample warning if it ever needs to change. In the mean time, it would be good to get used to using the IBR files and let us know if any issues come up with them.

Travis

Thanks for the shortcut Travis, although it would be nice to have a setting in preferences where you could set which default format you would like to save the file in. I understand the .ibr is more compact but the csv files are small anyway and disk is cheap. What other benefits\reasoning was there for changing to .ibr ?

[cdesmet]

Since the software update, I have problems with the ride analysis. Especially the screen with the road analysis does not react: I cannot 'accept' the analysis nor can I change the wind factor. the screen remains 'still' and only by using the escape and waiting for minutes will the screen disappear.

[vmi2uscg]

First, I think it is great that iBike improves software all the time and doesn't charge for it. More people ought to follow their lead.

In reference to the csv issue, I recommend that iBike post the last version of iBike software that did not have the new (more difficult) file format. Then, people can use which ever version they like! I lost my old version of the software due to a computer crash and would love to be able to save as csv.

Anyone of similar mindset? Maybe John H can weight in on this? I'll take easier use over 1% more accurate any day.

Thanks,

Brian

[RGA]

There is a new version that came out 6.1.2 that fixes several bugs ... take a look at it.