Thread: Testing NTU maps on an old Nuvi 1340T

@asprin624
The initial problematic use of NTU in 11xx/12xx/3xx/14xx series has been discussed in scattered threads on the forum many years ago but it's not so easily found so thanks for succinctly bringing it together here in a discussion thread.

Although old, the 1xxx devices are versatile, light, robust and were sold in very large numbers. Therefore, many are still in use. It was the last highly popular series to be designed solely for NT map use (1xxx was released in 2009?), shortly before Garmin introduced NTU in parallel with NT mapping for Europe to cater specifically for Cyrillic based languages.

There certainly were initial problems with 1xxx using NTU in the past, particularly with address search and not limited to addresses with non-Latin characters either. However, at some point Garmin did a firmware update, probably in late 2012 when there was a flurry of updates from 5.90 to 6.20 in a short space of time (they withdrew V6.00 quickly too, due to some flaws). Although there's no specific explanatory note in the Change History, one of those hastily issued versions allowed at least partial compatibility with NTU maps. That fix mostly eliminated the address search errors. However, only fully compatible devices have this entry in their GarminDevice.xml: "<Name>UnicodeMaps</Name>". That's lacking in 1xxx and earlier series XMLs and only appears in the fully NTU compatible devices starting with nuvi 2xxx/3xxx from around 2010 onwards. That said, 1xxx devices with later firmware mostly will function properly using NTU maps and even ancillary files such as JCVs work ok.

I don't use NTU mapping "on the ground" as I'm not in Europe but welcome any discussion and posted experiences in this thread from members using NTU EU in 1xxx devices.

Super interesting to read this facts. are there any other series that were like this?