Measurement Studio 2013 Torrent
Jennifer Kovachick
Measurement Studio is the only set of .NET tools designed for building engineering applications in Microsoft Visual Studio to acquire, analyze, and display measurement data. You can present data clearly with engineering UI controls that are compatible with hardware-acquired data types. Measurement Studio removes the complexity of hardware communication through high-level, intuitive, object-oriented hardware class libraries. You can add custom information to acquired data by using the fastest and most flexible format for storing measurement data to disk, TDMS. You can also perform inline analysis in real time on acquired signals without the difficult task of writing custom parsing algorithms.
Hey, I am looking into how I can use NI DAQ equipment with C++ and I found two alternatives: Measurement Studio or implement the drivers directly into a C++ project.
I am focusing on the former in this post: How compatible is measurement studio, for Visual Studio 2019, with C++? As I understand it is not possible because MFC is legacy since 2010?
DAQmx is a normal C API. Nothing about it is C++-ish. So you won't find any C++ related documentation. But C++ can of course perfectly call C APIs so just go through the DAQmx online help here and then move over to the related C Documentation for DAQmx. That's all you should need to be ready to start rocking.
Thanks for your reply. It did not quite answer my question. Maybe I should not have mentioned the latter part you answered to because it is not the main topic, my brain got a bit fried from having looked at every source I could find on this subject so I mentioned it, maybe mostly to myself, to make sure that I already know about using the NI C-drivers in C++. But I want to know if MS can work in C++.
Some say yes-ish to this as if it was obvious which makes me unsure if they actually are talking about MS in C++ or just NI c-drivers in C++ in general. The link from NI I provided seems to state MS in C++ is possible? How, I cannot find the help manual for visual C++ as they mentioned. Projects can only be created in C# or VB. From what I understand there used to be a way with MFC legacy but it's gone since 2010.
In the end I skipped Measurement Studio and used the C-drivers with QT instead as GUI... It is not the direct solution to my question but this is what ended up happening in this instance because it seems too uncommon to work with MS in C++ even if it is stated as an option by NI themselves.
It would be nice to use NI's tools more but with QT I am not relying on a tool that I'm not sure how well maintained it will be and seems to be a bit uncommon.
Measurement Studio is a set of libraries and tools that provide an easy-to-use interface for acquiring, analyzing, and presenting data from National Instruments DAQ hardware. Measurement Studio supports various programming languages, including C++.
Measurement Studio provides a set of libraries that can be used directly in your C++ projects to interface with National Instruments DAQ hardware. These libraries are designed to work with both MFC and non-MFC applications. However, MFC is not a requirement to use Measurement Studio in your C++ project.
Regarding your concern about MFC being legacy, it is true that Microsoft has shifted its focus away from MFC in recent years. However, MFC is still supported in Visual Studio 2019, and you can still use MFC with Measurement Studio if you wish.
In summary, Measurement Studio is compatible with C++ and supports both MFC and non-MFC applications. So, you can use it to interface with National Instruments DAQ hardware in your C++ project without any issues.
It's probably a dumb question, but I can't seem to start my evaluation of Measurement Studio 2019. I've downloaded and installed it - the NI license manager shows it's available for evaluation. But when I open Visual Studio 2019, nothing happens. I'd like to create a Measurement Studio project, but it's not available and neither are its menu and toolbox. What am I missing?
I installed Measurement Studio Pro thinking it would work with the VS 2019 Community edition. After finding out it needs VS Pro or Enterprise I installed the VS Pro demo, then had to un-install and re-install mstudio so it could find the right VS folders. It took a couple reboots for some reason but I finally had the Measurement Studio sub-menu under Extensions and the NI controls in my VS toolbox. Make sure you follow the install order so the two products can communicate with each other.
I also had some licensing issues due to the MS project references in the examples defaulting to the .Enterprise version when I have the .Professional. I needed to change the reference and update the last line in the .licx file.
I wish I could be more help but I'm a LabVIEW guy with some C# skills that just bought Measurement Studio to update some old test stations. Here's another couple links I found while I was having the same issues that may be relevant:
Thanks NIquist. Yes, I've done all the steps you've recommended. That wasn't the problem. However, the issue identified in the links you provided was the real culprit. The option "Allow synchronous autoload of extensions" in VS should be checked before installing Measurement Studio (BTW: MS does not recommend it!). When this is done the rest of the "magic" happens as expected. After wasting a ton of time on this, it's finally working. I wish NI people produced a better guide for going through this.
I'm glad you got the extension working but I was hoping that would not be the solution. As you said, it is not recommended by MS. FYI, I have that setting unchecked. It IS possible that it has something to do with your Measurement Studio being in evaluation mode. Perhaps you can switch that option off if you decide to purchase it.
I must say I'm struggling a bit with C# and .NET compared to the ease of using straight LabVIEW but I'm learning fast and enjoying the challenge. Measurement Studio is definitely helping me and I'm very glad my employer approved it. If I decide to consult during my retirement I plan to buy a personal copy.
This first bumpy step got me worried about Measurement Studio. I sure hope it's not representative of its capabilities. Either way I'll probably have a lot more questions about it in the next 45 days.-) It's good to have people around who can answer them. Thanks!
NI Measurement Studio is a set of test and measurement components built by National Instruments, that integrates into the Microsoft Visual Studio environment. It includes extensive support for accessing instrumentation hardware. It has drivers and abstraction layers for many different types of instruments and buses are included or are available for inclusion.
Measurement Studio includes a suite of analysis functions, including curve fitting, spectral analysis, fast Fourier transforms (FFT) and digital filters, and visualization. It also includes the ability to share variables and pass data over the internet with network shared variables.[1]
Measurement Studio 7.0 adopted support for .NET and allowed for native .NET controls and classes to integrate into Visual Studio. As of Measurement Studio 8.0.1, support for Visual Studio 2005 and .NET 2.0 framework have been included, with support for Windows Vista first adopted in version 8.1.1. Current version of Measurement Studio drops support for multiple versions of Visual Studio including 2008, 2005, .NET 2003 and 6.0.
National Instruments also offers a product called LabVIEW,[2] which offers many of the test, measurement and control capabilities of Measurement Studio. National Instruments also offers LabWindows/CVI.[3] as an alternative for ANSI C programmers.
Selecting option 1 takes and restarting measurement studio takes you back to the first option screen described above. Selecting option 3 makes the nag message go away and then the Measurement Studio extension under Extensions->Measruement Studio appears to behave as expected.
To see how Visual Studio is keeping track of this request from the menu select Extensions->Manage Extensions and select the text "Change your settings for Extensions" which is down under the left column. You are then presented with the Options dialog with Extensions highlighted on the left. All 6 checkboxes should be checked. The last checkbox is for :
Multiple things are going on here. My first attempt at installing Measurement Studio 2019 did not allow me to see the Measurement Studio extension show up under Extensions at all. There were no NI projects available when selecting File->New->Project. To get things shook loose I did the following steps :
I launched Visual Studio 2019 and selected Create a New Project. Then I searched for "Meas" and selected NI Window Forms Application (which was not available before I uninstalled and reinstalled Measurement Studio as described above). I chose the default name and clicked the Create button.
Pressing OK on this error put me back into the project wizard with the options of Back and Create. Create took me to the same service error and Back allowed me to pick another project. After I ran the above process of making sure that Visual Studio 2019 was allowing existing extensions to run using deprecated APIs and restarting Visual Studio 2019 I was able to complete the NI Windows Forms Application (Configure your new project) wizard as expected.
UPDATE: I forgot to mention this in my previous post. Having a copy of Visual Studio 2017 Community installed seemed to hamper my ability to get measurement studio working under Visual Studio 2019. Removing Visual Studio Community 2017 and then uninstalling Measurement Studio and re-installing Measurement Studio was required on a machine I just performed an update on to get the Measurement Studio extension working under Visual Studio 2019. I remembered that I had manually removed Visual Studio Community 2017 from the machine that I was describing my installation in my previous post.
Measurement Studio 2019 and Visual Studio 2019 are not supposed to work together yet. Which makes sense because the release dates of both software were very close. We are currently developing a patch to make that possible and also clarifying that in our public documentation.
b37509886e