Measurement Studio

Similar Questions

• Siemens simatic wincc SCADA and LabView/Measurement Studio

  Hi all

  I am currently working on the design of wireless data acquisition system using materials. Input signals captured by wirelessDAQ NOR will appear eventually in WinCC from Siemens SCADA system.

  Is there a way to make this configuration? I thought to is to develop software for the acquisition of data using LabView/Measurement Studio and link code to WinCC via Visual Basic (for example via DAQmx). Thanks for all your comments.

  Hi kid_26,

  I'm sorry.

  It is the only option.

  If you press the cost, write a VB6 to call DAQmx is an option.

  Sincerely, Kate

• Measurement Studio 2015 lack of reference to Assembly for "NumericControlCommands."

  I just migrated my project Studio 2012 measurement to Measurement Studio 2015 and udpated VS2013 references.  I get the following error in my XAML

  Type reference cannot find the named type ' {http://schemas.ni.com/controls/2009/xaml/presentation/primitives} NumericControlCommands'.

  It turns out that it was an indirect exception related to a few of my files that I still need to change "NumericControlCommands" to "ControlCommands".  The project seems to work fine now.

  Thank you

• License with Measurement Studio and Visual Basic 2008 Express problem

  Hello!

  I have a license for the professional edition of studio measure 8.5 and I use the express edition of Visual Basic 2008.

  I am trying to use the FFTfunction, but get the exception {"NationalInstruments.Restricted.AnalysisLicenser is unauthorized."}

  Does anyone have an idea?

  Thanks in advance!

  Andreas

  Here is the full error message:

  System.TypeInitializationException wurde nicht Festival.
  Message = "Der Typeninitialisierer as 'NationalInstruments.Analysis.Dsp.Transforms' hat eine exception caused."
  Source = "NationalInstruments.Analysis.Professional"
  TypeName = "NationalInstruments.Analysis.Dsp.Transforms"
  StackTrace:
  BEI NationalInstruments.Analysis.Dsp.Transforms.RealFft (Double [] realData)
  EIB LDS. LDS_Form1.ButtonFFT_Click (Object sender, EventArgs e) D:\devel\LDS\pc\LDS\LDS\LDS_Form1.vb:Zeile 1700.
  bei System.Windows.Forms.Control.OnClick (EventArgs e)
  bei System.Windows.Forms.Button.OnClick (EventArgs e)
  bei System.Windows.Forms.Button.OnMouseUp (MouseEventArgs mevent)
  EIB System.Windows.Forms.Control.WmMouseUp (Message & m, MouseButtons, Int32 clicks button)
  EIB System.Windows.Forms.Control.WndProc (Message & m)
  bei System.Windows.Forms.ButtonBase.WndProc (Message & m)
  bei System.Windows.Forms.Button.WndProc (Message & m)
  EIB System.Windows.Forms.Control.ControlNativeWindow.OnMessage (Message & m)
  EIB System.Windows.Forms.Control.ControlNativeWindow.WndProc (Message & m)
  bei System.Windows.Forms.NativeWindow.DebuggableCallback (IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
  bei System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW (MSG & msg)
  bei System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop (Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
  bei System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner (Int32 reason, ApplicationContext context)
  bei System.Windows.Forms.Application.ThreadContext.RunMessageLoop (Int32 reason, ApplicationContext context)
  EIB System.Windows.Forms.Application.Run (ApplicationContext context)
  BEI Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun)
  BEI Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel)
  BEI Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run (String [] command-line)
  EIB LDS. My.MyApplication.Main (String [] Args) in 17d14f5c-a337-4978-8281 - 53493378c1071.vb:Zeile 81.
  bei System.AppDomain._nExecuteAssembly (Assembly, String [] args)
  bei System.AppDomain.nExecuteAssembly (Assembly, String [] args)
  bei System.Runtime.Hosting.ManifestRunner.Run (Boolean checkAptModel)
  bei System.Runtime.Hosting.ManifestRunner.ExecuteAsAssembly)
  bei System.Runtime.Hosting.ApplicationActivator.CreateInstance (ActivationContext activationContext, String [] activationCustomData)
  bei System.Runtime.Hosting.ApplicationActivator.CreateInstance (ActivationContext activationContext)
  EIB System.Activator.CreateInstance (ActivationContext activationContext)
  BEI Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssemblyDebugInZone)
  bei System.Threading.ThreadHelper.ThreadStart_Context (Object state)
  bei System.Threading.ExecutionContext.Run (ExecutionContext executionContext, ContextCallback callback, Object state)
  bei System.Threading.ThreadHelper.ThreadStart)
  InnerException: System.ComponentModel.LicenseException
  Message = "NationalInstruments.Restricted.AnalysisLicenser is unlicensed."
  Source = "NationalInstruments.Common"
  StackTrace:
  AT NationalInstruments.Restricted.LicenseBase.ShowUnLicensedBehavior (Type type, object instance)
  BEI NationalInstruments.Restricted.LicenseBase.a (String Type A_0, A_1, A_2 object)
  BEI NationalInstruments.Restricted.LicenseBase.a (Type A_0, A_1 object)
  AT NationalInstruments.Restricted.LicenseBase.RunTimeCheck (Type type, LicenseContext context, object instance)
  BEI NationalInstruments.Restricted.LicenseProviderBase.GetLicense (context, type, object, Boolean allowExceptions instance Type, LicenseContext)
  bei System.ComponentModel.LicenseManager.ValidateInternalRecursive (context LicenseContext, Type type, Object instance, Boolean allowExceptions, license, licenseKey, String & license)
  bei System.ComponentModel.LicenseManager.ValidateInternal (Type type, Object instance, Boolean allowExceptions, license & license)
  bei System.ComponentModel.LicenseManager.Validate (Type type, object instance)
  EIB NationalInstruments.Restricted.AnalysisLicenser... ctor()
  EIB NationalInstruments.Analysis.Dsp.Transforms... cctor()
  InnerException:

  Hi Andreas,

  It is scheduled for any Visual Studio Express edition, because these editions do not allow 3rd party integration. So, you will need to perform some additional steps to get a license to work properly.  Refer to the Measurement Studio for Visual Studio Express Editions support KB (in particular, paragraph 2 pointing you to our help).

  Best regards

