Advanced Search

I understand that any computer will do but with my previous set up I've ran into issues with the actual computer being unstable. Halfway threw cutting the thing crashes complete freeze up. I am looking for a computer that is able to handle being left on for days on end no instability.

How do you intend to send the count and control signals to the PC?

www.google.com/search?q=linuxcnc+arduino...4IoB&sclient=gws-wiz

Micro2000 wrote:

What about redeon/amd

Hit and miss, some work nicely, some do not.

What about redeon/amd

Awesome thank you!! So If I want to use easy probe I need to upgrade my version of LinuxCNC?

I'm still not sure exactly how to describe this issue, I can only demonstrate it.
You can see here how G61/G64 are related to this:

The larger the P value the further into the program the interpreter will be able to read.
If the interpreter has reached a queuebuster when the program is aborted, the interpreter state and machine state will be synched properly(?)

My problem is how to write hal configuration for this operation i'm fimilier with arduino code but i'm new to linuxcnc can you help me with hal config

rtt min/avg/max/mdev = 0.044/0.061/9.253/0.062 ms

The 9.253 ms is the issue

I suspect you have Realtek Ethernet hardware so need to install the DKMS driver

You mean the RTAI kernel?
It should be on our server as it also goes with the RTAI version of LinuxCNC.
See the documentation on how to proceed for 2.8.4
Edit
That does not mean you keep the 1050, it has to go out, NVIDIA cards cause latency issues, so should not be used.

Nicely done, thank you.

Is there a specific version or just newest stable?

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/

great news! glad it sorted out!

looks like a hardware compatibility issue with vtk. did you check the compatibility per the docs for opengl?