02-27-2018, 02:55 PM
For the machine I am building I am developing a few motion programs that are often used and reused as utilities. Specifically, other NC programs that my end user will write and run should be able to call my motion programs.
I am wondering what are the pro/cons of developing these motion programs as custom MCode, volatile subprograms, or non-volatile subprograms (or something else that I have't thought of)
Goals:
* Must be able to be called from NC files that are run through the NC interface
* Sub programs should be written in motion program format including GCodes.
* Fairly easy for me as a machine integrator to see and update the subprograms
* Ideally would be nice to call them with easy human readable names instead of program numbers (nice to have if possible)
Thoughts?
I am wondering what are the pro/cons of developing these motion programs as custom MCode, volatile subprograms, or non-volatile subprograms (or something else that I have't thought of)
Goals:
* Must be able to be called from NC files that are run through the NC interface
* Sub programs should be written in motion program format including GCodes.
* Fairly easy for me as a machine integrator to see and update the subprograms
* Ideally would be nice to call them with easy human readable names instead of program numbers (nice to have if possible)
Thoughts?