Press "Enter" to skip to content

nuxx.net Posts

Moving from Ascent to rubiTrack

Since getting a GPS-based cycling computer and finding that Garmin’s offline analysis software, Training Center, is a bit lacking I’ve been using Ascent to log and aggregate my ride data. Ascent is okay, has some bugs, and seems to work but is otherwise abandoned. It also doesn’t work on the forthcoming OS X Mavericks, which means I need to find some other way to do offline ride analysis.

I enjoy tools such as Strava (and to some degree Garmin Connect), but I don’t like the idea of keeping my ride data on someone else’s system without an easy way to export it. Sure, I could back up the FIT files (raw files from the GPS unit), but that doesn’t include post-ride metadata that I’d add like the a name and general description of the route, or notes about the ride itself.

Stereo from the Reddit /r/bicycling IRC channel pointed me to rubiTrack, whose version 3 seems like it’ll be a good replacement for Ascent. There’s some claims of bugginess, and it’s lacking some features that Ascent had (eg: equipment maintenance log), but it otherwise seems good and is actively being developed. I’ve now switched over to it, so I wanted to give some details as to what it took to move my data over.

Here’s what I did:

  1. Buy rubiTrack, install the license.
  2. Launch Ascent.
  3. Show each activity as a separate row. (At the top of the Ascent window click the gear button and hold, then select Browser View, All Activities. Alternately, press Option-A / ⌥A.)
  4. Select a range of activities, perhaps a year at a time. Attempting to export too many at once will result in Ascent crashing.
  5. Right click in the Activity Browser (on the highlighted events) and select Export as tcx…. Give the export file an appropriate name.
  6. Repeat selection and export until all activities are exported.
  7. Quit Ascent.
  8. Launch rubiTrack, create a new set of data.
  9. Import each TCX file one at a time. Note that importing takes a while, and the rubiTrack UI doesn’t look like it is doing anything during the first import; be patient. During the subsequent imports an animation will display next to the Latest Import section.
  10. After importing, some of your activities may be listed as something other than Biking. By selecting multiple entries, right-clicking and picking Edit… you can change multiple activities to Biking all at once.
  11. Unfortunately, the TCX exports won’t contain either the name or equipment, so each activity will need to be edited to note these. Instead of a name, rubiTrack supports both a Location and Route, where Route (if present) is a subset of the location. For example, Stony Creek Metropark could have routes such as 6/12 Hour Race, Group Ride + Bonus, etc. Before beginning the renaming, go into Preferences and uncheck the Set similar locations automatically option in the General tab. Setting this automatically renames other activities in the same geographic area, which doesn’t work well if one regularly rides in a given area. Note that the options Import Category as: and Import “Name” as route on the Import tab do not help get names when importing from Ascent-exported TCX files.
  12. In Customize, Activity Types, Manage… delete other activities as needed so that only Biking, Racing, and Trainer exist with colors being Green, Blue, and Red, respectively. Set Biking to the default. Find appropriate icons in …/rubiTrack 3.app/Contents/Resources/ as atb_*.png. (Other people may want to keep these, but I wanted to reduce clutter… I can always add other activities if I decide to track them.)
  13. Define Heart Rate Zones as appropriate. More info on my HR zones can be found in this post, and I colored the zones the same as the LW Coaching chart.
  14. Define equipment via Window, Equipment. This, unfortunately, is not as useful as Ascent’s equipment log in that it can’t serve as a maintenance log. I have one entry for each bike and the trainer, with each bike or bike+trainer used with each activity. I may replace the maintenance log with a spreadsheet.
  15. Edit entries one at a time to have an appropriate location and activity type. Most of my Locations were copied from Ascent’s Title field. Autocomplete and the ability to select multiple entries at once and edit them en masse made this go quickly.
  16. Rides starting from home were tagged From Home and those which are part of certain group rides are tagged CRAMBA-IMBA Group Ride.
  17. After editing entries, the left side bar which groups rides by Location can be used to refine the listed locations. For example, I may have interchangeably used CRPT and Clinton River Park Trails, or RB and River Bends, depending on the ride. With a comprehensive listing of all locations used its easy to refine these for greater consistency.
  18. Play with the Options… on a given ride, in particular the Original device data and Use speed and distance data from device in chart options. Currently, with my Edge 500 and 510 data, this is a bit problematic. With Original device data checked the distance seems to reflect the distance that the unit showed (from the wheel sensor), but the Total Duration and Active Duration match and are short. Without this checked the Total Duration and Active Duration vary appropriately, illustrating the amount of time stopped, but the distance seems to be based on GPS and thus under recorded. This has been reported here and I hope that it’s fixed soon.

