There's hope yet 

I'm trying to set up the DB25 board to connect to a geckodrive G540 and running into some confusion. Currently reading the byte2bot guide on this and I'm confused about the hal_gpio pin naming. Where are these pin numbers for "pi5 2025" coming from?  They don't seem to match any pin mapping I've seen in any other online source. Do I use the 2023 or 2025 one? 

Image of pinout naming matrix below.

Hallo @nichtAlex, 

welche Treiber sind das von StepperOnline? 
Ich überlege, die A6-Serie (AC) zu nehmen, doch die von StepperOnline konnten mir nicht versichern, dass diese mit LinuxCNC funktionieren. Sie glauben es zwar, getestet haben sie es aber noch nie. 

Was mich noch interessieren würde: Was stört dich an den IOs der Motortreiber, sodass du sie nicht nutzen möchtest?
Hast du den Home-Eingang dann nicht in Benutzung? 
Sind das AC- oder DC-Motortreiber bei dir? 

Gruß Mücke 

I think that's a good thought, however, I've found M19 is not available to directly remap according to this .
14.1. Existing codes which can be remapped
The current set of existing codes open to redefinition is:
Tx (Prepare)
M6 (Change tool)
M61 (Set tool number)
M0 (pause a running program temporarily)
M1 (pause a running program temporarily if the optional stop switch is on)
M60 (exchange pallet shuttles and then pause a running program temporarily)
S (set spindle speed)
F (set feed)

Hallo zusammen,

ich möchte einen 400V Synchron-Servomotor in LinuxCNC über EtherCAT (CiA402) einbinden.

Ursprünglich war der Motor mit einem proprietären Encoder geplant, das habe ich jedoch verworfen.
Ich gehe nun davon aus, dass ein Standard-Drehgeber (z. B. Inkremental TTL/HTL oder BiSS) verbaut ist.

Der Drive muss also:

• den Motor regeln (Drehmoment / Drehzahl / Position)
• den Drehgeber auswerten
• EtherCAT mit CiA402 unterstützen (CSP bevorzugt)

Motordaten:

• Typ: 400V Synchron-Servo
• Nennspannung: 400 V
• Stillstandsdrehmoment: 51 Nm
• Spitzenmoment: 120 Nm
• Nenndrehzahl: 4500 rpm
• Max. Strom: 122 A
• Keine Haltebremse
• Geber: Standard (kein proprietäres Protokoll)

Die Anwendung ist eine rotierende Achse mit Getriebe, keine hochdynamische Robotik.

Meine Frage:

Habt ihr eine Empfehlung für einen bezahlbaren EtherCAT-Drive mit CiA402, der:

• 400V Klasse
• ca. 50 Nm Dauer / 120 Nm Peak
• Standardgeber (TTL oder BiSS)
• sauber mit LinuxCNC (IgH + cia402.comp) läuft?

Der ursprüngliche Hersteller-Drive liegt bei ~4.000 €, das ist für mein Projekt zu hoch angesetzt.

Falls ich etwas übersehe:

Reicht es korrekt betrachtet aus, wenn der Drive:

• den Motorstrom regelt
• den Encoder auswertet
• CiA402 unterstützt

Oder gibt es bei 400V-Servos noch typische Stolpersteine, die ich beachten sollte (z. B. Kommutierungsanforderungen, Encoderauflösung, Stromgrenzen etc.)?

Ich freue mich über konkrete Modell-Empfehlungen oder Erfahrungswerte mit LinuxCNC.

Viele Grüße
Mücke 

I was just in the garage using the mill with the pendant. And thought that maybe I should post a mood picture, so we don't forget why we put effort on improving the pendant software
 

Hello JT,

It's a real shame that you don't have access everywhere.

Installing a Joomla + forum is not difficult in principle – the real challenge usually lies in maintenance and upkeep.

From what I've read so far, there are a few problems with the forum. Some functions do not work correctly or have been deactivated due to errors. In addition, the forum is often unavailable, which I find very unfortunate, as the community suffers as a result.

It may be possible to create a new folder under root and create a new database (the database software is already available). In this new environment, you could reinstall everything and set it up cleanly on a trial basis.

The new folder could be assigned a subdomain (e.g., forum-test.xyz.org). Everything could be installed and configured there at your leisure. Once everything is running smoothly and error-free, the subdomain could be adjusted accordingly and the old forum could be left as an archive – for reference and review.

I completely understand that your time is limited—we all feel the same way. Nevertheless, I would be delighted if we could find a solution together. This would certainly be very valuable for the community.

I would also set up a Joomla + forum myself, but I only have 5 GB of web storage—unfortunately, that's not enough. Therefore, it would make sense to implement it on your server.

Best regards
Mücke

Translated with DeepL.com (free version)

Big Thanks

Am I right in thinking you have battery-buffered encoders?Then you don't need homing.First remove the loops and see if the errors decrease. Dmesg requires admin rights.

@Aciera you should come play with the primary vtk display for qtpyvcp!! looks like you have sorted a good bit out, would love to have it native without needing a secondary add-in for simulation.

@andrax
I will purchase CAT6 cables as short as possible to prevent any loops probably the next week. I do not think there should be any EMC since, as I mentioned earlier, the drives and motor are on my testbench. There is no high voltage machine around, just computers.  Still, I do not exclude that EMC is the actual problem. I attached pictures of the drive setup and the mini pc I use.
By the way, when I try the command “dmesg | grep ethercat”, I got an error: "dmesg: read kernel buffer failed: Operation not permitted". Only "sudo dmesg" works.
Another interesting fact that I observed is that when I type "ethercat pdos", there are a few rows where it show 0x0000:00, 0bit, 'Gap''. As if there are missing PDOs. I might be wrong but, should I somehow define in the servo drive what PDOs and SDOs to be mapped in the variable PDO and SDO mapping.

@3404gerber
The truth is that I compiled the cia402-homecomp from source a few days ago and the example is a much older.

@rodw
I checked the original version of the component and the example there has only one row for homing that receives the index pulse from the servo drive but still I could not execute a successful homing procedure with it as well.

correct, from within the opened running fully loaded qtdesigner you open your templates for editing.

I don;t know if you noticed but that procedure returns 1 when the machine s turned on so until it does that, you just wait... Then you do all the homing and other things

Hakan, as far as I can tell, the component should try to reconnect after a failed asyncSetupTransfer in case you comment out the assert call. It should then after a short while fail on libusb_control_transfer, which then calls setDoReconnect(true), which in turn should cause a restart of the USB stack.

If you run the component with the -a flag, the console output when it fails would be interesting to see.