Measurement Studio Evaluation Software - Instrument Driver Factory

Greetings,
I have a copy of the Measurement Studio Evaluaiton Software CD. I've
installed the Labwindows/CVI Demo and Component Works Demo. Wanted to
check out the Instrument Driver Factory (located in VB\Instrument
Driver Factory). When I launch IDF.exe I get an error which states
that I have to install Labwindows/CVI. I tried the installation a
couple of times with the same results.
Has anyone else had this problem?
Thanks,
Rick

Mika,
I have tried the installation on two machines.
The first system has Windows XP Pro along with Labview 6.0.2 / MAX /
PCMCIA-GPIB / Visual Basic 6.0 / Visual Basic.Net
The second system has Windows 2000 and Visual Basic 6.0
The Instrument Driver Factory error reads:
The ComponentWorks Instrument Driver Factory cannot locate
Labwindows/CVI. In order to use the factory, please install
Labwindows/CVI version 5.0 or greater.
The Measurement Studio Evaluation Sofware CD installed Labwindows/CVI
5.5 The CD picks a path of "C:\MeasurementStudioDemo\CVI\"
The Instrument Driver Factory is installed in
"C:\MeasurementStudioDemo\VB\Instrument Driver Factory\"
The Instrument Driver Factory is installed when the Component Works
for Visual basic is
installed.
The part number on the installation CD is 350654B-00
Thanks for your help.
Rick
On Mon, 25 Nov 2002 14:00:06 -0600 (CST), mfukuchi wrote:
>Hi!
>I would like to reproduce the problem on a test machine. Could you
>please tell me what OS you are using, and if you have any other NI
>softwares installed on your machine. Also, am I correct that you have
>Measurement Studio Evaluaiton Software for version 6?
>
>Mika Fukuchi
>Application Engineer
>National Instruments

Similar Messages

Remove Measurement Studio Enterprise trial computers with activated Standard licenses