• Measurement Studio 2015 Installer creator vs WIX

  What is the reasoning behind the development of the new measurement feature Studio Installer?  I have never had any problem using Wix for mixed deployment c#, C++ that use Measurement Studio products.  It just seems like an odd sense to send the development resources, opossed say, improve support WPF?  Or documentation of the product and samples for WPF?

  Mark DeArman

  Hi, Mark

  The reasons that we have dedicated development resources by creating a builder application to install for Measurement Studio are:
  1. Once Visual Studio has diminished in favour of their native installation project, the number of support requests involving the deployment of Measurement Studio has increased considerably.
  2. Apart from the Setup project, the only other method of deployment which Measurement Studio is fully supported is Windows Installer XML (WiX), which was not well received by customers. Almighty, WiX has a steep learning curve, even to accomplish a simple deployment.
  3 measurement Studio does not support InstallShield, among other popular solutions to WiX for the deployment.
  4. the supported deployment methods, no guide customers what drivers OR and components attached to their application to ensure good run time behavior.

  Builder installer helps to solve these problems and has already received positive feedback from many customers.

  Please let us know if you have any other questions about the Builder installer; We would be happy to help you!

  Thank you

• Measurement Studio for visual studio 2008 8.1.2

  Hello, I installed Visual Studio 2008 and I use the Visual C++ 2008 him.  However, Measurement Studio 8.1.2 (which I have) do not natively connect to VC 2008.  I tried to manually add the box controls to tools... but namespace NationalInstruments.UI.WindowsForms seems not to be there?  Maybe I need to change something somewhere?  Any help would be most appreciated.

  Defiance-

  If I understand correctly, you are trying to add references to assemblies .NET Measurement Studio for a C++ 2008 project. Is this correct?

  In this case, when you have created your project, you chose one of the models in the CLR (see screenshot) category?

  If so, then to add references to assemblies Measurement Studio, you go into the Visual Studio point Project menu > properties and select common properties > structure and references > add a new reference. MStudio 8.1.2 assemblies should appear in the list. If this isn't the case, you can navigate to them. They have installed by default on \Program Files\National Instruments\MeasurementStudioVS2005\DotNET\Assemblies\Current. Make sure that you add all required dependent assemblies (usually NationalInstruments.UI.dll and NationalInstruments.Common.dll).

  Also, you should be able to create a box Tools tab and add controls.

  If you try to do something else, could you give more details on exactly the type of project you want to create?

  David Rohacek

  National Instruments

