Does it matter what os is used ?
the OS in test equipment is only there to provide basic things like networking , file operations and the GUI. apart from that it stays out of the way.
you can't even open a shell on them
The 2xxx 3xxx and 4xxx run Windows CE. so does the 335xx series of function generators. so does many other an agilent instrument that has a full color lcd graphical interface with 320x240 or more...
The reason is simple : it allows the designers to quickly develop the UI code with standard tools like microsoft studio. they get networking / usb operations / etc thrown in for zero effort.
There is no need to worry about viruses and hacks and other crap as these things are NOT pc's. They are ARM based to begin with , the processor is an ASIC ( Spear600 ) of which zero info is available to the unwashed masses / script kiddies/ pfy hackers , and they are set up to run 1 and only one application. you can't run anything else on them. the roms are most likely statically compiled.
you can argue 'why not linux' and the answer is very simple. Too fragmented , no tools, no ports for xyz , no support.
Before you blow a fuse reading the above let me explain :
- too fragmented : there are hundreds if not thousands of builds of linux based OS... which one to pick ? ( remember we need not only the kernel , we want networking , file exchange, usb , display drivers etc .. drop and run...)
- no tools. : name me a ready out of the box environment like visual studio for linux: graphical ui builder , debugger ( remote debugger ! ) code wizards , that can also can cross compile to non-native cpu... ( develop on x86 , run on arm .. ). an environment that simply needs one to launch 'setup' and works. out of the box , without configging , mucking with link scripts , install scripts and other 'tripe' like eclipse and the other 'spit and duct-tape' requiring tools...
- no ports : remember this thing is running on an ASIC featuring an A9 core. Microsoft happens to support that one. yeah , linux too.. but you end up with the endless which flavor question ? and you wil have to spend an immeasurable amount of time tweaking and porting it and you will have to do all the work whenever a patch is required. use a prepackaged system and you do not have to spend time on that. your engineers can focus on the instrument and don't need to muck with the OS itself. that's what you pay MS for.
- no support : you are not depending on the goodwill of a bunch of goodhearted people trying to make it work. or relegated to forums where the question will end up in flamewars between vi-emacs and kde-gnome. you pick up the phone , call the paid support line and you WILL get an answer WITHIN a fixed amount of time.
remember : you work for a big-name outfit like Agilent who HAS the power to make microsoft dance... your time-to market is driven by time to develop. it only makes sense to use a prepackaged build that is supported by its maker and let's you focus on your part of the design ( the instrument ). you don't need to know how the os works or how to configure it. drop it on and run. if you pick up that phone and call the supplier you will get first class support. you will not have to disclose anything to the outside world and you will get a solution in time to release.
that is why you find windows CE in such machinery. because in the long run it is the cheapest solution. you as an instrument maker don't need to muck with anything. you develop your application and hardware , compile it and sell it. you never touch the OS. the OS is only there to make your life easier and provide things like netwrorking , remote operation , user interface etc. stuff everyone does these days and you don't want to spend a single dime on development.
Buy it. If there is a problem : yell at the supplier and demand a fix. Good luck yelling at the linux supplier ...
- who are you going to yell at ? the thousands of unconnected people spending their free time coding ?
- 'you got it for free', They don't care about your problem. Microsoft does , as their paycheck is depending on it..
-' you got the source' . I don't want the source , i want a fix !
- 'sorry we are on vim we don;t deal with emacs suckers' . OS abd devtools come from 1 source. no endless banter and fingerpointing...
- 'you got the wrong color scheme or desktop',
- 'don't be a noob everyone knows its grep-$ blah.blip >vim -u -t -e:50 -e -$option .....'. I am developing an application. i don't want to muck with the OS !
- ' and you MUST post back the fix.. because it is 'open sauce' .... yeah right. like i'm going to let the competition in on what i'm doing ...
that does not fly in the real world...