"This thread has had over 1200 views" so why are more people not jumping in to verify that 3.4 is the greatest update in the history of updates?
LOL
Guess we will see when my replacement comes. Who knows maybe my unit (and the others voicing dissatisfaction) is only defective on 3.4.. If that's the case I will certainly post that fact here. If it's not the case and the replacement acts in the same manner then it will go back for another and the process will be repeated until I either get a magical unit or the firmware is fixed, whichever comes 1st.. :D
Why does your retort not surprise me? :D
Glad to hear your trying another unit. Will make for a interesting data point.
There are currently 63 replies to this thread, nearly half of them are from one person, guess who?
Yawn..
Who cares who most of the replies are from? Another attempt to discredit someone? Why are you even posting in this thread since you have had, and continue to have, absolutely nothing relevant on the topic to say / add?
Anyway, to the block list with you as this type of behavior, based on your past post history, appears to be an ongoing thing with you for some very, very odd reason..
Most electronics manufacturers source various parts from different sources so I wonder if this may be the case with the RTL?
That might explain why some have issue on 3.4 and a few don't.
Could it be that the 4.3 update is only causing problems for the RTL that have a specific part that was sourced from a different manufacturer?
For instance:
RTL 1: Specific internal part(s) made by company A = Works fine RTL 2: The same part(s) except these were made by company B = Detection issues
I guess only Garmin would know that and I am positive they would not answer the Q..
This point crossed my mind also so we will see. I felt right along that there was something inherent in your total set up causing the detection issues with V/3.4 but I cannot get a handle on it so the replacement unit is a good step. By the way did you set up expedited shipping with Garmin where you pay up front and get a refund later.I just wish I could install my magic unit on your bike and see how it performs with your overall set up but alas.
What is the serial number of the RTL you are using now??? Mine is 48D025306. Would be interesting to know what the RTL serial number is of the the other poster or posters with detection issues with V3.4.
My setup is not this issue. If I were the only one having issues then I might agree and /or if the problem stretched across all versions leading up to 3.4 I'd agree..
I actually get outstanding performance from 3.0. so nailing down why some have issues on 3.4 and not on other versions is the trick.
The only logical explanation I can come up with is that the 3.4 update issues are caused by different internal parts and that only certain RTL's with that part are effected..
Might be easier if you get the SN# of the only other RTL that is properly functioning under 3.4. There are only 2 and you have one of them.. :p
Hopefully my replacement arrives soon and I'll compare it to the other. What would be even better is if Garmin fixes the issue with another update, ASAP.. :D
I stopped on the local bike path today to talk to a fellow cyclist. After our visit and ready to mount my bike I got a Varia radar beep. I looked around and saw 5 cyclists in a group approaching. I looked at my 520 and everyone was tracked and all five dots showed up and disappeared as they passed. The point is the Varia radar discriminating capabilities are pretty good considering the small detection surface areas compared to vehicles and the closeness in the group of the cyclists. Obviously, the cyclists were exceeding the threshold detection limit of 6 mph. Very impressive.
This does not directly address the issues with multiple vehicles misses other posters are seeing but demonstrates some of the capabilities that the Varia has are pretty darn good.
