Run from line problem

Thanks for investigating. At least the fact that you can get the same behaviour on a sim means that there is some chance of tracking down the issue.

I had some time in the workshop today, testing on the machine. Testing run from line.
Behaviour is as the simulation, most subroutines as described before are executed before jumping to startline, which is pretty bad. Having a long drill clamped, but the subroutine is supposed to do some engraving...
(DEBUG, RPM: #<_rpm>) is showing a value, M3 is there, but motion.spindle-at-speed is 0, and the machine is moving without rpm. Helpless how to make all that bulletproof, i am going to use my workaround at the moment. Just in case someone can discover spindle misconfiguration in hal. I had to use timedelay for the spindle to speed up. G4 P4 made a mess, hard to escape, if pause button was pressed during dwell.
Thanks for help so far.

did you set the defaulte in DISPLAY section INI file
DEFAULT_SPINDLE_SPEED = 1000 - The default spindle RPM when the spindle is started in manual mode. if this setting is not present, this defaults to 1 RPM for AXIS and 300 RPM for gmoccapy.

ini entry DEFAULT_SPINDLE_SPEED = 6000 is there for the ac spindle.
and hal with lincurve works perfect, any rpm lower than 6000 set to 6000 rpm, if I run program.
This problem beside a few more problems exist only when run from line, otherwise everything is fine.

If you put [code](DEBUG, Task Mode = #<_task>) in the G-code subroutines what do you see? And is that different between normal use and run-from-line?
(I am wondering if the graphical preview and run-from-line are causing bother together)

Did some testing this evening, the result is the same for both, value returned=1.
I also did hal watch the pins for spindle. If i do run from line, there are no pin changes at all, spindle-brake is the only yellow marker but the machine is running the program, without M3.Start the spindle in MDI, and then run from line is possible.