When I try the recommended break in procedure CM is having the spindle go to max speed and then complaining about unsupported commands in the GCode and drops connection to the machine.
So I created a quick action with just M3 and then S6000. It still spins up to max speed so I have to stop it.
I have opened a ticket but thought someone here may have some words of wisdom.
I think I got it figured out. I added forward slashes to the start of the lines in the quick action. I also discovered that the timing appears to be in seconds, not milliseconds as the breakin procedure indicated.
So I have:
/M3S6000
/G4P1200
And then ramp that up through 9k, 12k, 18k and 24k and finish with an /M5.
Some controllers/controller software don’t recognize the P as milliseconds, and ignore it reverting to full seconds.
Mine recognizes the p as milliseconds.
But that’s why we provide it in raw text, so that you can modify as necessary. It’s only a guide anyways, and just because it’s done, doesnt mean it’s ready, but then also just because it hasn’t finished yet doesnt mean it’s not ready either. Environmental considerations and time since last used are more important than the time.
I did a write up in the Facebook group when i was using my shapeoko, but i don’t know if it’s still there since I’m on a social media hiatus. I used g4p6000 for a 6 second delay instead of having it get up to speed while cutting or moving to a cut. I didn’t use carbide motion, and if you do, that software is really restrictive with what you can do.
Actually the break in procedure worked ok but real jobs still had the ramp to max speed issue.
I finally figured it out. The machine was acting like the BitRunner was enabled even though I had switched it to VFD.
I went back into setup and could see the VFD selected but the BitRunner checked and greyed out.
I switched back to the router unchecked the box and completed setup. Then I went in again changed to the VFD and now it’s working. That may be something you could add to Carbide Motion specific instruction if the customer had both a router and a BitRunner prior to the spindle.
At some point in there the Spindle Speed change popup got selected and I had to go back through setup and make sure that was cleared.
BTW, I wasn’t busting anyone’s chops on the milliseconds vs seconds. I assumed it was a difference in the controller. I am glad I figured it out by doing a small test first though as I would not have wanted to wait 1200000 seconds.
It’s also mentioned here, and i found it by searching full. It’s also mentioned on the shapeoko 5 quick start guide, but I’ll add it to the quick start guide for those that use the Molex connector.
I can’t put special emphasis on anything, because then I’ll have to do it on everything, and if i do that, nothing gets a special emphasis.
I would love to get everyone all the information they need, but i dont know how to do that. If you have ideas I’m all ears.
I’m not trying to bust your chops either, but being in charge of documenting, i don’t know how to get all the information out there because it’s a sea of tidbits like “disable bit runner, and even if it’s ghosted, it’s still enabled”. We’re all about creating a self serve information hub because knowing the information now beats waiting for an answer and a downed machine is a missed opportunity.
I can read gcode, but writing it, that is more complex (time consuming) unless it’s a crude and basic gcode, like i could have written the bit setter gcode macro for cncjs, but neil ferreri did it better than i would have, but that doesnt mean i didn’t modify his beyond what your expected to modify.
That being said, i wrote both of the gcodes for warm up and break in which is why i put the comment for what the time was supposed to be and so you could wait 15 min at the 6k rpm mark and scratch your head. It’s better to err on the side of caution, otherwise 10 min for some could be .6 seconds for others, and that’ll be bad. I was able to get g4p6000 to work for 6 seconds when i was using cncjs and my shapeoko 3. Must be another thing that carbide motion does on its own.
