Visual Studio or LabWindows/CVI?

I have a bit of a dilemma.
I currently own Visual Studio 2010, IMAQ Vision Development Module 2013, and Measurement Studio (not sure of version). I currently do all of my programming in VB.net. Because IMAQ VDM is stuck in .Net framework 3.5 and there will be no further .net development by NI, I need to plan for the future. My applications need run on Win 8, 9, 43, or whatever my company decides to migrate to from Win 7.
My understanding is that the NI modules I currently own will work with LabWindows/CVI. Correct? I also believe I can use them with C++ using the VS IDE. Is this also correct?
Within my applications I do a lot of interfacing with Excel, writing text files, and interfacing to non-NI devices (cameras, DAQs, scanners, etc). I am able to do these things pretty easily using VB.net using vendor-provided SDK's.
Therefore, my question is this...given the investment I have in software already, do I gain anything by migrating to LabWindows/CVI? What do I lose?
I should point out that regardless of the path I choose I will need to bone up on my programming skills in the corresponding language.
Thanks for all your help!

Hello Steverino!
Here are some advantages when using LabWindows/CVI over Visual Studio, which make the product more suitable for various industry-related applications:
You are correct, LabWindows/CVI integrates with the NI platform: NI hardware and software, like TestStand or LabVIEW (e.g. debugging source code from one software to another, seamlessly).
NI hardware and third-party hardware connectivity.
OpenMP support.
CVI integrates with intrument control.
CVI Run-Time benefits from User Protection.
Run-Time checking (e.g. for uninitialized variables).
Scientific User Interface Controls and GUI Editor.
Advanced debugging capabilities:
Remote debugging support from ADE.
Real-Time debugging support from ADE.
Memory leak detection using the LabWindows/CVI Resource Tracking Window.
Just-In-Time debugging.
Deployment: build custom installers and patches that you can ship as stand-alone easy-to-use installers.
LabWindows/CVI libraries: Advanced Analysis, Toolbox, Connectivity (Network Variables, Network Streams, DataSocket), etc.
Support for LabWindows/CVI Toolkits: SQL Toolkit, Vision, PID, RT.
Regards,
- Johannes.

