Unexpected realtime delay

Hey everyone-

I've been getting this error intermittently on one toolpath for a new part. Sometimes it happens in the first few seconds, sometimes it takes 5 minutes or so, but it always happens eventually running this program. It seems to "lose" it's place in the Y axis and will machine features offcenter in Y after the error occurs. I've spent several hours trying to internet diagnose it myself, and have realized I'm waaaaay out of my depth... most of the time was spent googling what all the acronyms mean.

I've read that it may have something to do with acceleration speed, so I tried slowing it down to a crawl, but still get the error. I've also read that it can have something to do with latency... I ran the test overnight, abused it as much as I could, and came up with max jitter base thread of 22,000. Originally I had it set up for 25,000, but upped it to 30,000 and still get the error.
I've found at least somewhat similar threads in many places with suggestions about RTAI, ACPI, APIC, disabling things in BIOS, something about kernels, graphics cards, etc and pretty quickly realized that this is an enormous language that I definitely don't speak.

Anybody able/willing to walk a dummy through troubleshooting this?

Update: I've now tried setting base period maximum jitter to: 10,000 15,000 25,000 30,000 and 50,000 and all of them give me the same error

I can’t stress enough how Greek this is to me... I’ve never built/worked on a computer of any sort in my life, and so far have found Linux to be endlessly frustrating although I’m sure it’s from a lack of experience.

tommylight wrote:

What PC?
Start by removing the processor cooler if it is an older PC, high temps will force the processor to reduce speed causing high latency spikes, check if it is sitting properly, fan spins freely, the thermal paste is not hard and replace the paste if possible.

It’s an older HP desktop. I can look at/grab pics of anything if that helps? The machine was in use when I bought it, and as far as I can tell the seller was trustworthy.

Processor cooler is the fan inside the computer I’m assuming?

tommylight wrote:

Then remove memory modules, leave only one and test, then the other module etc etc, of course if there are more than one.

Memory modules are inside the computer as well?

tommylight wrote:

What does
uname -a
in a terminal say?

I attached a pic below

tommylight wrote:

Disable hyperthreading is possible in bios, C states, modem, serial, virtualisation, TPM, speedstep, turbo, etc.

Can you walk me through how? I’ve read “disable xyz in bios” in a bunch of different places, but can’t figure out how to actually do it

tommylight wrote:

setting the Base Period to 100000 will limit the step rate but might remove the issue, then try 80000 and check how that does.

I’ve tried many different base period settings, but anything I enter over 50,000 defaults back to 50,000. The previous owner had it set at 28,000 seemingly with good results.

Bigger picture and probably dumb question: is there a kind of requisite minimum level of tech/programming/computer science knowledge necessary to run a machine using Linux? I originally liked the idea of having an older, heavier machine with a modern control, but the gap between setup and actually making parts is starting to seem astronomical.

I suppose I’ve only noticed it running an actual part, but I’m not sure I’d be able to see it naked eye cutting air. The part is long and narrow... op1 is a 2d contour of all the outside geometry, and op2 is the one I’m having trouble with. I notice the y error in op2 because there’s that sort of “known good” frame of reference from op1. There’s a few on center features in op2 that will be visibly offcenter after the error occurs... maybe .100 or so