User variables must be defined before they can be used (read/write). The following rules must
be observed in this context:
● GUDs must be defined in a definition file, e.g. _N_DEF_DIR/_N_UGUD_DEF.
● PUDs and LUDs must be defined in the definition section of the NC program.
● The data must be defined in a dedicated block.
● Only one data type may be used for each data definition.
● Several variables of the same data type can be defined for each data definition.
Syntax
LUD and PUD
DEF <type> <phys_unit> <limit values> <name>[<value_1>, <value_2>,
<value_3>]=<init_value>
GUD
DEF <range> <pp_stop> <access_rights> <data class> <type>
<phys_unit> <limit values> <name>[<value_1>, <value_2>,
<value_3>]=<init_value>
Meaning
DEF: Command for defining GUD, PUD, LUD user variables
<range>: Range of validity, only relevant for GUD:
NC: NC-global user variable
CHAN: Channel-global user variable
<PP_stop>: Preprocessing stop, only relevant for GUD (optional)
SYNR: Preprocessing stop when reading
SYNW: Preprocessing stop when writing
SYNRW: Preprocessing stop when reading/writing
<access rights>: Protection level for reading/writing GUD via NC program or OPI (optional)
APRP <protection level>: Read: NC program
APWP <protection level>: Write: NC program
APRB <protection level>: Read: OPI
APWB <protection level>: Write: OPI
<protection level>: Range of values: 0 ... 7
See "Attribute: Access rights (APR, APW, APRP, APWP, APRB, APWB)
(Page 412)"
<data class>: Data class assignment (only SINUMERIK 828D)
DCM: Data class M (= Manufacturer)
DCI: Data class I (= Individual)
DCU: Data class U (= User)
Work preparation
3.1 Flexible NC programming
NC programming
398 Programming Manual, 12/2019, 6FC5398-2EP40-0BA0
To Next Page
Loading...
Need help?
General