• Best way to generate the software clock for USB-6501 of Measurement Studio for c# VS2008

  Hi all

  I wonder if there is a better way to generate a clock software for USB-6501 of Measurement Studio for VS2008 in C Sharp?

  I have developed a clock using C Sharp "Thread.Sleep (msecPauseTime)"; and statements to switch digital output high and low. There are a few things I noticed in creating a software clock in this way:

  1. The smallest delay by the Thread.Sleep command time is 1 millisecond (which means higher clock period is 2 msec-500 Hz, not holding not ball account no. 2 below).
  2. Sometimes the delay I see on an oscilloscope is considerably longer than the delay that I specified in the sleep command.

  In my application, I create signals (a clock, a latch enable and data series) to control what an attenuator step through the USB-6501 RF connected to a USB 2.0 on my computer. This particular step RF attenuator can accept clocks with frequencies up to 10 MHz, so I would like to generate a software clock (without having to connect to an external clock to a line of input on the USB-6501) which is closest to this maximum frequency, and I think that the USB2.0 line could handle clock speeds over 500 Hz. Also, I would like to know why the delays that I see on the scope are sometimes longer than the time specified by the Thread.Sleep command. Is it caused by the suspension of the execution of my program processor for something else, as I suspect? Of course, this isn't a big deal, because it does not affect the time as my serial data and pieces change compared to my clock. However, I would like to know why it does this.

  I appreciate your help.

  Thank you

  Jonathan Becker

  Doctoral research engineer

  Carnegie Mellon Silicon Valley

  Jonathan,

  Since the USB-6501 DIO is software programmed, you are at the mercy of the planning of the operating system and won't be able to work reliably with an external clock in the software.

  You can try to set the priority of your thread 'generation of clock' to improve performance, however, because Windows is not a deterministic operating system, there are still no guarantees.  Operating systems are not required to honor the priority of threads.  You can find examples and information on the definition of the priorities of the threads in c# here:

  http://msdn.Microsoft.com/en-us/library/system.Threading.thread.priority.aspx

  Kind regards

