Also, here is some detailed information about Insight Map Creator with supported Navico products and legacy devices no longer supported for the purposes of experimentation.
Summary of at5 support:
Version 6 is used for really old devices.
Starting from AT5 Version 7, InfoBox on point features and raster is supported, not no unit ever used the raster.
AT5 version 10 was the officially supported raster display units.
Starting from AT5 Version 12, Unicode support, polygon elevation/percentage range, elevation on point
features and percentage on any feature is supported. Version 12 also supports submeter data storage in at5.
Below is everything we have quick access to with legacy devices. This is something I am passing along for your reference.
DISCLAIMER:
Hence the information below is provided for reference only as no support will be given. If you choose to make mapping products for these legacy products, you are allowed to but we will not be able to assist in unit or mapping support except for what little information we already have a seen below. Ultimately you will be responsible for support of these legacy products if you decide to supply a map card for it.
OLDER MAPPING TOOLS WITH KNOWN COMPATIBILITY ISSUES ON SUPPORTED UNITS
The LCMMapEdit is a 3rd party tool. It was not fully implemented so it has some gaps that caused LCM files from it to render lake polygons as a pile of spaghetti noodles on the screen for newer devices. The IMC creates version 6 at5s and version 7 at5s that actually work on new units because all data standards are accounted for. Hence most issues can be avoided, but these old products may still have issues if their display is a custom display that does not match up to the current displays we use (like older monochrome units).
ENDURA
The endura is not a legacy device, but it does not support at5 at all for vector. It supports .PSF format. However the endura does support raster at5 version 10.
LEGACY DEVICES ONLY SUPPORT VECTOR AT5s
Legacy devices as described below only support either at5 version 6 or at5 version 7, with the exclusion of XOG which actually supported version 7 or possibly ver10 at5 (I think, and supported raster at5 if you know how to enable it).
MAPPING DEVELOPMENT NOTES FOR LEGACY UNITS NOT SUPPORTED
Below is the LCX version information:
The IMC produced content may support content for the LCX if you use the legacy at5 version.
UNSUPPORTED LCX
Please note the LCX series units and the card sizes vary significantly. For example: Even though the LCX-104C has a limitation of “up to 1GB card reader”, this means that some units were created with a 512MB reader. The whole series is this way hence the comment “up to…”.
product Navionics Chart support limitations OS Link to updates page Date Current Version File Size
LCX-104C 2Gb Navionics cards not supported up to 1Gb card reader LCX-104C
8/31/2004 1.8.0 7MB unit manual and accessory information in primus
LCX-110C 2Gb Navionics cards not supported up to 1Gb card reader LCX-110C
9/20/2007 2.1.0 8.6MB
LCX-111c HD 2Gb Navionics cards not supported up to 1Gb card reader LCX-111C HD
9/20/2007 2.1.0 8.6MB
LCX-112C need to verify up to 2Gb card reader LCX-112C
7/29/2009 2.5.0 8.6MB non-hard drive counterpart of the 113
LCX-113 HD need to verify up to 2Gb card reader LCX-113C HD
7/29/2009 2.5.0 8.6MB
LCX-15 CI 2Gb Navionics cards not supported up to 128Mb card reader LCX-15 CI
9/25/2003 3.1.0 6.8MB
LCX-15 CT 2Gb Navionics cards not supported up to 128Mb card reader
LCX-15 MT 2Gb Navionics cards not supported up to 512Mb card reader LCX-15 MT
12/29/2006 3.7.0 6.8MB
LCX-16 CI 2Gb Navionics cards not supported up to 128Mb card reader LCX-16 CI
9/25/2003 3.1.0 6.8MB
LCX-16 CT 2Gb Navionics cards not supported up to 128Mb card reader
LCX-17M 2Gb Navionics cards not supported up to 1Gb card reader LCX-17M
10/13/2005 1.6.0 7.0MB
LCX-18C 2Gb Navionics cards not supported up to 1Gb card reader LCX-18C
8/31/2004 1.8.0 7MB
LCX-19C 2Gb Navionics cards not supported up to 1Gb card reader LCX-19C
8/31/2004 1.8.0 7MB
LCX-20C 2Gb Navionics cards not supported up to 1Gb card reader LCX-20C
12/29/2006 1.8.0 7.1MB 20 replaced 18
LCX-25C 2Gb Navionics cards not supported up to 1Gb card reader LCX-25C
9/20/2007 2.1.0 8.6MB 25 replaced 19
LCX-26C HD 2Gb Navionics cards not supported up to 1Gb card reader LCX-26C HD
9/20/2007 2.1.0 8.6MB 26 is hd counterpart HD = hard drive until HDS came out
LCX-27C need to verify up to 2Gb card reader LCX-27C
7/29/2009 2.5.0 8.6MB CI and CT are international certifications
LCX-28C HD need to verify up to 2Gb card reader LCX-28C HD
7/29/2009 2.5.0 8.6MB
LCX-37C need to verify up to 2Gb card reader LCX-37C
7/29/2009 2.5.0 8.6MB
LCX-38C HD need to verify up to 2Gb card reader LCX-38C HD
7/29/2009 2.5.0 8.6MB
LEGACY LMS Units
I think some of the LMS units are monochrome and are not supported at all with the IMC as it does not use a monochrome display. Also most of the iFinder units are monochrome so they will not be supported either.
LEGACY Mapping folders directory structure needed on SD card
Legacy Units (such as iFinder, iWay, XOG, LCX, Global Map, etc.) might work if Vector AT5 files are stored in a “Maps” folder on the root directory of the card.” The legacy units have card reader size limitations, legacy devices won’t support raster at5 files, and legacy devices may support only up to at5 version 6 (not 7). iFinder, iWay, XOG, Global Map, LCX will either use version 6 or version 7 AT5.
Operating system differences
in the old Elite 5, Elite 4, and Mark 4 units (before HDI and CHIRP), these units only supported up to at5 version 10 vector. They also had a 2GB card reader limit. Larger cards simply will not work.
The new Elite 7 HDI, Elite 5 HD, Elite 4 HD, etc. actually use a newer operating system so we should distinguish the two. The HDI and CHIRP Elite and Mark units support up to at5 version 12 for vector and raster.
Please note also, if you duplicate any shape record in elite or mark Lowrance products, this feature will dissappear (Elite and Mark do not handle duplicates or multiple layering). The Lowrance HDS, Simrad, and B&G will support multiple layers. So you cannot mix IMC generated maps on Elite or Mark, but you can mix maps on Lowrance HDS, Simrad, and B&G displays, but conflicts will still occur due to layering and overlap.
Lowrance HDS, Simrad, and B&G supports vector chart category enabling/disabling. Lowrance Mark and Elite series units do not support vector chart category enabling/disabling.
Altas Versions
Sets the output version for the final AT5 file. In general it’s best to use the latest version but some
versions are not supported on earlier devices and some versions have better support for different
features.
Version 6 is used for really old devices.
Starting from AT5 Version 7, InfoBox on point features and raster is supported
Starting from AT5 Version 12, Unicode support, polygon elevation/percentage range, elevation on point
features and percentage on any feature is supported. Version 12 also supports submeter data storage in at5.
Version 13 at5 currently only works with HDS 3.0 software.
Language support and legacy devices
Russian and Czechoslovakian languages can be used in the old Elite or Mark units (Before HDI or CHIRP) as at5 version 10 via IMC, but otherwise the only languages supported were windows 1252 ANSI characters for legacy. We will not provide tools or documentation to implement this, it is too complex, rather there are some limited conversions behind the scenes in the IMC and options for testing these characters in the IMC. The latest products of Violet and NOS (excluding indigo OS) support Unicode:
The IMC has functional support for 59 different codepages on shapefiles.
The names can either be specified for their formal text values or the ESRI aliasing values - support.esri.com/cn/knowledgebase/techarticles/detail/21106
"Apple Roman"
"Big5"
"Big5-HKSCS"
"EUC-JP"
"EUC-KR"
"GB18030-0"
"IBM 850"/"850"
"IBM 866"/"866"
"IBM 874"/"874"
"ISO 2022-JP"
"ISO 8859-1"/"88591"
"ISO 8859-2"/"88592"
"ISO 8859-3"/"88593"
"ISO 8859-4"/"88594"
"ISO 8859-5"/"88595"
"ISO 8859-6"/"88596"
"ISO 8859-7"/"88597"
"ISO 8859-8"/"88598"
"ISO 8859-9"/"88599"
"ISO 8859-10"/"885910"
"ISO 8859-13"/"885913"
"ISO 8859-14"
"ISO 8859-15"/"885915"
"ISO 8859-16"
"ISCII-Bng"
"ISCII-Dev"
"ISCII-Gjr"
"ISCII-Knd"
"ISCII-Mlm"
"ISCII-Ori"
"ISCII-Pnj"
"ISCII-Tlg"
"ISCII-Tml"
"JIS X 0201"
"JIS X 0208"
"KOI8-R"
"KOI8-U"
"MuleLao-1"
"ROMAN8"
"Shift-JIS"/"SJIS"
"TIS-620"
"TSCII"
"UTF-8"/"65001"
"UTF-16"
"UTF-16BE"
"UTF-16LE"
"UTF-32"
"UTF-32BE"
"UTF-32LE"
"Windows-1250"/"1250"
"Windows-1251"/"1251"
"Windows-1252"/"1252"
"Windows-1253"/"1253"
"Windows-1254"/"1254"
"Windows-1255"/"1255"
"Windows-1256"/"1256"
"Windows-1257"/"1257"
"Windows-1258"/"1258"
"WINSAMI2"