Four errors on a 90 minute ride yesterday. Any hope for a fix for this? Maybe just say "RECONNECTING" rather than a modal error box. Seems kinda dangerous to keep having to take my hands off the bars to manually clear this error.
Four errors on a 90 minute ride yesterday. Any hope for a fix for this? Maybe just say "RECONNECTING" rather than a modal error box. Seems kinda dangerous to keep having to take my hands off the bars to manually clear this error.
It's definitely to do with RF interference which is fine, what's not fine is a modal error box that forces me to manually touch the device while I'm riding. It happens in San Francisco every…
In the past I've had the F:C error and Garmin indicated to me that it's a fault in the Varia and they replaced it for me. After that I haven't gotten the same error even once. If you get multiple…
I've got error 0:9 alway at the same location and on the same direction, no problem when I'm back, so I'm on the other side of the road.
It’s not a fault with the Radar or Edge . It is caused by interference from things like traffic light sensors and cars with proactive radar detectors.
Right, but is it safe to require users to take their hands off the bars to clear this error? The disconnect/reconnect is usually really brief. Maybe there should be a warning on the Varia RTL-515 box. "DO NOT USE NEAR MOTOR VEHICLES! IT IS NOT GARMIN'S FAULT IF YOU USE THE VEHICLE DETECTING SENSOR NEAR ACTUAL VEHICLES!"
Errors from yesterday's ride. Just a reminder, this is NOT a fault with any of Garmin's products. It's completely normal for a vehicle detecting sensor to error out every twenty minutes if you use it near actual vehicles. This is my fault using the Varia to detect vehicles.
No more dangerous than taking your hands off the handlebars to signal in to traffic. If you do find it dangerous maybe you shouldn't be riding a bike ! I ride some 8000 miles a year with the Edge 1050 and radar it isn't a bi g issue.
We're all agreeing with you. It makes sense for the car detecting sensor to error out when cars approach. This is expected behavior and it's not Garmin's fault.
In the past I've had the F:C error and Garmin indicated to me that it's a fault in the Varia and they replaced it for me. After that I haven't gotten the same error even once. If you get multiple F:C in a ride you should give Garmin a call. I agree with you the error message requiring a tap on the screen is annoying. I hope you'll get this resolved.
I get an occasional F:C and a continual stream of 0:9s on the Edge 1050. But Rogis and Garmin Support keep telling me I'm at fault for using the Varia to detect vehicles. Garmin already replaced my RTL-515 once.
I've got error 0:9 alway at the same location and on the same direction, no problem when I'm back, so I'm on the other side of the road.
It's definitely to do with RF interference which is fine, what's not fine is a modal error box that forces me to manually touch the device while I'm riding. It happens in San Francisco every 20 minutes or so. When I'm riding in Marin County, it happens less, but still occurs when vehicles with lane-assist are nearby.
It's completely fine if the device reconnects. The disruptions are all less than a second. What I keep telling Garmin Support is this...
(1) Just display a "Varia reconnecting" message when it's happening.
(2) If it's less than a second, probably don't even report it.
(3) if it's five seconds or more, there should be a more visible warning.
What's really, really annoying is having to clear this message, OVER AND OVER AND OVER AGAIN!
I've been screenshotting these errors for at least two years, but Garmin still adamantly refuses to fix the firmware because "THIS IS AN ERROR".
I'm agreeing, it IS an error, but I don't need to know about it unless I'm disconnected for more than 2-5 seconds.
Edit: I just realized you are having a temper tantrum. Comment removed.