Problem Homing DDCSV3.1

Belwect

Problem 1: when executing the Home command, the axes move to the sensors at a speed of 50 mm / min, the parameters are set to 1000 mm/min.The HOME speed does not change.Problem 2: when setting the distance of the axis departure from the sensor, for example, by 10 mm, in the parameters, the axis runs over the sensor, i.e. it works out this rebound in the wrong direction.the current firmware version is 2020-03-06-112NOR

grasvezel

Is your home position on the positive or negative side? Have you tried entering a negative value? Is the motor direction correct during other operations? It can be inverted in the settings. As for the speed, I have a similar problem where the home speed seems to be ignored. Instead Maximum M_Ctr speed seems to be used.

Belwect

The home position is on the negative side. It is not possible to enter negative values. The direction of movement in other operations is correct.

jps

so homing z at top position, ie positive end is possible?

jps

is your problem solved?

Belwect

No, the problem is not solved. The developers are not responding.

Belwect

The" 0 " of the Z axis is at the top.

jps

do you mean that the only way to make ddcnc work, is to set z zero/ 0 at the top,
or do you mean that is how you want it to be?

z "0" is normaly at the table top surface;
positive coords is away from table,
and negative coords toward the table, i.e. tool tip touching table surface = z0

but since its risky/impractical to home z at the negative end, its better to home at the top max,
and tell the system to set(offset) this position as the distance between the tool tip(spindle nose)
and table surface, so that the z machine coord displays "200" mm or whatever your true distance is,

this is how i set up my milling machine, but it was only possible after i disabled the clear/backing-off homing switch function
(because it backs off the wrong direction and crash into the hard limit)

i also have the set z homing direction "negative" to make travel/seek home in positive/up direction

so there seem to be a some sort of bug here..