Machine Initialization…nothing new here except not probing
Zeroing process…new steps to probe bit after zeroing regardless of whether that was with a BitZero or manual. Process is the same after zeroing is complete.
Job start process…difference here is that after probing bit length CM compares it against the stored bit length for validation and acts accordingly if things are out of sync.
Mid job zeroing process…difference here is that a new Z’ is persisted along with WZ being updated as per tool length delta.
A happy path workflow where the user does what he is supposed to. Followed by one where he does not. CM is able to detect that he has not and prevents the job from being ran until the situation is corrected. This is not something the current workflow can detect and would allow the user to shoot themselves in the foot.
NOTE: All this is predicated on there being a method to store a Z’, either in a previously unused grbl setting or in a file in CM.
I don’t find CM intrusive.
I have to assume there are people smarter then me that have the knowledge and history / experience to figure out the workflow. I believe CM has certain goals to meet to provide a good don’t get yourself in trouble workflow for hobby cnc machines and new users. There are other G code senders available that may be considered more advanced and have a more open workflow. And we are free to try them.
I appreciated the workflow when I first started this hobby.
My wishlist item re air passes.
Currently I do an air pass at say, 1mm above the work as a sanity check (saved my bacon this morning). Then I have to hit pause and then stop and wait until the machine initialises to 0,0. Then I go to my work piece and set the new Z height and continue.
I would like to have Air Pass as an option when I go to run my toolpaths, so I can say Yes, or No and continue.
No need to disable/reenable bitsetter for large batches. Just save the carbide file as gcode, open and remove m6 command, save and run that file instead of carbide file.
Wow, Carbide 3D, do I get a cookie for the post with the largest response? Love to see all the enthusiasm guys. I’ll pass on a couple of tips that I learned recently (I know, wrong post, but this post has gotten pretty loose). The VFD with a 1.5"dia surfacing carbide 4 insert cutter should not be set to take a .070" cut in Acacia, stalled it. On Amz, you can get a box of 3 different size Acacia cutting boards for $40; they make great project matl for plaques, etc.
Sounds like we are speeding up the process, I love it!! The only other feature I would like to have is a process repeat but maybe this will shorten run times. Will suggested a way to incorporate it in the code, it works, but maybe something a bit easier to implement would be nice.
In an unrelated topic: Carbide Create needs a Command+W in the Edit menu to close a window. Every Mac app worth its salt has this. Additionally, how difficult would it be to have Carbide Create remain “Open” or running when a window is closed? The application currently “Quits” when a window is closed and does not seem to support two open files at the same time. We should be able to have two instances or files open at the same time. That would make it easy to copy and paste elements between files.
That isn’t an uncommon problem with apps for OSX. One example that quickly comes to mind is the Eclipse IDE software. A simple cheat for this is to make a copy of the app in your Applications folder, giving it a different name. You can the open each individually. There are probably cases where this doesn’t work but it has been my go to when in needed.
I tried what you suggested. For a minute I thought it would work. The copy of Carbide Create did open in a separate window on my Macintosh. However, I could not copy from one instance and paste into the second one. I could only paste into the instance from which the copy was made.
I was very surprised that both copies of the program opened at once. I never thought to try that. Great experiment. I still wish they would add the Command+W to the Edit menu. Carbide Create should quit when I tell it to, not when I simply close a window.
