Gin Version

The default output GIN file version is 3.34 for compatibility with widely deployed tools. GIN files are binary files and are not backwards compatible – tools that open GIN files such as GWv4 must be recent to be able to load a specific version of GIN file.

Use -v3.35 to explicitly select version 3.35 when the tools consuming the GIN file support it. Newer supported formats do not automatically change the default.

If you need to build a GIN file for an older GW release, use the -v switch. e.g. For a GWv3 version 3.18 release, use the ‘-v3.13’ option for Ginmake.

Version 3.17+ supports profiles, “old names” and “ignore in compare / convert”.

Table - GIN version compatibility matrix

GIN Version Ginmake Version GW Version
3.33 2.25 4.03.45
3.32 1.87 4.02.58
3.31 1.71 4.02.43
3.30 1.59 4.01.32
3.29 1.56 4.01.12
3.28 1.55 4.01.09
3.27 1.54 4.01.07
3.26 1.53 4.01.03

Table 2 - GIN version FEATURE matrix

GIN Version Features added
3.33 User defined units. ENUM/OPTLIST, USERSCALAR/OPTUSERSCALAR – Added: DESCRIPTION, ATTRIBUTES, IDENTIFIER, LONGIDENTIFIER, DISPLAYIDENTIFIER. USERSCALAR/OPTUSERSCALAR – Hide from units configuration using ‘!’ name prefix.
3.32 All objects – Bitmask shift, per-object endian mode. All objects except ENUM/OPTLIST, USERSCALAR/OPTUSERSCALAR – Added: DESCRIPTION, ATTRIBUTES, IDENTIFIER, LONGIDENTIFIER, DISPLAYIDENTIFIER. ENUM/OPTLIST – Define default text if mapping unsuccessful, range. Axes – Added option steps. CCP / XCP extensions.
3.31 Change audit and digital signatures.
3.30 24/32/64-bit values and floating-point raw values.
3.29 Axes, USERSCALAR - Value formatters.
3.28 Dynamic object names.
3.27 All objects except USERSCALAR/OPTUSERSCALAR – Hide in GWv4 using ‘!’ name prefix. Indirect axis tables/parameters. Dynamic units.
3.26 ECU_STRING. Remote feature upgrade features.

ECUDEF files

ginmake 2.07+

Ecudef is a container file that can contain a LZMA compressed GIN file. Such files are typically tens of kB instead of hundreds/thousands.

Ecudef also includes a small uncompressed header to make it possible to identify the ECU it represents quickly without decompressing the GIN file and reading it.

For simulink based gems ECUs, the matching of an ECU identity to a definition file is more complicated than just using the ECU name/version - the model loaded into the ECU can affect the binary layout of memory.

Ecudef can alternatively contain an A2L file for XCP based ECUs.  These serve the same purpose as GIN files but are the ASAM standard.

In short, ecudef offers a way to unify GIN / A2L formats, allow rapid file identification and reduce file sizes.  In future it will also allow encryption and other augmentation such as inclusion of tab files etc.

Ginmake will produce both a GIN file and an ecudef file. Either can be installed into compatible tools. The installation will compress GIN files to ecudef before placing into the ecu definition file store in order to reduce disk usage.