When I install Measurement Studio 2013 on a development computer, activate my Standard Development serial number and license that PC over the Internet, and build some software in Visual Studio, the Enterprise Development trial is automatically selected in the build process. After 30 days, the license expires, and the software behaves as if it is unlicensed - that is, it crashes. A Clean and Rebuild must be run to select the Standard Development license and make the software work again. I believe that this default behavior is incorrect. This 30 day window is often shortly after delivering the machine to a customer, so it fails on their floor right after we leave! This is not good for our reputation or for NI's reputation.
One or more of the following options would be the preferred behavior:
(1) Do not automatically enable the "Enterprise Development" trial. This trial should be deactivated by default when a Standard or Professional license is activated, and a user should be able to open NI License Manager and Activate it as required.
(2) Show a warning on start-up whenever a trial license is used. This is what LabVIEW does: upon launch of LabVIEW the user would see something like "Evaluation License - 5 days remaining". Measurement Studio users do not see this upon launch of Visual Studio, upon building the project in Visual Studio, or upon starting the resulting software. It would be nice if you could provide a link that would instruct users on how to deactivate the Enterprise Development license in this warning.
(3) Use the lowest possible development system. If Enterprise-only features are used and a Standard license and Enterprise trial are available, then the trial is necessary (though a warning as in #2 above would be nice), but otherwise use the Standard or Professional license. This issue has caused us some embarrassment several times. Please fix it!
The workaround, according to Michael Keane from NI (in Service Request #7454045, if anyone from NI is reading this), is as follows:
I assume that in License Manager during those 30 days you would see a green box next to Standard edition and a half white / half yellow box next to Enterprise. The workaround for what you are describing would be to go into ProgramData (hidden folder, will have to type it into Windows Explorer) >> National Instruments >> License Manager >> Licenses and move the Enterprise .lc file outside the Licenses folder. It probably has "TmpEthernet" in the name. This way, License Manager would not be able to find an evaluation version license and I would expect the checkbox next to Enterprise to appear white after refresh. Then, the software would have to look toward the full license and no builds would be expiring.
This works, but is still leaves the possibility for the step to be forgotten and the software to fail shortly after delivery, which is obviously no good at all! Please fix this!

Thanks for the response Daniel,
The issue and behavior are a little different than your scenario. First, I don't add a reference to Analysis.Enterprise.dll. I only use DLLs which my standard license covers. However, if I had used Analysis.Enterprise.dll, there would be no build error. When I activate Standard edition, the Enterprise trial remains active, and is not cancelled or superceded by the Standard edition license.
The process is similar to what you've described, though. I think that the evaluation period is longer than 7 days - I see that described at http://www.ni.com/mstudio/download/, but the manual at http://www.ni.com/pdf/manuals/350836e.pdf says on page 7 "Any applications you build with the Measurement Studio Evaluation package have a 30-day evaluation period.", which matches my experience. The process goes like this:
I first install Visual Studio 2012, and license it.
Install Measurement Studio 2013 (2015 now!), which defaults to the Enterprise evaluation, licensing itwith my Standard serial number. This is a part of the installation process: Download http://ftp.ni.com/evaluation/labview/ekit/other/downloader/MStudio2015_downloader.exe on a fresh install and click through, and you'll see that there's a screen in the installer which requests the serial number. I enter it in this step; there's no reason for it to be licensed with the Enterprise trial at any time.
Then, I check out the application from our source control, and open it in Visual Studio. The check out includes the DLLs:
NationalInstruments.Common.dll
NationalInstruments.DAQmx.dll
NationalInstruments.MStudioCLM.dll
NationalInstruments.NiLmClientDLL.dll
NationalInstruments.UI.dll
NationalInstruments.UI.Styles3D.dll
NationalInstruments.UI.WindowsForms.dll
(note that Enterprise Analysis is not included) and the license file:
NationalInstruments.UI.WindowsForms.ScatterGraph, NationalInstruments.UI.WindowsForms, Version=13.0.45.242, Culture=neutral, PublicKeyToken=4febd62461bf11a4
NationalInstruments.UI.WindowsForms.Legend, NationalInstruments.UI.WindowsForms, Version=13.0.45.242, Culture=neutral, PublicKeyToken=4febd62461bf11a4
(note that Enterprise Analysis is not included; these are the only UI components that the application used). The project file references the DLLs in the project folder:
<Reference Include="NationalInstruments.Common, Version=13.0.40.190, Culture=neutral, PublicKeyToken=dc6ad606294fc298, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>lib\NationalInstruments.Common.dll</HintPath>
<Private>True</Private>
</Reference>
<Reference Include="NationalInstruments.DAQmx, Version=14.1.45.13, Culture=neutral, PublicKeyToken=4febd62461bf11a4, processorArchitecture=x86">
<SpecificVersion>False</SpecificVersion>
<HintPath>lib\NationalInstruments.DAQmx.dll</HintPath>
<Private>True</Private>
</Reference>
<Reference Include="NationalInstruments.MStudioCLM, Version=13.0.40.190, Culture=neutral, PublicKeyToken=dc6ad606294fc298, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<EmbedInteropTypes>False</EmbedInteropTypes>
<HintPath>lib\NationalInstruments.MStudioCLM.dll</HintPath>
<Private>True</Private>
</Reference>
<Reference Include="NationalInstruments.NiLmClientDLL, Version=13.0.40.190, Culture=neutral, PublicKeyToken=dc6ad606294fc298, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>lib\NationalInstruments.NiLmClientDLL.dll</HintPath>
<EmbedInteropTypes>False</EmbedInteropTypes>
<Private>True</Private>
</Reference>
<Reference Include="NationalInstruments.UI, Version=13.0.45.242, Culture=neutral, PublicKeyToken=4febd62461bf11a4, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>lib\NationalInstruments.UI.dll</HintPath>
<Private>True</Private>
</Reference>
<Reference Include="NationalInstruments.UI.Styles3D, Version=13.0.45.242, Culture=neutral, PublicKeyToken=4febd62461bf11a4, processorArchitecture=x86">
<SpecificVersion>False</SpecificVersion>
<HintPath>lib\NationalInstruments.UI.Styles3D.dll</HintPath>
<Private>True</Private>
</Reference>
<Reference Include="NationalInstruments.UI.WindowsForms, Version=13.0.45.242, Culture=neutral, PublicKeyToken=4febd62461bf11a4, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>lib\NationalInstruments.UI.WindowsForms.dll</HintPath>
<Private>True</Private>
</Reference>
<Reference Include="NLog, Version=2.0.0.0, Culture=neutral, PublicKeyToken=5120e14c03d0593c, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>lib\NLog.dll</HintPath>
</Reference>
Note that NiLmClientDLL and MStudioCLM are not copied to the output folder. A later entry in the project file includes the license file in the build:
<EmbeddedResource Include="My Project\licenses.licx" />
I then build the project, make whatever customizations required for this particular build, and we ship the machine. Then, the customer calls 30 days later, complaining that the program won't start.

Compatibility of NI IMAQ with measurement studio

I would like to know where the NI IMAQ driver software is compatible with measurement studio.

Hello,
NI-IMAQ driver and its API is fully compatible with Measurement Studio. If you have already installed NI-IMAQ with Measurement Studio support, see the following directory (default path) for shipping examples
C:\Program Files\National Instruments\MeasurementStudio\CVI\samples\IMAQ
Let me know if you have further questions on this.
Regards,
Yusuf C.
Applications Engineering
National Instruments

Measurement studio expired first day I install

Hi,
I download Measurement Studio 2009 for Visual Studio Evaluation yesterday. I installed it with Labview 2009 and DAQmx 9.2.1. My OS is XP sp3. I have a DAQ card DAQ-6024E. And I tried to output a analog signal using the card. So, I found out there is an example from NI after installation named "GenVoltageUpdate" in the folder \NI-DAQ\Examples\MStudioVC2008\Analog Out\Generate Voltage\. I used VS 2008 to try to run this program in debug mode. There was a box popped up "The Measurement studio evaluation has expired". I checked the Measurement Studio>> License, and it shown as the figure attached. None of them has expired yet.
I don't know why there is such message about expiration. I hope someone can help me.
Thank you very much.
Attachments:
新图片.jpg ‏246 KB

Hi, I installed today (02-12-2011) the evaluation version of Measurement studio 2010 for Visual Studio 2008.
Checking the licence page from the Measuremt studio menu I get thet all the components I installed should expire on 13/03/2011.
The problem is that if I try to execute any sample code provided I get the following error:
System.ComponentModel.LicenseException was unhandled
  Message="NationalInstruments.UI.WindowsForms.WaveformGraph evaluation period has expired."
  Source="NationalInstruments.Common"
  StackTrace:
   at NationalInstruments.Restricted.EvalReleaseLicense.ShowEvalBehavior(Type type, Object instance, String licenseString)
   at NationalInstruments.Restricted.EvalReleaseLicense.ComponentRunTimeCheck(Type type, Object instance, String licenseString)
   at NationalInstruments.Restricted.LicenseBase.PerformRunTimeCheck(Type type, Object instance, String runTimeLicense)
   at NationalInstruments.Restricted.LicenseBase.RunTimeCheck(LicenseContext context, Type type, Object instance)
   at NationalInstruments.Restricted.LicenseProviderBase.GetLicense(LicenseContext context, Type type, Object instance, Boolean allowExceptions)
   at System.ComponentModel.LicenseManager.ValidateInternalRecursive(LicenseContext context, Type type, Object instance, Boolean allowExceptions, License& license, String& licenseKey)
   at System.ComponentModel.LicenseManager.ValidateInternal(Type type, Object instance, Boolean allowExceptions, License& license)
   at System.ComponentModel.LicenseManager.Validate(Type type, Object instance)
   at NationalInstruments.UI.WindowsForms.WaveformGraph..ctor()
   at NationalInstruments.Examples.Plotting.MainForm.InitializeComponent() in C:\Documents and Settings\All Users\Documenti\National Instruments\MStudioVS2008\DotNET\Examples\UI\WindowsForms\Graph\Plotting\cs\MainForm.cs:line 64
   at NationalInstruments.Examples.Plotting.MainForm..ctor() in C:\Documents and Settings\All Users\Documenti\National Instruments\MStudioVS2008\DotNET\Examples\UI\WindowsForms\Graph\Plotting\cs\MainForm.cs:line 37
   at NationalInstruments.Examples.Plotting.MainForm.Main() in C:\Documents and Settings\All Users\Documenti\National Instruments\MStudioVS2008\DotNET\Examples\UI\WindowsForms\Graph\Plotting\cs\MainForm.cs:line 274
   at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
   at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
   at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
   at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
I tried using the Measurement studio active-X License fixer. In the Licensed controls list there is "3D Graph control 8.0" but in the Elvaluation Licenses list and the Broken Licenses list the is no controls at all.
Is there something else I can do?
Best regards,
Mark

Using software instruments that are stored on an external drive.

I recently bought Logic 9. Doing a custom install, I stored the instrument library on an external disk thinking it would be easy to use the instruments at a later time. Now, however, when I create a software instrument track, I only see the basic exs instruments. I can't find any further help on how to use my full library of instruments stored on my external drive. This must be simple, but I can't figure out. Any help would be much appreciated.

Logic looks at the Garageband library for these.
You'll need to go in there and create an alias to where you've put your content, otherwise they won't show up in the Garageband instruments section.

How can I get Measurement Studio out of Evaluation Mode in Windows XP

I have a licensed Measurement Studio version 7.1. for Visual Studio 6. I have been using this no problem on a Windows 2000 computer. I installed this on my WindowsXP computer and it installs all the VB libraries put not the C++ libraries. I message pops up stating that I need Service Pack3 for WindowsXP. First of all, I don't think service pack 3 for Windows XP exists yet. Luckily, I have been able to still use all my DataSocket components. I believe Datasockets are part of Measurement Stuidio. I notice that CWgraph has evaluation mode on the graph and I get a popup message in VB6 stating I'm using Measurement Studio in evaluation mode.

Hello,
The service pack in question is not for Windows XP. The Measurement Studio installer required the VC++ 6 service pack 3 or higher. I know that Microsoft has a service pack 6 for Visual C++ 6, and this is what you should install to get the C++ libraries on your machine.
There is a tool on the CD that is in the ActiveXLicenseFixer folder that you can run to fix up the license. If you have a valid license on the machine it will correct any licenseing issues.
-Jeff
NI

Can I use instrument driver in a software application

Hi,
I'd like to develop a generic driver to control any instrument from a software application . Can I use the LabWindows/CVI wizard to succeed ?
Once I have created my dll, does it mean something to call IVI function from a sofware application ? (for example : in a Visual C++ application, can I call Prefix_init and after Prefix_WriteInstrData if I have connected an Instrument with an input ?).
Thanks

Hi,
Using the IVI class driver in your application you can at least use the same program to communicate with instruments belonging to the same class.
To acomplish this you need the specific driver for the instrument. The class driver provides a standard API you can use in your application. The class driver in turn calls the specific instrument driver that you have configured.
If you call WriteInstrData you still need to determine the command string you need to send to the instrument. The IVI driver wraps the instrument I/O, using the attribute model or high level functions.
DiegoF.
National Instruments.

Problems with cwStats (MS 6) after evaluating Measurement Studio 7

I have the Full version of Measurement Studio 6 installed on my development machine. I recently installed Measurement Studio 7 to begin migrating our application to .NET. While recently doing some upgrade work on our VB6 project I started receiving an error when using the "full" capabilities of the cwStats control. It basically tells me that I do not have a license for the "full" version. I have installed the latest updates for MS6 but am still having the problem. Is this a known issue and is there a workaround?

Hello,
With Measurement Studio 7.0 we shipped a utility called ActiveX License Fixer. This was due to this known issue that the license of a released 6.0 will go into evaluation mode for 30 days if someone installs 7.0 released over the controls.
You should run this utility from the Measurement Studio 7.0 CD (it has a readme) and it will fix everything up for you.
Regards,
Jeff
NI

Measurment studio will not recognize LabWindows/CVI installation?

It order for me to use the Driver factory program to make a DLL, the program requires that LabWindows/CVI version 5.0 or greater be installed. Version 5.5 was installed first and Measurment studio does not recognize it. After installing the DAQ software, MAX does recognize both LabWindows/CVI and Measurment studio. Help!
Steve

Hi Steve,
What the IDF does, is
(1) Look for the installation of CVI in the registry under HKLM/Software/NationalInstruments/CVI/xxx. "xxx" being the version number.
(2) If there are multiple CVIs on the machine, IDF uses the highest version number of CVI located i.e.if you have
HKLM/Software/NationalInstruments/CVI/5.0
and HKLM/Software/NationalInstruments/CVI/5.5 it will pick 5.5.
(3) IDF will then look up the installDir key under this folder.
If either of (2) or (3) fails, you get the message you've been seeing.
So what do you see under that registry location ? Is the registry version folder, or the installDir key missing?
It is possible that the machine had installed a higher version of CVI , then uninstalled, but the folder a
nd key is still there, so you have a key with a higher version of CVI, with the installdir key pointing to a "" value, instead of a valid path....
If things do appear fine in the registry, then please reconfirm the software you have installed, as i under stand it, you have CVI 5.5, then installed MesurementStudio 6.0 ? I can try to then reproduce this.
I sincerely apologize for all the trouble that you have been having...I hope this makes things little clearer and hopefully we can get you started soon..
With regards to the other thread that you pointed to , it's possible that the evaluation CD did not install all the registry keys or installed them to a different location, or the user, did not install CVI at all...
Best Regards,
Nandan
Nandan Dharwadker
Staff Software Engineer
Measurement Studio Hardware Team

What version of Measurement Studio do I buy for Visual Studio 6.0?

I am consulting for a company that requires me to use VB 6.0 and I am looking for the NI Measurement Studio version to purchase but this particular part of this web site is as confusing as HP's(Agilent) so I have yet to figure it out. The evaluation software I have for Measurement Studio lists Visual Studio.net 2003 as a requirement. Has NI assumed everyone has migrated to .net?

National Instruments is actually one of the few companies that IS still supporting Visual Basic 6.0. We currently offer both an evaluation for Visual Studio 6.0 and Visual Studio .NET. From the Measurement Studio home page (ni.com/mstudio), you will see two different path options: 6.0 & .NET. If you select the 6.0 option and scroll down, you will see the option to request the 6.0 evaluation software here: (https://sine.ni.com/apps/we/nigb.guestbook?code=GB_EVALMSSTUDIO6〈=US&gb_prof_id=1907&scode=&pr=1907).
To purchase the 6.0 tools, you simply need to purchase Measurement Studio 7.0 which includes the 6.0 tools as outlined in the package comparison chart here: http://volt.ni.com/niwc/common.jsp?page=mstudio_package_compare&node=3769
The Measurement Stud
io 7.0 packages (Professional and Enterprise) include both the Visual Studio .NET and Visual Studio 6.0 tools.
Please feel free to contact me if you have any further questions.

My application conflicts with another Measurement Studio based application.

Hi,
Our instrument is made by a third party, and they appear to use Measurement Studio in the development of their control software.
We use Measurement Studio when developing our test software. When we install our test application on a production machine (no programming environment installed), we sometimes get a message about only being able to use controls for 5 minutes in an "evaluation-only" mode.
It is clear that there are some library file revision conflicts, e.g.: in cwui.ocx and presumably others. The third party is using a slightly different revision of these files to ourselves. What is the the best way to consistently resolve these conflicts?
Thanks,
Richard Brockie

Hi Richard Brockie,
You are correct in assuming there is a conflict with cwui.ocx.
If the target computer does not have Measurement Studio, it will not contain the .ocx and .dll files required for the executable to run. Microsoft Visual Studio .NET has a Setup and Deployment Projects type that allows you to create a MSI installer that finds all of the dependencies for the project and then installs them on the target machine when the setup is executed.
I've included the following link that demonstrates the process of creating an installer for a Windows application, using .NET or Active X controls.
http://digital.ni.com/public.nsf/websearch/ED87C183E056CAC386256DF1004E54C6?OpenDocument
Please respond if you have further questions or if this does not resolve your issue,
Chad AE
NI

Can I acquire data with VB from my DAQCard without using Measurment Studio?

I have the Measurement and Automation Software on my computer and VisualBasic.NET. Do I need any other software if I am receiving 2 analog signals and outputing 1 analog signal on my NI DAQCard-6024E PCMCIA?

The short answer is yes, you can acquire data with VB.NET from your DAQCard without using Measurement Studio.
There are a variety of ways to do it. All of them require that you install either the Traditional DAQ driver or the DAQmx driver in addition to Measurement and Automation Explorer. The DAQ drivers are included on a CD or CDs with your hardware. They are also available on the quarterly National Instruments Device Driver CD.
1) You can use the Measurement Studio DAQmx .NET API. This is far and away the easiest API to use to program DAQ cards in VB.NET and C#. This API is included in the DAQ installer and does not require you to purchase Measurement Studio. However, without Measurement Studio you do not get the benefit of the DAQ Assistant integrated into Visual Studio .NET. The DAQ Assistant, when integrated into Visual Studio .NET, allows you to graphically configure your DAQ tasks, generates the code you need to configure your tasks, and generates a .NET user control (with user interface) that demonstrates how you use the tasks that you created. The caveat to this approach is that PCMCIA cards are not directly supported under DAQmx 7.0. There is, however, a beta versin of DAQmx PCMCIA support as described in this KB article.
2) You can use the .NET P/Invoke services to call the Traditional DAQ or DAQmx C API directly. See MSDN for more information about P/Invoke. If you choose the DAQmx API, you will need to install the beta of the PCMCIA support as described in this KB article. National Instruments does not provide any examples, language-specific documentation, or code generation for this method. You'll need to look at the C API documentation to see what to do.
3) You can use the Measurement Studio Traditional DAQ ActiveX controls. These are included in the DAQ installer and do not require you to purchase Measurement Studio.
The absolute quickest and easiest way to get started using an NI-DAQ card in VB.NET is through the DAQ Assistant and Measurement Studio Professional or Enterprise edition.
Your next best approach is to use the native .NET DAQmx API. This API was designed from the ground up to support .NET languages. There are examples written in VB.NET to help you get started.
If for some reason, you don't want to use the native .NET API (or your hardware is not supported under DAQmx), whether you use P/Invoke or the ActiveX controls is a toss-up. It depends mostly on whether you are already familiar with the C API or the ActiveX API.
David Rohacek
National Instruments

