GIGABYTE GA-D525TUD Intel Atom D525

I got the gigabyte GAD525TUD board today and installed it into a Thermaltake Element case, took about 30 minutes to get it running. I haven't had much time to tweak it but with stock bios settings and a fresh install of linuxcnc, I'm getting latency max of 13835. After fighting two machines for way too long I am thus far excited with the results. I'll try to give more numbers tomorrow as I set this up and hopefully start cutting.

I haven't had much time to tweak it but with stock bios settings and a fresh install of linuxcnc, I'm getting latency max of 13835

You should be able to get the latency lower just by using the isolcpus boot time parameter.
wiki.linuxcnc.org/cgi-bin/wiki.pl?The_Is..._Parameter_And_GRUB2

The Intel version of this board is reported to run sub 10K max jitter after this.

regards

OK just tested the GA-D525TUD (with 10,04/2.5.1), and I get much worse latency but I was pretty tough on it,
running flash videos and multiple glxgears, I had as bad as 49000 base thread latency. This is in the range that I can measure with the scope on all the Atom MBs (the latency test is not to be completely trusted as it does no hardware I/O that may be blocked) The isolcpus trick seems to make the average jitter better but the worst case stays about the same

The ASUS E35M1-M was significantly better with 21000, 26000 (servo/base) thread max jitters so seems like a fairly nice fanless LinuxCNC system

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