INOS
Configuration

Overview

There are several ways to configure a project. The obsolete ones (IMD config, ICT config, .dat files) will not be explained anymore. The currently used config methods are .dt2 files and .xml (COP) files.

Configuration storage

Usually all the configuration files (.dt2, .bin, .xml etc) are all in a directory in the project directory. They don't need to be in one place, they can be grouped in sub directories for better organisation.

Examples:
Config files separated by fieldbus:

config\ginlink;config\infolink;config\copbus;config\system
CINOSMcModuleWaitVar
Definition cinosmcmodule.h:1900

Config files on network drives common for all machines:

X:\path\to\config\base;X:\path\to\config\machine1

Configuration download

Upon downloading the Trans32 tool will descend the whole config tree(s) and gather all known files (depending on the extension). These files will then be loaded or burned into the target. Which files are taken into account can be defined in the trans config file.

The known files are loaded and parsed if necessary. Errors in the files are reported (unless indel image is used). Unknown files are just ignored.

Trans32 Config File

<binaryfiles>
.bmp;.def;.txt;.gcode;.stream;.bin;.lua;.xml;.cdc;.df;.hpgl;
</binaryfiles>
<textfiles>
.txt;.stream;.xml;
</textfiles>

Configuration busses

  • See documentation about GinLink.
  • See documentation about CopBus.

Configuration types

Configuration security