Similar Messages

  • How can I debug a DLL created with MS Visual Studio C++ using CVI?

    I have developed a DLL using MS Visual Studio C++, which is called by an other application written in CVI.
    My goal is to debug the DLL written with C++ when is called from CVI.
    So far I have some msg popups, but I would like to have more debugging capabilities.
    Thanks, Adalbert

    Hello Adi11,
    As documented in the CVI Help under "Debugging DLLs": "In the LabWindows/CVI development environment, you can debug only DLLs you create in LabWindows/CVI with the Create Debuggable Dynamic Link Library command. Other development environments cannot debug DLLs you create in LabWindows/CVI."
    This information was also mentioned on the following discussion forum.
    Thanks.
    Wendy L
    LabWindows/CVI Developer Newsletter - ni.com/cvinews

  • I would like to know how to transform an API C++ application in MFC C++ application to use the measurement studio components or Labwindows CVI

    I don t know the way used to transform a C++ with API program in an MFC application using measurement studio or Labwindows CVI.
    Thank you for you help.

    You can use the Measurement Studio Add/Remove Components Wizard to add Measurement Studio components to your C++ application. For more information, see the "Adding and Removing Components from Measurement Studio Projects Using a Wizard" topic in the Measurement Studio reference. You can find it in the table of contents under:
    Visual C++ Help
    Tutorials
    Measurement Studio for Visual C++ 6.0
    If you're using the Measurement Studio update for Visual C++ .NET, this topic will be under:
    Visual C++ Help
    Tutorials
    Measurement Studio for Visual C++ .NET
    - Elton

  • How can I convert a project from LabWindows/CVI 2010 to a Visual Studio 2011 project?

    I have a good sized project, 12 source files, 14 headers, 1 uir, that I want to be able to edit and compile in MS Visual Studio 2011, MSVC++.
    I remember being told that LabWindows dropped support for C++ in 2008 and no longer had a wizard for converting projects. I know I can go the DLL route, but I have never created a DLL before and wouldn't know where to begin with it. What would be the best way to go about this conversion?
    Solved!
    Go to Solution.

    CVI 2010 still supports the Visual Studio Conversion Wizard for Visual Studio 2005/2008. We do plan to add support for VS 2010 in a future release.
    If you need a VS 2010 project now, you can use the Visual Studio 2008 conversion wizard, then upgrade the VS 2008 project to VS 2010.
    National Instruments
    Product Support Engineer

  • An error occured while creating a project Visual Studio 2010 & CVI 2012

    While creating a project from VS2010, with CVI 2012 install. I get this error after attempt to convert or create a CVI project. Also the CVI dialog has no details.
    Solved!
    Go to Solution.

    I did installed Labwindows 3 weeks ago. I installed visual studio yesterday. I updated labwindows for Visual Studio supprt. I was tried to create anew project from Visual Studio using CVI app wizards. Both wizards end with same results
    Thanks for posting reply

  • Calling CVI DLL Function from Visual Studio

    HI all ,
    Iv'e created a DLL using CVI and i'm tring to call one of it's function from visual studio 6.0
    I'm getting a general error , is there a specific prototype that i need to set my functions in ordrer to call them ?!  
    Kobi Kalif
    Software Engineer

    You will need to distribute the CVI RTE along with your DLL, since anything you write in CVI is going to use the RTE.
    As far as calling the DLL functions, you can use the CVI defined macros
    <return type> DLLEXPORT DLLSTDCALL <function name> (<param1 type> <param1> ...) {
    to declare your functions in the DLL for access by a VS application.
    for example
    int DLLEXPORT DLLSTDCALL myfunction (int funparam1, double func param2) {
    There are options for identifying which functions to export from your DLL, I use "functions marked for export" but there are other choices available.  I also include a type library so when you type the name of a DLL funciton in VS6 you see a balloon popup with the function signature.  This is a check box in the target settings.  You have to create a ".fp" file (function panel file) to collect the function info for the library.
    From VB6 you can access the DLL a couple of ways, but I usually add the DLL as a reference.

  • 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

  • Remote debugging of a CVI DLL running on PXI with visual studio

    Hello!
    I would like to build my application using the CVI "module" for Visual studio but my problem is that i'm only capable to build DLLs which are able to run on the PXI but i can't remote debug them. 
    Is it possible to somehow set visual studio to remote debug the PXI?
    Thanx in advance! (:

    Hi,
    What do you mean by debugging the PXI? What exactly is the dll doing ?
    I will need more details before I can make any suggestions.
    Kind regards,
    Ion R.

  • Intégration d'un FP (CVI) sous Visual Studio Express

    Bonjour
    Je souhaite basculer une de mes projets LabWindows sous Visual Studio Express 2013.
    J'ai réussi à intégrer mes panel et différentes varialbes et fonction mais je coince sur l'intégration des drivers instruments (Fp)
    Comment puis je faire pour intégrer mes Fp dans un projet sous Visual Studio?
    Merci pour votre aide.

    Bonjour,
    Pouvez vous me préciser le matériel utilisé ?
    Je vous conseille de passer par les compteurs pour cela je vous invite à regarder les deux liens suivants :
    http://zone.ni.com/devzone/cda/tut/p/id/4523
    http://zone.ni.com/devzone/cda/tut/p/id/3117
    Aussi, étant donné que l'on est dans le domaine échantillonné, il faudra que vos coefficients (de division et multiplication) soit des multiples entier de la fréquence source.
    Cordialement,

  • Using DLLs created with LabWindows/CVI 8.0.0 in LabWindows/CVI 8.0.1

    Hi,
    I have created a project containing some methods with LabWindows/CVI 8.0.0 and then build the project and generated the DLL and LIB files. These DLL and LIB files are working fine in another projects created in LabWindows/CVI 8.0.0 (even on another machines).
    But when I use these DLL and LIB files in a project created with LabWindows/CVI 8.0.1 on another machine and try to call the methods of these files, the following error occurs: -
    "The program has caused a 'Unknown' fault at 001B:7C812AFB"
    Is this error occurs due to ther version mismatch or there is some other problem?
    Please help me to resolve this issue.
    Thanks,
    Sarabjit Singh

    Judging from this, I don't think NI has a newer version of this tool:
    http://forums.ni.com/t5/Measurement-Studio-for-VC/Convert-project-from-LabWindows-CVI-to-Visual-Stud...

  • Connect LabWindows/CVI to Opto22

    I would like to connect the hardware of Opto22 to the software of
    LabWindows/CVI. I thought of using OPC but I don't understand really
    how to setup an OPC server. Is there another way to connect these 2
    items using a driver of maybe DDE? I quite new in these things so
    forgive me if I ask stupid questions.
    Sent via Deja.com http://www.deja.com/
    Before you buy.

    Hi nqn,
    There are actually two conversion wizards that CVI offers with regards to integrating with Visual C++. You can read about them in the Integrating LabWindows/CVI with Microsoft Visual C++ KnowledgeBase.  The only problem is that we don't have conversion wizards available for Visual Studio 208.  We only have conversion and project wizards available for Visual Studio 2005, Visual Studio .NET 2003 and Visual Studio 6.0.  I will say that we are planning on creating wizards for Visual Studio 2008 but this is several releases away. With that said, I would suggest that you submit a product suggestion so we know people are wanting this. 
    So for right now, I would suggest using the conversion wizard in Visual Studio 2005 and then just upgrading that project to VS 2008. 
    Best Regards,
    Jonathan N.
    National Instruments

  • Where can I get Labwindows/CVI v4.0?

    Hi,
    I have been programming with Labwindows CVI at work for the past 4 years
    and I would like to buy a legit copy for my home. I can get buy with 4.0
    asopposed to 5.0 mainly because of price. Does anyone have a copy that
    they don't need after upgrading to 5.0 ?
    email me at [email protected]
    Thanks,
    Russ
    Sent via Deja.com http://www.deja.com/
    Before you buy.

    Hi Russ,
    What is the price you're looking to pay for CVI 4.0?
    Because once you have CVI 4.0, you can upgrade to the Measurement Studio
    Full
    Development System (which has CVI 5.5 and other tools for Visual C++ and
    Visual Basic)
    for $295.
    And this is a really good deal because if you want to buy the base package
    of Measurement
    Studio (which has CVI 5.5 as well) it's $995 and the Full System is $1995 !!
    So you save big time by buying a cheap (hopefully) CVI 4.0 and then later on
    you can upgrade
    to CVI 5.5.
    Just adding my two cents.
    Azucena
    wrote in message news:8dodr2$vvn$[email protected]..
    > Hi,
    >
    > I have been programming with Labwindows CVI at work for the past 4 years
    > and I would like to buy a legit copy for my home. I can get buy with 4.0
    >
    asopposed to 5.0 mainly because of price. Does anyone have a copy that
    > they don't need after upgrading to 5.0 ?
    >
    > email me at [email protected]
    >
    > Thanks,
    >
    > Russ
    >
    >
    > Sent via Deja.com http://www.deja.com/
    > Before you buy.

  • Can Labwindows​/CVI work with Opencv?

    OpenCV is a good and free lib for computer vision developer. I know it's an option to use it through Measurement Studio and Visual studio. But, can we use it in the CVI environment directly?  

    OpenCV does work with LabWindows. If you successfully "installed" the latest openCV, which is at the time of my post version 2.4.3, the header file "core_c.h" along with corresponding lib and dll files must be added to you project tree in order to use openCV functions. "core_c.h" includes "types_c.h" which for some reason LabWindows/CVI doesn't really like. The problem starts on line 137:
    #ifndef CV_INLINE
    #  if defined __cplusplus
    #    define CV_INLINE inline
    #  elif (defined WIN32 || defined _WIN32 || defined WINCE) && !defined __GNUC__
    #    define CV_INLINE __inline
    #  else
    #    define CV_INLINE static
    #  endif
    #endif /* CV_INLINE */
    The only option CVI likes is the last one (CV_INLINE static), so simply modify this segment so that it's the only choice and compile!

  • Software Development Engineer positions at Hysitron, Inc. in Minneapolis (LabWindows CVI exp preferred)

    Software Development Engineer
    Hysitron, Inc. is a premier scientific instrument manufacturer. Founded in 1992 with headquarters located in Eden Prairie, MN we are committed to promoting nanotechnology by developing advanced transducer and control technology. This leadership has made Hysitron the world leader in nanomechanical test instruments. The TriboIndenter®, TriboScope®, Ubi, and other Hysitron innovations have opened new horizons for scientists interested in investigating and understanding mechanical properties of materials at nano-scale. Hysitron fosters an environment and culture where innovation flourishes, teamwork is encouraged, and superior performance is rewarded.
    Hysitron invites applications for multiple software development engineer positions from those aspiring to explore and succeed in the nano world. Hysitron, Inc. is an Equal Opportunity Employer M/F/D/V
    Job responsibilities
    The software development engineers would be responsible for developing test and measurement software applications for nano-mechanical testing instrumentation. Job deliverables would include:
    -          Develop software applications in C based Labwindows CVI for Hysitron Instrumentation
    -          Support the development of applications to address challenges in instrument automation and control
    -          Test software applications using debugging and simulation tools
    -          Perform software releases and software quality assurance activities
    -          Participate in the design of new software products
    -          Perform maintenance activities for existing products
    -          Adapt and deliver on quality software development practices
    Minimum qualifications
    -          BS in Computer Science/ Computer Engineering/ Equivalent Scientific or engineering discipline
    -          Min of 3 yrs experience in Instrumentation software development in an industrial or R&D environment
    -          Expert at programming language C, knowledge of C++
    -          Working knowledge of various communication protocols, e.g. USB, RS232, IEEE, RS485, TCP/IP, Modbus
    -          Knowledge of general software design/documentation processes in test and measurement systems
    -          Proficient problem solving skills
    -          Strong analytical and technical skills
    -          Excellent communication and interpersonal skills
    Preferred Qualifications
    -          Proficient with LabWindows CVI and XML
    -          Working experience with DSP(Code Composer Studio) and/or FPGA level programming
    -          Exposure to digital electronics and instrumentation
    -          Working experience in Robotics interface programming
    -          Experience with Controls/Automation engineering
    Application and Information
    Qualified candidates should send a letter of application and their resumes to (please include ‘SW Engineer’ in subject line):
    Hysitron, Inc.
    10025 Valley View Rd
    Eden Prairie, MN 55344 USA
    Phone: (952) 835-6366
    Fax: (952) 835-6166
    E-MAIL: [email protected]
    Web: www.hysitron.com

    This position is still accepting resumes/CVs.

  • Calling a function from a dll written by using visual studio c++

    Hi, how can i call a function from a dll which is written by visual studio c++ in test stand?  Although the functions in dll are exported and i've chosen c/c++ adapter, i saw no function in test stand. Is there a different step while i'm calling a function from a dll written by c++ than calling a function from a dll written by cvi?

    Hey Sadik,
    Selecting the C/C++ DLL Adapter Module should be sufficient for this. When you drag an action step for this onto the Main Step and navigate to the location of the DLL, the function list should populate and you should be able to select the function you want to use. If this is not the case, would you be able to post this DLL so that we can test this on our end?
    Regards,
    Jackie
    DAQ Product Marketing Engineer
    National Instruments

Maybe you are looking for

  • How to find out which feed is used by iTunes

    Hi! I've tested several feeding methods before i made submitted my podcast to itunes store, now  i don't know which feed is used by itunes.. Is there a way to determine this? Thank you!

  • DVI KVM Switch??

    Hi, I have a G5 running tiger (soon to be running leopard hopefully) with a DVI cinema display. I have a PC that I use for testing my work on the Web. I was able to switch back and forth easily with a Belkin KVM switch back when I was using a VGA mon

  • Price from Contract should default in the PO according to delivery date

    Hi Gurus, The scenario is: I am creating a PO w.r.t. a contract. Now, the material in the contract line item has two different prices in two different validity periods. For eg, the price from Jan to Mar31st is Rs.5.00/unit. Now, in the next validity

  • Checking for calibration time

    I have a requirement to perform a daily calibration of an instrument on a daily basis.  The time of calibration must be user configurable.  So, what I have done is created a menu item which allows the operator to control the user time.  Additionally,

  • Editing Executable's INI file with "HideRootWindow"

    Hello I'm trying to create an executable so that it shows only one window in the taskbar. On one of the Knowledgebase articles (http://digital.ni.com/public.nsf/allkb/6E660558F3D420C786256FCB005B4F52) I had read about setting HideRootWindow=True in t