The program always hangs after the command M3

Hi,

Can someone please help with the following problem?
Whenever located in program command M3, stops the program, and it can not run further.
The tool is replaced and agree with the tool number in the program.
I provided that the program is waiting for a signal to achieve the required spindle speed.
Also in MDI mode, the M3 command switches the relay but this immediately switched off.
Pin 14 of parallel port is configured to ON (non-PWM).
I read even this forum:
forum.linuxcnc.org/forum/20-g-code/21087-m3-stops-axis-movement
Unfortunately I do not know what should I do or change.
Thank you in advance for any help.

Not the spindle speed is always specified - S has always been stated.

Thanks for your reply.
I use a probe to isolation milling PCB - auto leveling. But the probe is not a problem. I tried to remove - did not help. The tools are all defined.
Is there need something somehow to change this:
spindle-at-speed
...?

In Gmoccapy - When I click on the icon, the spindle starts to spin without problems.

Attached is an example of a program that operates without line 3. If the line 3 S1000M3 present, the program stops on the line 7th.

I think the problem might be the spindle at speed, You have it connected to a signal, but that signal isn't connected to anything
net spindle-at-speed => motion.spindle-at-speed
If you are going to use that pin I think you need to connect it to a digital output from your vfd.
Try this as a test, start a milling file, and while the machine paused after a spindle start command, open Halshow (in the AXIS menu under Machine/Show HAL Configuration) then in the Test Hal Command box type
sets spindle-at-speed true
Then press Execute.
If the file then resumes running you need to connect an output to the "spindle-at-speed" signal. This can be either a proper digital signal from your VFD or a dummy signal from a delay timer. (or just comment out or remove the line "net spindle-at-speed => motion.spindle-at-speed" in your hal file (if you can live with the program not waiting for the spindle to get up to speed). Alternatively you can live with out a spindle up to speed signal by simply programming a G4 pause command in the G-code after your spindle starts.

Thanks for your reply.

After typing: sets spindle-at-speed true
resumes program run.
Deleting a "net spindle-at-speed => motion.spindle-at-speed" in the configuration file ends with an error message.
Inserting a G4 pause will not help.