To prevent this from happening, the curve tables concerned can be locked, using the
CTABLOCK(...) language command. In this case, it should be noted that the curve tables
concerned are then unlocked with CTABUNLOCK().
●
Table n
CTABISLOCK(n)
Result:
> 0: Table is blocked
Reason for block:
1: by CTABLOCK()
2: by an active coupling
3: by CTABLOCK()and by an active coupling
= 0: Table is not blocked
- 1: Table does not exist
● Check whether the curve table exists
CTABEXISTS(n)
Result:
1: Table exists
0: Table does not exist
●
CTABMEMTYP(n)
Result:
0: Table in static SRAM NC memory
1: Table in dynamic "DRAM" NC memory
-1: Table does not exist
● by an active coupling periodic
CTABPERIOD(n)
Result:
0: Table is not periodic
1: Table is periodic in the leading axis
2: Table is periodic in the leading and following axes
-1: Table does not exist
b) Curve table segments
● Determine number of used curve segments of the type memType in the memory range.
● CTABSEG(memType, segType)
● If memType is not specified, the memory type specified in the following machine data:
MD20905 $MC_CTAB_DEFAULT_MEMORY_TYPE
Result:
>= 0: Number of curve segments
-2: Invalid memory type
If segType is not specified, the sum is produced via linear and polynomisl segments in the
memory type.
-2: segType not equal "L" or "P"
Axes and spindles
Function Manual, 06/2019, A5E47437747B AA
Determine block condition
Determine memory type of a curve table
M3: Coupled axes
14.2 Curve tables
449