Mazda NB1 (JUST discussions here). See Tutorials for HowTo

I've also struggled with wonky routing. Sometimes, taking me down a main road in my small town it will ask me to go down a parallel service road for a couple of hundred metres when the road is completely clear (as it normally is). When I was in Portsmouth a fer days ago its routing back to my work was simply dreadful. I have not checked back yet with the original maps.

[Login or Register to remove this advertisement]

Do you have put ALL ? Replacement Files into the Mapfolder ? In your List i missing a "jvimg.ttd" with 65 MB Size and a "jvdat.ttd". Maybe thats important files


Edit :
oh, my mistake, these files already exist in the map yes

I worked out that these files relate to mapshare:
MapServerPatch.dat
PatchFilter.dat
ServerLineIndex.dat
ServerNameIndex.dat

I tried removing those, but routing was still erratic.

I also tried turning off IQ routing. This seems fix the erratic routing behaviour. It would be a shame not be able to use IQ routing though ��

Anyone know what the ARP_0_300 files are for?

UPDATE!

Ok, made some progress. Went through some process of elimination today to try work out this routing anomaly. I base my tests on entering the same destination on my original unpatched maps, and then updated patched maps and compare the route. The original maps were always generated fast and were logical. The patched maps took much longer to generate route, and routes were... Well... Crazy!! Believe me, ridiculous route rendering the whole thing unusable.

Test 1.
Wanted to eliminate the possibility my SD card was a problem. Duplicated original SD card to new SD card - tested fine with both generating same logical route.

Test 2.
Kept original maps but added latest speed cams patched with fast activate. Both tested fine with normal routing.

Test 3
Downloaded maps version 955.6746 from alternative source. Overwrote original files in Australia folder with these ones. (Note: There are about 10 additional files that are on the Mazda card that are not in 955.6746!) Patched with fast activate. Failed test, with the patched version coming up with a vastly different and unusable route.

Test 4
Tried renaming cphoneme.dat to cphonmlh.dat (as it is named on my original sdcard) test failed, route still unusable.

Test 5
Tried replacing all additional files that are not included in the 955.6746 maps. Overwrote all additional files from original sdcard with additional files on an original Mazda 955.6810 maps download. Test failed. No change.

Test 6
Tried removing the 3x ARP files that are on my original sdcard (also on 955.6810 genuine Mazda download. These files are NOT in the 955.6746 download.
arp_0_300_10_10_f.dat 13.3mb
arp_1_300_10_10_f.dat 11.4mb
arp_2_300_10_10_f.dat 2.3mb

SUCCESS! With these files removed, routing on the patched Maps is fast like the original, and comes up with the same route. Any insight into what these files are for and why they are affecting IQ routing?

I will obviously need to test this more thoroughly, but so far seems promising.

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

Ironically these files (as per other forum) are probably responsible for faster route planning but nothing for sure ...

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

There's no prob for NAV3 owner to clarify this - just plan a long route WITH these files (using original NAV3 map of course) and without them on same route. then compare times for each route planning.

I've deleted my equivalents (2000 in the name instead of 300) and I'll see what it does on my 15mi journey home tomorrow.

I have done some further comparisons. I'm lucky enough to have an copy of the 955 maps from a genuine mazda sdcard (955.6810) to compare with the 955.6746 files I have had to use due to available meta.

There are some discrepancies in files sizes between the two as listed below:
cline.dat
Mazda 955.6810 - 73.1mb
Generic 955.6746 - 70.6mb

cnode.dat
Mazda 955.6810 - 13.2mb
Generic 955.6746 - 13.1mb

jvimg.ttd
Mazda 955.6810 - 67.2mb
Generic 955.6746 - 28.5mb

tables.dat
Mazda 955.6810 - 606kb
Generic 955.6746 - 594kb

Some unusual discrepancies - and quite a substantial difference in jvimg.ttd

Seems logical that the integration of the ARP files could be screwed up by the differences in these core files. Obviously, in my case, the ideal solution would be if I had a valid meta for 955.6810 so I could use it in its entirety. The problems seem to come when using the ARP files from mazda sdcard (955 or earlier) with the map files of 955.6746

Quote:

Only the registered members can see the QUOTE Contents. Please Login OR Register.

If you are the owner of the map - why don't you extract meta.txt from it yourself?
If experienced any difficulties with it - please PM me.

On my journey home with arp_0_2000_10_10_f.dat, arp_1_2000_10_10_f.dat and arp_2_2000_10_10_f.dat deleted, it did not do anything stupid although I do not agree with its route. Replanning was much snappier. I'll try to do a better test soon but I'm looking to update to the 960 maps tonight first.

I am planning to use the Europe 960.7056 (just downloading the last piece now) but was also wondering about 960.7082 as both support cspeech and Android. I can only see a truck version of 7082. If there were a normal version, which one would be preferred or am I using completely the wrong one?