• problem reading DAQmx using Measurement Studio 2010 (even with examples OR)

  Hi all

  I'm reading the voltage using a map of NOR-DAQ-6211 with Measurement Studio 2010 SP1 V9.1.0.204. using Visual Basic .net 2010.
  When I create the task of data acquisition with the measurement studio Wizard, (Assistant DAQ) everything works fine. However, when I try to create my own task player in looking over the "ContAcqVoltageSamples_IntClk" everything I read is a value in the range of Vmin to Vmax (or to Vmin Vmax) and then she stays there no matter if I change my diet. Vmin and Vmax does not yet match my values of voltage. (It acts like that on my application and example of OR) I guess I missed a few initial settings. The config of AIChannel in two projects (manual task and Augo-Gen) use AIChannelConfig.RSE (I tried other options, but no luck).

  The only wiered thing is that when I open examples of projects, VS does not recognize the object references of NOR. Workspace names DAQmx. When I check the references, it shows that it does not find the reference to NI.Common. To make it work/compilation, removed from the solution and I again added. (I don't think this is related, as it seems that there are available tensions but not read correctly).

  The other thing is that my input voltage is 3 or 0 volt. When you use the manual DAQtask, when I toggle the voltage, the values displayed change momentarily the order of 0.001 Volts and then go back to their previous values of Vmax and Vmin.

  Is there more information I can provide?

  Help, please
  Thank you

  Yay! I just solved my problem,

  From the first moment I knew there was something fishy about this AITerminalConfig thingy! I made two errors:

  1. in the code example Configuration AI is encoded: CType (-1, AITerminalConfiguration) that caused the code example does not work for all channels to HAVE it

  2 - also, I have in my code, I had put this config to the correct value, but I was checking ai0 all the time while the signal was on another I. I was under the impression that since the example does not work for all my channels, then probably my code does not work as well.

  If after changing the line in the example for the correct terminal configuration settings, he began working for the AI number I was looking for too much and I found that my code worked for my AI # correctly from the beginning. I wasn't just to see it!

• Measurement Studio for purely GUI using?

  Hi all

  I find graphical LabVIEW + fantastic approach to the acquisition, transfer and processing of data from data flow programming. The façade is also ideal for stand-alone single screw, or quick hacks to try a code.

  However, when it comes to creating a professional quality for a large application GUI, I find offers of tedious LabVIEW and strains to use. So far, I used objects of façade regular, XControls, event structures and property nodes.

  I am now looking at Measurement Studio. Here's what I think:

  • Implement business logic in LabVIEW (compiled as a DLL)
  
  
  • Implement GUI in XAML or C++ - primarily use native Windows elements, but bring in the Measurement Studio controls a graphical representation

  Is this a viable, reasonable approach? Is there a "witch hunt" s that I should look out for?

  Thank you!

  Hi JKSH,

  Everything you described should be possible that LabVIEW can create DLLs and assemblies. He may ask you to register an assembly that is added to your project so that everything works correctly when you compile. In addition, you must have LabVIEW Run time engine (RTE) installed on the machine that you are running the application on. If this is the same machine that LabVIEW is installed, you should be all set and if not this editor is available on our website (ni.com/downloads).

• Visual Studio 2008 Pro takes a long time to start after the installation of measurement Studio 2009

  After installing Measurement Studio 2009, I noticed that it takes a long time (30-60 seconds) to open a Visual Studio project.

  I do not have an internet connection on my development computer and suspect he might be waiting on some kind of operation of the network to time out.  I had problems with Visual Studio in the past as well and had to work around them by adding entries to my hosts file (to redirect some addresses of Microsoft to the local IP address - this causes network operations to expire immediately).

  Just curious if anyone has encountered this kind of slow startup time and found a solution.

  Thank you!

  I found an article referring to a question similar to MS 8.1.  I don't know if the problem has simply not been corrected or why I am still having this problem.  Workaround "per computer" listed in the article solved my problem.

  http://digital.NI.com/public.nsf/allkb/18E25101F0839C6286256F960061B282 I have

• Measurment Studio 2015 Builder installer not conditioning not DLL Analysis.Professional

  Hello

  My application uses the package MS Anaylsis I want is not included in the Installer Setup Builder installer. I checked the "OR Measurement Studio Anaylysis .NET language runtime 2015 for .NET 4.5" in the Section of the driver NOR.

  After the execution of the installation on a machine of own generation Win8-64 my application generates a "could not find error Assembly" to "NationalInstruments.Anaylsis.Professional, 13.0.45.242 Version.

  A careful review of all available libraries does not suggest there is a more appropriate library to include in the build. My installation Builder is for a mixed environment, but my request is built as x 64.

  Can anyone suggest a solution?

  Thank you, Frank.

  Hi, Frank

  On your deployed machine, can you check the following directory and take a screenshot?

  C:\Windows\Microsoft.NET\assembly\GAC_MSIL\NationalInstruments.Analysis.Professional

  It is possible that this happens because your application was built against the 13.0.45.242 version of NationalInstruments.Analysis.Professional, but the version installs the 15.0.45.49153 OR Measurement Studio analysis .NET Language Runtime install. If this is the case, you can do two things:

  • (Recommended) Rebuild your application against the Measurement Studio .NET assemblies 2015 versions before you redeploy using the 2015 runtime installation programs.
  
  
  • Create an application configuration file that redirects 13.0.45.xxxx to 15.0.45.49153 NationalInstruments.Analysis.Professional.

• Measurement Studio 2015 under VS2012 c# IntelliSense does not

  I upgraqded my MS2013 MS2015 and now intellisense on MS all controls is no longer works. For all other controls language intellisense works normally. When I open an existing project using MS control (Gauage, plots, etc.) all the properties of control NOR and methods are of red color. When I press period after an instance control no properties or methods appear. Exisitng with methods and properties valid projects still compile without error.

  Hi Frank334,

  I tried to recreate what you see by creating a project using measures Studio 2013 for Visual Studio 2012 that mimics the code in your screenshot, installation of measurement Studio for Visual Studio 2012 2015 and again opening the project. Here's what I see:

  

  Everything seems to work. Can you walk us through the process you used to update to Measurement Studio 2015? Have you tried anything to refresh the IntelliSense information for your project? I found this article of stack overflow that can help: http://stackoverflow.com/questions/13375961/visual-studio-2012-intellisense-sometimes-disappearing-b...

• WiX Installer Measurement Studio merge modules

  Is there a tutorial somewhere on how to create a WiX Installer for a Measurement Studio application similar to the http://digital.ni.com/public.nsf/allkb/ED87C183E056CAC386256DF1004E54C6Knowledge Base article? I have an application Measurement Studio c# which I am creating a WiX Installer for and I have problems to get the measurement of inside studio merge modules. I get errors ICE30. I'm using WiX 3.0.

  Hi d_sdl,

  Our merge modules should work in WiX, as I have tested this several times. When you say that you have found ICE30, that fails your build? As you probably already know, one of the nice features of WiX is that you can set a flag so that whenever WiX compiles and links your source, it works ICES on them. This allows you to catch problems early in your development process. I guess you do is put the WiX linker fails if ICE warnings/errors are thrown. You can configure WiX for actions based on ICES advice you get. What is important is that you can turn off this setting, but it depends on how you are nvoking WiX (i.e. through NAnt, MSBuild, Votive, etc.). In any case, there are different ways to disable this option. What I would say is to disable the option, or be specific about which ICES to ignore. This decision would be to the you. The key is to understand what actually means ICES and determine if they are legitimate questions.

  ICE30 can indicate a variety of different things, but a common reason corresponds to the entries of the SFN. Some of our merge modules are always generated through Visual Studio deployment projects and VS created RFU very well. Thus, you're left with SFN entries duplicated in the MSM. Long file names are different, but the short file names are the same. WiX does this correctly which is nice, but unfortunately we can't convert some of these modules more MSM because of VS restrictions and limitations, that we found. It would be nice if better RFU created VS.

  Attached is a zip file that contains two projects that are:

  • C# project that produces the binary file that the Setup program will install
  • Project of WiX that creates the MSI file

  First, be sure to build the c# project. I tested the MSI that result, and it works very well on a target system.

  Note If you want to load the wix project, you must have the final version of Votive on your system.

  Best regards

• OR e/s 14 Instrument installation wizard is not compatible Measurement Studio

  Hello

  I want to create an Application for Windows OR VISA using Visual c#, but I can not find this new project dialog box template.

  I also read this post (http://forums.ni.com/t5/Measurement-Studio-for-NET/Can-t-find-Microsoft-templates-for-Measurement-St...), but it seems that it is not my problem.

  When I tried to reinstall Wizard NI Instrument of e/s, I found that it provides no support for Measurement Studio.

  I installed MS Visual Studio Ultimate 2012, Measurement Studio Enterprise 2013, NI-VISA 5.4, OR-488. 2 3.1.1 OR August 2014 by this order device driver. My OS is Windows 7 Professional 32 bit.

  What should I do now?

  Thank you
  Thang

  Hello thangvq,

  I took a look at the Release Notes for measurement Studio 2013, and it seems that the Instrument i/o Assistant OR not is not supported in versions of Visual Studio 2010 at the latest.  Take a look at the Support section of the drivers on page 5 for more information.

  Myriam

• DAQ Assistant does not appear when starting a new project in Visual Studio 8 with Measurement Studio

  Hello

  I have installed a system with the following configuration:

  Windows 7 Prof

  OR MAX

  Visual Studio 2008 Standard

  Measurement Studio 2013 (evaluation)

  Device drivers OR Feb 2013

  When I start a new project in Visual Studio, I can choose a model with NEITHER Windows forms application. After that I get an overview of the classes, but after that, I get no DAQ assistant. What Miss me as is actual references in the Toolbox, with the exception of the buttons and graphics of NOR.

  Someone at - it a solution for this problem?

  Thanks in advance,

  Erik

  Dear Erik,

  I saw the same problem and I think that you can solve with the installation of the DAQmx 8.8 and make sure to include the Visual Studio integration.

  If you have any questions just reply to this email.

  Have a good time.

  Kind regards

  Hossein

• Measurement Studio help

  Hey,.

  I tried to access the MeasurementStudioHelp (2012) in the menu in visual studio 2010.

  He brings me here, but the page is no longer available. She moved?

  http://msdn.Microsoft.com/query/dev10.query?AppID=Dev10IDEF1&l=en-us&k=k (FUSINGNIMSTUDIOHELP) & rd = tru...

  Im a beginner with the software NOR, so any help is appreciated

  Hi Jules,.

  It's a little tricky with Visual Studio 2010, as microsoft does not allow third parties to automatically install the help files. That means these files must be installed manually. There is a short explanation of the following link explaining how:

  Configuration of measurement Studio help in Visual Studio 2010

  http://digital.NI.com/public.nsf/allkb/8C2C52759863304D86257811007F709C?OpenDocument

  Hope this helps you.