Software instruments not playing

I had to reload my hard drive after a re-format, in doing so my GB has been working funny. My software instruments play only as a keyboard, with slight variation despite what instrument is selected. It does this with or without the midi keyboard connected. I reinstalled it from factory disk and the problem still exists. Ideas?

Oops, I didn't read your entire sentence, I missed the last bit. I actually didn't realize you could use the onscreen keyboard while the Create DialogBox was open.
In fact, naughty GB programmers, that's a Modal Dialog, you shouldn't be able to use the onscreen keyboard while it's open.
But as you correctly posted, it does work

Any example for a MFC, WTL or Win32 without Measurement Studio?

It seems that NI wants you buy their Measurement Studio which can easily cost you a fortune. I am looking around a simple example for MFC, WTL without touching the measurement studio. But if you do not have measurement studio, NI only gives you very old examples in ANSI C which is difficult to implement to MFC or WTL. Apparently they want to increase their revenue by forcing you to buy the Measurement Studio. But I will not buy their hardware in the future if this is their strategy.
Anyone successfully implement the ANSI C example to MFC or WTL without measurement studio? Can you share an example?

Junqi,
Im a little confused with this request in general. What development environment are you using? Visual Studio? Also, what language are you coding in? We provide C, C#, VB.net, and legacy VB6 examples with our DAQmx driver that do not require measurement studio. They can be found in documents\National Instruments\NI-DAQ\Examples
Now forgive me if Im misinformed about this, but MFC and WTL are just libraries that have some of the windows API wrapped into them, correct? If so, I dont see how interfacing with them is any different than interfacing with any other library, or why this would cause issues with doing DAQ calls. If you need help with the MFC or WTL library, there are many good places to find help with on the internet. MSDN, codeproject.com, and many others come up as having examples of using MFC in various projects.
The MS examples dont install withough MS because they wouldnt be able to be used because they use libraries that are installed with measurement studio, so they would be nonfunctional and largely useless.
Regards,
Kyle Mozdzyn
Applications Engineering
National Instruments
Regards,
Kyle M.
Applications Engineering
National Instruments

Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW

