Software Issue?

[bkhutchison55 (BK Hutchison)]

I just upgraded to a new Windows 11 Tablet (Fusion5). Downloaded the latest Carbide Motion Build 364. I can connect to the cutter, but it will not initialize. It starts but does not bring the spindle forward for a bit change, doesn’t go to bitsetter. Further, Under Jog - Rapid Motion, it moves maybe an inch and stops.

My first actions was to delete Carbide Motion and the reinstall. Didn’t help.

I thought maybe the Shapeko Pro was “acting up”, but then decided to use my old Windows 10 tablet, which I had previously been using - the micro TF Card slot failed - which is why I changed tablets.

With the Windows 10 tablet - Carbide Motion Build 537, it works perfectly. Initialized, goes to bit change, goes to Bitsetter, zeros correctly.

Any thoughts on what might be wrong?

[Nessk (Kenneth)]

Latest build is 564.
https://carbide3d.com/carbidemotion/download/

But to me it sounds like the machine size is not defined. Select your machine and send configuration. After that’s done, carbide motion will put realistic limits for the travel.

If not, email support or wait for @WillAdams

[WillAdams (William Adams (Carbide 3D))]

Correct.

Each computer you install Carbide Motion on needs to be configured for machine type/size/accessories. See:

Setting Grbl Configuration in CM 517 and later

Carbide Motion 517 uses a new system for setting Travel Dimensions which is potentially confusing: [image] Pressing the Load Defaults button takes one to a window which allows one to select first machine size: [image] and then Z-axis type: [image] after which selection the Travel Dimensions for the selections made are entered into the dialog and will be preserved if one clicks “Ok” (and of course that change discarded if one selects “Cancel”). In addition there is a “Send Configuration…

[bkhutchison55 (BK Hutchison)]

Thank you. Got it up and running!

[bkhutchison55 (BK Hutchison)]

Thank you! Got it up and running. I’m learning everyday.

[gdon_2003 (Guy Donham)]

When you send the configuration you are of course configuring the Shapeoko but you are also configuring CM. The Shapeoko knows what it is from the last time you sent a configuration but a new instance of CM does not know what you are attached to except it is a Shapeoko.

Even upgrading CM to a new version you should always send the configuration mostly to connfigure CM.