
- Nuvi-265-Instruction-Delay-Factor
- 03-19-2010
![]() ![]() Re: Nuvi 265: Instruction Delay Factor?
| (PeteCresswell) | 03-19-2010 |
![]() Re: Nuvi 265: Instruction Delay Factor?
| Peter H. Coffin | 03-20-2010 |
![]() ![]() Re: Nuvi 265: Instruction Delay Factor?
| (PeteCresswell) | 03-20-2010 |
If you were Registered and logged in, you could reply and use other advanced thread options
My Nuvi 265 consistently gives instructions like "Turn right on
exit 285a" too late. They're almost concurrent with passing the
target exit.
Not a religious issue bc it give a warning a few tenths of a mile
earlier.
But I figure the thing has to know how fast it's traveling and
maybe there's a programmable delay factor that would move that
last instruction to take an exit back a second or two.
Or am I just wishing?
--
PeteCresswell
I've found the timing in the nuvi's way better than in my previous
2610. Nothing's perfect, of course, but it's rare for me to get the
instruction (from a 200, 205, 250w, 760 or 765t) too late - usually
it's just right.
wrote (with clarity & insight):
Per Wayne R.:
> but it's rare for me to get the
>instruction (from a 200, 205, 250w, 760 or 765t) too late - usually
>it's just right.
>instruction (from a 200, 205, 250w, 760 or 765t) too late - usually
>it's just right.
The last couple have been essentially concurrent with arriving at
the turnoff point.
Seems impossible that everybody is experiencing that - so I was
looking for some sort of user-settable parm.
--
PeteCresswell
With the 205 I find that the instructions on multi-exit roundabouts
can come too early, i.e., at the exit prior to the correct one
On Fri, 19 Mar 2010 18:00:41 -0400, (PeteCresswell) wrote:
> My Nuvi 265 consistently gives instructions like "Turn right on
> exit 285a" too late. They're almost concurrent with passing the
> target exit.
> Not a religious issue bc it give a warning a few tenths of a mile
> earlier.
> But I figure the thing has to know how fast it's traveling and
> maybe there's a programmable delay factor that would move that
> last instruction to take an exit back a second or two.
>
> Or am I just wishing?
> exit 285a" too late. They're almost concurrent with passing the
> target exit.
> Not a religious issue bc it give a warning a few tenths of a mile
> earlier.
> But I figure the thing has to know how fast it's traveling and
> maybe there's a programmable delay factor that would move that
> last instruction to take an exit back a second or two.
>
> Or am I just wishing?
In short, how soon it gives directions and what style and phrasing
depend a LOT on conditions.
Generally it's also given you those instructions when you've turned
onto the current leg of the trip ("Drive seventeen miles West on I74 to
Exit 285A on right"), about a minute before now ("In point six miles,
take exit 285A on right"), then at the ramp itself as close as it can
managed, to make sure to differentiate 285A (Mitchum Road northbound)
from 284E (which is 200 yards behind you now and goes to I374, and 285B,
which is 100 yards further on under Mitchum that ends up on Mitchum as
well, but southbound. I gather this because it did NOT say to "Take exit
285A on right, then turn left" or something, which ALSO tells a great
deal about what the interchange looks like (single ramp with choice of
directions at the bottom).
Oh, another thing that will help? Using the map display in 2D with
North Up seems to take a boatload less processing power to manage than
Track Up or 3D view.
--
Whenever you look at a beautiful woman,
always remember that somewhere, someone is tired of her.
- Best price on Nuvi 680?
- Garmin GPS
- 2008-04-30
- Nuvi 760 latest map update
- Garmin GPS
- 2012-02-22
- Nuvi 350: Loud buzzing from speaker
- Garmin GPS
- 2012-02-10
- nuvi 1450LMT On/Off Switch
- Garmin GPS
- 2012-02-08
- Garmin Nuvi 350
- Garmin GPS
- 2012-01-04
- Replacing battery - Nuvi 270
- Garmin GPS
- 2012-01-26









>exit 285a" too late. They're almost concurrent with passing the
>target exit.
>Not a religious issue bc it give a warning a few tenths of a mile
>earlier.
>But I figure the thing has to know how fast it's traveling and
>maybe there's a programmable delay factor that would move that
>last instruction to take an exit back a second or two.
>
>Or am I just wishing?