GIGABYTE GA-D525TUD Intel Atom D525

Yes it was just replaced by the E45M1-M which looks identical except for a
chipset upgrade (e450 instead of e350 APU) so its a tiny bit faster.

I checked the latency with a scope by toggling an I/O bit in the servo thread

(I originally did this to see why, even though they often show good latency test results,
the Atom motheboards wont run a servo thread above about 1.5 KHz without error)

As an addenda the E35M1-M cheerfully runs a servo loop at 2KHz and will run at 4KHz but has real time errors at startup (but never again)

I've always wanted to know.. can one live with the initial realtime error, if then it doesn't appear anymore during use?

Hi

You mustn't confuse notifications with occurrences.

Linuxcnc only produces one realtime error warning at the first instance, no matter how many further instances there are.
If you get one straight away after starting axis, it generally means you have a serious enough problem for it not to run properly.

regards

The error is definitely just a startup error, and is visible on a scope as such.
It causes other problems that happen only at startup as well

Thats interesting, any time I have had a realtime error immediately at startup, either the base thread has been set too fast or the machine is useless.
Quite a few of the latter!

I have no base thread and am trying to find out why there are startup delays that are never repeated. Next step is to instrument the real time performance with a hardware stepgen set to 10 MHz

Well I do have a Dell that will spike one time in the first 3 minutes. After that it is fine in use for hours and testing overnight.

Rick G