Bumpkin
Registered user
Recently upgraded from a Quest1 to a 2720 and this morning got the 1st opportunity to try it out in earnest on a 110 mile trip to head office. Admittedly I was in the car but at least that gave me the opportunity to try out the traffic receiver.
Some of my observations below (firmware is latest - 7.20):
Lag in pseudo 3D
Although the pseudo 3D display is a bit of a gimmick I thought I'd give it a go, problem was the display seemed to lag my real position, depending on speed, by quite a way and sometimes delayed and then caught up. It seems that the processor isn't up to the task
I switched to 2D track up, what I'm used on the Quest and my preference anyway, and everything was much smoother and seemed spot on. Although very occasionally there was a momentary blank area ahead this never effected the cursor at my position.
My car does have an athermic windscreen but I'm using an external Holux antenna. The built in antenna does seem a lot more sensitive than on the Quest as it will work indoors away from a window so long as you give it time to acquire. Will be interesting to see if this problem is replicated on the bike when using the built in antenna.
On my return trip in a few days time I might try disabling the TTS voice and see if that has an effect on the screen lag
Traffic info
I have a GTM10 traffic receiver which I've installed in the car (not that relevant on the bike). I was impressed when it gave warning of several impending traffic delays of varying severity and tried to automatically divert around the worst (red). Just as a test I ignored them and there was nothing out of the ordinary by the time I got there. Admittedly it did warn me first about 40 miles away but still tried to divert when I was almost there. Obviously the system can only act on the data it receives and if that is delayed or inaccurate then it's not really worth having.
Announced routing via-points
Mentioned here before, very annoying that via-points added purely for the purposes of dictating the route (dragged and dropped using the routing tool in Mapsource) get announced. I now know about PONI Killer thanks to replies on the other thread but... come on Garmin, this needs addressing in a firmware update. PONI Killer requires recalculation be disabled which doesn't fit in well with my usage.
Otherwise very happy with the unit. The bike cradle arrived from GPS Warehouse the other day so I might get the chance to try it on the bike soon.
Some of my observations below (firmware is latest - 7.20):
Lag in pseudo 3D
Although the pseudo 3D display is a bit of a gimmick I thought I'd give it a go, problem was the display seemed to lag my real position, depending on speed, by quite a way and sometimes delayed and then caught up. It seems that the processor isn't up to the task
I switched to 2D track up, what I'm used on the Quest and my preference anyway, and everything was much smoother and seemed spot on. Although very occasionally there was a momentary blank area ahead this never effected the cursor at my position.My car does have an athermic windscreen but I'm using an external Holux antenna. The built in antenna does seem a lot more sensitive than on the Quest as it will work indoors away from a window so long as you give it time to acquire. Will be interesting to see if this problem is replicated on the bike when using the built in antenna.
On my return trip in a few days time I might try disabling the TTS voice and see if that has an effect on the screen lag
Traffic info
I have a GTM10 traffic receiver which I've installed in the car (not that relevant on the bike). I was impressed when it gave warning of several impending traffic delays of varying severity and tried to automatically divert around the worst (red). Just as a test I ignored them and there was nothing out of the ordinary by the time I got there. Admittedly it did warn me first about 40 miles away but still tried to divert when I was almost there. Obviously the system can only act on the data it receives and if that is delayed or inaccurate then it's not really worth having.
Announced routing via-points
Mentioned here before, very annoying that via-points added purely for the purposes of dictating the route (dragged and dropped using the routing tool in Mapsource) get announced. I now know about PONI Killer thanks to replies on the other thread but... come on Garmin, this needs addressing in a firmware update. PONI Killer requires recalculation be disabled which doesn't fit in well with my usage.
Otherwise very happy with the unit. The bike cradle arrived from GPS Warehouse the other day so I might get the chance to try it on the bike soon.
