10-22-2019, 05:04 AM
(10-21-2019, 11:27 PM)Gordax Wrote:move cloc( 0, 400, 0, 300, 0, 0, 0, 0, 0)The position flags are manipulated with loc_flags_get() and loc_flags_set() functions as described in the RAPL-3 reference:
Its throws an error and asks for position Flag
Code:
全球const LOC_INVALID = 0 x00
global const LOC_VALID =0x01
global const LOC_CALIBRATE =0x02
global const LOC_MARKER =0x04
global const LOC_NULL =0x08
global const LOC_METRIC =0x10
global const LOC_TOOL =0x20
global const LOC_BASE =0x40
global const LOC_OFFSET=0x80
Probably you need at least LOC_VALID and might want LOC_METRIC and LOC_BASE.
You can take current position with here() and use loc_flags_get() and loc_cdata_get() to see what kind of flags and position it uses by default.
The manual has some examples where cloc constants are used as arguments to e.g. tool shift, in which case the flags don't seem to matter. But when passing it to move() directly, you need to set them.