Oemrules.py - Rule-Based Configuration File For Columns - HEIDENHAIN iTNC 530 HSCI Technical Manual

Hide thumbs Also See for iTNC 530 HSCI:
Table of Contents

Advertisement

OEMRules.py
July 2013
The entry range_s = '<number>' specifies the number of precalculated tool
calls for the "T usage order" table. Remember: The larger the number of values
to be calculated, the higher the load on the control. Look-ahead calculation is
possible for up to 50 tools. If you enter a fixed value in '<number>', the
number of lines displayed in the table will be exactly the number of lines
specified. If you use a fixed value in NC programs with many tool calls, not all
of the tool calls of the program might be displayed. This can be avoided by
entering a '+' sign in addition to the number, e.g. '30+'. In this way, you can
ensure that at least all of the tools (tool calls) programmed in the NC program
will be displayed in the "T usage order" table. Otherwise, the entered number
of precalculated tool calls will be displayed (here: 30).
Rule-based configuration file for columns
Rules are used to define the individual columns in the configuration file
OEMRules.py. Using rules, you can use or process the columns of the known
tool or pocket table and the two tool usage lists, and display them in the new
tool management.
Every column defined by the configuration can be used in multiple views if the
possible tables links allow it.
The data of the existing views (tables) are accessed in the same way as table
data are usually accessed from Python. The following tokens are currently
possible for tool management:
TOOL – active tool table
TOOL_P – active pocket table
GEO\channel\0\toolPrep\toolingList – list of all available tools of the
currently selected NC program (software option 93)
GEO\channel\0\toolPrep\toolSequence – tool usage order in the currently
selected NC program (software option 93)
Configuration
In general, the JH Python functions make it possible to read the tables in the
control line by line. A string called the ID string must be entered for identifying
each individual line. An ID string must identify the path to the table and the
desired data contents (also see the supplement to the Technical Manual:
Python in HEIDENHAIN controls).
Examples:
The line identified by "T=5" is read from the "TOOL" tool table:
\\TABLE\\TOOL\\T\\5\\*
The length "L" entered in the line identified by "T=5" is read from the "TOOL"
tool table:
\\TABLE\\TOOL\\T\\5\\L
The complete line identified by "P=1.12" is read from the "TOOL_P" pocket
table:
\\TABLE\\TOOL_P\\P\\1.12\\*
An asterisk ("*") at the end of the ID string means that the complete line is
read. But you can also specify a certain column, e.g. "L". Then only the cell
value of the desired line and column will be returned.
8.15 Tool changer
1645

Advertisement

Table of Contents
loading

Table of Contents