Advanced Search

No I didn't get a blinking green light, the 7i77 flickered a few times and went back to red.

Hello,
iḿ a newbie (from Germany) and i just build a new mill. Now I want to configure my Mesa 7i76e. However, I can't get TB5 and TB6 to activate. Just TB2/TB3, P1 and P2 are visible.
Please help

Danke, das ist schon mal ein Ansatz! 

Im Moment sehe ich da zwei Möglichkeiten:
- Raspberry Pi 5 + ein Parallel Hat von byte2bot
byte2bot.com/products/parallel-port-rasp...gak8F2DJq1o7WoFK2x-g

Verstehe ich das richtig, dass damit die Erzeugung der Signale die an meine Fräse gesendet werden im Raspberry stattfindet, und somit von der Systemauslastung, Latenz, etc.. abhängt?

- Raspberry Pi 5 + MESA 7C81
Während hier die Signale in/von der Mesa Karte erzeugt werden?

In beiden Fällen muss ich die .hal Dateien so anpassen dass die korrekten Pins angesprochen werden, das ist mir klar.

Aber funktioniert das grundsätzlich so, oder liege ich daneben?

I assume the ERC60 just reports back the commanded position as actual position, without knowing if it lost steps.
Have you verified with halshow that  joint.2.motor-pos-fb =cia402.2.pos-cmd and cia402.2.drv-actual-position = lcec.0.5.actual-position?

That looks like the situation I had yesterday. Traced it to a bad kernel (I think I traced it there).
I upgraded the kernel to latest 6.12-48 and all problems went away.

I got lot's of errors yesterday and going in and out of PREOP. 
It might have been a bad kernel. I upgrade to latest 6.12-48 and the problems went away.
Think the bad one was 6.12-38.

Got that too yesterday. Traced it to a bad kernel think it was 6.14-38 or so. Upgrade the kernel is my advice.
 

Well, I just found another mistake.
My spindle driver only has two pins: forward and reverse; it doesn't have an enable pin.
And I had wired spindle.0.on to the driver's forward pin instead of spindle.0.forward.
The good news is that the PID speed still works fine.
The bad news is that the orientation doesn't move at all anymore, nothing...

 

Today i tried active DC mode on and linuxcnc keep spamming this error:

Failed to get reference clock time: Input/output error
Failed to get reference clock time: Input/output error
Failed to get reference clock time: Input/output error
Failed to get reference clock time: Input/output error
Failed to get reference clock time: Input/output error
Failed to get reference clock time: Input/output error
Failed to get reference clock time: Input/output error

What causes this error? I'm using Linuxcnc 2.9.4 install from iso file.Here is my xml file and driver document:
drive.google.com/file/d/1ZTNpSNYDF0IL-IE...Bn4/view?usp=sharing
 
 

Das Problem hab ich gefunden nur keine idee wie ich es umgehen kann. Es wird ein Feedback vom Motor/Encoder erwartet aber der ECR60 hat keinen. Hat jemand einen Lösungsvorschlag um das zu umgehen?

I have 3 iX7NH servo drives connected via ethercat. I have installed ethercat (IgH EtherCAT master 1.6.8) to the linuxcnc 2.9.4 ISO from repositories as described in this thread .

Using ethercat -p0 upload -t int16 0x2003 0 I can request that word from any drive, but it frequently fails with Failed to upload SDO: Input/output error.

dmesg reports:
[316.525911]EtherCAT WARNING 0-0: Other mailbox protocol response from eoe0s0.
[316.537792]EtherCAT ERROR 0-0: Reception of CoE upload response failed: No response.
[316.537797]EtherCAT ERROR 0-0: Failed to process SDO request.

I can run linuxcnc, and it will throw for one or two drives that same error I received with ethercat, but for different drives each time. I was once lucky enough to have it throw no such errors, but within a few minutes, one of the drives refused to communicate. When the drives do communicate, the DRO fields will update as I turn the motor shafts by hand.

I have seen drives flap betweep PREOP and OP status, while linuxcnc was running.

I also have some mesa daughterboards served by a 7i94. Occasionally, they will stop responding, showing all comms error lights, and linuxcnc will say "error finishing read".

I have installed r8168-dkms, and the realtek interface is using that driver. The other interface is supposedly an Intel card, using the igb driver, but it came from China, so there's no guarantee. Naturally the r8169 driver gave the same problems. I have tried other ethernet cards, but they all have realtek silicon.

The latency histogram does not exceed 10uS. Ping to the 7i94 is 112uS average, 203uS max.

What can I try next?

Hello
thanks for your reply, andypugh!
Another one question. If i have reel (not bar). My material reel will became short and i will have to change material by new reel. I needed to change new reel and put in a couple meters. But if i will manually push material in, my x axis became to count. And axis measurement mismatch. How correctly to do material change and  put off old material, and replace by new material in, until push roll will engage to roll-in my new material? And how to simultaneously jump back to previous gcode block (previous produced part)?

I've only connected two slaves this time, and I've confirmed that neither of them has EOE functionality.
I've recorded the dmesg output after the rescan.
Why is the connection process relatively slow?
In which direction should I focus my troubleshooting efforts?
Thank you in advance for your guidance!

