I noticed that when using the latest build (613) of CM, repeated keystrokes to jog the machine seems to overrun the system. The display shows BUSY and you need to wait a few seconds before it becomes responsive again. It seem like you need to wait a second or two between keystrokes. I’m not sure if this is a bug, or something added intentionally for some safety reason. In previous versions of CM, this was not the case. You could repeatedly press a jog key and the motion was nice and smooth. Looking at the release notes for v613, I notice the mention of “nudge jogging”. Does anyone know what this is referring to?
1 Like
If you mean:
- (NEW) Nudge jogging for BitSetter positioning.
that was the introduction of the ability to move the machine after moving to the default BitSetter position
Basically a “nudge” is a movement of the machine w/ a keypress.
That makes sense.
Does the v613 release change how the keyboard jogging is handled? More specifically, multiple keystroke in a row seems to over run the system causing a constant BUSY state. In the the previous versions, if you pressed the left arrow five times in a row, the machine would move 5 times the increment selected. Now it will move once and show BUSY for a few seconds.
I don’t know.
If you’re having a specific problem, let us know the specifics of your system and how to consistently cause it at support@carbide3d.com and we will try to look into it with you.
Are you using windows, Mac or PI?
I have the same issue on a PI.
i am on windows and have the same issue.
if i push any of the jog buttons too many times, i get a busy state and have to wait for the program to figure it self out. other times jogging the machine too many times (1 mm movements) while CM goes into a busy state and just freezes there…leading me to restart the program or restart my laptop
My understanding is that there’s a roughly half second input lockout when jogging to prevent accidental double-registration of inputs. I’ve noticed these lockouts can actually be cumulative though, which may be why CM appears to freeze for a few seconds if you tap rapidly. Definitely not a desired behavior and something I think would be easy to fix (hopefully on our programmer’s radar and will be fixed soon), but this may be somewhat worse if your CM install gets stuck permanently in Busy mode. Can you take a video of CM freezing up like this, and also giving it like a couple seconds to see it it clears itself? Also worth installing the latest version first.
1 Like
I am out of town now but will be home this weekend. I can easily replicate the issue and get it on video. It works great when using the touch screen for input but the attached 9 key causes the issue every time. I modified the repeat rate and it helped but it still happens.
Following this as I’m having the same issue on v617 with my gamepad controller on a Mac running the Gamepad Mapper software to map the keyboard buttons. Interestingly enough, the keyboard buttons work just fine holding down the keys. And the gamepad works fine when “Keystroke repeat” is turned off, but then I’d have to keep pressing the buttons to make it jog long distances as opposed to holding down the buttons.
Here is a different thread I put a video link in because I couldn’t find this one the other day.
One thing that I never noticed until actually watching the video is that the “Busy” indicator stays on briefly when using the touch screen after I let go. In the video you can see where I chose a different operation in the touch screen and it worked even though it still indicated busy.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.