[RuslanRobot]

Good day!

Help please.

Here is the InitKstep4axis file (compiled without errors). I configured the INIT button on the KMotionCNC panel that runs file InitKstep4axis.
Before flashing, when the machine is turned on, I press the INIT button twice (I load the KMotionCNC file two times), the first time I press it, the motors go into hold mode, but the axes remain yellow and do not move. The second time I press INIT, the - axes become active (green) and I can start working.
Then I made flashing Kflop (download InitKstep4axis into User Memory). The engines started to go on hold automatically (I don't need to run the InitKstep4axis file), but the axes still remain inactive (yellow). Only after an additional run (now on?e) of the InitKstep4axis file, the axes become active (green) and I can start working.

What do I need to do, so that the axes become active (green) immediately automatically in KMotionCNC, without the need to additionally run the InitKstep4axis file?

[TomKerekes]

Hi,

The KStep Opto Inputs require a small amount of time (a few time slices) to be fully configured and to begin updating. So the inputs should not be tested until a short time after KFLOP is informed that a KStep is present. KStep Opto Inputs will be 0 after power up until updated which is your condition for EStop. Try adding a 10 millisecond delay after setting KStepPresent such as:

    KStepPresent=TRUE;
    Delay_sec(0.01);

We don't recommend Flashing anything to KFLOP. See here. You can restore KFLOP to its original state by re-Flashing New Version.


Note this code is not indented properly and confusing using double NOTs.

        // if ESTOP present disable any enabled Axis ??
if (!ReadBit(ESTOP_BIT)!=0)

Simpler would be:

        // if ESTOP present disable any enabled Axis ??
        if (ReadBit(ESTOP_BIT)==0)

HTH

[RuslanRobot]

YES! Work. Thank you!