Advanced Search

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

 

Hi all;

I've been converting from MACH3 to LCNC. In MACH3 I had configured an XY positioning laser using a macro that would allow me to jog to the program zero for a given project, then once positioned at the appropriate point I would click on a button that would calculate the X/Y offsets, move the spindle to the true program zero then set the G54 X/Y DROs to zero. This was very fast and accurate way to perform this task and along with a tool probe to zero the Z axis, program home is quickly established.

I would like to do something similar adding a button in the pyVCP to turn on the laser and once positioned a second button to compute the offsets, move the spindle to program zero, set the X/Y DROs to zero and turn off the laser.

Searching the forum, I've not found any info to work from. Has anyone configured a positioning laser on their system?  I'm a little rusty on my Python, but I can get back into it quickly or would classic ladder be a better option?  Any help would be greatly appreciated.

Kind regards

Thanks Peter.,

There was no change after adding chokes at both ends of the RS-485 wire. Checking the wire I discovered that it was not shielded. Ordered a few feet of 18 gauge shielded wire for CNC VFD use. First attempt I received the wrong wire. Finally got the right wire today.

After installing ferrules on both ends with minimum wire exposed and installing it, I double shielded it by adding a choke at the VFD end of the wire as close to the terminal block as I could and grounded the shield at the dongle to the PC.

Restart was successful. No issues running the spindle after the upgrade.

Thank you for your guidance.

Kind regards.

Have you seen this?
linuxcnc.org/docs/devel/html/gui/qtvcp.html

I have no clue why this didn't work yesterday as it is working for me today... maybe a typo in the ini file who knows.

In 2.9.0~pre that ships with  Debian 12 only the reverse caps work so that's why it didn't work for me as I only tried the forward caps.

JT

It still feels like a misuse of this parameter...

Thank you, thats definetly worth a try.

Try the following:
in hal connect your input pin to PDO 2004 Index 02 or 06 or 0A (pos limit, neg limit, home)
like
net y-limit-ext lcec.0.something.din-2 => lcec.0.X.pos-limit

in ethercat-conf.xml
<pdoEntry idx="2004" subIdx="02" bitLen="16" halPin="pos-limit" halType="u32" />

do not connect anything physically to the servo drives DI inputs.

Hi all,
I need a little help, it's about QTVCP surfaces. I'll take QtDragon as an example. The graphical user interface is created with the QtDesigner, the file is called qtdragon.ui. This includes the handler file qtdragon_handler.py
What I have not yet understood is how these two files work together? How are the functions in qtdragon_handler.py called? Are there any documents or help where I can read and understand this? Is there a kind of “framework” of the handler file that you can build on?
I know there are a lot of questions. It's not easy to get started with QTVCP.
Thank you very much.
Peter

 

Hello,

I think "almost everything is possible" somehow, but to be honest I did not really follow what you exactly want to do. Maybe you need to elaborate your "functional description" more?

e.g. On my small hobby mill (LinuxCNC) the speed depends on how fast I move the MPG (Manual Pulse Generator). (I never missed jogging at constant speed here, for small stuff I use MDI). (e.g. G91 G01 x10 F200 G90)

Most commercial machines that I see around here, have a separate set of jog buttons. 
And sometimes a selector switch for the jog speed.

Greetings Timo