[Hancockbs]

Hey, sorry I couldn’t make the HH, but happy to see I actually won a major award! Thanks for sponsoring LhasaCM. As I said in another thread, the cap actually made me ride farther than I otherwise would have, so when I hit 100 each week, I was pretty well toast. Congrats to my No Name Team 7 teammates as well!

[Hancockbs]

@Steve O 189232 wrote:

PI’m almost positive it’s not the device that does this, but Strava.

Probably a moot point but I know Garmin devices will show both total elapsed and moving time. Wahoo does as well (active and total).

[Hancockbs]

@jrenaut 189229 wrote:

I know some people ride to work, turn off the gps, then turn it on to ride home. Does this give them 8 hours in the saddle?

I’m fairly certain all devices differentiate between active riding (moving) and stopped time. I know Strava shows it that way.

[Hancockbs]

If you are father south, Danny, owner of Bull Run Bicycle in Manassass is a great guy and does very fairly priced, quality work.

[Hancockbs]

@chuxtr 189066 wrote:

We can make that part of the registration process and create #TeamAntiSocial.

Where we all ride our bikes separately together!

[Hancockbs]

@chuxtr 189048 wrote:

All,

The fact that there was as wide a spread in the results as there was means that a lot of people didn’t ride to their expected weekly mileage. I’m guessing that Team 7 rode to more (probably a lot more) than their expected weekly mileage. In the end, it all comes down to how many people on a team are able/willing to ride as many miles as possible.

The 100 mile cap actually made me ride farther than I would have otherwise. I expected to get 50-75 miles per week, but having the cap encouraged me to meet it every week, which I did. So, yes, I as one member of Team 7, did ride farther than anticipated.

[Hancockbs]

RCPT ‘temporary’ crowd control barriers at Kennedy Center were laying in the path today, effectively blocking the half nearest the river. Hopefully they got picked up at some point!

[Hancockbs]

Can’t make it this year, but this is a great ride to start the year off!

[Hancockbs]

Very odd sighting this morning on the ART. Sorry, I don;t carry my cell phone, so no picture from me. A car t-boned a utility pole, which might not be all that odd, except it occurred in a segregated bike lane here:

https://www.google.com/maps/@38.9054535,-76.9488311,214m/data=!3m1!1e3

The car was traveling south east when it hit the pole pretty hard. Somehow it got into the bike lane, either a 1/2 mile or so up the street where there is a crossing, or it jumped the 7″ curb. I saw no indication of the latter, so I assume it traveled a ways in the dedicated lane. Even more odd, just beyond the left turn, in the park, there was a large box, approximately 2’x2’x2′ that had been dropped in the middle of the train and broke open. It appeared to have old shoes, books, and VHS tapes as I rode by.

[Hancockbs]

@Mtansill 187569 wrote:

January 10th: Morning of the happy hour. Going around the corner on the quay at the Navy Yard. Overcompensated to avoid a jogger and the front tire got stuck in one of the tire-eating sidewalk cracks. Into the wrought iron bar fence I go. Sad. Bike is still perfectly rideable. Helmet scuffed but still perfectly integral. About 4 different bruises on the legs and one on the right shoulder.

I came very close to this late last year, but must have been heading the other direction, because I almost ended up in the river. Somehow managed to recover just before going over the edge. Those cracks are terrible!

[Hancockbs]

ART was largely clear from Capital St to Rt 50, except the slush pond at the National Parks Pavilion. North of Rt 50, there are a number of significant ice patches, some in the middle of turns. The path near RFK also had a couple of large ice patches.

[Hancockbs]

I found and installed a spoke magnet for the speed sensor this morning, which seems to have corrected the problem. The distance was ever so slightly off, 16.9 v 17.4 on Strava, but I can live with that. I still don’t agree with them setting the algorithm this way though.

[Hancockbs]

@josh 187026 wrote:

I’ve been too lazy to move my speed sensor from my lone cross wheelset to my other wheelset on my cross bike since the season ended, and I have a cadence sensor mounted on the crank. I haven’t had any of these issues (viewing rides on the Bolt itself, the Wahoo app, or whatever gets uploaded to Strava), so I wonder what the difference is. This is the Elemnt Bolt with the Wahoo sensor pack (cadence, speed, heart rate).

Interesting. So you do read and record cadence the way it is currently set up? My sensor is a Garmin ANT unit. The Bolt reads it fine, but perhaps being Garmin is part of the problem. I have one on both of my bikes and I didn’t want to go to the expense of replacing them both. Wahoo has offered to send me a Wahoo sensor.

[Hancockbs]

I played around with it enough to figure out the problem is related to the cadence/speed sensor. When I delete that sensor, it seems to record properly. I’ve always used it for cadence only and never installed the speed magnet, because I used GPS for speed and distance. This was never problem for my Garmin Edge units (500 and 800). It appears that Wahoo’s algorithm overrides GPS speed and distance with the speed sensor data. This makes zero sense to me since it ls has an inside/outside setting that disables the GPS function for use indoors. I’m waiting on Wahoo to reply, but it looks like my options are to install the speed sensor magnet or stop using the cadence sensor. Neither of these is rational t me. I bought a GPS unit to use GPS functions nd data, not to have it overridden by other data .

[Hancockbs]

@LhasaCM 187002 wrote:

I’d make sure you’re using the latest firmware and see if that helps.

However, looking at the Strava track: it doesn’t appear that it really missed anything so it doesn’t seem that the GPS is off – it’s just reporting the wrong distance traveled from A to B for the total of the ride. However, each segment looks like it was captured correctly (e.g., you did the 3.16 miles from the CCT Head to Dalecarlia in 13 minutes, but the overall ride shows that as only 1.3 miles). Does Strava give you the option to “Correct Distance?” when looking at it on the website? If so, does that “fix” the data issue for at least this ride, or does it not change things at all?

Also – how did the ride show up in the Wahoo software or on the device? Was it a 19 mile ride or just 7?

Updating the firmware is the first thing I did out of the box. I agree with your logic that it seems to have recorded the whole track, just not correctly. Right now, I don’t want to play with the starve data so it stays intact for trouble shooting. Wahoo has asked for and I provided the FIT file for analysis. We’ll see where that goes. It is annoying to me that their first response didn’t even bother to take the time to understand the problem.

[Author]

Posts