Garmin speed sensor problems.
Answered
I have the Garmin Speed Sensor 2. It is on the hub of the rear wheel. I have it connected to the K2 above the GPS in the sensor list. It is connect by ANT+ to the K2.
A few problems are noticeable
1. Auto wheel circumference is overestimated, which throws off speed and total distance numbers when uploaded to Strava. Annoying.
2. Auto pause is set to 0 mph, but the speed sensor takes 2-3 seconds to notice I am not moving. I do NOT have speed displayed as 3s avg or avg speed or anything like that. This never happens with my Garmin 530. I do not know how the auto pause work on that (GPS or speed set).
Both of these problems point to a problem with the K2 and the Garmin speed sensor. I don't know how often the K2 addresses the speed sensor to update the speed, but it seems like the connection is not great given the slow update of speed and overestimation of the wheel circumference. I figure that this speed sensor is pretty common given Garmin's market share. And this sensor works fine with my Edge 530. I put a new battery in the speed sensor to make sure it wasn't that.
I'm losing patience. It doesn't seem like anyone is listening. I commented on someone else's post that is having the same auto wheel circumference problem and the response is like "1-2% difference is normal"- NO it is NOT. Not in wheel circumference. My Garmin has it down to 9mm difference from a chart value and it is probably right as my tires are underinflated a little, so the circumference is likely less than printed. That is like 0.4% difference, almost an order of magnitude. Someone needs to look at this problem and take it seriously. Should I just unpair the sensor and use the GPS for speed and distance and auto pause?
It's not the FIT file or the algorithms. My K2 isn't playing well with the garmin speed sensor. And while I love the K2's screen, and mapping, TBT, phone connection, I need it to report and record data accurately first and foremost. I feel like I am beta testing...
-
@Gordon: We apologize for the issues you are facing with the inaccuracies in the recordings from your Garmin speed sensor. We would like to investigate the issue and see what is happening in the backend. I have created a support ticket requesting the FIT file of the relevant ride and the serial number of your Karoo 2. I request you follow-up on the ticket.
-
I was just searching the comments and saw this group. I left my old Cateye computer on my bike together with my new K2 and it was odd that I was consistently going ~0.5 mph faster as recorded on my K2 compared to the Cateye readout. I carefully calibrated the Cateye based on a wheel roll-out. The other day, I did a ride with a friend who was using a Garmin 530, and at the end of the ride, we had measured different mileage for the ride (the K2 was almost 10% greater than his Garmin readout). Now, I am thinking that I am experiencing the same situation as described above. I, too, have a Garmin speed sensor. thanks!
-
you could ride the k2 with deactivated speedsensor and compare it the garmin and you will see that without the use of the speedsensor everything is fine ... which is even more weird because gps data should be used to calibrate the speedsensor automaticly but obviously its not happing in the right way!
-
well I don't agree .. the weird thing at my k2 is that it automatically calculated the same circumference as the garmin just that the k2 shows the wrong speed and so the wrong distance ... the speed ist 2kph off ...the difference calculated was just 1mm .... anyway ... things like that should just work on the k2 without any manual settings ... on my edge it works
-
If I m on gps only at the K2 it shows the same speed as the Garmin which is using the Speedsensor... just if I connect the k2 to the same speed sensor ... speed is different even thought the automatic calculated wheelsize is the same on the k2 as on the garmin ... so it makes no sense to type in the wheelsize manually as it is shown/caculated correct on the k2 .. and I disconnected the speedsensor already and connected it again ... same issue ........... anyway ..I have another speedsensor and will check this one soon .
-
@Benno: I could enter it manually. I have many bikes. It is a pain to manually enter the wheel circumference every time. This is why it is nice to have an accurate auto wheel size, like I already enjoy on my Garmin.
The whole thing is moot anyways. I got tired of having to do more/forgive more/overlook more things to have a pretty screen. It got sent back months ago. Got tired of beta testing.
If things get fixed, I would come back and be a customer again. but clearly its still a problem months later.
Please sign in to leave a comment.
Comments
7 comments