Jump to content
AVIC411.com

Opinion -- JVC KD-NX7000


Recommended Posts

  • 2 weeks later...
  • 2 weeks later...
  • 2 weeks later...

Definitely do a full review.

 

The only thing I don't care for on the NX7000 is every screenshot and video I've seen of it, the POI search is always an ABC keyboard and I greatly prefer QWERTY. On the other hand, it looks like you don't really have to type much to find a POI on the JVC since it has a constantly updating list on the right-hand side so maybe that makes up for it.

Link to post
Share on other sites
  • 2 weeks later...

Installed my NX7000 (UK version) into my Audi TT-S last week, full write-up with pictures is here on the TT-Talk forum (apologies if linking is a problem).

 

15082008355tu4.jpg

 

Had a Kenwood DNX-5220BT in there previously but IMO this is a better unit.

 

I think that the AV quality and funtionality of the JVC is top notch, but that the SatNav is a disappointment and really only good for occasional use. (But then how often do you really use your SatNav anyway?)

 

EDIT : Forgot to mention. You can connect a reversing cam and external AV to the unit for back seat viewing (comes with a remote too!). The parking brake can be grounded as a full bypass. If enabled, the system will auto-switch to the reversing cam when you put the car in reverse. Not sure if there is any other way to activate it as I dont have a cam installed (took me a while to realise why I had a blank screen when reversing!).

 

PS. Any help on accessing the POI database so that I can add my own categories and POIs greatfully recieved! All I have been able to discover so far is that the database sits on a WinCE 5/ Windows Automotive platform and *might* use a file called ADDR.ZDR ...!

Link to post
Share on other sites

OK, been using this unit more and getting more and more disappointed with the navigation.

 

The Sat Nav is complete rubbish. I've had to resort back to my old Nuvi for guidance. Finding a POI without a postcode is stupidly restrictive.

 

I've emailed a list of bugs to JVC :

 

1. The speed pulse is showing speeds that are 125% of the actual speed

 

2. When a GPS signal is lost, the unit gets very confused and shows the car driving off the road into fields or other roads that were nearby when the signal was lost. It keeps trying to recalculate and gives (very) incorrect guidance until it locks back onto the GPS signal. This issue may be related to 1 above - I have recalibrated twice so far but this keeps happening.

 

3. On occasion, the spoken guidance will tell me to "keep left" at junctions where the (correct) route is shown onscreen to keep right.

 

4. The software keeps showing "Saint Sampson" in search results and as local road names - there is no such place near me!

 

5. I would like to add new POI categories and POI's through the SD Card update feature.

 

6. The voice almost always speaks the road number rather than the road name. Most minor roads are not signposted with the number so the direction to "turn left onto the A307" is meaningless when both the signposts and the map onscreen both say "Portsmouth Road".

 

So far no response...

Link to post
Share on other sites
OK, been using this unit more and getting more and more disappointed with the navigation.

 

The Sat Nav is complete rubbish. I've had to resort back to my old Nuvi for guidance. Finding a POI without a postcode is stupidly restrictive.

 

I've emailed a list of bugs to JVC :

 

1. The speed pulse is showing speeds that are 125% of the actual speed

 

2. When a GPS signal is lost, the unit gets very confused and shows the car driving off the road into fields or other roads that were nearby when the signal was lost. It keeps trying to recalculate and gives (very) incorrect guidance until it locks back onto the GPS signal. This issue may be related to 1 above - I have recalibrated twice so far but this keeps happening.

 

3. On occasion, the spoken guidance will tell me to "keep left" at junctions where the (correct) route is shown onscreen to keep right.

 

4. The software keeps showing "Saint Sampson" in search results and as local road names - there is no such place near me!

 

5. I would like to add new POI categories and POI's through the SD Card update feature.

 

6. The voice almost always speaks the road number rather than the road name. Most minor roads are not signposted with the number so the direction to "turn left onto the A307" is meaningless when both the signposts and the map onscreen both say "Portsmouth Road".

 

So far no response...

 

Trick,

 

I'm sorry for you to see your bad experience on this unit, at least on the NAV side. But I'm thinking there are some major differences with the US version and the UK.

 

This is from your review from TT forum:

 

"The sat nav is OK, although nowhere near as good as the Kenwood's Garmin nav. Once calibrated, it uses the speed pulse and an internal 2D gyro to determine position if it loses the satellite signal. (it took about 400 miles to calibrate on mine, but worked perfectly fine in carparks etc even when calibrating). The nav uses TeleAtlas maps."

 

1st - The US version uses the NAVTEC maps not TELEAtlas. To me it can be the source of wrong text to speech indication from what the screen tells you.

 

2nd - the US version doesn't use the speed sensor. The unit totally rely on the SAT for that. This is where I can see your inaccuracies of your speed.

 

3td - I can't tell if or not the US version has the internal 2D gyro. I'm looking at all reviews, infos & docs and your the only one that mention that. Again this may be the cause of lost position when you loose SAT signal.

 

I'm looking at this unit too and before I purchase I want to make sure that the NAV is very good. So far, you are the only one that doesn't like the NAV and I'm thinking it may be related to a bad integration for the UK version.

 

Let us know.

 

Regards,

 

Charles

Link to post
Share on other sites

