Advanced Search

EDIT Nov. 3 2024. THERE IS A WIRING ERROR IN THE PICTURE BELOW. THE OE LINE NEEDS TO BE CONNECTED TO 3.3V OR AN OUTPUT. WILL CORRECT THE DRAWING AND UPLOAD AGAIN ONCE TESTED.
This one is actually how I want to connect the joints. I have a total of 4 joints (dual Y axis motor), but only draw joint 1 and 2 for the moment.

 

BaxEDM wrote:

Ah yes! After switching off EEE and aspm, I ran the machine for over 3 hours straight without encountering any servo following errors. I captured everything I did in order to do a full problem free installation in this procedure for my customers, this might be useful for others as well:

baxedm.com/linuxcnc-installation-for-edm...-on-linux-debian-12/
 

Nuce writeup. I hope you don't mind but I added it to my Debian 12 document
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing

Ok, so do I have the wrong W5500? I was planning to use it like in the attached picture.

Lcvette wrote:

PCW wrote:

Lcvette wrote:

@PCW who would be the person group best suited to fixing it, and do they know about it? is this a linuxcnc thing or a debian thing?
 
Honestly its a Linux thing (broken driver) but would be easier to fix in a non debian compliant ISO
Ultimately it should get fixed in the kernel driver so the proprietary Realtek driver is not needed.

Interesting, would it help the intel adapter performance as well? bring it back to the 4.9 kernel day performance?  i miss those days...lol

I don't think this is a kernel bug but related to some decisions made with the kernel inclusions for realtek NIC drivers. The R8169 driver is a generic NIC driver for the Realtek cards but it fails in a Real Time environment on the R8168/R8111 hardware (And also the Realtek R8125 driver). I suspect it is related to restrictions on the code licencing of Realtek binaries  and FOSS.

Pre kernel 5.10 (Bullseye), you had to download the driver sources from Realtek and build your own driver but this was kernel specific. Users of the Odroid H2+ will remember having to compile the R8125 driver. It was hard to find a working version for your kernel. Somewhere around kernel 5.9, I think the  Realtek code was separated into different drivers and the R8169 was included in the kernel. But the non-FOSS code from Realtek was separated out into DKMS driver modules. DKMS allows kernel modules to be distributed in source code and built for a specific kernel automatically. This  is recompiled if you upgrade your kernel.

So here is the problem. the R8168_dkms driver is not part of the kernel so its not considered a kernel bug. the RT project does not see it as part of their remit as a driver is available.

I have tried reporting Bugs with Debian and the RT kernel team but it is exhausting and non productive so I gave up.

It does get a bit worse as because the R8168_dkms driver not a kernel module, the dkms driver is not included in the Debian non-free-firmware module so your sources.list specifically still requires the non-free module. (We add this for you in the Linuxcnc ISO).

Can you post the .pnconf file that causes the error?

@rodw, mb2hal also works with TCP/IP:
 

 

linuxcnc.org/docs/html/gui/gladevcp.html

Isn't MB2hal require a  RS485  connection (serial port)? In that case, you need a RS485 port (like a USB to RS485 interface) 
Ethercat master requires a network port
These two interfaces are totally different

Not much to go on. Please post your current .hal and .ini files or compress your entire machine config and post it here.

You error is nothing to do with Linuxcnc but related to your hardware. We need to know about your PC, (CPU and network card) First you need to disable any power saving features in your bios that affects latency.

Then follow my advanced guide here which covers all of the gotchas with modern hardware and operating systems.
docs.google.com/document/d/1jeV_4VKzVmOI...diY/edit?usp=sharing

That is W5500 mini, and from your attached picture it does not have 5V, while the normal longer W5500 has 5V and 3.3V power.

Try this

Read on the right side how to ....

Well, I don't have 5V on my W5500. This is the only schematic I found online.

Hello all it's been a number of years (3+) and i've finally got around to getting this working on this. I graduated as a mechanical engineer and felt comfortable enough to understand this stuff now.  I was able to connect my mesa 7i96, problem was that my linux distribution had issues connecting to the 7i96. I basically upgraded to the latest linuxcnc (currently on debian 12 with linux 2.9.3) and i have the machine moving using AXIS, for some reason when i try to setup the QTPlasmaC and it will not operate .

Here are the errors i'm getting(see image attached), what doesnt make sense to me is that my jitter is the same as when im using AXIS... and AXIS works great!

Honestly my only goal is for the machine to cut metal with the plasma torch and have a functional torch height controller, i dont care which GUI is used.

If anyone could please help me get this machine going i'd greatly appreciate it!!! I have projects that require plasma cut parts and i'm desperate for this machine to work.

Thank you in advanced , have a great day everyone!


 

Hello, I created a panel in Glade. However, when I load it in LinuxCNC, it appears faded and shadowed. What could be wrong?