beckhoff TwinCAT 2 — 5.6 Process image of an NC axis

TwinCAT NC Axis components 5.6 Process image of an NC axis The process image of an axis is used to connect it to different drive components. In the simplest case, a link is established between the axis and the drive and the necessary links between the process images are made automatically. In individual cases, in particular when unknown hardware components are integrated in the system, these links must be established manually. To this end, the process image of an NC axis is described in the following. NOTICE The data structures described here form an internal interface between NC drivers and connected drive hardware.

This interface is constantly under development and can change in the future. Encoder process image of an axis Various encoder hardware or the corresponding Bus Terminals for detecting the position of an axis are connected via the encoder process image (cyclic data exchange). Insofar as this hardware is directly supported by the system, no manual configuration of individual variables is necessary. Input data to the encoder process image of an axis Numerical Control (NC) Basics 43 Version: 1.2 I/O variable Description Remark nInData1 Current actual position of the encoder or the drive in increments.

The incremental value is processed by the NC and converted to the actual position in physical units, e.g. mm or degrees. Overflows of the incremental values are also counted by the NC. The system normally makes no distinction between incremental and absolute encoders (see also encoder parameter Reference System INC/ ABS). Unit: increments [INC] Data type: DINT (32 bit). sometimes also INT (16 bit) nInData2 Optional actual latch position of the encoder or the drive in increments. The incremental value is processed by the NC and converted to the actual position in physical units, e.g. mm or degrees. (see also function block MC TouchProbe _ TcMc.lib). Unit: increments [INC] Data type:

DINT (32 bit). sometimes also INT (16 bit) nStatus1 Optional status information e.g.: Participant in Data Exchange, Encoder Error, communication to Position Latch or Register Communication. This information depends on the type of encoder or drive. nStatus2 Additional optional status information e.g.: Communication to Position Latch, communication Encoder Reset, communication to Read an Absolute Position This information depends on the type of encoder or drive. nStatus3 reserved nStatus4 Optional field bus-dependent IO status such as WcState (Working Counter) in the case of EtherCAT or CdIState in the case of Beckhoff Lightbus. Meaning: 0 = I/O data valid 1 = I/O data invalid