Hey!
I just upgraded carbide motion today to 617, and my Bitrunner seems to have stopped working. When I was on 582 it was working well, I have tried to follow the steps in the wizard, and every time under debug it still shows “bitRunnerEnabled”:false. I have used the switch on the Bitrunner and set it to “On” instead of “Auto” and confirmed that the router and those connections are working. Any advise is appreciated!
My setup:
Shapeoko3 Standard
Bitrunner v1
Bitsetter v1
Bitzero v1
Dewalt DWP611
With version 617 we’ve lost some functionality and gain some annoyance :
no more option to set the BitSetter position (so if you change $100 and $101… you might not be able to reach the BitSetter as you can’t set the new position)
no more option for BitRunner for those who have one
For each spindle speed change, we get a popup dialog asking us to set the speed… it’s a VFD controlled spindle… the gcode does this !
sometimes the “Jog” menu jus disappear (even if connected and was used just before… I saw this a few times going in and out of MDI and Jog disappear)
Full screen toggle… get you to full screen… trying to get out … not always.
I’m thinking of going back to a 5xx version as this release brings more annoyance and bugs than actual useful feature (at least for me with a Shapeoko Pro Standard and a VFD Spindle).
Yes, the spindle speed prompt is a problem for sure. I tried forcing it to stop by choosing the router and unchecking that notification, then changing to the Spindle where it’s grayed out, but no dice. That’s the issue I came searching for today.
I’ve also seen people talking on Facebook about how it’s noticeably slower to start and find the machine. I have also seen some folks talking about disliking the new “bit change location” but I think that’s a definite upgrade.
I would like to see a way to choose the router vs spindle easier than having to completely set up a new machine. Or the option to save two configurations.
I have not seen people swapping their router and spindle back and forth. When you run two machines with the same instance of Carbide Motion then CM remembers the last machine used and uses that. I used to have two machines and had to send the configuration if the machine in current use was different from the last time I used CM. When you send a configuration you are mostly setting up CM. The machine knows what it is but CM remembers what the Z is and where the BitSetter is located along with several other things. So on two or more machines it cannot know about the second machine until you tell it about it., CM assumes it is (second machine) was the last one used.
