Advanced Search

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.

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.

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.

BUTTON_1_NAME = ZERRO\Materialit
BUTTON_1_CODE = G10 L20 P0 X89 Y29.5 \ G53 G0 Z-10
This is just to give you an idea, i use this on my plasma machines with laser cross.

Okay, I've been looking into this. I've already added exceptions for all the unique tools. The main feature I want to add now is the ability to switch tools between the spindle and carousel without unloading the tool from the spindle. To make that work, I need a way to store the current tool number somewhere temporarily.

At the moment, I'm trying to find a method to manually edit the carousel positions—specifically, assigning a tool number or 0 to each slot.

I think the simplest approach might be to build a custom UI. I’m not entirely sure how to implement it yet, but I’m imagining a subroutine that lets you set a given tool number into a specific carousel slot (addresses 4001–4012).

I briefly considered removing the randomisation from tool numbers, but that doesn’t really help with the main issue. What I need is a fast way to manually update the carousel—without relying on the machine to handle the full tool change process.

What's strange is that I haven’t come across anyone else doing this, at least from what I’ve been able to find. If anyone has suggestions, I’d really appreciate them.

You do not absolutely need to have switches on a gantry
but if not, you need to use an "immediate" homing setup:


linuxcnc.org/docs/html/config/ini-homing.html#_immediate_homing