I upgraded my navi DVD in my 05TL from version 3.40 to 3.60 in November. The new disc does not recognize many of the roads in the DC area-- 66 inside the beltway, Rock Creek parkway.

The dealer (Radley) said that the software developer did this on purpose. Roads with time restrictions like HOV during rush hour are not used in routing. However, they said that you could "override" this by waiting until you are on the road to enter the destination.

This turns out not to be true. If I am on 66 it will not recognize it and it will give screwy directions-- teliing you to make a u turn or that you're on a different road. This is VERY annoying!

Does anyone else have this problem? Does anyone have the '07 navi in the DC area? Will it route you over roads like 66? I would not buy a TL with a navi that has limitations like that.

 

Have you tried the alternate routing methods? Other than "Direct Route" there are options for "Shortest Distance" and "Most Use of Freeways" that may give you varying results.

BTW, if you try to get directions from Mapquest, Yahoo Maps, or Google Maps and they match up with your navigation, it's not Acura's fault. They all use data provided by Navteq.com.

 

I have 3.5 and it has serious issues with 66. The dealer gave me the same BS answer about the HOV status and such, but completely ignore that if I went from point A (Arlington) to point B (Rockville) its directions sucked, but from Point B to Point A it had absolutely no issues taking 66. From what I can tell, at least in my case it just doesn't have the Glebe/Fairfax 66 ramps correct. But who knows.

 

Last month I was driving from my home in Kingstowne (Van Dorn exit on the Beltway) to a friend's place on Tennyson Street NW (off Oregon Avenue up past the Rock Creek Park golf course). The Navi initially wanted me to go I-395 to the Third Street Tunnel, up North Capitol Street to Missouri Avenue, then back across to Military Road to Oregon Avenue. Actually not a bad route during the daytime (would NEVER try that at night) and not one I would have thought of on my own. When I got across the 14th Street Bridge it suddenly, and for no apparent reason, changed its mind and wanted me to get off at Maine Avenue, loop around past the seafood market in Southwest, go up 17th to Connecticut, something screwy....I ignored it and tried the original route and it kept trying to get me to go back across town. Very bizarre stuff. Eventually, once I was on North Capitol Street, it shut up and just guided me.

I have not had the Rock Creek Parkway issue because I haven't been on that road in years. I did find one time that it won't guide you onto the RFK Stadium Access Road (the one down the end of the Southwest-Southeast Freeway) and will tell you that the destination was not found.

