I'm having issues with F360 always posting M0 commands, even though I turn optional stop off in the post process options. Searching around, I believe that's the right function for posting M0's, so stop me if I'm wrong.
I'm using the TinyG config that comes stock for F360.
Obviously, I can go in and CTRL+F to find and delete these, but boy is it annoying doing it for EVERY file.
M0 is a *Program Stop* and is usually put there for some good reason. (Check a tool, Check a dimension, etc)
M1 is a *Optional Stop* that can be overridden at your control.
Where are M0's posting in your code? Can you attach an example as well as your post processor?
Is the option for Manual tool change set for the tool in your tool library?
IS the Gcode one toolpath or many with the same tool, and can you post a Gcode with this problem put it in the code tags popup click on this above to get it to pop up </>
@Anonymous wrote:M0 is a *Program Stop* and is usually put there for some good reason. (Check a tool, Check a dimension, etc)
M1 is a *Optional Stop* that can be overridden at your control.
Where are M0's posting in your code? Can you attach an example as well as your post processor?
That's good info to know. Usually I flip on the M6 toggle for tool changes. While writing up this post about where the M0's are, I realized that I had changed the tool for the second operation, but never changed it for the first 😩. That explains the second M0. I'm still not sure why the program puts the first one in right at the beginning, but maybe that's just standard, and I didn't notice it until I noticed the second one.
Anyways, apologies for the waste of time. Once again the problem is user error.
Without seeing the program I am guessing that the M0 is at ANY tool change. The one at the beginning is there because if you finished program with second tool you would need to change tools back to the first for the restart of the program.
Can't find what you're looking for? Ask the community or share your knowledge.