Advanced Search

There is a whole thread on this subject on CNCzone, here is a description of my solution.
www.cnczone.com/forums/mini-lathe/63621-cnc.html#post509784
But it was a long time ago and all the images have bitrotted...

There are some pics of the machine here, but not the critical ones:
photos.app.goo.gl/nwM9Ze59j3zi5TB77

The basic idea is to have a T2.5 pulley small enough to fit under the cross-slide, and next to that a needle roller bearing running on a plain section of the ballscrew. Then the thrust control is handled much closer to the operator, in the micrometer dial housing, with a pair of angular contact bearings, where there is a lot more diameter to play with.

What command and feedback method do the drives and axes require/provide?

You might want to look at the "HD" cards too, such as the 6i24 as those have rather more pins. For example 6i24 + 7i36. The 7i36 can connect one smart-serial board for GPIO, and then you could add a 7i44 if one sserial board isn't enough.
Look at the 7i43 to simplify the control panel wiring too.

You might want to consider adding this to the "Contributed Components" on wiki.linuxcnc.org

LinuxCNC expects the encoder counts to be zeroed at the index. (then LinuxCNC uses the small number of remaining counts that accumulate as the axis comes to a stop to calculate the exact index position).

If your ethercat encoder counters don't do this then you will see the behaviour you describe. And, also, your home position will be wildly inconsistent.

If you have good homing switches you may be able to just not use home-to-index. Alternatively some HAL magic might be used to latch the C phase to look like the edge of a switch (and2 with the actual switch).

Reset on index might be a configurable option in the encoder counter.

eusurplus.com/index.php?route=product/pr...ct_id=96&search=7i73

You may have cut off the most important part of the error chain, the real problem is likely to be near the bottom.

Which libgpiod?

Just to let you know, that the SPI connection (generic) also works with the Orange Pi 5 and the TangNano9k.
Great work meister!

By the way I think that supporting Mesa boards would be beneficial for many, since it's much easier to adjust the functions of the pins.

Die Mesa Karte ist direkt über ein Netzwerkkabel mit dem PC verbunden. Das Kabel habe ich schon ausgetauscht - keine Änderung.
Die Spannungsversorgung erfolgt über ein 5V Hutschienen Netzteil 5V 3A

Aktuell ist außer der Stromversorgung nichts an der Mesa Karte angeschlossen.

​​​​​​Den Ping Befehl habe ich jetzt noch mit 10 Minuten ausgeführt. Die Werte sind praktisch identisch zur letzten Messung (1 Minute)

Der Fehler tritt zufällig auf. Manchmal nach wenigen Sekunden manchmal erst nach 20 Minuten. 
Unabhängig davon ob das gmoccapy Fenster maximiert, klein oder im Hintergrund ist. 
 

Not sure what's wrong, that's a 31 ms delay!

Ergänzung

Die Maschinenkonfiguration ist für die Tests ganz einfach gehalten. Erstellt mit PNCCONF XXYZ mit 1280steps/mm keine Endschalter, Spindel oder sonstige Ein / Ausgänge.
Wirklich minimal gehalten. Außer den Verfahrwegen nur Standardeinstellungen.
Die Karte läuft auf dieIP 10.10.10.10 am PC ist noch ein USB W-Lan Stick eingesteckt. Dieses Netzwerk ist 192.168.1.XX
Als Oberfläche habe ich gmoccapy gewählt.

Any plan to bring those in?
store.mesanet.com/index.php?route=produc...69_70&product_id=116

Kind regards/Stefan

your best bet is to use this installation method:

github.com/Lcvette/qtpyvcp-bookworm-installer

Thank you!
I finally found it will deep dive in to this later if I need to.
I gues it kind of ancient by now as not much development have been made for a century.
/Stefan

Es sind 2 Fehlermeldungen 

hm2/hm2_7i96s.0: Wachdog has bit! (set the .has bit pin to False to resume)

Unexpected realtime delay on task 0 with period 1000000
This Message will only display once per session. Run the Latency Test and resolve before continuing.

Die Ursache scheint wieder im Bereich read.tmax zu liegen. 

cnc@cnc:~$ halcmd show param *.tmax
Parameters:
Owner   Type  Dir         Value  Name
    36  s32   RW              0  hm2_7i96s.0.read-request.tmax
    36  s32   RW       96523036  hm2_7i96s.0.read.tmax
    36  s32   RW         390944  hm2_7i96s.0.write.tmax
    29  s32   RW          65448  motion-command-handler.tmax
    29  s32   RW         138712  motion-controller.tmax
    39  s32   RW           6464  pid.s.do-pid-calcs.tmax
    39  s32   RW           6196  pid.x.do-pid-calcs.tmax
    39  s32   RW           4464  pid.x2.do-pid-calcs.tmax
    39  s32   RW           6624  pid.y.do-pid-calcs.tmax
    39  s32   RW           6464  pid.z.do-pid-calcs.tmax
    30  s32   RW       96637576  servo-thread.tmax 

Vielen Dank

Grüße Erwin