Advanced Search

Thank you very much! I will do that tomorrow (german time) and report the result!
Have a nice day!
Sincerely,
Hanno

Ok

issue of not being able to cut arcs due to radius error is sorted. User error as normal. For some reason I had it in my head that the statements in the gcode regarding the hole processing were commented out with a #. When I did actually comment them out with a ; the code loaded and ran with no issue.

the realtime error is possibly resolved but will know for sure when I do some more cutting tomorrow. I changed the Ethernet cable and also removed the WiFi nic. Will do more testing tomorrow and update the post if I can confirm which cured the issue, if it is cured that is.

Doesn't even look like the current hal file would run
as there are two different signals connected to
hm2_7i76e.0.7i76.0.0.spinout:

net pdnt.spindle-speed-abs => hm2_7i76e.0.7i76.0.0.spinout
#net spindle-vel-cmd-rps-abs => hm2_7i76e.0.7i76.0.0.spinout
net pdnt.spindle.is-on => hm2_7i76e.0.7i76.0.0.spinena
net spindle-cw => hm2_7i76e.0.7i76.0.0.spindir
net spindle-vel-cmd-rpm-abs <= spindle.0.speed-out-abs => hm2_7i76e.0.7i76.0.0.spinout

I would first get things running in the usual way by adding

net spindle.0.on => hm2_7i76e.0.7i76.0.0.spinena

commenting out

net pdnt.spindle.is-on => hm2_7i76e.0.7i76.0.0.spinena

and uncommenting:

#net spindle-enable             <=  spindle.0.on

When this is working I would look into the pendant spindle control options