Windows embedded (7) - repurposing a thin client PC

[Doddy]

Clive - Cheers - clearly I shouldn't write early in the morning - I meant Stretch (not Squeeze) - I've amended the post above.

[Voicecoil]

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.

That's cool, didn't realise you could do stuff like that.

[Doddy]

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.

[Voicecoil]

That's kind of odd - you would have thought that with a thin client in it's intended role getting all it's data and apps from the central server decent ethernet would have been the first thing they'd get right.

[Doddy]

Light weight IRQ handling? I don’t know.

As OP to this thread if you have the inclination to take this thread to a conclusion then I’d happily throw the 610 in your direction if you can source a W7CE install/licence. PM me if interested

[Voicecoil]

Well I've been using the machine for real for something like 4 weeks now, so thought I ought to report on what I ended up with computer-wise. My original plan to run UCCNC on the HP610 that Doddy kindly gifted me (or an old Dell I had knocking about) came to nowt as they wouldn't support the version of open GL that the latest version of UCCNC uses, so I swapped out for the Dell/Wyse D90D7 I was using to run my audio test gear (£30 from the Bay of fleas). Some probing about revealed that you can't easily get these devices to run any other version of Windoze apart from what they came with, so I set about trying to make it work on Windoze CES7. I deleted all the networking stuff and had a few fights with the FBWF (File Based Write Filter) that's used when it's a thin client, but after that it seems to work pretty well. To change anything you have to log in as Admin, but when it comes to actual machining, I just turn it on and plug in a USB stick with the G code files. If I wasn't working remotely from my design PC I's have had a shot at networking it, but since they're 3 miles apart we'll leave that for a bit.

[Doddy]

Interesting write-up - I think we all like the idea of a dedicated, small, contained (and in my case, cheap) controller. Something that doesn't bugger off on a 2 week vacation whilst it updates to the latest and greatest patch.

I have to admit that I don't practise what I preach and I prefer a machine that I can CAD/CAM and machine as an all-in-one, simply I do not have the space for multiple monitors, keyboards and mice (even now I'm behind KVMs for linux and windows with a WAN and two LANs for the two separate machine controllers).

Just a thought - and I'm showing my ignorance for CE - is there no general "config" file used to configure what is supposed to be a deployable embedded system - that you could offer as a starter-for-ten for others here that may want to use a similar thin client? (I'm thinking if the settings are held in a single file, rather than the usual bloated windows registry crap.

EDIT: "gifted"?, hardly, we came to an arrangement that you honoured.

[Voicecoil]

Just a thought - and I'm showing my ignorance for CE - is there no general "config" file used to configure what is supposed to be a deployable embedded system - that you could offer as a starter-for-ten for others here that may want to use a similar thin client? (I'm thinking if the settings are held in a single file, rather than the usual bloated windows registry crap.

Well, I spent a bit of time looking into that side of things - being a bit perfectionist I wanted to slim down the Windoze Compact Embedded (WCE) as much as possible - but didn't really manage to sort it. It appears you're largely stuck with what you've got, the only way to thoroughly customise it is to create your own WCE image which you then install that can have as few or as many features as you want. To do that requires a development kit, one day if I'm feeling brave and with a lot of time to kill I might just give Microsoft a buzz and find out how you get one, however I can't help but feel it will be expensive.

PS there seem to be some 3rd party developers doing development kits which might be worth a look at too. With WCE7 coming to end of life in 2021, there might be something going cheap?

PPS Another thing I discovered is that WCE (unlike NT based versions) is a real time OS.

EDIT: "gifted"?, hardly, we came to an arrangement that you honoured.

Yes, with all the chaos of the last few weeks I'd forgotten that - but it was a generous arrangement and I thank you for it.

[jessieba]

You can easily do this using Windows. Compatible with DOS applications. Working in a Windows environment does not force you to give up using DOS programs. Moreover, to run DOS programs, as a rule, there is no need to exit Windows. However, DOS programs running Windows are slower. By the way, what I like about Windows is that it is absolutely unpretentious in terms of licenses. You can always find even Windows activation keys. For example, using a website mysoftwarekeys.com . I hope this information will help you.

[mra4nostop]

I found your write-up on repurposing a thin client PC quite interesting. I totally get the appeal of having a dedicated, compact, and cost-effective controller that doesn't go on vacation for software updates! Personally, I prefer an all-in-one machine for CAD/CAM purposes, considering the space constraints.
Regarding the configuration of embedded systems, I'm not an expert, but I think it would be great if there were a general "config" file that could simplify the process for others. Maybe someone in this forum knows more about it and can offer some insights.
Have you checked out the Reddit sub that discusses various Windows-related topics? They might have some helpful information for you. It's a great community to connect with fellow Windows enthusiasts.