<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data Definitions :: Ginmake Manual</title>
    <link>https://gems.co.uk/data-definitions/index.html</link>
    <description>Reference for Ginmake data definition directives and related syntax.</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://gems.co.uk/data-definitions/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Option, Channel, Table and Map Definitions</title>
      <link>https://gems.co.uk/data-definitions/common-definitions.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/common-definitions.html</guid>
      <description>Definitions for these kinds of objects are based upon the number of fields in the definition &amp; do not have a directive name.&#xA;Note&#xD;Channels were formerly called ‘parameters’ in older versions of Ginmake. They were renamed to avoid confusion with the concept of ‘parameters’ in Simulink and also to better reflect their purpose as a channel for the value of a parameter (or other variable) that is used in the ECU’s memory.</description>
    </item>
    <item>
      <title>_DEFINE</title>
      <link>https://gems.co.uk/data-definitions/define.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/define.html</guid>
      <description>Supported by Ginmake v1.74 and later.&#xA;Syntax [_DEFINE,name] [_DEFINE,name,value] Define pre-processor symbols via ginmake comments instead of in the source code itself.&#xA;e.g.&#xA;1// [_DEFINE,HAS_FLUX_CAPACITOR] 2// [_DEFINE,POWER_REQUIRED_GW,1.21]</description>
    </item>
    <item>
      <title>_IF, _IFDEF, _IFNDEF</title>
      <link>https://gems.co.uk/data-definitions/if-ifdef-ifndef.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/if-ifdef-ifndef.html</guid>
      <description>Supported by Ginmake 1.32 and later&#xA;These are used for comment-based conditionals. If the statement is false, then the rest of the comment line is not parsed.&#xA;e.g.&#xA;1;[_IF,OMEX == 2][Inj Advance Mod,...] 2;[_IFNDEF,SOME_SYMBOL]...&#xD;This will only include Inj Advance Mod if the OMEX symbol has a value of ‘2’ or equates to hat value. Any arithmetic or relational operators may be used in the expression.&#xA;_IFDEF evaluates to TRUE if the symbol in the following field is defined.</description>
    </item>
    <item>
      <title>_IF1, _IFDEF1, _IFNDEF1</title>
      <link>https://gems.co.uk/data-definitions/if1-ifdef1-ifndef1.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/if1-ifdef1-ifndef1.html</guid>
      <description>Supported by Ginmake 1.42 and later&#xA;Has the same effect as _IF, _IFDEF and _IFNDEF. The difference is that it only applies to the next object definition (excluding any more pre-processor definitions and/or _WARN directives).</description>
    </item>
    <item>
      <title>_WARN</title>
      <link>https://gems.co.uk/data-definitions/warn.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/warn.html</guid>
      <description>Supported by Ginmake 1.41 and later&#xA;Supress output of a warning for the next object definition.&#xA;e.g.&#xA;1// [_WARN,4017][expression generating warning 4017...]</description>
    </item>
    <item>
      <title>ADDROFF directive</title>
      <link>https://gems.co.uk/data-definitions/addroff-directive.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/addroff-directive.html</guid>
      <description>Syntax [ADDROFF,n] Similar to [SIZEOF]&#xA;Causes the base address of the next defined object to be adjusted.&#xA;For example, if there is a word value defined:&#xA;1USERMSG1 DS.W 1 ;[User Message,,,,r,,,,H,]&#xD;A 8bit alias of the 2nd byte may be added:&#xA;1USERMSG1 DS.W 1 ;[User Message,,,,r,,,,H,] 2;[SIZEOF,1][ADDROFF,1][User Message B2,,,,r,,,,H,]&#xD;Following use of the ADDROFF override to create an object, the override is reset. The override also does not survive until the next source code definition (e.g. the next DS.B).</description>
    </item>
    <item>
      <title>ALIAS</title>
      <link>https://gems.co.uk/data-definitions/alias.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/alias.html</guid>
      <description>Ginmake 2.62+&#xA;Syntax [ALIAS,name,alias_name] [ALIAS,name,alias_name,type] Clone object named ’name’ of type ’type’ with new name ‘alias_name’. Type field is optional.&#xA;Note that for more control, the following is now also possible in ginmake 2.62+, to create a new object at the same location as the EXTEND item:&#xA;1// [EXTEND,TIC 01 Time][TC1,,,,r,+,i,,,]</description>
    </item>
    <item>
      <title>ATTRIBUTES</title>
      <link>https://gems.co.uk/data-definitions/attributes.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/attributes.html</guid>
      <description>Supported by Ginmake 1.24 and later, Gin file version 3.21&#xA;Syntax [ATTRIBUTES,attribute1,attribute2=value2,...] Allows the object to be tagged with various strings. These will be used to convey additional information about the object.&#xA;One such attribute is ‘fuel’. This allows maps that are not called ‘fuel’ to be interpreted as fuel maps and provide the user with additional fuel map specific options.&#xA;Example:&#xA;1// [Fuel1,VE,,,o,+,i,,,rpm Breakpoints,rpm,MAPSSTP,800,400,Load Breakpoints,(Load),MAPLSTP,0,10] 2// [ATTRIBUTES,fuel,another one,another two] Extension in Ginmake 1.33 and later, Gin file version 3.23</description>
    </item>
    <item>
      <title>CATEGORY</title>
      <link>https://gems.co.uk/data-definitions/category.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/category.html</guid>
      <description>Categories are supported in version 3.22 Gin files.&#xA;Syntax [CATEGORY,&lt;identifier&gt;,&lt;display_name&gt;,[&lt;parent&gt;]] Parameters identifier Unique identifier referring to the category display_name Name to be displayed in GWv4 Parent (optional) Identifier of the parent category. This allows tree structures of categories to be defined. A category generates a tag that is referenced by other objects in the GIN file. In Gwv4 objects are added to categories in the views tree to make the user interface more logical.</description>
    </item>
    <item>
      <title>CONNECTION</title>
      <link>https://gems.co.uk/data-definitions/connection.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/connection.html</guid>
      <description>Supported by Ginmake 1.33 and later, GIN file version 3.23.&#xA;Syntax [CONNECTION,type[,param1,param2,...]] Connection definitions give GW a hint as to how the ECU should be connected to. The idea is to be able to provide a better user interface if it appears that the user is having trouble connecting to the ECU. It is mandatory to have at least one connection defined in GIN files of version 3.23 or later.</description>
    </item>
    <item>
      <title>DELETE</title>
      <link>https://gems.co.uk/data-definitions/delete.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/delete.html</guid>
      <description>Supported by Ginmake 2.38 and later.&#xA;Syntax [DELETE,name] [DELETE,name,type] Extend an existing item of the given name and, optionally, type in case of ambiguity.&#xA;e.g.&#xA;1// [DELETE,Engine RPM] 2// [DELETE,Load,table] 3// [DELETE,Load,channel]</description>
    </item>
    <item>
      <title>DESCRIPTION</title>
      <link>https://gems.co.uk/data-definitions/description.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/description.html</guid>
      <description>Supported by Ginmake 1.33 and later, GIN file version 3.23.&#xA;Syntax [{object}][DESCRIPTION,text] Tags a description to the preceding object. This will be used in Gwv4 for extended information (e.g. tool tips for options).&#xA;See also XMLDESCRIPTIONS.&#xA;1// [Fuel,....] // fuel map 2// [DESCRIPTION,Configures the amount of fuel injected at different load and speed values] In ginmake 2.37 this can be used in conjunction with EXTEND to place descriptions in a separate file.</description>
    </item>
    <item>
      <title>DIRECT_CAL_DISABLE</title>
      <link>https://gems.co.uk/data-definitions/direct-cal-disable.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/direct-cal-disable.html</guid>
      <description>Ginmake 2.62+&#xA;Syntax [{object}][DIRECT_CAL_DISABLE] For Simulink builds, if direct_cal_access is enabled, this post-fix directive disables direct access for the associated object.&#xA;The controls the way in which get/set functions are generated for the object. If direct_cal_access is enabled, then by default get/set functions will be generated that access the calibration memory / variable directly. This directive forces the use of XCU_memory_xx functions instead for the associated object.&#xA;In some cases, it may be preferred for some items to be read/written via the XCU_memory_xx functions instead on a case-by-case basis, even when direct_cal_access is enabled. This directive allows this to be done without having to disable direct_cal_access for the whole build.</description>
    </item>
    <item>
      <title>DISPLAY_IDENTIFIER</title>
      <link>https://gems.co.uk/data-definitions/display-identifier.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/display-identifier.html</guid>
      <description>Supported by Ginmake 2.37 and later, Gin file version 3.22&#xA;Syntax [{object}][DISPLAY_IDENTIFIER,identifier] Sets the ‘display identifier’ value on the prior object (as in Asam A2L DISPLAY_IDENTIFIER)</description>
    </item>
    <item>
      <title>ECU_STRING</title>
      <link>https://gems.co.uk/data-definitions/ecu-string.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/ecu-string.html</guid>
      <description>Supported by Ginmake 1.53 and later, Gin file version 3.26&#xA;Syntax [ECU_STRING,identifier] Adds an array of bytes that is readable from the ECU as a string.&#xA;e.g.&#xA;1example ds.b 6 ; [ECU_STRING,Example]&#xD;Adds a string that is 6 characters long and identified by the name ‘Example’.&#xA;Ginmake version 1.48.0+ supports ~ and ! characters as a name prefix, as for options, tables, maps etc for ignoring in conversions / hiding from the user.</description>
    </item>
    <item>
      <title>ENUM / OPTLIST</title>
      <link>https://gems.co.uk/data-definitions/enum-optlist.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/enum-optlist.html</guid>
      <description>Syntax [ENUM=name,string1,value1,string2,value2...] [ENUM,string1,value1,string2,value2...] [OPTLIST=name,string1,value1...] An enumeration (formerly ‘Option List’) allows a value to be represented by a string of text. Within GW the type (typically an option) can be modified by selecting a string from a pull-down list of strings within a combo box.&#xA;An enumeration is typically defined at the beginning of a file after a comment. A square bracket followed by the text ‘ENUM’ (or, for backwards compatibility, ‘OPTLIST’), any number of subsequent value/string pairs and a terminating close square bracket define an enumeration. For example:</description>
    </item>
    <item>
      <title>EQU_ANNOTATION</title>
      <link>https://gems.co.uk/data-definitions/equ-annotation.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/equ-annotation.html</guid>
      <description>Syntax [EQU_ANNOTATION,name,value] Causes the next item to be given an “_equ” attribute for display of this metadata in the GWv4 descriptions view.&#xA;Manual addition of these directives is not recommended – ginmake will automatically insert them during the pre-processing pass of ASM sources. See ticket #1526.</description>
    </item>
    <item>
      <title>EXTEND</title>
      <link>https://gems.co.uk/data-definitions/extend.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/extend.html</guid>
      <description>Supported by Ginmake 2.37 and later&#xA;Syntax [EXTEND,name] [EXTEND,name,type] Extend an existing item of the given name and, optionally, type in case of ambiguity.&#xA;e.g.&#xA;1// [EXTEND,Engine RPM,channel][RENAME,Engine Speed]</description>
    </item>
    <item>
      <title>FUNCTBL</title>
      <link>https://gems.co.uk/data-definitions/functbl.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/functbl.html</guid>
      <description>Function Tables are supported in v1.12+.&#xA;Syntax [FUNCTBL, FUEL, &lt;oorlowreal&gt;, &lt;oorhighreal&gt;, &lt;oorlowraw&gt;, &lt;oorhighraw&gt;, &lt;count&gt;, &lt;raw0&gt;, &lt;real0&gt;, &lt;raw1&gt;, &lt;real1&gt;, ...., &lt;rawcount-1&gt;, &lt;realcount-1&gt;] When defining a parameter, option, table or map, the scalar function is defined as a function table by specifying a name in brackets in the scalar field. For example:&#xA;1uint16_t FUELLVL; // [Fuel level,l,(FUEL),,r,+,i,,] The first label is always FUNCTBL and the name of the function table follows.&#xA;The raw (integer) value to which a real value is converted if it is lower than the lowest value in the table (oor meaning Out Of Range).</description>
    </item>
    <item>
      <title>HARDLIMITS</title>
      <link>https://gems.co.uk/data-definitions/hardlimits.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/hardlimits.html</guid>
      <description>Supported by Ginmake 2.04 and later, Gin file version 3.21&#xA;This is the same as VALIDRANGE except that values are specified in real (physical) values instead of RAW internal values. Values will be converted to RAW by ginmake and stored in the GIN archive in the same way as VALIDRANGE.&#xA;e.g.&#xA;1// [Rad Fan 1,,OL3,,o,2,i,,][HARDLIMITS,0,150] LIMITS and HARDLIMITS can be combined:&#xA;1// [LSB_FIRST][PT3,,,,,,f,,,][LIMITS,0.0,100.0][HARDLIMITS,0.0,100.0] For A2L output, HARDLIMITS sets EXTENDED_LIMITS on calibration objects (CHARACTERISTIC, AXIS_PTS and AXIS_DESCR). An omitted bound uses the corresponding data type limit after scaling. VIEWRANGE or LIMITS can independently set the normal display limits.</description>
    </item>
    <item>
      <title>IDENTIFIER</title>
      <link>https://gems.co.uk/data-definitions/identifier.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/identifier.html</guid>
      <description>Supported by Ginmake 2.37 and later, Gin file version 3.22&#xA;Syntax [{object}][IDENTIFIER,identifier] Sets the ‘identifier’ value on the prior object (as in Asam A2L IDENTIFIER)</description>
    </item>
    <item>
      <title>IDENTITY</title>
      <link>https://gems.co.uk/data-definitions/identity.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/identity.html</guid>
      <description>Supported by Ginmake 2.27.&#xA;Syntax [IDENTITY,name[,value[,nameN,valueN]]] Adds additional fields to the ECU identity JSON that is embedded in the GIN file. Multiple key-value pairs can be specified.&#xA;Multiple IDENTITY directives may be specified.&#xA;e.g.&#xA;1// [IDENTITY,GlsVersion,&#34;01V00&#34;] Indicates the supported GLS (GEMS Logger Setup) version (see GEMS doc 104172)&#xA;The JSON is output to a file ‘ginmake.identity.json’.</description>
    </item>
    <item>
      <title>INCLUDE_A2L</title>
      <link>https://gems.co.uk/data-definitions/include-a2l.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/include-a2l.html</guid>
      <description>Ginmake 2.39+&#xA;Syntax [INCLUDE_A2L,&lt;filename&gt;] Filename is absolute or relative to the file being processed.&#xA;When exporting A2L files, this command shall parse the supplied file (syntactically, not semantically) and then load that DOM directly into the MODULE node being exported.&#xA;At present, this will result in loss of formatting / comments from the source file.&#xA;There is some possibility that this could result in unwanted conflicts, so some care is needed to avoid that.</description>
    </item>
    <item>
      <title>INPUTS / OUTPUTS</title>
      <link>https://gems.co.uk/data-definitions/inputs-outputs.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/inputs-outputs.html</guid>
      <description>Supported by Ginmake 1.75.&#xA;[INPUTS,name1[,nameN]] [OUTPUTS,name1[,nameN]] List inputs and outputs of this object (e.g. a parameter name that represents the output of a map). This may in future enable automatic Audit graph generation and may also be useful for A2L export. These definitions generate inputs/outputs ATTRIBUTES.</description>
    </item>
    <item>
      <title>LIMITS</title>
      <link>https://gems.co.uk/data-definitions/limits.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/limits.html</guid>
      <description>Supported by Ginmake 1.92 and later, Gin file version 3.21&#xA;This is the same as VIEWRANGE except that values are specified in real (physical) values instead of RAW internal values. Values will be converted to RAW by ginmake and stored in the GIN archive in the same way as VIEWRANGE – i.e. they will not take into account any dynamic scaling.&#xA;e.g.&#xA;1// [Rad Fan 1,,OL3,,o,2,i,,][LIMITS,0,150] or&#xA;1// [LSB_FIRST][PT3,,,,,,f,,,][LIMITS,0.0,100.0]</description>
    </item>
    <item>
      <title>LITTLEENDIAN</title>
      <link>https://gems.co.uk/data-definitions/littleendian.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/littleendian.html</guid>
      <description>Syntax [LITTLEENDIAN] By default, ECUs are assumed to be big endian. To define an ECU as little endian simply add the line:&#xA;..anywhere in the code to be processed. ECUs are always little or big endian and cannot be mixed.</description>
    </item>
    <item>
      <title>LOGGINGSIZE</title>
      <link>https://gems.co.uk/data-definitions/loggingsize.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/loggingsize.html</guid>
      <description>The logging memory size can be specified for gin files of version 3.18 and greater. Often the ECU defines this in a parameter (“Log Size”) which is not available off-line. In the past it has been assumed that the logging memory size is 512*1024 (originally hard coded for AEM) when calculating the run time in GW.&#xA;The size can be defined as follows:&#xA;1// [LOGGINGSIZE=1024 * 1024] The value is specified in bytes.</description>
    </item>
    <item>
      <title>LOGMAP</title>
      <link>https://gems.co.uk/data-definitions/logmap.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/logmap.html</guid>
      <description>Log Maps monitor and store a pre-defined parameter into the map at sites corresponding to those of a base map. For example, a Lambda log map would log the lambda parameter, based upon the fuel map. As the load and speed approach a particular site in the fuel map, the value of lambda is logged into the lambda log map at the corresponding site. As more values of lambda are collected for that site, the site value is averaged out. As engine load and speed changes, the log map is built up to show how lambda changes across the entire load and speed map.</description>
    </item>
    <item>
      <title>LONG_IDENTIFIER</title>
      <link>https://gems.co.uk/data-definitions/long-identifier.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/long-identifier.html</guid>
      <description>Supported by Ginmake 2.37 and later, Gin file version 3.22&#xA;Sets the ’long identifier’ value on the prior object (as in Asam A2L LONG_IDENTIFIER)</description>
    </item>
    <item>
      <title>META</title>
      <link>https://gems.co.uk/data-definitions/meta.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/meta.html</guid>
      <description>Supported by Ginmake 1.33 and later, GIN file version 3.23.&#xA;Used to define additional, arbitrary ‘meta’ information in the GIN file.&#xA;Ideally, this should take the format:&#xA;[META,name,other stuff..n] Valid definitions:&#xA;CAN_CHANNEL_NAME Gives a human readable name for the CAN channel&#xA;[META,CAN_CHANNEL_NAME,1,Vehicle CAN] [META,CAN_CHANNEL_NAME,2,Engine CAN] UNSECURE_PAGES Identifies pages in the page table that can be read even when the ECU is secured.&#xA;This allows users access to some ECU areas whilst keeping other areas of the calibration locked.</description>
    </item>
    <item>
      <title>METAFILE</title>
      <link>https://gems.co.uk/data-definitions/metafile.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/metafile.html</guid>
      <description>Supported by Ginmake 1.41 and later, GIN file version 3.23.&#xA;Adds meta data from a file. This is generally used for output pin configuration files:&#xA;[METAFILE,pin_config,aem25_pin_config.xml] See the X25 source code for an example XML file. This enables ‘Configure Outputs’ on GWv4.</description>
    </item>
    <item>
      <title>MSB_FIRST / LSB_FIRST</title>
      <link>https://gems.co.uk/data-definitions/msb-first-lsb-first.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/msb-first-lsb-first.html</guid>
      <description>Endian Directives cause the next item to have the given endian mode applied.&#xA;[MSB_FIRST] (big endian) [LSB_FIRST] (little endian) e.g.&#xA;1uint16_t value; // [MSB_FIRST][Value,,,,,,,,,]</description>
    </item>
    <item>
      <title>MIN_VERSION</title>
      <link>https://gems.co.uk/data-definitions/min-version.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/min-version.html</guid>
      <description>[MIN_VERSION,&lt;version&gt;] Specify a minimum ginmake version to interpret this file, e.g. [MIN_VERSION, 2.22.0.0]. If minor revisions are not specified, they will be assumed to be 0, e.g. 2.22 = 2.22.0.0. An error will be issued if the current ginmake version is lower than the minimum.&#xA;Note: This feature was only added in version 2.22 so the directive will not be recognised for earlier versions of Ginmake. Instead, you can use the pre-processor code below to enforce a minimum Ginmake version.</description>
    </item>
    <item>
      <title>PACK_PUSH / PACK_POP</title>
      <link>https://gems.co.uk/data-definitions/pack-push.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/pack-push.html</guid>
      <description>Added in version 2.24&#xA;Syntax [PACK_PUSH,align] ... [PACK_POP] Pushes the current alignment (default is 4) onto a stack and sets ‘align’ as the current packing / alignment value.&#xA;Pushes the prior alignment value from the stack and sets it as the current packing / alignment value.</description>
    </item>
    <item>
      <title>PAGETBL / PAGETBLV2</title>
      <link>https://gems.co.uk/data-definitions/pagetbl-pagetblv2.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/pagetbl-pagetblv2.html</guid>
      <description>Note: in ginmake 2.19+. page tables can be avoided through using a combination of SEGMENT and SEGMENT_ADDRESS definitions.&#xA;A file containing a page table may be referenced in a header file using either PAGETBL or PAGETBLV2:&#xA;[PAGETBL=COMS.ASM] [PAGETBLV2=COMS.ASM] PAGETBL indicates an old-style page table and is present in most existing code. This is now restricted to 32 entries (to catch errors when upgrading to the extended comms protocol) and should have contiguous a EEROM segment. This version of page table allows ROMBS to be used as EEROM in ASM code if it directly follows the EEROM data.</description>
    </item>
    <item>
      <title>PARAMTBL</title>
      <link>https://gems.co.uk/data-definitions/paramtbl.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/paramtbl.html</guid>
      <description>Parameter tables are similar to tables but use live parameter data to fill the table.&#xA;A parameter table is defined with a name, axis start and offset labels, an optional axis parameter to determine the current site and a list of parameters defining the value at each site.&#xA;A parameter table is defined as follows:&#xA;Field Name Definition PARAMTBL This is entered as is and defines the values as a parameter table. Name Defines the name of the parameter table. This is displayed in selection menus and at the top of the table when displayed. Axis Parameter This is the name of the parameter used for the axis of a table (or x axis of a map). In some tables (e.g. battery compensation table) the parameter is used to determine the current position in the table. In others (e.g. speed table) the parameter is used by the maps that use the table as their axis. This name may also be the name of a table used for the axis of a table or map (as referred to in the speed table example). Note tables take precedence over parameters. You should avoid duplicating names of parameters, options and tables for values that are referenced by this field. If such a conflict exists, Ginmake will warn you. Axis Units The units for the axis (or x axis of the map). (May also be user scalar units as per field 2.). Defaults to an empty string. Start The axis value of the first step. This is an integer value. If preceded by a ‘*’ the subsequent real value is the first step value. Defaults to 0. Alternatively, this may be the name of an option if a table has not been used for the axis parameter. The name may optionally be placed in brackets. Offset The offset of each subsequent axis site from the start axis value. This is an integer value. If preceded by a ‘*’ the subsequent real value is the offset. Defaults to 1. Alternatively, this may be the name of an option if a table has not been used for the axis parameter. The name may optionally be placed in brackets. Parameter[1] Defines the parameter used to determine the value of the first site. This is followed by the names of the parameters defining the subsequent site values. Ginmake 1.78+ May also use a range expression here. There are 2 possible formats 1) A range of parameters separated by an ellipsis, which will include all parameters in declaration order between (and including) the start and end values given. &lt;param[1]&gt;…&lt;param[N]&gt; e.g. TPER00…TPER31 2) A printf style format expression, preceeded by an ellipsis, the bounds for the expanded range are placed in the next two fields following this field. e.g. [PARAMTBL,,,,,,…,first,last] For printf style formatting the format should follow printf style, See ​http://www.cplusplus.com/reference/cstdio/printf/ e.g. ;[PARAMTBL,PT2,Wheel Tooth,$deg$S,0,1,…TPER%02u,0,31] Will generate names with padded zeros: TPER00, TPER01, …, TPER31 Parameter[2] [Optional] Second parameter in the table. Parameter[n] [Optional] Nth parameter in the table.</description>
    </item>
    <item>
      <title>PROFILE</title>
      <link>https://gems.co.uk/data-definitions/profile.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/profile.html</guid>
      <description>Profiles are supported in version 3.17 Gin files.&#xA;Syntax:&#xA;1[PROFILE,&lt;profile name&gt;]&#xD;A profile generates a tag that is referenced by other objects in the GIN file. The profile can be used to hide various objects from the user.&#xA;The objects may be shown to the user by toggling an option in GW. The option will be labelled with the name provided in the PROFILE definition.&#xA;Profiles can be applied to options, tables, parameters and maps in the read/write field.</description>
    </item>
    <item>
      <title>PROTOCOL</title>
      <link>https://gems.co.uk/data-definitions/protocol.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/protocol.html</guid>
      <description>Supported by Ginmake 1.44 and later, GIN file version 3.24 or later.&#xA;[PROTOCOL, &lt;type&gt; {,&lt;MAX_READ&gt; {,&lt;MAX_WRITE&gt;}} ][PROTOCOL:&lt;conn&gt;, &lt;type&gt; {,&lt;MAX_READ&gt; {,&lt;MAX_WRITE&gt;}} ] 1#define MAX_READ_USB 256 2#define MAX_WRITE_USB 4 3 4// [PROTOCOL GemsExtended, 2, 2] 5// [PROTOCOL:LIBUSB, GemsExtended, MAX_READ_USB, MAX_WRITE_USB] ‘conn’ refers to the connection type to which to associate the protocol. If this field is not supplied, then the default protocol is defined. See [CONNECTION].&#xA;’type’ may be one of: Gems13bit [Existing protocol] GemsExtended [Extended address/size protocol]</description>
    </item>
    <item>
      <title>RENAME</title>
      <link>https://gems.co.uk/data-definitions/rename.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/rename.html</guid>
      <description>Supported by Ginmake 2.37 and later.&#xA;[RENAME,new_name] Renames the prior definition. If appropriate, the existing name will be added to the front of the old names list.</description>
    </item>
    <item>
      <title>SEGMENT</title>
      <link>https://gems.co.uk/data-definitions/segment.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/segment.html</guid>
      <description>Supported by Ginmake 1.61&#xA;[SEGMENT,&lt;mem_type&gt;,&lt;name&gt;,&lt;symbol_name&gt;{,&lt;checksum_name&gt;,&lt;checksum_type&gt;}] Defines segments that should be used by the page table and address assignment.&#xA;Segment definitions must precede the page table (PAGTBL or PAGETBLv2). Additionally, the definitions must precede the checksum locations.&#xA;Parameter Description&#xA;&lt;mem_type&gt; Describes the type of memory. One of: nvm: Non volatile memory (i.e. Calibration memory – options/maps). ram: Parameter memory (e.g. parameters, parameter tables). rom: Readonly memory (e.g. ECU header at DF00). Name of the segment. There should be a #define that equates to its address that is used during page table processing. e.g. EEROM, RAMBS etc. &lt;symbol_name&gt; Name of the symbol used for the storage attribute to in the C source code. For ASM compilations, this field is for segment lookups e.g. EEROM. The symbol name is case insensitive for historical reasons. e.g. idata, near (legacy names from X25 code). uint16_t near option_variable; // [Option X, …] This may use a #define that is not visible to ginmake code: e.g. #ifndef GINMAKE #define GXGRAM #endif uint16_t GXGRAM option_variable; // [Option X, …] &lt;checksum_name&gt; Name of region checksum variable. Optional. &lt;checksum_type&gt; Type of region checksum. Possible values: additive crc16 next_region [default] none Defaults</description>
    </item>
    <item>
      <title>SEGMENT Attributes (A2L Generation)</title>
      <link>https://gems.co.uk/data-definitions/segment-attributes-a2l-generation.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/segment-attributes-a2l-generation.html</guid>
      <description>Ginmake 2.39+&#xA;Since version 2.39, segments may have ATTRIBUTES specified. These attributes allow fine-tuning of the output when generating A2L files.&#xA;Attribute Meaning NO_A2L Do not export the segment in the A2L file PrgType Set the PrgType field of A2L MEMORY_SEGMENT. Possible values: CALIBRATION_VARIABLES, CODE, DATA, EXCLUDE_FROM_FLASH, OFFLINE_DATA, RESERVED, SERAM, VARIABLES, MemoryType Set the MemoryType field of the A2L MEMORY_SEGMENT. Possible values: EEPROM, EPROM, FLASH, RAM, ROM, REGISTER, NOT_IN_ECU, Attribute Set the Attribute field for the A2L MEMORY_SEGMENT. Possible values: INTERN, EXTERN, XCP_CHECKSUM Set the CHECKSUM field of the XCP IF_DATA on the MEMORY_SEGMENT. ADDRESS_MAPPING Set the ADDRESS_MAPPING block of the XCP IF_DATA on the MEMORY_SEGMENT. This attribute is a semicolon separated list of integer values source, dest, size for the address re-mapping values. SECTOR Sector number (XCP IF_DATA of MEMORY_SEGMENT) NUM_PAGES Number of Pages (XCP IF_DATA of MEMORY_SEGMENT) ADDRESS_EXTENSION Memory address extension value (XCP IF_DATA of MEMORY_SEGMENT) COMPRESSION_METHOD Compression Method, relates to PGM commands (XCP IF_DATA of MEMORY_SEGMENT). This is an 8 bit unsigned integer, the host does not do anything with this value. ENCRYPTION_METHOD Encryption Method, relates to PGM commands (XCP IF_DATA of MEMORY_SEGMENT). This is an 8 bit unsigned integer, the host does not do anything with this value.</description>
    </item>
    <item>
      <title>SEGMENT_ADDRESS</title>
      <link>https://gems.co.uk/data-definitions/segment-address.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/segment-address.html</guid>
      <description>Supported by Ginmake 2.19+&#xA;[SEGMENT_ADDRESS,&lt;segment_name&gt;,&lt;gemscom_address&gt;,&lt;size&gt;[,&lt;physical_address&gt;[,gcc_section]]] Defines address / size of a segment previously defined by a SEGMENT definition. This removes the need for PAGETBL / PAGETBLv2 – memory segments can be defined purely with SEGMENT and SEGMENT_ADDRESS since ginmake 2.19. This is preferable for code that does not use a page table for gemscom address translation.&#xA;Parameter Description&#xA;&lt;segment_name&gt; Name of the segment to match that in its SEGMENT definition &lt;gemscom_address&gt; Address of the segment used over the gemscom protocol. This is a virtual address and is remapped by the ECU to a physical address. Size of the segment, in bytes. At time of writing, GWv4 will read/write entire calibration (NVM) segments. &lt;physical_address&gt; Optional physical address of the segment from the perspective of the target computer (the ECU). This may be useful for diagnostic purposes in future. &lt;gcc_section&gt; Section name used by linker for this segment that will appear in the GNU linker map file. Example</description>
    </item>
    <item>
      <title>SEGMENT_BEGIN</title>
      <link>https://gems.co.uk/data-definitions/segment-begin.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/segment-begin.html</guid>
      <description>Supported by Ginmake 2.19+&#xA;[SEGMENT_BEGIN,&lt;segment_name&gt;] Start a segment section. This allows C code to avoid placing a segment location on variables defined between SEGMENT_BEGIN and SEGMENT_END. Or particular use if C style structs are used to define the memory of a region.&#xA;Segments may not be nested.&#xA;Parameter Description&#xA;&lt;segment_name&gt; Name / symbol of the segment to match that in its SEGMENT definition Example&#xA;1// [SEGMENT_BEGIN,SEG_NVM] 2uint32_t param1; // [,,,,,,,] 3uint32_t param2; // [,,,,,,,] 4uint32_t SEG_NVM param3; // [,,,,,,,] OK – SEG_NVM is same as scope 5uint32_t SEG_RAM param3; // ERROR – placed SEG_RAM within SEG_NVM 6// [SEGMENT_END,SEG_NVM]</description>
    </item>
    <item>
      <title>SEGMENT_END</title>
      <link>https://gems.co.uk/data-definitions/segment-end.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/segment-end.html</guid>
      <description>Supported by Ginmake 2.19+&#xA;[SEGMENT_END,&lt;segment_name&gt;] Closes segment opened with SEGMENT_BEGIN.&#xA;Parameter Description&#xA;&lt;segment_name&gt; Name / symbol of the segment to match that in its SEGMENT definition Example&#xA;1// [SEGMENT_BEGIN,SEG_NVM] 2uint32_t param1; // [,,,,,,,] 3uint32_t param2; // [,,,,,,,] 4// [SEGMENT_END,SEG_RAM] // ERROR – different closing segment.</description>
    </item>
    <item>
      <title>SIZEOF directive</title>
      <link>https://gems.co.uk/data-definitions/sizeof-directive.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/sizeof-directive.html</guid>
      <description>[SIZEOF,n] Causes the base size of the next defined object to be reinterpreted.&#xA;For example, if there is a byte value defined:&#xA;1USERMSG1 DS.B 1 ;[User Message1,,,,r,,,,H,]&#xD;A 16bit alias may be added that also spans the next byte:&#xA;1USERMSG1 DS.B 1 ;[User Message1,,,,r,,,,H,] 2;[SIZEOF,2][User Message1W,,,,r,,,,H,]&#xD;Following use of the sizeof override to create an object, the override is reset. The override also does not survive until the next source code definition (e.g. the next DS.B).</description>
    </item>
    <item>
      <title>SL_PREFIX</title>
      <link>https://gems.co.uk/data-definitions/sl-prefix.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/sl-prefix.html</guid>
      <description>Added in version 2.65.&#xA;Add / change the prefix used for generated Simulink signal name. For builds using XCU API, signals are prefixed with XCU_ by default. Specifying [SL_PREFIX,] overrides the default, removing the prefix, which can be useful for legacy name mappings (e.g. EM80M compatibility layer).&#xA;This is a post-fix directive and may be used on any object that may be used to generate a signal.&#xA;Additionally, the directive may be used as a post-fix on [SEGMENT] to apply the prefix to an entire memory segment.</description>
    </item>
    <item>
      <title>STRUCT</title>
      <link>https://gems.co.uk/data-definitions/struct.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/struct.html</guid>
      <description>Added in version 2.24&#xA;Instantiate a struct. The struct being instantiated must currently be included within a STRUCT_BEGIN / STRUCT_END block.&#xA;[STRUCT,name] As of ginmake 2.24, simple struct typedefs are parsed.&#xA;As of ginmake 2.41, if the name ends with a ‘#’ character, it shall synthesize names in the format ’name #NNn member’, instead of using array syntax ’name[N].member’. If the name ends with ‘#.’, then the format will be dotted, e.g. ’name_#NNn.member’.</description>
    </item>
    <item>
      <title>TYPEDEF_SIZE</title>
      <link>https://gems.co.uk/data-definitions/typedef-size.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/typedef-size.html</guid>
      <description>[TYPEDEF_SIZE,name,size,[align]] Introduces a type name to the C parser. Used for e.g. structs to declare their size for ginmake.&#xA;‘align’ is optional as of Ginmake 2.24.0 and is the alignment value of the structure. If elided then the default alignment value is used (see PACK_PUSH / PACK_POP).</description>
    </item>
    <item>
      <title>UNIT</title>
      <link>https://gems.co.uk/data-definitions/unit.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/unit.html</guid>
      <description>Unit definitions allow additional units to be specified by this ECU definition file that are not in the list of predefined units (See Units and Quantities).&#xA;Field Name Definition UNIT This is entered as is and defines the values as a unit definition. Name Defines the name of the unit. If blank, this is the same as the unit ID’s unit name. Unit ID Defines the unit ID of this unit. e.g. afr:AFR Ammonia for Air Fuel Ratio This MUST include the quantity ID of the unit and the unit identifier. Display Unit The display unit. If blank, this is the same as the unit IDs unit name Aliases Semicolon separated list of aliases used for lookups. E.g. km/h might have an alias ‘kph’. M Defines the default scalar. Defaults to 1. This value indicates the linear conversion from the relative unit to convert from a value in the relative unit to this one. For example, if defining kilograms relative to grams, then the scaling factor would be 0.001. C Defines the default offset. Defaults to 0. As with ‘M’ this is the offset from the relative unit being derived from. Relative To Unit ID of the unit that this unit is derived from. If not given, the scaling is relative to the reference ‘unity scaled’ (root) unit for the given quantity. A quantity must always have a ‘root’ unit. The quantity does not need to be provided here – derived units may only belong to the same quantity as the unit they are relative to. If the quantity is given it will be checked. Example:</description>
    </item>
    <item>
      <title>UNITQUANTITY</title>
      <link>https://gems.co.uk/data-definitions/unitquantity.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/unitquantity.html</guid>
      <description>Defines a custom unit quantity to be added to the set of predefined units for this GIN file (See Units and Quantities). If a unit quantity is defined and there is a predefined quantity of the same ID then the defined quantity will replace the predefined one.&#xA;Unit quantities must always include a ‘root’ unit; root units are those that have unity (‘identity’) scaling where m = 1 and c = 0 in the linear scaling function f(x) = m.x + c.</description>
    </item>
    <item>
      <title>USERSCALAR / OPTUSERSCALAR</title>
      <link>https://gems.co.uk/data-definitions/userscalar-optuserscalar.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/userscalar-optuserscalar.html</guid>
      <description>User scalars allow the units, scalar and offset to be defined by the user within GW. By specifying the units (including table axis units and map x and y axis units) as a name in brackets (e.g. ‘(load)’) a user scalar is created with the appropriate name (if necessary) and assigned to the type.&#xA;Since GIN version 3.33, DELETE&#xA;Supported by Ginmake 2.38 and later.&#xA;1[DELETE,name[,type]]&#xD;Extend an existing item of the given name and, optionally, type in case of ambiguity.</description>
    </item>
    <item>
      <title>VALUES (Default Value)</title>
      <link>https://gems.co.uk/data-definitions/values.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/values.html</guid>
      <description>Supported by Ginmake 1.25 and later, Gin file version 3.21&#xA;Objects may be supplied with default values. For many objects, it is acceptable that they are initialized to zero. For others it is not so good (can result in damaging behaviour from the ECU).&#xA;Default values can be specified in one of two ways:&#xA;An initializer list: 1[VALUES={1, 2, 8, 16, 5}]&#xD;An expression: 1[VALUES=10] 2[VALUES=@8u:0xFFFFFFFFFFFFFFFF] 3[VALUES=_x \* _y] 4[VALUES=BILINEAR_INTERP(_x, _y, MAPSSTP, MAPLSTP, 10, 100, 80, 255)]&#xD;The specified values correspond to the raw values that would be expected in the ECU memory.</description>
    </item>
    <item>
      <title>VALIDRANGE</title>
      <link>https://gems.co.uk/data-definitions/validrange.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/validrange.html</guid>
      <description>Supported by Ginmake 1.24 and later, Gin file version 3.21.&#xA;This sets up its preceding object with a range of valid values. This will be used by GW in doing a sanity check on a given calibration and note possible problems.&#xA;e.g.&#xA;1// [Rad Fan 1,,OL3,,o,2,i,,] 2// [VALIDRANGE,1,255] In this example, it suggests that Rad Fan should be in the range 1…255.&#xA;The minimum or maximum may be omitted if there’s no limit:</description>
    </item>
    <item>
      <title>VAR_PREFIX</title>
      <link>https://gems.co.uk/data-definitions/var-prefix.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/var-prefix.html</guid>
      <description>Supported by Ginmake 2.41 and later.&#xA;This sets a prefix for all following variable names. Can be useful for disambiguating identifers in A2L export when structures are used.&#xA;e.g.&#xA;1// [VAR_PREFIX,measurements.] 2uint8_t adr1; // [ADR1,…] variable name is measurements.adr1</description>
    </item>
    <item>
      <title>VIEWRANGE</title>
      <link>https://gems.co.uk/data-definitions/viewrange.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/viewrange.html</guid>
      <description>Supported by Ginmake 1.24 and later, Gin file version 3.21&#xA;This is similar to VALIDRANGE but sets up a default range for views in the user interface. This can be useful if the range normally used is only a small subset of the total possible range. This is a soft limit – the user may specify values outside of this range. For ‘strong’ limits, use VALIDRANGE or HARDLIMITS.&#xA;e.g.&#xA;1// [Rad Fan 1,,OL3,,o,2,i,,][VIEWRANGE,1,100] Values are RAW unscaled values.</description>
    </item>
    <item>
      <title>WORDWRITES</title>
      <link>https://gems.co.uk/data-definitions/wordwrites.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/wordwrites.html</guid>
      <description>DEPRECATED – use [PROTOCOL] in new code.&#xA;Version 1.07 generates v3.10 GIN files that include a word writes flag. The flag can be set by adding a comment in the source containing:&#xA;[WORDWRITES] This allows data to be written two bytes at a time and increases comms performance. Note that word writes are always aligned to word boundaries.</description>
    </item>
    <item>
      <title>XMLDESCRIPTIONS</title>
      <link>https://gems.co.uk/data-definitions/xmldescriptions.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://gems.co.uk/data-definitions/xmldescriptions.html</guid>
      <description>Supported by Ginmake 1.44 and later, GIN file version 3.24.&#xA;Embeds an XML description file into the GIN file. See example_descriptions.xml.&#xA;[XMLDESCRIPTIONS,&lt;filename.xml&gt;] The XML description file allows GWv4 to display descriptions about objects within the GIN file. This format file is extensible so that new features may be added to description files and GWv4 without requiring a new version of GIN file.&#xA;Example XML file:&#xA;Counter for LEDs Size of the logging memory Analogue input 9 My Long Description Does something with Foo Note some of the features here. This follows standard basic XML formatting – if you are unfamiliar, refer to http://www.w3schools.com/xml/default.asp .</description>
    </item>
  </channel>
</rss>