[ 5140.632281] EtherCAT 0: Re-scanning now.
[ 5140.640312] EtherCAT 0: Scanning bus.
[ 5141.334336] EtherCAT WARNING 0: 5 datagrams TIMED OUT!
[ 5141.334343] EtherCAT WARNING 0: 5 datagrams UNMATCHED!
[ 5142.333525] EtherCAT WARNING 0: 13 datagrams TIMED OUT!
[ 5142.333531] EtherCAT WARNING 0: 13 datagrams UNMATCHED!
[ 5143.332840] EtherCAT WARNING 0: 7 datagrams TIMED OUT!
[ 5143.332847] EtherCAT WARNING 0: 7 datagrams UNMATCHED!
[ 5144.331944] EtherCAT WARNING 0: 4 datagrams TIMED OUT!
[ 5144.331950] EtherCAT WARNING 0: 4 datagrams UNMATCHED!
[ 5145.335015] EtherCAT WARNING 0: 1 datagram TIMED OUT!
[ 5145.335022] EtherCAT WARNING 0: 1 datagram UNMATCHED!
[ 5146.333852] EtherCAT WARNING 0: 4 datagrams TIMED OUT!
[ 5146.333858] EtherCAT WARNING 0: 4 datagrams UNMATCHED!
[ 5147.332551] EtherCAT WARNING 0: 3 datagrams TIMED OUT!
[ 5147.332558] EtherCAT WARNING 0: 3 datagrams UNMATCHED!
[ 5149.333802] EtherCAT WARNING 0: 4 datagrams TIMED OUT!
[ 5149.333808] EtherCAT WARNING 0: 4 datagrams UNMATCHED!
[ 5150.256544] EtherCAT 0: Bus scanning completed in 9624 ms.
[ 5150.256552] EtherCAT 0: Using slave 0 as DC reference clock.
[ 5150.276608] EtherCAT 0: Slave states on main device: PREOP.
[ 5150.332789] EtherCAT WARNING 0: 2 datagrams TIMED OUT!
[ 5150.332794] EtherCAT WARNING 0: 2 datagrams UNMATCHED!
[ 5150.625634] EtherCAT ERROR 0-0: Reception of CoE download response failed: No response.
[ 5150.625642] EtherCAT WARNING 0-0: Failed to set number of entries.
[ 5150.625643] EtherCAT WARNING 0-0: Currently mapped PDO entries: 0x2600:01/16 0x2600:03/16 0x2600:04/16 0x2601:02/16. Entries to map: 0x2600:01/16 0x2600:03/16 0x2600:04/16 0x2601:02/16
[ 5150.625657] EtherCAT WARNING 0-0: Failed to configure mapping of PDO 0x1602.
[ 5151.331810] EtherCAT WARNING 0: 7 datagrams TIMED OUT!
[ 5151.331816] EtherCAT WARNING 0: 7 datagrams UNMATCHED!
[ 5155.334342] EtherCAT WARNING 0: 7 datagrams TIMED OUT!
[ 5155.334348] EtherCAT WARNING 0: 7 datagrams UNMATCHED!
[ 5156.316919] EtherCAT WARNING 0-0: Slave did not sync after 5000 ms.
[ 5156.327444] EtherCAT 0: Domain 0: Working counter changed to 3/6.
[ 5156.332974] EtherCAT WARNING 0: 5 datagrams TIMED OUT!
[ 5156.332979] EtherCAT WARNING 0: 5 datagrams UNMATCHED!
[ 5157.667444] EtherCAT 0: Domain 0: Working counter changed to 6/6.
[ 5158.334745] EtherCAT WARNING 0: 5 datagrams TIMED OUT!
[ 5158.334751] EtherCAT WARNING 0: 5 datagrams UNMATCHED!
[ 5158.671444] EtherCAT 0: Domain 0: 4 working counter changes - now 6/6.
[ 5160.132443] EtherCAT 0: Domain 0: Working counter changed to 0/6.
[ 5160.140193] EtherCAT ERROR 0-0: Reception of CoE SDO description response failed: No response.
[ 5160.144210] EtherCAT 0: Slave states on main device: OP.

I've carefully reviewed the configurations of my two previous systems. For the first system, I didn't intentionally disable EOE, so it should have been enabled by default.

For the second system, I'm somewhat uncertain whether EOE was actually disabled when checking dmesg, because I've seen similar posts suggesting that disabling EOE might be beneficial.

Another finding: I tried compiling EtherCAT version 1.5.2 on the second system (replacing version 1.6.1), and it did successfully connect quickly and enter OP state.

However, during operation, when I used watch -n 1 ethercat slaves to monitor, I noticed that it would occasionally flash "0x0000:0x0000" for all slaves. At these moments, it seemed like all my IO modules disconnected, but they recovered quickly.

This instability makes me hesitant to use this setup.

I would greatly appreciate any help or suggestions from the community. Thank you very much!

Hi everyone, I'm back. I've carefully reviewed your replies and compared the dmesg information from my two systems.

I noticed that the second system has started the EOE thread again, and afterward, it logged many EOE-related errors/warnings.

I'm thinking about trying to completely disable the EOE function. I remember that I manually compiled the EtherCAT driver on the second system. According to the documentation, I configured it with something like --enable-eoe=no.

Is there a way for me to verify whether the EtherCAT I compiled actually has the EOE function disabled?

Of course, I can also recompile it, but I'm not entirely sure how to completely disable the EOE function.

Thank you for your help!