I can confirm what Radley said about restricted roads sometimes working if you are already on the road. If I turn on the Navi while in the express lanes on Shirley Highway, it does OK, but if I enter the express lanes while following a plotted route it becomes upset (although it cannot always tell whether I'm in the express lanes; it usually figures it out down at the US-1 interchange near Woodbridge and then tells me that no route can be found; I have to hit Menu and then select a routing option, and then it works fine). The part about not routing people on roads that are sometimes restricted or closed makes perfect sense, though. They're trying to avoid someone following the directions and then suing them, but on the other hand, isn't that what the nag screen is for?

I do seem to recall it routing me onto I-66 in Arlington once, though. I think I had "Maximize Freeways" turned on.

The other road that confuses the crap out of the Navi is I-270 in Maryland where it's a quad-carriageway design. We were going out to a place somewhere up the end of Montgomery Village Avenue once and at one point the Navi wanted me to go out into the local lanes WAY in advance of our exit, then move back into the express lanes. I ignored this part of the directions because I knew which exit I wanted and I only need the Navi for after we left the highway. (I've noticed that on I-395 it sometimes gets confused as to which carriageway I'm on, the local or express lanes....I usually drive home in the express lanes and take that slip ramp just south of Duke Street. When I'm in the express lanes, it thinks I'm not, then when I exit from them it thinks I entered them. Very weird stuff.)

I should note that aside from these issues, and aside from the obvious situations like the Springfield Interchange or Wilson Bridge where there are all new ramps and what-not, the Navi does pretty well in both Virginia and Maryland for me when I have it on. BTW, I have an '04 TL and I have not gotten a new DVD.

 

The current TL route agrees with the Google Map, but the older DVD (3.40) provides a route over 66, agreeing with Mapquest.

None of the route options work with the new DVD (3.60). The problem is the current disk (software) does not permit routing over roads that have restrictions based on time of day. The program doesn't know whether you are permitted on the road or there are restrictions.

My problem is there is no override. The technician at Radley said that if you were on the roadwhen you entered a destination it would override the restriction and route you accordingly. This made sense and would be an OK compromise, but it is not true. Under no conditions does the software with disc 3.60 ever recognize roads like Rock Creek Park or route 66.

 

I have an 07 TL with Ver 4.56a and I have to say I'm not impressed with the Navigation System at all! We bought the TL with Navi because my wife wanted it. We have a TomTom 300 we paid $300 for that does a better job than the $2K Navi System in the TL! Sorry to say, but I wish we had passed on the Navi and saved $2K and just kept using the TomTom.

The update DVD for the TomTom is only $59.00, it recognizes our home address (we've lived there since 2003, yet the Acura Navi still shows our street doesn't even exist on the map!). Finding destination is difficult as well. On the TomTom we can chose POI's along the route, and it will only list destinations a head of you listing from closest. The Acura Navi shows destination in other states before it shows the closest, and when you actually do get it to list the closest, it includes even the ones behind you. Well, if your in an unfamiliar area, this can lead to you doubleing back and loosing a lot of time on a trip!

Needless to say, Acura/Honda/Alpine really need to get their act together! This was a $2K mistake as far as I'm concerned, and will request an extensive test drive before I buy another vehicle with factory installed Navi! Thank God we keep our $300 TomTom in the car, it saves a lot of time and headaches!

 

I have the same problem - It only occured after I upgraded. I think it is an HOV issue handled badly. My guess is Navteq got complaints from people who got tickets following the Navi directions. Rather than put in an HOV option, they just made the roads un-routeable. Not an acceptable solution, but a solution. If you find an answer - please let me know.

 

Oh yes, its a problem with the Acura nav systems (04-05). I was able to get a refund from the disc manufacturer. This took multiple calls to ACS, and the Nav company. The explanation that the dealer gives is crap, as Honda nav systems recognize I66 just fine.

The tell tale sign is that I66 wasn't even included as a known road; I have so many "breadcrumbs" on the map from many back and forth trips on 66 where the vehicle position bounces all over the place. My hypothesis is that Navtec used a trucking database (No trucks inside the beltway) for the early versions of the Acura NAV.

If you live in the DC area and this bothers you, start making complaints; maybe someone at Acura will get a clue (and hopefully you can recover some cost of the overpriced disc).

BTW, my answer to the nav company/dealer stating that the HOV restriction caused the mapping issue, is simply supplying them a list of roads in other areas(i.e. HOV ramps in MD or 24 hour HOV routes in Atlanta) where the NAV maps away just fine. Also remind them of the other competitors vehicles that also recognize the major interstate just fine.

PM me if you want to discuss further; I have been on a mission to get someone at Acura to pay attention to these sort of oversights.

 

The last time we discussed this issue.....

https://acurazine.com/forums/car-parts-sale-361/fs-2001-2002-acura-cl-s-wheel-one-151494/

 

Sorry for bumping an old thread, but doesn anyone know if this has been fixed? I do a lot of travel in the DC area in my '04 TL, never upgraded. It's getting to the point where upgrading makes sense (3-4 years, there are enough new roads and POI's to make it worthwhile), but I'm sticking with the old version unless this has been resolved?

Anyone know?? thanks.

John

 

Last time I had my car in to the dealer & complained, he said it was a NAVTEQ issue. They do not program routes onto roads that have time restrictions. Rock Creek & 66 inside the beltway are two examples I've enountered. My 2005 disk does program these roads.

Two observations-- Google maps routes agree with the current NAVTEQ routes, Mapquest uses 66 for routes.
The dealers said that if I waited until I was on 66 to enter the destination the program would over-ride the restriction and use 66 to complete the trip. It does not.

 

I was in DC area last month on my way back to NY from VA. We stopped by a few places in metro DC (which looked like 2-3 year old residential developments) but the streets there were not on the nav map. Also, when we tried to get back on I-95, the navi gave crazy directions making us go in circles. Finally, we just followed the road signs instead of the nav directions and got on a new ramp to I-95. At that point, the navi showed that we were flying over blue bodies of water. Acura's nav database is outdated and we should let Acura know about this.

 

THanks. Guess I'll stick with the original.

John

 

Last month, I was driving from Tenelytown to RFK Stadium using Rock Creek Pkwy. Once I hit Rock Creek the NAV displayed a message along the lines of the road is unavailable. I forget what the actualy text stated.

 

The message was probably "Unable to complete route. Try again from a different starting location" or something like that... I think that's what our '07 says any time I drive onto 66 while there's a route entered. Then I have to wait a few minutes, cancel the route, and re-enter it. Really annoying. We've also lived on our street since 2000 (when the street was completed) and the nav doesn't have our street.

 

I have an '05 TL w/ the original disc. I travel through Rock Creek Park a lot and I've noticed two separate issues:

1. The nav just won't route you through the park. You need to be 3/4 through before it stops telling you to make a u-turn.
2. When you go south, towards watergate, the effect is that the nav cannot keep you on the road. You switch from in the park, to roads outside the park and back and forth. I believe the problem is that the data for the park has the elevations wrong. This screws up the calculations, and makes tracking very difficult.

I've also noticed both the "go into local lanes-then leave" local lanes on 270.

When going out to Dulles, the nav really can't tell if you are on the toll road or the airport road. Problem is, when you are on the airport road and it says the exit is a mile a head, but does not mention that you need to switch over to the local piece first. I ended up in the District once when I wasn't paying attention.

 

I haven't been on the forum in a while. I used the Navi last month to go to the Legg Mason tennis tournament near the Rock Creek Park golf course. As others have noted, it wouldn't route me on Rock Creek Parkway or Beach Drive. I expected this and drove that way anyway, and the funny thing is that where I had to make a left to bypass part of Beach Drive that is closed on Saturdays, the Navi suddenly picked right up and worked fine for the rest of the way (I believe this stretch is the one between Piney Branch Parkway and Military Road).

Going home, we started down 16th Street because I didn't really want to go down Beach Drive on a very dark night, but I got fed up with the traffic and decided to go through the park after all. The Navi didn't seem to have a problem that time when I started through that way, but then, I turned off the routing after going partway down Beach Drive because I didn't need it to get me home and because Ms1995hoo would have gotten annoyed when the Navi lady would start giving me directions that I would ignore.

 

That is the message I get if I'm going south in the express lanes on I-95 south and I hit the US-1 interchange at Woodbridge (I think it's Exit 161). The express lanes move left there to accommodate exit ramps, so the Navi suddenly realizes which lanes you're using and it balks. If I wait 30 seconds until I'm on the bridge over the Occoquan, I can hit "Menu" and reselect the same routing option and it will work fine. Strange stuff.