[shawnrw]

Gents,

While doing my first test run on aluminum today I received some phantom limit switch activations. I assume adjusting the de bounce, adding shielding and checking connections will address this problem.

My question is what is the best way to restart the code? After the event it often gives a radius error and forces me to select begin from this line. After selecting begin from this line, the code scrolls through, ask me if it's ok to move the tool and then starts working again. The problem is it scrapes across the face of material, skips forward in the gcode missing machining portions and often scraping the material surface where it is not supposed to as it moves to another section.

Open to any ideas, best practices to help correct this...

Thanks for the help..

Regards,
Shawn

[ger21]

Assumung you're using Mach3, try enabling Safe Z (Config > Safe Z)

That should prevent it from dragging across the workpiece.

[shawnrw]

ger21,

Once again thanks for the help.. I will try and report back.

Regards,
Shawn

[RCaffin]

what is the best way to restart the code?

Don't.
Fix the hardware problems instead.
No matter what SW fix you come up with, hardware glitches (mainly noise) will defeat all your attempts.

Cheers
Roger