Other than the issue mentioned in #18, I’m pretty happy with rubiTrack. I’m particularly fond of its use of OpenStreetMap data, as this means that the trails that I’ve mapped in OSM (eg: Addison Oaks) have their routes right in my preferred analysis software. This is probably going to make me map even more stuff…

It’s also great for viewing things like heart rate data, where stops were made, high elevation points along the way, and also comparing rides. The author seems actively engaged in making it better, it should work with 10.9, is much faster to save, and is much nicer for answering questions like “How many races have I done in X year?” or “How many times did I ride at Stony Creek?”.

1 Comment

Clement X’Plor USH 120 TPI

On Joe Seidl’s recommendation I picked up a set of Clement X’Plor USH for the Jamis Nova. While I’d originally intended to get the 60 TPI version, QBP being out of stock and a convenient find (just in time for a planned long ride) resulted in my getting a 120 TPI set. I’m not sure how much the difference matters, but I don’t mind the more supple casing even if it came at a slightly higher price.

At 80 PSI on the 622-14 Ritchey Silhouette Comp rims that came with the bike the casing measures 32mm wide and to the outer edge of the knobs it measures just about 35mm. The solid center and file tread sides of this tire really appeals to me, as it looks good for mixed pavement / dirt road / rail trail riding; exactly what I intend the Jamis to be used for.

Using the charts in Frank Bertro’s article All About Tire Inflation (mirror) I put the pressure at 65 PSI and went for a test ride from home up to 51 North in Lake Orion, meeting some friends part way. Since I was early to meeting Erik and Kristi in Rochester I poked around Bloomer for a bit, including riding some low/flat parts of the mountain bike route. This gave me the chance to try these tires out on pavement, smooth crushed limestone, looser gravel, sand, light mud, and some damp clay. On each of these surfaces this tire behaved exactly as it felt like it should, with no surprises, and much nicer than the Serfas Seca did when I tried taking it off road at Island Lake.

Thus far I’m really happy with this tire. It seems to be a great all-around tire for this area, and as long as it keeps performing as it did tonight I’ll be happy. There’s still the question of longevity, but that’ll clearly take some time.

Leave a Comment

Bike Fit Tweak Before and After

Earlier this week I visited Fraser Bicycle and Fitness where Melissa and Chris put me and my bike on a trainer and gave me a bunch of help and advice on basic bike fit issues on the 2007 Jamis Nova that I picked up a couple weeks ago. This is the first drop bar bike I’ve had, so I really wasn’t sure where to start for getting fit right. Thanks to them I’m now in a position on the bike where I’m much more comfortable, something that’ll be pretty important if I ride this bike frequently.

By moving the saddle 5mm forward, switching to a 75mm 11° stem (from a 100mm 6°), and adjusting the bar and lever position they were able to put me in a much better position on the bike. They also gave me suggestions for how to position the levers and bars, including some nifty tricks such as ensuring the axle is obscured by the bar while on the hoods, and nose being over the bar while in the drops. Additional testing on the trainer at home and on a ride around the neighborhood showed that it’s definitely more comfortable, and thus far I don’t notice a difference in steering. (Steering becomes twitchier with a reduction in distance between hands and the steerer tube, but I don’t seem to notice this, likely because I find road/CX bikes to be twitchy anyway compared to my mountain bikes.)

The animated GIF above is intended to show the differing position on the bike before and after fit, and I think it does a decent job, even though I’m probably not as settled into a riding position in the Fixed image as I would be while out on a longer ride. I’m more upright, supporting myself a bit less on my arms, and my forearm-to-hand position is more of a straight line.

While I didn’t get a full bike fit, I was in the room where they do such fittings, and Fraser’s setup is really impressive. They’ve got everything from a full Retül system that allows bar/saddle/pedals to be positioned every which way to a motion capture system to see exactly what is going on when one’s pedaling. It’s a really serious setup. Their full bicycle fits are designed to get everything as ideal as possible.

4 Comments

Oyster Mushrooms!

Earlier this year I mentioned that oyster mushrooms were starting to grown on the Cascadia Mushrooms kit that Danielle and I had received. They’ve been growing in weird spurts, with extended periods of nothingness, then some small starts that died off. For some reason they recently started growing nicely again, and I was able to harvest this cluster which I used to make some dinner.

I didn’t cook the mushrooms for long enough, but they still tasted quite nice. Hopefully another cluster like this will grown soon and I can cook them down a bit more properly.

Leave a Comment

Heyco 2590 for Bicycle Accessory Holes

