Hello
I am new to the group and very pleased to be here as I can’t believe what great things are happening here. I built my own cnc machine 2 years ago so have some experience with things. I use Mach 3 on my machine. I wish I could do something to help but tonight I have a couple of questions.
What software are most people using?
How can you set the order of cut? I have the problem of cutting the outside of a job, have it fall off then of course nothing there for the machine to cut.
Once I set a zero location is there anyway to get back to that location?
Is there anyway to find how long the job will take or a progress indicator when it may be done?
Is it possible to stop the job if something goes wrong other than the emergency stop as it seems the “abort job” seems very slow? I don’t like to hit the stops on the table if I make a mistake.
Is there any type of soft limit of the table that will indicate if your job may
run off the table where its set up?
If there is a spot that does not cut out is there anyway to return to that spot via the gcode and continue the cut from that spot?
I use the queued commands number to manually estimate the job time. As I usually record via webcam (in case I have issues, I can use to report) I can see time elapsed (you could use stopwatch maybe) & then just calculate based on how many queue items I started with, how many are left & how long it has currently taken. Or alternatively, I calculate based off how many mm on the Y-axis has been done & how many more mm on the Y-axis are left.
+Peter van der Walt Could we display the queued items as Total : NumberLeft : % completed? Won’t give an estimated time, but will at least make it simple to determine how much has been done already & can manually work out the time left easier.
I’m curious, if I fork & add that into the code (or something else at a later date), how do I make it so you can merge it?
@Yuusuf_Sallahuddin_Y The “normal” way to submit a feature via Github is to fork the project, clone your fork to your local machine, make a feature branch, commit to the feature branch, push the feature branch back to your forked project, and then generate a pull request from your branch on your fork. It sounds like a lot of steps, but it goes very quickly. There is a firehose of information on this here: https://help.github.com/categories/collaborating-on-projects-using-issues-and-pull-requests/