Is it possible to program in Visual Studio/Measurement Studio for CompactDAQ Stand Alone Chassis Running WES7?

[DieselPower]

Thanks.

[Paul-D]

Greetings Michael!  Indeed the Stand-Alone NI CompactDAQ systems can be programmed with Visual Studio/Measurement studio.  The system performs as a fully functional computer that is attached to the CompactDAQ backplane, and will work just like any other system that you've worked with.  Also, in regards to WES7, for your purposes, just think of it as Windows 7 that had a few extra functionalitys pulled out that weren't necessary for a system like this.  Also, any code you've already written for other DAQ systems should be portable to this system.

If you haven't already checked it out, give http://www.ni.com/compactdaq/stand-alone/en/ a look, and let us know if you have any further questions!

Thanks,

Paul

[DieselPower]

Thanks.  One more question...well, maybe two.  I can only get a 9Hz (System.Timers.Timer) loop in Windows 7.  Would I be able to get 10Hz with WES7?  Is WES7 necessarily more stable than W7?

Thanks again.

[Paul-D]

Hey Michael, hopefully another Applications Engineer should be following up with you about your question the timers loop as I'm not familiar with that functionality.  As far as stability goes, to my knowledge WES7 isn't necessarily any more or less stable than Windows 7.  The features that are removed aren't so much for stability, but to save space, and because they aren't necessarily needed for a testing type environment.  As a general note however, this system compared to your development could be more stable just from the fact that you probably won't be loading a lot of extra software and stuff onto the system beyond the things you would need to run your code (although it is certainly capable of doing that).  Additionally, the embedded controller has been designed and tested by National Instruments, so there should be a confidence level there of it interacting with other NI hardware and software.

[mudson]

Hello Michael,

From what I've been able to find on msdn.microsoft.com, that timer is reliant on the system clock.  However, most of the time limitations I've found seem to put the minimum period at about 55ms (~18Hz), so the ceiling you've hit does seem unusual.  A caveat that should be included with that last statement: the timer's are based on the system time, and since we're working in Windows, determinism is not guaranteed.  This article (social.msdn.microsoft.com) seemed pretty helpful.