Along with replacing the rim strips and tubes on my fatbike to save weight I decided to see if I could find a suitable hole filler for accessory mount (eg: water bottle, rack, etc – photo) holes on the bike frame. Some digging turned up Heyco Dome Plugs Part No. 2590 (PDF) and they are a perfect fit. Ordered from Mouser (Part # 836-2950 – photo) they cost $0.13/ea ($0.09/ea in 100 piece quantities) and snap snugly into mount holes. Removing them may be a bit of a pain, but a pick or serrated needle nose pliers will likely pull them right out.

By replacing 13 of the cap head stainless steel screws on my fatbike I cut 45g off of the bike’s mass. (The screws were 46g, and 15 of the dome plugs registered as 1g on my scale.)

While I’m not particularly concerned about such a small savings on the fatbike, I’m glad to find a cost effective item which can be used to fill accessory mount holes and prevent extra snow and water and such from getting in. I think they also look a bit nicer than simply leaving the holes empty, and don’t have the add-lots-of-shiny-stuff look (photo) that filling the holes with screws gives.

2 Comments

Bye Bye, Rockhopper

My first real mountain bike, purchased at the very end of 2007 and heavily modified since, was sold this evening. After purchasing the Jamis Nova from Ryan I realized it was a better solution to every need that I kept the Specialized around for, so it was time to sell it. A posting to Craigslist on Monday returned a few hits, and this evening I met up with someone at River Bends who is really excited to get back into mountain bike riding, fit nicely on the bike, and purchased it from me. This Specialized Rockhopper is a very nice bike that saw me through a lot of learning, but I no longer had a need for it. Due to the memory-based object attachment which most of us are familiar with I didn’t want to part with it, but it was for the best.

The person who purchased the bike lives very close to River Bends, and as he and I were talking I learned that he’s regularly out on the trails at River Bends, hasn’t had a mountain bike in a couple years, and is planning on regularly riding it there. When passing through one short, dry section of trail (it’s pretty muddy out there in general) I got the feeling that he really, really missed riding on dirt. It’s some of these very same trails that first made me realize that I liked riding bicycles on single track; exploring the casually-created segments that were eventually incorporated into an official mountain bike route.

In the midst of the project to build trails at River Bends I never imagined their draw would foster the sale of the bike which first got me interested in trails themselves, but it’s really nice to see things come full circle. It feels very complete.

Leave a Comment

2007 Jamis Nova

This past weekend I picked up a cyclocross bike from my friend Ryan. He’d had this bike for a while, but it was a bit small for him and he’d been wanting to sell it. He heard that I’d been looking for a road-ish bike, and one thing led to another and we met at the Tree Farm for a ride and I went home with a new-to-me bike, an almost stock 2007 Jamis Nova.

That afternoon I picked up a TIMBUK2 Bike Seat Pack XT to hold tools, a Topeak Road MasterBlaster frame pump, added a Garmin mount, fitted my preferred saddle and pedals, and set out for a ride on the Macomb Orchard Trail. It was this ride that really sold me on the bike. Before this I had very little experience with drop bars and bikes with smooth tires, but 23 miles of pavement showed me that this kind of riding can be quite a bit of fun and that I’m extremely glad Ryan sold me this bike.

Over the following two evenings I set about getting familiar with the bike, and ended up giving it a very detailed cleaning, replacing the derailleur housing and cables, and getting everything set up for me. I’ve still got some playing (and a lot of reading) to do with the bar position, but for now I think I’ve got it somewhere that’s comfortable.

As mentioned before, this bike is almost completely stock, with the exception of the tires and front shift/brake lever. At one point the front lever broke, and the shop gave the option of either waiting for a new 105-level component (to match the rest of the bike) to come in, or having it immediately replaced with a Tiagra-level part. The Tiagra part was chosen, so the levers don’t match. The feel for the two is very similar with the hoods being practically identical, and being the front shifter any potential difficulties with a lower-level part don’t concern me.

I’m planning on swapping tires to some Clement X’Plor USH tires that Joe Seidl recommended to me, and whose 35mm width, solid center and file tread sides look quite appealing. While I opted for the cheaper 60 TPI version, I hope (and based on reviews suspect) that these’ll do nicely for mixed pavement and gravel road riding.

Everything is now set up as I want it for a longer ride on the bike, so I’m hoping to get out on a 30-50 mile ride before the weekend is out. If things go as planned, I may try to fit this in Friday evening along with picking up the tires from Trail’s Edge. It looks like I’ll be able to ride from downtown Milford out to Island Lake by way of Kensington Metropark. This might be worth doing, should time permit…

If you’d like to see more photos of this new bike, they can be found here: Jamis Nova.

Leave a Comment

Removing 1.3 Pounds of Rotating Weight

Spending less than $30 I was able to remove 1.3 pounds of rotating weight from my fatbike. How? By replacing the Surly Toob and Rim Strip with lighter weight parts. Namely, a Kenda-manufactured Q-Tubes Superlight 26 x 2.4-2.75″ tube and some 2.25″ wide red polyester ribbon (photo). I decided to try these parts out after reading a number of forum threads about fatbike weight savings and discussing it with some local friends. This technique/setup is pretty well tested and should work out nicely.

I simply removed the heavier parts, looped some ribbon snugly over the rim holding it in place with a bit of gaffer tape (photo), and put the wheels back together with the Superlights. The significantly lighter tubes filled the tires evenly and the woven ribbon seems to be doing a fine job keeping the tube away from the nipples and edges of the holes in the rims.

For now I don’t see any reason why these lighter weight parts shouldn’t hold up as well as the originals. I suspect that having lighter weight wheels (especially with the weight savings coming from the outer edge) will be noticeable as well, particularly when accelerating.

Weight (or mass) for each of the components involved in this can be seen here:

Actual Original New Delta
R. Wheel 9.20 lb 8.56 lb 0.64 lb
F. Wheel 7.60 lb 6.94 g 0.66 lb
R. Tube 464 g 227 g 237 g
F. Tube 460 g 229 g 231 g
R. Strip 83 g 11 g 72 g
F. Strip 84 g 11 g 73 g

Calculations based on the mass of the strips and tubes showed that there should have been slightly more savings (0.68 lb and 0.67 pounds for rear and front wheels, respectively), but I figure the difference is from the air put into the wheels. Using the rear wheel as an example Wolfram Alpha shows 36g (~0.4 lb) of air as having 28.2L of volume, which sounds about right, as I had the rear wheel inflated to ~30 PSI (to ensure the tire gets seated on the bead) when putting it on the scale.

Update (May 26, 2014): I experienced my first failure of this system. I’ll keep an eye on it, but there’ll be a little more maintenance required in the future because these tubes appear to fail early on due to exposure or overstreaching. Read about this here.

Leave a Comment

Eight Grams of Security

When riding at Yankee Springs two weekends ago I thought I identified the cause of some bike noise on my Salsa El Mariachi Ti: the rear skewer. After trying out an old Shimano XT skewer from another bike during some local rides it held solid, and Lumberjack seems to have proven it out. I was subsequently able to acquire a new Shimano M770 skewer (so the old one can go back on the old bike) and I’ll use this one instead of the Salsa Flip-Off that came on the bike. This comes at a whopping eight gram penalty (55g for the Salsa Flip-Off vs. 63g for the Shimano M770), which I think is worth it for a more secure rear skewer.

I’m actually quite surprised that I had difficulties with the Salsa skewer as the other two that I own have been very solid. I suspect it has a bit to do with the way the rear triangle flexes, so maybe the different cam design of the Shimano (which I believe to be easier to get very tight) is what’s needed. A through-axle would be another good way to sidestep this, but I don’t have a TA-compatible rear wheel, so I can’t do that yet…

Leave a Comment

Garmin Edge 500 Time Issues during Lumberjack 100

After getting back home from completing Lumberjack 100 I was excited to review the logged data from my Garmin Edge 500 bike computer. A few times during the ride the unit lost GPS signal, but as I’ve had this happen on other rides without issue I didn’t pay it much attention. Unfortunately, it looks like this time the data really went odd. After poking with the data and attempting to correct it in Ascent I downloaded Fit File Repair Tool to see what it could tell me.

As shown in the screenshot above (click to embiggen), roughly 15.52 miles in, at 44.2119°N 86.1295°W, just beyond the Steinberg Road crossing in Road Monkey during my first lap (map here), the recorded time suddenly jumped from June 15, 2013 to October 19, 2019. This explains the strange duration I’d been seeing in analysis software, with everything from Ascent and Strava both reporting an elapsed time of around 55619:03:11, the length of a ride which I don’t quite think the Edge 500’s battery would endure, but which matches the 6-some year offset. Weirdly, Garmin Connect doesn’t show the issue (link), almost as if they filter out this problem.

When this issue occurred my Garmin was running firmware v3.00, something which I was hesitant to change soon before the race. Since the changelog to v3.20 only lists two minor changes which aren’t useful for me (power meter serial number display and a change to support manufacturing) I didn’t see a good reason to rush to upgrade. It’d also worked otherwise well for long rides, so I didn’t anticipate any problems. I upgraded the unit to v3.20 today and I’ll see if similar problems arise, but I can’t imagine I’ll be doing that length of ride any time soon, so it’ll be hard to get an equivalent test.

If any of you wish to review this damaged FIT file from Lumberjack 100 it can be found here: svigneau_2013_lumberjack100.fit.

Leave a Comment