Advanced Search

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.

If you need startup jogging and you need to tune the servo ... you need to turn off Lag monitor under the  Axis X.. Parameter ... Monitoring: Position Lag Monitor = False ...

If you have reduction factor ... you will determine it in the nominator and denominator rows somewhere in the drive manager ...

Yes one motor revolution == one encoder revolution ..

Yes HD should reverse you motion .. every odd 

This setting you generally free enable movement... next tune or you will need firmware update to start autotunnig the servo system ..

How did you wire your home and limit switches?
If you push the siwtches by hand, do you see the "pins" change in halshow?

I would recommend to wire the limit and home switches to the servo drives DI inputs.
Then you can see the signals in PDO 60FD.

e.g. add this to your ethercat-conf.xml for each A6 servo:

<pdoEntry idx="60FD" subIdx="00" bitLen="32" halType="complex">
<complexEntry bitLen="1" halPin="limit-neg" halType="bit"/>
<complexEntry bitLen="1" halPin="limit-pos" halType="bit"/>
<complexEntry bitLen="1" halPin="home-switch" halType="bit"/>
<complexEntry bitLen="13" />
<complexEntry bitLen="1" halPin="din1" halType="bit"/>
<complexEntry bitLen="1" halPin="din2" halType="bit"/>
<complexEntry bitLen="1" halPin="din3" halType="bit"/>
<complexEntry bitLen="1" halPin="din4" halType="bit"/>
<complexEntry bitLen="1" halPin="din5" halType="bit"/>
<complexEntry bitLen="1" halPin="din6" halType="bit"/>
<complexEntry bitLen="1" halPin="din7" halType="bit"/>
<complexEntry bitLen="1" halPin="din8" halType="bit"/>
<complexEntry bitLen="1" halPin="din9" halType="bit"/>
<complexEntry bitLen="7" />
</pdoEntry>


I use negative logic. You have to configure this on your drive to match the limit/home switches. This is permanently saved in the drive.
e.g.
# set operating mode
ethercat upload -p 2 --type int8 0x6060 0x00
ethercat download -p 2 --type int8 0x6060 0x00 8

# set "active low" DI input logic
ethercat upload -p 2 --type uint16 0x2004 0x02
ethercat download -p 2 --type uint16 0x2004 0x02 1

ethercat upload -p 2 --type uint16 0x2004 0x06
ethercat download -p 2 --type uint16 0x2004 0x06 1

ethercat upload -p 2 --type uint16 0x2004 0x0A
ethercat download -p 2 --type uint16 0x2004 0x0A 1

You also have to set homing mode  (PDO 0x6098) - see manual 

Have a look at monokrom. it might do this already as the designer did the ramp piercing and pushed to qtp. It has a proper SQL database