Jogwheel + start of any gcode motion causes Following Error

Ok. I did some basic testing with qtaxis and didn't see any obvious problems.
The user had some other problems fixed so maybe it was unrelated to this work.
Thanks

I think "the user" is me, right?

No other probs other than I think not being able to move coordinated joints in Joint mode, prior to homing, is a significant problem. An unrelated issue.

This Following Error is the only unexplained prob I have now that is keeping me from upgrading our makerspace CNC router to 2.8.

dannym wrote:

This Following Error is the only unexplained prob I have now that is keeping me from upgrading our makerspace CNC router to 2.8.

I think that you should be able to install the 2.8 deb from the buildbot, then reset the repository settinngs to the main server. That should bring in the f-error fix and then prompt to install the next 2.8 release (with the fix) when that is released.

Great- can you explain it like I'm 5?
I'm not familiar with buildbot or repository settings

Looking forward to this fix

There are instructions here.
buildbot.linuxcnc.org/
Follow then”alternative” route to installing the keys.

There are instructions here.
buildbot.linuxcnc.org/
Follow then”alternative” route to installing the keys.

I have installed it, and it is magic

Thank you!

I just got this strange error when I handed the mpg to a student and had them press "Probe Z".  Never saw this with 2.6  I couldn't repeat it.  He swears he didn't move the jogwheel while pressing Probe Z."Probe tripped during a coordinate jog""joint jog requested for undefined joint number = -1 (max=0, min=4)"??

That is weird, because I don't know of any way to select a joint to jog by number. (each joint has a pin to select it for jogging, and you can't select a joint that doesn't exist)

It's possible that the probe trip is the only real issue, and the rest is a result of an aborted jog.