Hmm, that’s odd. I just “upgraded” from 537, maybe I shouldn’t have. I never change a tool with the bitsetter without using the tool change button, so I guess I don’t really see the purpose of the dialogue at all. I was hoping it was going to be a one time dialogue, but apparently not.
1 Like
My assumption is people change tools without using “change tool” button and this behaviour was associated with jogging manually prior to changing, so this was added to cut down on support calls.
1 Like
Sure, I get that I guess, hence the preference. I feel like it could be on by default, but a simple preference to shut it off.
if (changeToolPreferece = 0) {
displayToolDialogue();
}
There, fixed.
1 Like
I’m a coding naming pedant, and insist you correct your variable name’s spelling. Also, it’s == not =. And it might be good to say getPreference(“changeToolDialog”) to save an unnecessarily verbose prior preference fetch…
Bah… it’s the weekend. Must stop pretending it’s work.
(edit: I’m being silly in case it’s not clear)
3 Likes
LOL, I like to use all different naming conventions to confuse myself, it’s more fun that way.
Stupid =, I wish I would say I meant to do that, but sadly it’s my most common syntax error.
lol, yep, got that.
1 Like
I completely understand the support issue around people changing the bit without letting the machine know and the need to remind people. If that is the actual reason for the message ? However should everyone suffer because a handful need to be reminded every time. 
I personally only need to be told 8 times 
. Do the needs of the one out way the needs of the many ?
I believe it is common practice for educational or reminder messages to have the check box. "Don’t ask again ". Are not user’s just asking for what is already a common or best practice.
With how many times users have provided feedback on this, it seems obvious to me that although with best intentions, it might have missed the mark and that maybe there is a better way to deal with this support issue. If in fact it is just a reminded. Could we not just have a one line reminder at the top of the jog window without the need to click.
However, I still love CM and will keep clicking it
1 Like
Totally agree!!! Most of my runs take from 3 to 5 minutes and I have to click on the damn popup 3 to 5 times for each? Change the bit: I rarely change bits. Change the speed to 18000 rpm? Does my router actually go that fast? Turn off the spendle? Why? Just move it out of my way and let me run the project again.
I second the idea for a “don’t show me this message again check box” or “Never show them to me again”
Oh, and if you hit resume too soon, you then have to hit start again, making yet another time I have to dismiss the model.
An alternative is a permanent on screen indicator, with some text in it, that is red when you can’t change the tool, and green when you can. Requires no interaction but is an easy instruction for new users - “don’t change the tool if the indicator is red”.
As a bonus, it would remove the need to fix the wrong spelling of ‘necessary’ too
3 Likes
My biggest problem with it is I don’t really think it even solves the problem I’m assuming it was designed to fix. Most of the time if I change a bit without using the tool change button, I would do it AFTER jogging the tool, not before. For instance, I might (first dismiss the message), move my tool to the center, change out for my dial indicator, then put my previous bit back in and do a tool change. In that case (which is literally the only time I change my bit without the button) I dismissed the dialogue anyway and still have to go back to another screen to re-measure the tool.
Hey folks, is there an ETA for support for the new spindle kit? Just got mine last week, and I’m looking forward to trying it out. Once you’ve gone Pi, you really don’t want to go back to a laptop
1 Like
After setting the max RPM in GRBL, have had no issues using build 537. The only hiccup I’ve noticed is that manually hitting the “Spindle on” button will be at a speed that isn’t enough to kick in the VFD. Not a major issue in regular running, was only when setting up the dust collector and fine tuning things that I had to manually do M3S12000 to get the spindle going at 12,000.
2 Likes
Thanks a lot for this, Greg! Finally gonna get around to trying this out this weekend 
Thanks for this! Just started testing CM with my RPI4 and the official RPI 7" touch screen. While it’s great that CM starts in full screen mode, I’ve noted that it occasionally exits and due to the aspect ratios of the 7" screen, I’m unable to go back into full screen mode. Is there a setting or feature to force full screen mode?
We just uploaded the latest build for the Pi to https://carbide3d.com/carbidemotion/pi . Grab it and check it out.
5 Likes
Got my Shapoko Pro back up and running with this on a Pi 4 with 4GB Ram. Ran into two issues… one may be user headspace related. I am having problems with my Bit Runner 2.0. Can’t get the spindle to turn on. [edit] well turns out it was a me thing and a bit runner thing. Hadn’t sent the configuration, and the connection to the control board was wonky… seems bit runner is working now. [/edit]
The other issue is jogging often returns a “busy” indicator. Didn’t keep me from getting anything done but it is rather annoying when you have to move more than a couple of inches. Seems to be less common with mouse clicks, happens primarily when holding down the w,a,s,d keys.
Really really hope you guys make this an official support at some point. I really didn’t like having my nice laptop near the machine while it was running and I haven’t been able to sort out an enclosure. Being able to have a <100 computer and old monitor in there is awesome.
Also… as many stated early on, making sure the UI supports the larger readily available 7 and 10" touch screens for RaspberryPI would be awesome. It is a decent jump to a 1080p touchscreen and I have yet to fine one that is designed with a Raspberry Pi mount designed in like the smaller ones. 1200x800 is pretty common seems. More than enough with small tweaks to the UI… or maybe you can find a scaling solutoin that is consistent (good luck…).
The RasPad 3 is 1280 x 800 and includes space for securing a Raspberry Pi 4 and batteries:
Pretty sure this has to do with the USB implementation on the RPi. Someone here pointed this out to me and recommended a fix. I just never bothered to do it. If I can find the post I will link it. These kinds of problems are ultimately why I did not stick with an RPi.
1 Like
I use the 7" Pi touch screen, rapid jogging is continuous. I very tried a keyboard last week and did notice it would stutter randomly.
I am using a Raspad 3, and I don’t use the keyboard for jogging, instead I use a wired game controller for jogging. No issues.
1 Like
Wow…big improvements! I finally had a chance to upgrade & try out the latest MotionPi build(v5.63) & it was really nice!
Did not encounter any UI issues with Button Sizes/LabelText/Status Text being cut off/squeezed down. The job Preview function seemed to work nicely & displayed fine on the 7" official Pi screen(800x480px Official Raspberry Pi 7" Touch Screen Display with 10 Finger Capacitive Touch (pishop.ca)), even if it was a little small - it was really great to verify the shape, size & 0-point of the loaded job right on the screen without having to deciper my file-naming scheme. Also what stock size the job was designed for & orientation setup on the Shapeoko bed.
Many thanks to the Carbide Team for the continued progress!
3 Likes