Hello All,
Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW
http://zone.ni.com/devzone/conceptd.nsf/webmain/9A93316BEBEDB17786256FA300675A0A
But I can not find any hyperlinkt to download
"LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers"
Is there any evaluation version for downloading?
Thanks,
nonomiya

So strange,
I go through three pages but does not find any entry for download,
hmm...,
1. After press the hyperlink,
See Also:
LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
2. and for a resuest info. form.
3. press download..
====
LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
System Requirements
NI LabVIEW 7.1 or later
Windows 2000/NT/XP
Use the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers to create LabVIEW VIs for VXIplug&play and IVI-C instrument drivers from function panel (.fp) files.
Instrument Driver Network
Before using the conversion utility to create a new instrument driver wrapper, please visit ni.com/idnet to see if a LabVIEW Plug and Play instrument driver is available for your device. The Instrument Driver Network (IDNET) provides support for more than 3,000 different instrument models from over 170 different instrument vendors.
Recommendations
This utility was created for developers of C-based instrument drivers who wish to provide a LabVIEW interface, but do not develop a LabVIEW Plug and Play driver. By developing the C and LabVIEW interfaces together, it keeps the components synchronized, and eliminates the need for customers to create their own LabVIEW interfaces. Vendors should distribute the LabVIEW wrapper files with the associated VXIplug&play or IVI instrument driver, so that end users do not have to visit multiple web sites to download the complete driver.
If you are not an instrument vendor, we recommend that you use this utility only if you have instrument driver expertise. Access to the instrument driver source code is preferred, in case you need to edit the C instrument driver in LabWindows/CVI.
After generation, the wrapper VIs should be tested with the instrument.
Instructions
Once you install the software, simply access the utility from the Tools>>Instrumentation>>Import CVI Instrument Driver...menu in LabVIEW. This software replaces the built-in tool and provides feature enhancements.
For additional information on this utility, view the resources below.
Readme for the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
Submit your Driver
Visit the Instrument Driver Network
nonomiya

Measurement Studio Evaluation Software - Instrument Driver Factory

Similar Messages

Maybe you are looking for