You are here: / / Windows 10 vs Linux (Ubuntu) for ModBus TCP/IP Master
Hello Modbus experts,
After reading John’s article on Windows vs Linux I was intrigued about the idea of using Windows 10 to host my Modbus master in a production environment.
We already have a prototype written in C#, but our client has some concerns about the reliability (and response speed) of Windows. In the past he experienced some times where Windows would delay before processing network requests (I’m wondering if it was related to the Nagle algorithm), so he’s advocating Linux.
Some details on the project:
– The hardware will be a little PC stick with a Quad Core Intel Atom CherryTrail processor
– We need a data read rate of 4Hz
– We want a very short ‘processing’ time on the master side, so the client doesn’t get held up by the master
I’ve got quite a bit of experience using Windows for desktop apps, console app and web sites, but not near-realtime processes like this.
– Is Windows 10 (not IoT) sufficient for the task or is Linux better suited?
– If not, is Windows IoT any better?
I suspect Windows 10 with the hardware we have will be fine (and we may need to disable the Nagle algorithm) but I’d love some experienced, expert advice.
I can’t imagine you would have any issue running Modbus on either platform and achieving 4Hz.
If this is Modbus RTU the serial baud rate and number of register being R/W could be factors but the processing on either of Windows or Linux would not be a significant time-suck. Time on the wire with RTU would be the biggest factor.
There are real time extension for both you may consider if you are having performance issues.
You must be logged in to reply to this topic.