Which HF data can be collected via SINUMERIK Connector?

CYCLE

The actual cycle counter which will be increased on every position control cycle. This is an ID for the time slice.

This data point can be used to synchronize data of different qualities.  

limited: (2^32/2) -1 values: 0 - 2147483647

This data point can only be used if at least one other available HF data point has been subscribed in acquisition mode "High frequency data". Otherwise, the configuration will be rejected.

HF_EVENT

This data point must be configured if HF events like “block events” or “sub program calls events” are to be received.

string

This data point can only be used if at least one other available HF data point has been subscribed in acquisition mode "High frequency data". Otherwise, the configuration will be rejected.

ENC_POS

Actual position of the active encoder

mm or degree

-

DES_POS

Position command after the fine interpolator (correspond to cmdContrPos in opi, but without filter and compensation values)

mm or degree

-

CTRL_POS

Position at the input of the position controller (includes the filters and the feed forward balancing)

mm or degree

-

CTRL_DIFF

Position controller input difference including compensation of DSC effects (same value as the system trace offers in opi trackErrContr)

mm or degree

-

CTRL_DIFF2

Position controller input difference without DSC compensation (available in HF_Probe only)

mm or degree

-

CONT_DEV

Contour difference (lag – lag-model correspond to opi trackErrDiff)

mm or degree

-

VEL_FFW

Velocity feed forward to be added to the position controller output

mm/s or degree/s

-

TORQUE_FFW

Torque/force feed forward the NC sends to the drive

Nm or N

-

CMD_SPEED

Speed command the NC sends to the drive

mm/s or degree/s

-

ENC1_POS

Actual position of encoder 1

mm or degree

-

ENC2_POS

Actual position of encoder 2

mm or degree

-

TORQUE

Drive momentum setpoint ($VA_TORQUE, aaTorque)

Nm or N

-

POWER

Drive actual power ($VA_POWER, aaPower )

W

-

CURRENT

Drive actual current ($VA_CURR, aaCurr)

A

-

LOAD

Drive load ($VA_LOAD, aaLoad)

%

-

A_DBD

Read the Synchronous Action variable $A_DBD[]. This can be used, to read values from the PLC by using the FB {} in your PLC program. Give the varIndex as the byte address of the 32 bit integer in the "A_DB" DB. The varIndex must be a multiple of 4 within the range 0 … 4092.

Attention: Do not use this variable for time critical use cases. Depending on the amount data written by the PLC program, a new value may need several bus cycles to get updated.

Attention: Subscribing to PLC parameters will lead to more NC load.

32-bit signed integer

-

A_DBR

Read the Synchronous Action variable $A_DBR[]. This can be used, to read values from the PLC by using the FB {} in your PLC program. Give the varIndex as the byte address of the 32 bit integer in the "A_DB" DB. The varIndex must be a multiple of 4 within the range 0 … 4092.

Attention: Do not use this variable for time critical use cases. Depending on the amount data written by the PLC program, a new value may need several bus cycles to get updated.

Attention: Subscribing to PLC parameters will lead to more NC load.

32-bit IEEE float

-

A_DLD

Reads an NCU-link variable. Give the index as the byte address of the 32 bit integer in the "A_DB" DB. The varIndex must be a multiple of 4 within the range 0…$MN_MM_SIZEOF_LINKVAR_DATA.

Attention: Do not use this variable for time critical use cases. Depending on the amount data written by the PLC program, a new value may need several bus cycles to get updated.

Attention: Subscribing to PLC parameters will lead to more NC load.

32-bit signed integer

-

A_DLR

Reads an NCU-link variable. Give the index as the byte address of the 32bit integer in the "A_DB" DB. The varIndex must be a multiple of 4 within the range 0…$MN_MM_SIZEOF_LINKVAR_DATA.

Attention: Do not use this variable for time critical use cases. Depending on the amount data written by the PLC program, a new value may need several bus cycles to get updated.

Attention: Subscribing to PLC parameters will lead to more NC load.

32-bit IEEE float

-

DPIO_IN2

Read a value from one of the NC "DPIO" Profibus/Profinet input ranges. Must be a multiple of the value type byte count (2 for 16-bit int). Interpret it like this: the thousands position specifies the DPIO range index [ 0 … 31 ], the three lower positions specify the byte offset within the range [ 0 … 126 ] e.g.: 15042 specifies a variable starting at byte offset 42 within the DPIO range index 15. The same information can be read from the Synchronous Action variable $A_DPSW_IN[15,42] (but this is updated in the IPO-cycle only). This variable can be used e.g. for reading values from analog sensors that are converted using an ET200 module connected to the NC via PROFINET IRT.

Attention: Do not use this variable for time critical use cases. Depending on the amount data written by the PLC program, a new value may need several bus cycles to get updated.

Attention: Subscribing to PLC parameters will lead to more NC load.

16-bit signed integer

-

DPIO_IN4

Read a value from one of the NC "DPIO" PROFIBUS/PROFINET input ranges. Must be a multiple of the value type byte count (2 for 16-bit int). Interpret it like this: the thousands position specifies the DPIO range index [ 0 … 31 ], the three lower positions specify the byte offset within the range [ 0 … 126 ] e.g.: 15042 specifies a variable starting at byte offset 42 within the DPIO range index 15. The same information can be read from the Synchronous Action variable $A_DPSW_IN[15,42] (but this is updated in the IPO-cycle only). This variable can be used e.g. for reading values from analog sensors that are converted using an ET200 module connected to the NC via PROFINET IRT.

Attention: Do not use this variable for time critical use cases. Depending on the amount data written by the PLC program, a new value may need several bus cycles to get updated.

Attention: Subscribing to PLC parameters will lead to more NC load.

32-bit signed integer

-