| dfutrell |
This may have been discussed before, but what does the Nav system used in calculating the estimated time enroute? Even the cheapest handhelds use some kind of algorithm based on average speed over some prior time period, but this system does not seem to notice whether you're driving 20mph or 100mph.
Does it plug in some constant speed (57.45mph?) instead of using the data it already has about how fast you're traveling?
If so, is there some hidden option that will allow me to change this?
Thanks! |
|
|
| msu79gt82 |
I do not know the answer to your question, but for us the estimate is amazingly accurate so I have never wondered about it.
For example we left Anniston, AL yesterday morning for home (Katy, TX) at ~9:00am - the Navi estimated travel time for the ~765 miles to be ~12 hours. We arrived home at ~9:00pm just as predicted:cool: |
|
|
| jatharp |
| Yesterday we were driving back from Greenbay Wisconsin to the Chicago area, Sometimes we were driving 80 mph and other times at a complete stop on the Interstate 94, It would keep recalculating the arrival time as we drove to compensate for the variable speeds. |
|
|
| Number 6 |
| you all must have a different nav system than ours... i bought our MDX in the bay area and drove it to houston, tx. the nav ETA was never even CLOSE. for example, san antonio is about a 3 hour drive from our house yet the nav said it was about 5 hours and change. same for the rest of the trip... WILDLY inaccurate... probably a factor 40% or so. |
|
|
| msu79gt82 |
quote:
Originally posted by jatharp
Yesterday we were driving back from Greenbay Wisconsin to the Chicago area, Sometimes we were driving 80 mph and other times at a complete stop on the Interstate 94, It would keep recalculating the arrival time as we drove to compensate for the variable speeds.
Outside of Nashville (on the way to Knoxville) we ran into a traffic slowdown (jack-knifed 18-wheeler on its side blocking all three lanes:3: ) where we crawled about 10 miles in 1.5 hours. The ETA went real high while we were stuck in traffic and then re-adjusted after we passed by on the shoulder. |
|
|
| cmdpm |
Number6,
i also have an '03 MDX with the nav.
the system initially gives the eta based on posted speeds of the roads but recalculates periodically based on
true speed/traffic/stops/etc.
maybe there are area of the country where the system is less accurate but i do not think that should be the case as the gps info should be processed by the system regardless.
maybe you should have the system checked by acura service.
good luck,
chris |
|
|
| jat3 |
You can actually 'reverse compute', once she displays the distance and estimated travel time.
But if I remember correctly, she made the computations based on 55mph, when we drove from ID to CA, and that's definitely not based on current driving speeds, as we were not mobile when I entered the destination. But she would do some 'corrections' along the way.
Oh, and this is on '03 Nav. |
|
|
| hockeyplayer |
| I just noticed that the 03 owners always say "she" when talking about the nav. I know that you can have a male voice as well.....does anyone use it?? |
|
|
| bluskryn29 |
quote:
Originally posted by hockeyplayer
I just noticed that the 03 owners always say "she" when talking about the nav. I know that you can have a male voice as well.....does anyone use it??
I think the default voice is female. Mine came with "her". I don't know but it just feels weird when a male voice is giving me directions. :8: I like the female voice better. But, that's just me.
My wife, on the other hand, likes "him" ... and usually doesn't switch it back to "her" after using the X. I hate it when she does that. |
|
|
| jat3 |
quote:
Originally posted by hockeyplayer
I just noticed that the 03 owners always say "she" when talking about the nav. I know that you can have a male voice as well.....does anyone use it??
we've actually tried getting directions from him and her, and we ended up sticking with her. |
|
|
| dfutrell |
After reading some of the replies to this thread, I decided to shut up and collect more data. I took the X on a longish trip over the weekend and had the opportunity to play with the Nav to try to see what was going on with the ETA function.
I found that if I set a destination 200 miles away while driving 70mpy. I set a destination right on the interstate where the speed limit was 65pmh). The ETA started out with some ridiculous estimate like 5 hours enroute, but would quickly adjust in the correct direction. However, it doesn't adjust NEARLY enough.
I checked it frequently, and it seems to allow for a maximum speed of something less that 50mph. It won't adjust the time downward (i.e., account for actual vehicle speed) beyond this even with driving steadily above 70mph for more than an hour.
I can't imagine that this is a problem with my particular vehicle; it appears to be designed this way...i.e, hopelessly pessimistic.
Overall, I'm very pleased with the Nav system, but this "feature" is completely worthless. It provides incorrect results even though it has all of the data available to provide a very accurate estimate. I can do better by looking at the distance remaining, the speedometer, and my watch. |
|
|
| pmsmith66 |
Interstate ETA experiences with my '03 have been exactly like yours. The ETA is based on a speed that is FAR lower than legal limits. I know others in this thread and elsewhere have had better luck but I don't understand how or why.
On the flip side, my metro-area driving ETA is very accurate...not that I personally give a rip about metro ETA. I typically know how long those trips take. |
|
|
|
