If you're looking to put Linux on a thin client PC, then there's quite a bit of useful info. here:
https://www.parkytowers.me.uk/thin/
... just wish I had the time to properly learn a new OS
Printable View
If you're looking to put Linux on a thin client PC, then there's quite a bit of useful info. here:
https://www.parkytowers.me.uk/thin/
... just wish I had the time to properly learn a new OS
I can get a new OS on okay, it's trialling UCCNC on W7CE (native install) that's problematic
Experience so far, dry-fitting a LinuxCNC install. Wheezy (Debian 7 based) has the latency test spiking around 130us, and Stetch (Debian 9) around 180us. Looking at the graphs these are frequent large spikes (circa 1-second, short duration - interrupts? but seemingly random in nature) against a baseline of around 20us. I've looked at SMI and power management - no gains there, and similarly with disconnecting Ethernet and WiFi. Under Wheezy I couldn't get WiFi operation (and it's too archaic to be a comfortable installation). Upgraded 4GB ram to 8GB ram under Stretch with no improvement (though general usage feels better).
Beautiful, small form-factor - the T610Plus is a nice, silent and cool running PC (the fan on a Raspberry Pi 4 drowns out the HP), good connectivity, but not good real-time performance out-of-the-box.
Having scrimped on this, I've now had to spend £300 on a 7176e card to support (though that's as much for the I/O that I want for MPGs and spindle encoders) - I don't think there was much mileage in using the PP for this. Of course, for a linux buff, if you can set core-affinities to OS/interrupts onto one core and LinuxCNC onto the second - your results may vary.
I think Stretch is the preferred version for Mesa cards.Quote:
Experience so far, dry-fitting a LinuxCNC install. Wheezy
http://linuxcnc.org/downloads/
Clive - Cheers - clearly I shouldn't write early in the morning - I meant Stretch (not Squeeze) - I've amended the post above.
Okay, perhaps a little premature but this is the first day that I've had a controller wired-up (standalone stepper), the Mesa 7i76E and the thin-client (T610 plus, 8GB memory).
I knew the latency test was a bit mheh!, averaging around 200us but figured having an Ethernet motion controller would offset that. Prior to this I'd been doing all the Debian updates, updates to non-free graphic drivers, increasing system memory, and following as many (diverse!) opinions on tuning a LinuxCNC installation as I could as well as disabling all power-management under the BIOS. Now, this was the first time I've had to configure an interface (previously ran under the simulation mode for familiarisation), but in a nut-shell... it's pants! Frequent error messages through through what appears to be loss of ethernet packets. I've tried point-to-point as well as through a standalone switch - I can run from seconds to minutes, but ultimately it fails.
Still treading carefully on new territory for me, I've reconfigured an old XP box (Viglen Genie - great little boxes) previously used for Mach/PP/Ethernet to LinuxCNC (latest, and same install as the thin client). 40 minutes later I've got rock-solid performance and latency in the 3-6us range.
Perhaps will a bit of tlc the thin client is a possibility, but facing a number of learning curves at this time I'm taking it off the table for now and sticking with a standard machine, which, thinking about it, cost less than the thin client and is only marginally larger.
Your experience may vary.
EDIT:
For S&Gs, if I get time this afternoon I might try walking the path of getting LinuxCNC onto a RaspPi4 that's otherwise collecting dust.