Advanced Search

Hey guys!
My linuxcnc / probebasic started to show a weird behaviour today.
After I start the system and home the machine, I get a popup saying "KeyError" _everytime_ when I jog any of the axes.
I can ignore that message, but it comes back everyime I jog again (no matter if via keyboard, softkey or pendant).

BUT - what I found out... as soon as I zero one of the axes (or all three), the error is gone.
I have not changed anything in my (software) config the last week, BUT I have modified my x axis yesterday and therefore moved the limitswitch a bit. 
Can this somehow be related? The popup says somewthing with "...active.WCSoffset..."... maybe some cached value doesnt fit anymore after I moved that switch?


Thx in advance!

net canMove not.0.out => stepgen.3.enable

My guess is that this causes the following error
when motion starts and this is still false.
That is, the commanded position is changing but
the stepgen is disabled so cannot follow ( so the
stepgen feedback is static) so you get a
following error.

Edit:

If linuxCNC is allowed to start motion before the brake is released,
Expanding the following error limits seem like the easiest solution.
However now this joint will lag the others so coordinated motion would
not be possible.

Is there some way to use digital inputs and outputs in the
gcode to manage the brake? That is, use a digital output
to enable the brake and a digital input to signal when the brake was
full applied and fully released. You would do this using M62,M63 and
M66 in the gcode and the hal digital input and output pins.

www.linuxcnc.org/docs/devel/html/gcode/m...e.html#mcode:m62-m65

If I understand the BUTTON_1_CODE correctly, the G10 L20 P0 coordinate system is always offset to the fixed values defined by X and Y. How does positioning the cross-hairs to a difference starting position translate the offsets to the new location correctly?

Well all I can say is that clearly your G54 offset values are wrong. So if those values are set in Fusion then you would need to look there.
Also you have tool offsets not only in Z but also in X and Y which is a bit unusual.

Hi,

No thanks, i already got it working with the same EL7 homecomp and forgot to update this
Was waiting for the beckhoff modules to arrive and got them today, so i can finally continue now!

I have an axis that I use with a stepper motor with brake. Before this axis starts moving, I have to disable the brake, wait for the mechanical delay and then move it. And when the movement is finished, I have to activate the brake immediately. I used the following commands to do this.
I can do what I want in manual movement with these commands. But when I use it with mdi commands, it gives “joint 3 following error” error.

How can I solve this?

That makes sense , this has Linear Scales for Feedback with Steppers.

"unless the error log states "no permission" the issue is a permission error"

What does this mean exactly?

If the error log states "no permission", there is NOT a permission issue, correct?

dunnitagain wrote:

Todd , what do the halscope files do ? Are they a test ? All the Bios settings appear to be correct , to allow the Boot from ISO, tried several times with Tommies advice , still no luck.
 

The halscope files are saved from the Halscope oscilloscope app. They are merely a record of the scope settings and signals that were being used at the time it was saved. So for example I have some Halscope files saved for the settings I use for tuning each of the servos on one of my machines. Using them makes opening and configuring Halscope quicker when doing something you might need to do the same again later or after a restart. But they certainly are not needed for running Linuxcnc.

You would replace /usr/bin/pncconf with the pncconf.py file, ie "sudo mv pncconf.py /usr/bin/pncconf". You might also need to do a "sudo chmod +x /usr/bin/pncconf". I would suggest making backup copies of those files first just in case.

I just upgraded from 2.7.14.  (No laughing please.)  I find the other supported guis not as friendly.  They have features of no value for a Sherline mill.

Did you try Ventoy?

www.ventoy.net/en/index.html

Ventoy has worked for me on systems where Rufus did not.

I do not recommend BalenaEtcher; it's so-so.

Any have any thoughts on this? I'm kind of stuck! Thanks

It sounds like something was up with your offsets. Are you using g54? Make sure to switch into g54 or 55, 56, ect before touching off. That, or maybe you had cutter comp on and a large diameter in the tool table?

peterdownunder wrote:

as an aside, how do i mark this as answered ??

Done, thank you.