Hmm. That is the version I have and I did not apply the fix from the other thread. I didn’t do any updates to that image since January which was before the troubles seemed to start.
Trivial request: The “Connect to Cutter” button gives no indication that it’s been pressed. I see 5-10 second delay between pressing it and seeing any reaction from the SO5 or CM. The Initialize button does dim when it is pressed though.
Hey Rob and Will, i downloaded CM 621 last week and from the first time i opened it and set my machine up until now, it takes as long as 9 min to start up when opening. Once CM finally lets me initialize it runs without flaw, its just at start up.
Ive done the normal things a non computer wizard like me does and uninstalled it and re-downloaded from the website 3 times now with same results. Once in awhile when starting up it will show the “not responding” for just a sec and if i just wait it will evently load. No support ticket has been sent, ive just been kind of putting up with it and watching the forum for a fix but it could just be my DA.
Have you gents heard of anything similar going on and maybe have a fix i just didnt see in the forum? I hate to bug support on it.
Have you tried the standard troubleshooting techniques?
shutdown
reboot
check for updates
reboot
Is this on Mac OS or Windows?
If on Windows, please go to the Start Menu, type “sysinfo”, run the System Information tool and save the output from it as a text file using your last and first name and send that in to us
Either platform, please let us know about this at support@carbide3d.com and we will try to look into this with you.
After sending (or loading I suspect) a new project I just found the feedrate adjustment I used for the previous run enabled. This would have made the new run go WAY too fast. I would prefer that each new loaded/sent run reset feedrate. Rerunning the same project could keep the feedrate adjustment, but I think that is a little dangerous as well.
Hey All
New Bullseye upgrade killed CM Pi. CM cant see the machine after a update
So here is the story, I got a brand new Rpi 4 back in Sept. this morning I decided to get it running. New Bullseye install and loaded CM 622 and it was working fine. A couple glitches I noticed later on that.
The boot loader chip was from Sept or more. I skipped the check for updates during the install. And then after testing the new CM 622 it was time to run the update ( Icon on the top ribbon). I rebooted and then could no longer detect the machine. Hmm
By chance I had ordered 2 new Rpi 4s so I had another original SDchip. I cloned it over the failed one and did it again. Same thing; it ran fine until the upgrade
One note I also tested the old CM 547. which also worked pre update and then failed to see the machine after the update
I can only assume a new library was updated and some function was depreciated. That’s a big guess there
So my word of caution is not to update your Rpi OS without a copy of you SD
Has anyone else stopped connecting after the last update ???
Luckily I still have my Rpi 3 with CM547 working, so I am not down and I can load a older bullseye. Just can update
And now it is 3:30 in the morning and I have way too much time into this Time for bed
I found a couple of items in CM 622 on Rpi
I just played with it and did air cuts
It says you can skip the upload of the config to the machine if you are sure it is good or something like that. But then how do skip it ?, you have to hit the load in order for the NEXT button to activate, did I miss something?
I have a Pro XXL and Y should be 850 not 859. I can jog until it hits and crashes into the front support caps. Unlike the older versions, you cant tweak these settings any more The setup wizard is nice but Hmmm. We will get there I assume the 0 and 9 are side by side on the top of the keyboard so this is most likely a typo in the default config for that machine ?
OK I had a bit more time, just a bit
I took my old Rpi3 running bullseye that I mentioned above and cloned it.
I then hit the update button on the right hand side of the menu bar.
Updated fine but CM could not connect same as above.
All I can conclude is a Library was updated and it no longer supports a function call that CM is calling for to connect to the USB device.
The USB is recognized by the OS. you can see it come and go in “lsusb” when you plug it in and out. Just cant seem to talk to it anymore.
OK
so to all you Rpi CM users. make sure you have a backup up. DO NOT run the updates.
Awesome
Thanks
I will try that. Maybe tomorrow.
I do see that I have that version in the machine that online right now, strange I have it in 3 systems or more. More strange that it been around so long without a fix. Hmmmm
LOL I hear that
I am busy for a couple of days but will update if it fixed the issue. It looks promising. Very strange it has not been resolved yet in the updates.
I only had a bit of time but it appears it may have worked
The Wget statement did not work for me so I cut and pasted it in.
I read some of the bug, Interesting it goes way back, so is it a permeant fix or a temp fix. Have they change the way they support the Symlink and this may not be a place to tap in to any more. It looks like it was said one Symlink worked but not another. What do I know
Thanks again