Jogwheel + start of any gcode motion causes Following Error
31 May 2022 01:18 #244252
by cmorley
Replied by cmorley on topic 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
The user had some other problems fixed so maybe it was unrelated to this work.
Thanks
Please Log in or Create an account to join the conversation.
31 May 2022 18:55 #244305
by dannym
Replied by dannym on topic Jogwheel + start of any gcode motion causes Following Error
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.
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.
Please Log in or Create an account to join the conversation.
02 Jun 2022 10:08 #244436
by andypugh
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.
Replied by andypugh on topic Jogwheel + start of any gcode motion causes Following Error
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.
Please Log in or Create an account to join the conversation.
03 Jun 2022 01:43 #244482
by dannym
Replied by dannym on topic Jogwheel + start of any gcode motion causes Following Error
Great- can you explain it like I'm 5?
I'm not familiar with buildbot or repository settings
Looking forward to this fix
I'm not familiar with buildbot or repository settings
Looking forward to this fix
Please Log in or Create an account to join the conversation.
05 Jun 2022 13:17 #244613
by andypugh
Replied by andypugh on topic Jogwheel + start of any gcode motion causes Following Error
There are instructions here.
buildbot.linuxcnc.org/
Follow then”alternative” route to installing the keys.
buildbot.linuxcnc.org/
Follow then”alternative” route to installing the keys.
Please Log in or Create an account to join the conversation.
05 Jun 2022 13:17 #244614
by andypugh
Replied by andypugh on topic Jogwheel + start of any gcode motion causes Following Error
There are instructions here.
buildbot.linuxcnc.org/
Follow then”alternative” route to installing the keys.
buildbot.linuxcnc.org/
Follow then”alternative” route to installing the keys.
Please Log in or Create an account to join the conversation.
14 Jun 2022 05:46 #245099
by dannym
Replied by dannym on topic Jogwheel + start of any gcode motion causes Following Error
I have installed it, and it is magic
Thank you!
Thank you!
Please Log in or Create an account to join the conversation.
01 Jul 2022 05:53 #246341
by dannym
Replied by dannym on topic Jogwheel + start of any gcode motion causes Following Error
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)"??
Please Log in or Create an account to join the conversation.
01 Jul 2022 09:29 #246348
by andypugh
Replied by andypugh on topic Jogwheel + start of any gcode motion causes Following Error
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.
It's possible that the probe trip is the only real issue, and the rest is a result of an aborted jog.
Please Log in or Create an account to join the conversation.
Time to create page: 0.216 seconds