Advanced Search

I have a new section in the error codes where it does say it can see the 7i84. So it must be my call-out for the pins are incorrect. I am referencing a project where the guy had his 84 wired to his 7i77 but I am using the 7i74 to communicate with the 7i84 and 7i73. Is the pin call-out different currently it is "HM2_5i25.0.7i84.0.2.output-10"

I decided I didn't like the looks of the Ethernet cable I was using so I went and grabbed 2 different ones to try. When I plugged it in a new yellow light turned on and when I launched the CNC page it blinked green a few times before giving me the same error pins on 7i84 don't exist.

I saw the question and you have now attached exactly the relevant files. Thanks, I'll be happy to think about it!

OK. Best of luck Rod.

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?