2
ID24
17.12.3
Reading and writing PLC variables
DB4900
PLC variables [r/w]
PLC interface
Byte
Bit 7
0
1
2
...
4094
4095
Note
The programming engineer (NCK and PLC) is responsible for organizing (structuring) this memory area. Every storage
position in the memory can be addressed provided that the limit is selected according to the appropriate data format (i.e. a
'DWORD' for a 4byte limit, a WORD for a 2byte limit, etc.). The memory area is always accessed with the information about
the data type and the position offset within the memory area. The PLC variables can be read or written in the NC program
$A_DBB[n] ("n" stands for the position offset in bytes).
17.13
Axis actual values and distance-to-go
DB5700 ...
Signals from axis/spindle [r]
5704
NCK -> PLC interface
Byte
Bit 7
0
4
Note
The axis actual values and distances-to-go can be separately requested:
DB2600.DBX0001.1 Request axis actual values
•
DB2600.DBX0001.2 Request axis distances-to-go
•
If the particular request is set, then the NCK supplies these values for all axes.
17.14
Maintenance scheduler: User interface
17.14.1
Initial (start) data
DB9903
Initial data table [r16]
Byte
Bit 7
0
2
4
6
8
10
11
14
...
438
Synchronized action with ID...can be blocked from the PLC
ID23
ID22
Bit 6
Bit 5
Bit 6
Bit 5
Axis distance-to-go (REAL)
Bit 6
Bit 5
Number of warnings to be output 1
Number of warnings to be output 2
ID21
ID20
Bit 4
Bit 3
Offset [0]
Offset [1]
Offset [2]
...
Offset [4094]
Offset [4095]
Bit 4
Bit 3
Axis actual value (REAL)
Bit 4
Bit 3
Interval 1 [h]
Time of first warning 1 [h]
Reserved 1
Interval 2 [h]
Time of first warning 2 [h]
Reserved 2
...
ID19
ID18
Bit 2
Bit 1
Bit 2
Bit 1
Bit 2
Bit 1
Commissioning Manual
6FC5397-4EP10-0BA8, 07/2018
ID17
Bit 0
Bit 0
Bit 0