About 2 weeks ago, we released CM656 as a beta to help eliminate crashes related to the Qt framework we depend on by updating to the latest Qt release. We didn’t see any crashes, so we moved it to the main download page about a week later.
Since then, we’ve seen zero crashes reported in BugSplat, which exceeded all of my expectations. We’d planned to do the same for Create for the next major update, but the Motion update has been so smooth that I think we ought to update Create now.
So, if you haven’t updated Motion yet, it seems very safe. If you get any crashes, make sure to report them in the BugSplat popup. Unless we see a problem in the next week, we’ll start the Create update now.
Rob,I have used it about 4 times now and gone faultless,I used to get the drop out on doing the zeros etc prior to run on previous version,this one has so far great.Mac book air M2
That’s great to hear. We got burned by Qt years ago, and a consultant warned that most of their clients were staying with the old version we were on, so I think we were overly cautious in putting this off.
@robgrz, CM656 has been working excellently for me under Win11 on my Nucbox. As I posted in another thread, it entirely cured my jog shuttle wonkiness and the shuttle is a joy to use (which I know was your vision all along!)
The only thing I noticed is that when viewing G-Code in the preview window, you can no longer expand the pane horizontally to view the longer lines of code. This is a minor annoyance, not a big problem…
@robgrz, my only remaining issue with CM656 running my N4, is that continuous (button) Z jog is as fast on LO as it is on HI. X and Y continuous jog are noticeably slower on LO than on HI, i.e respecting the speed setting, but the Z continuous jog, even by audible frequency, is no different between the settings. Incremental/wheel jog on Z does respect the HI/LO setting, i.e. the increments are noticeably different.
I downloaded the new carbide motion a couple of days ago. All went well except for one issue.
In Carbide Create v8 I now have a very sluggish response to commands. Like, I leave a file and open a new window, there is big lag before anything happens. Sometimes the “Not Responding” message comes up. Should I reload CCv8?
It turns out that I spoke too soon. The glitchy behavior is showing up again (stuttering continuous jog, queued incremental jogs producing runaway movement (I had to use the eStop button this morning on a runaway Z- jog…) When it is good it is very very good, and when it is bad it is horrid…
This is on a Nucbox running Win 11 Pro, not connected to the Internet so no updates and a stable system.
About the jog pendant issue…i got an early one running on CM 651 several months. Have purposely not updated CM seeing other issue reports. Jog pendant was 95% reliable sometimes a little glitchy on X and Y but never Z. Last 2 weeks noticed the same issue as you…very sluggish then runaway moves. I got it in my head it was USB related don’t know why, Reboot computer and reinitialize and the issue is gone every time. Could be not the same as you but I wonder if some windows update affected.
Thanks, @mookie. My equipment has been powered up less than 24 hours–I had it unplugged since before the storm on Tuesday here. It has a 2GHz Intel N97 with 12GB RAM, running 24H2 Build 26100-3194 and has never been connected to the Internet. It’s actually kind of an overkill for a machine only running CM, ioSender and OrcaSlicer (only one at a time)… I might try running Win11Debloat on it and see if that helps things.
I’m wondering why there would be two versions of the USB driver installed… I’m wondering if one is a legacy of having the (now passed on) Nomad883 Classic+ hooked up and briefly using old CM versions (368 and 582) with it before I updated its firmware… Per @WillAdams suggestion, I need to contact Support and ask these questions…
Nope, running Win11Debloat (getting rid of as many background processes as possible), rebooting, uninstalling all C3D software, rebooting, fresh-installing only CM 656 and rebooting again (also power-cycling the N4) and doing the machine setup afresh, and the jogging issues are present from the start. Contacting support it is!
