January 2012 8.1 PLC Functions 1483
Individual structure elements are accessed by indexes (except for the "General
data" group).
Example of a PLC command line:
L PlcApiAxis[x].NN_AxInMotion
IFT
...
ENDI
ApiMarker.def
definition file
HEIDENHAIN makes the ApiMarker.def file available to the PLC developer. As
soon as the file is included in the PLC program via the INCLUDE command, the
control uses the symbolic API 3.0. Collected in structures, the file contains all
symbolic PLC operands.
Example:
* ==================================================
#TYPEDEF PlcApiAxis
* ==================================================
internal D
NN_AxLogNumber D * logical axis number
NN_AxDriveReady M * drive is ready to work
PP_AxDriveOnRequest M * drive on request
NN_AxDriveOn M * drive is on
.
.
.
HEIDENHAIN releases a revised version of the ApiMarker.def file at irregular
intervals. The most recent version of the ApiMarker.def file is automatically
transferred to the control when the NC software is updated. The old
ApiMarker.def file in the main directory of the PLC program will not be
overwritten in order to ensure executability of the PLC program.
After an update of the NC software, you will find the current version of the file
in the following directory of the control:
PLC:\proto\plc\ApiMarker.def
You can also find the file on the HESIS Web Including FileBase on the Internet
at http://filebase.heidenhain.de.
Further information about working with indexed structures is provided in
the online help of PLCdesignNT.
The ApiMarker.def file is located on the PLC partition of the control.
To Next Page
Loading...