1 - The navteq/teleatlas maps are just two different databases. I would assume that the system interprets the data within the database in the same way when navigating, maybe with tweaks for Left Hand Drive vs RHD. No idea why JVC decided to use 2 different suppliers, as Navteq are just as good (if not better) as TeleAtlas over here.

 

IMO, the problem with TTS is (a) that the software cannot deal with complicated junctions and (B) is not smart enough to handle roads which are not completely straight. Obviously the map database will play a part too, but it's not like these two map providers are small companies...

 

Also, there are times when the TTS is unintellegable. I had a traffic alert which I couldn't understand and could find no way to get the unit to replay the audio alert. In the end I had to pull over & go through the menus to get to the traffic alerts screen and then read it. Not good.

 

2+3. Maybe, but then what is the calibration option for (page 52 of the US manual)? Does it just use the gyro I wonder? Also, page 122 mentions the speed signal. Would be very bizarre for them to leave these features out of the US version, especially as they are there to help when the GPS signal is weak or missing (i.e. in cities, tunnels, carparks, etc).

 

In my opinion, the navigation on this unit is very poor, especially when compared to dedicated units like the Nuvi or TomTom.

 

For example. I've tested it on familiar routes alongside the Nuvi and the JVC has a tendancy to choose longer routes. I think this is because the criteria it uses to calculate a route is more simplistic.

 

I set "home" as being where I actually park my car. This is not on a road, so everytime I choose to go "Home" I get a warning that it's not on the map. I would expect some intellegence to add the route to "home" to the map when I drive it the first time, and to use that route for future route calculations. No such luck...

 

Looking up a POI is a PITA as you have to specify CITY for everything (except a Zip code or phone number search). Why it can't just use your current location as a starting point is beyond me. And who searches for places based on phone number anyway? Great for stalkers maybe...

 

I'm also concerned about getting support and map updates for the unit. So far JVC's support in the UK consisted of a guy telling me that "we never get support calls for car audio, and I cannot find the manual for this unit on our system. Suggest you write a LETTER to JVC Customer Service at the following address...".

 

An email via their website took a week to be answered and then the answer was .. check our website for software updates.

 

If navigation is your priority I would personally pass over this unit and find something else. However, no harm in seeing if you can find one installed locally and arranging a demo.

Link to post
Share on other sites
1 - The navteq/teleatlas maps are just two different databases. I would assume that the system interprets the data within the database in the same way when navigating, maybe with tweaks for Left Hand Drive vs RHD. No idea why JVC decided to use 2 different suppliers, as Navteq are just as good (if not better) as TeleAtlas over here.

 

IMO, the problem with TTS is (a) that the software cannot deal with complicated junctions and (B) is not smart enough to handle roads which are not completely straight. Obviously the map database will play a part too, but it's not like these two map providers are small companies...

 

Also, there are times when the TTS is unintellegable. I had a traffic alert which I couldn't understand and could find no way to get the unit to replay the audio alert. In the end I had to pull over & go through the menus to get to the traffic alerts screen and then read it. Not good.

 

2+3. Maybe, but then what is the calibration option for (page 52 of the US manual)? Does it just use the gyro I wonder? Also, page 122 mentions the speed signal. Would be very bizarre for them to leave these features out of the US version, especially as they are there to help when the GPS signal is weak or missing (i.e. in cities, tunnels, carparks, etc).

 

In my opinion, the navigation on this unit is very poor, especially when compared to dedicated units like the Nuvi or TomTom.

 

For example. I've tested it on familiar routes alongside the Nuvi and the JVC has a tendancy to choose longer routes. I think this is because the criteria it uses to calculate a route is more simplistic.

 

I set "home" as being where I actually park my car. This is not on a road, so everytime I choose to go "Home" I get a warning that it's not on the map. I would expect some intellegence to add the route to "home" to the map when I drive it the first time, and to use that route for future route calculations. No such luck...

 

Looking up a POI is a PITA as you have to specify CITY for everything (except a Zip code or phone number search). Why it can't just use your current location as a starting point is beyond me. And who searches for places based on phone number anyway? Great for stalkers maybe...

 

I'm also concerned about getting support and map updates for the unit. So far JVC's support in the UK consisted of a guy telling me that "we never get support calls for car audio, and I cannot find the manual for this unit on our system. Suggest you write a LETTER to JVC Customer Service at the following address...".

 

An email via their website took a week to be answered and then the answer was .. check our website for software updates.

 

If navigation is your priority I would personally pass over this unit and find something else. However, no harm in seeing if you can find one installed locally and arranging a demo.

 

Trick, you are dead right when you say the nuvi calculates longer routes.In another post I basically said the same thing about my 360.What I do to shorten my routing is input the route in the system then drive the shortest route I know to my destination ignoring the nuvi then when I'm not sure of the proper turn I let the nuvi/Eclipse nav. take over.That way I save alot of time and miles driving and it's faster.

Link to post
Share on other sites

Actually, I'm saying that the JVC calculates longer routes. Here's a route that I had to travel frequently over the last couple of months as I was working in the area...

 

Nuvi 360T route = 10.1 miles :

 

nuviroute101hq3.jpg

 

JVC Route = 11.3 miles :

 

jvcroute113qy1.jpg

 

Real-life is about 30 mins extra on journey for this route, as it has high congestion for most of the day from Claygate > Tolworth, a long 20mph zone, and lots of stops for lights, crossings etc.

 

Funnily enough, Google agrees with JVC about the best route. All I can say from experience is that the Nuvi route is the best.

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...