ACU-RITE MILLPWR G2, Техническое руководство

Страница: 83 / 546

4.4 Structure of a Parameter File 83
4.4 Structure of a Parameter File
The individual machine parameters are collected into parameter objects in the
*.cfg parameter files. A parameter object has a name, of which the first three
letters are always “Cfg.” The name is followed by an open parenthesis and a
“key” for identifying the parameter object. This is followed by the individual
machine parameters. A parameter object must be surrounded by parentheses.
If there are several input values for a parameter (such as separate parameter
settings for each axis), then the corresponding parameter objects are
addressed via the key, and therefore occur more than once.
The parameter objects in the system files have an “empty” key.
Rules for entries If changes to the files are to be made directly in a text editor, the following
rules must be observed:

“Key”: Each parameter object has a key at the beginning, which generally
represents the name of the axis or channel, but in certain cases can also be
empty. The control assigns this parameter object to the object addressed by
the key, for example to the axis “X axis”.

The characters := must come between the parameter name and the value.

Individual parameters must be separated by commas. No comma may fol-
low the last parameter.

Individual components, such as strings in a list or the components in the
array must be separated by commas. No comma may follow the last com-
ponent.

The different levels in path entries must always be separated by “\\”, for
example, “%SYS%\\CONFIG\\AXIS\\...”.

A list must always be in brackets [ ].

If data objects with the same names and same identifications (keys) are
present, the error message “Data object already exists in file” is displayed.

Comments are text that is ignored during transfer. You can enter two types
of comments:
• Comment in one line: After a double hyphen “--” the text until the end
of the line is ignored.
• Comments that are on more than one line must be surrounded like this:
(*comment*).

Comments in files that are overwritten by the control (such as files with axis-
setting parameters or oscilloscope parameters) are deleted. For this reason
you should only add comments to files that are not written to by the control.
Note
HEIDENHAIN recommends changing the parameter values directly in the
*.cfg files only in exceptional cases.