Advanced Search

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


 

Hi Chris,
yes, it is now. I'm going to start a few experiments now. Thank you very much for your tip!

Peter

So, I will need to install physical limit switches to the table for this homing setup?
Is there a tutorial and were for wiring limit switches correctly to the control board ST-V3. As I do not have any switches install at this time. It never needed them when I had the table setup for Plasma cutting. Now I have changed to Router it seems that this is an issue.

You need to keep name  for axis z as joint2. I noticed in your ini file you using the name joint 1 that should 2.
For the exposed pin from the vista pedant keep the names of the axis as number example vc-p1as.axis.0,
I attached revised hal file check for typos
revise your own ini file for joint names (numbers)

edit:
have read through this thread:
forum.linuxcnc.org/38-general-linuxcnc-q...ling-to-share#261003