Advanced Search

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

If someone still has an different idea on how i could use the absolute encode advantages but have the switches connected over the IO Modules, i would appreciate some alternatives. 

Thank you. I will try to define the same address exactly later.

Something like this:
In .hal:
setp joint.2.request-cia-homing 1
setp lcec.0.Y.homing-method 22 #or whatever homing method you choose - see manual
net y-start-homing joint.2.start-cia-homing => cia402.2.home

in .ini:
[EMCMOT]
HOMEMOD=cia402_homecomp

Thats some really good points about the gantry.
Appreciate your help.

Which driver would i need for this? Just the standard cia402?

I dont think, that is possible.

If you wire the switches to the servo drive, you can use one of the drives internal homing methods. They allow a combination of home switch and encoder zero position. That will give you very high repeatability.

If you dont wire the switches to the servo drive, you are forced to the linuxcnc internal homing. Same with limit switches. This will reduce your repeatability to the repeatability of the home switch (you will need high precision home switches).

However if you use the servos internal homing in a gantry setup, you have to wire both gantry drives to the same switches. Servo based homing does not know about the mechanics of your gantry. You do not want two servos fighting each other and bending something.
Also maybe limit the torque during homing (PDO 6072)

My home switches are wired to the IO Modules. I only have one switch per joint
If i trigger the switches manually they getting recognised correctly in the hal show.
Do you know by a chance if its also possible the other way around?
So telling the driver like pin xy was triggered over the ethercat way?

My brain blockade right now is the following:
I have home switches configured like i did with steppers before. When triggered, shouldnt LCNC tell the Servo stop moving? Why do i need to home hooked to the drives.