1644 HEIDENHAIN Technical Manual iTNC 530 HSCI
OEMRuleList.py Rule-based configuration file for tables
Definition of the following views in the rule-based configuration file
OEMRuleList.py:
Tool table
Pocket table
Tooling list (software option 93)
T usage order (software option 93)
The respective views (tables) are defined in the OEMRuleList.py file by a
sequence of column configurations (saved in OEMRules.py). The individual
tables are configured by specifying the column names. The column names
used must match those used in the OEMRules.py file for the definition of the
columns.
The individual tables have a permanent identifier (key) that is used to assign
the column list to the table:
rule_t: Identifier for tool table
rule_p: Identifier for pocket table
rule_u: Identifier for tooling list
rule_s: Identifier for T usage order
The columns are displayed in the configured view in exactly the sequence in
which they were defined.
The structure of the list of desired columns must match that of a Python list.
Example of configuring a tool table:
rule_t = [
rule_tt
,rule_pocket
,rule_time
,rule_rtime
,rule_mag
,rule_tplcbit0
,
]
range_s = ’19’
This example results in a tool table that consists of the six specified columns.
The structure of the columns is defined in the OEMRules.py file.
HEIDENHAIN recommends creating tables with a maximum of 1500 lines.
Basically, more entries are possible, but this affects computing performance
and may lead to unnecessary waiting times when accessing tables.