Labwindows/CVI multitaches: acquisition et contrôle d'instrument

Bonjour a tous,
Dans le cadre d'un développement sous labwindows/CVI je suis amené à réaliser une acquisition tout en contrôlant autre un instrument. Je pense que la solution est le multi taches.
Mon problème est que je ne connais pas du tout cette méthode, et je souhaiterais savoir si s'est une solution viable pour à la fois lancer une acquisition pendant que je contrôle un instrument (reset de son alimentation). Dans le cas contraire, pouvez vous m'indiquer une solution, avec la démarche a réaliser?
Je sais réaliser une synchronisation entre une génération et une acquisition mais dans ce cas, il faut gérer une carte d'acquisition et un autre instrument. Comment faire??
Je vous remercie
Cordialement,
Julien_B

Hello,
La bonne vieille recherche d'exemples (Help-> Find Examples) reste toujours efficace. Je vous suggère d'aller faire un tour dans la partie MultiThreading. On y trouve toutes les principales fonctions pour créer des threads et y exécuter du code (en parallèle, donc !).
Cet article est aussi un bon départ.
Cdt,
Eric M. - Application Engineering Specialist
Certified LabVIEW Architect
Certified LabWindows™/CVI Developer

Similar Messages

  • How's NI's support for LabWindows/CVI? How's it likely to be in the future?

    Hello Fellow LabWindows/CVI Users,
    Have you found that National Instruments provides good support for LabWindows/CVI?  If so, do you expect good support to continue in the future?
    Thanks,
    Gayle Roth

    Duplicated post
    Proud to use LW/CVI from 3.1 on.
    My contributions to the Developer Zone Community
    If I have helped you, why not giving me a kudos?

  • 82351a with labwindows cvi

    Hello,
    I am trying to use Labwindows CVI 2013 with a GPIB card, Agilent 82351a and it can't talk with a GPIB instrument connected to the GPIB card.
    NI-MAX can see the 82351a card but I can't use this card to talk with an instrument.
    I installed Labwindows CVI with NI-VISA 5.4, AGILENT IO suite 16.3 with Agilent Visa a secondary VISA.
    With NI-MAX, in the options VISA, I enable "Passport for Tulip" and with Agilent Connexion Expert, I tried to enable '"programs Agilent GPIB cards for 488" but it reboots the PC and the option remains not validated.
    I wan't to know if this Agilent 82351a card can work with Labwindows CVI 2013.
    thanks

    http://forums.ni.com/t5/Instrument-Control-GPIB-Serial/82351a-with-labwindows-cvi/m-p/2818356/highli...
    Paolo_P
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    Travaux Pratiques d'initiation à LabVIEW et à la mesure
    Du 2 au 23 octobre, partout en France

  • Writing a Compressed AVI File in NI LabWindows/CVI with the IMAQ Vision Acquisition

    I'm still facing some problems when I try to save pictures from a GigE Vision camera into a compressed avi-file in a LabWindows/CVI application on Windows7.
    The task is to grab images from the camera with 30 fps to monitor a process, evaluate the grabbed pictures to find certain characteristics of the monitored process and save them in an avi-file to have the possibility to load and evaluate them once again Offline if necessary.
    My questions: which compression filters can I get with the NI-Imaq Vision Acquisition and Vision Development Runtime 2012 SP1? Is a mpeg4 codec available to compress quickly and effective? Can I use a third party codec or only the ones delivered with NI-Vision?
    I posted the problem two times already, but there is little response up to now. Thanks

    The encoding algorithm, or codec, that's used for compression needs to present on your system. When I had done some research on this sometime back, I found that if your custom codec could align with the DirectShow architecture, then your codec would work with IMAQ AVI functions.The codecs that are available may vary from system to system, depending on what software is currently installed. Be sure to check out this article:
    Writing a Compressed AVI File with the IMAQ Vision Acquisition Software
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

  • Acquisition de température (Labwindows/CVI, NI9211)

    Bonjour,
    Je débute sur Labwindows/CVI, je suis entrain de concevoir un petit système de supervision. J’essaie dans un premier temps  de faire juste l’acquisition de température grâce un module NI 9211 et l’affichée sur une interface graphique de Labwindows/CVI. J’ai installé le DAQ mx mais je ne sais pas comment faire pour intégrer la mesure à mon programme. Si quelqu’un peux me dire comment faire ou me renvoyer sur un tutoriel cela m’aiderai beaucoup.
    Je vous remercie d’avance. 

    Hello there,
    The following tutorial might be of use to you: www.ni.com/white-paper/2931/en/
    Please let us know if you have any trouble with it!
    Thanks,
    Daniel D.
    National Instruments
    Automated Test Software R&D

  • Need to install LabWindows​/CVI PID Control Toolkit (Part Number 320794A-01​)

    Hello -
    I have a customer with a very old application who needs to upgrade their system to Win7 64-bit. The app references the old PID functions (manual here: http://www.ni.com/pdf/manuals/320794a.pdf) but no matter what I have searched for, I cannot find an installation for that toolkit. I have never had a need to use the current PID toolkit so I am not versed with it, and the difference in the functions do not seem to be a 1 to 1 change. Additionally, the customer is not paying for a code change - just assistance with the upgrade and reinstall. I would greatly appreciate if someone could point me to that download. 
    If such a download is not in existence any longer, I will need to request some assistance with modifying the source to use the current PID functions. I could attach the pertinent code if need be (there are not a great deal of references).
    Thank you.

    Hi CVIBri,
    The installation files for the LabWindows/CVI PID Control Toolkit 2.1 are located at the URL below.  I realize these are only officially compatible with versions of Windows up to Vista, however this is the most recent version of the toolkit that exists.  I've also provided a link to the Evaluation License Files.  That being said, LabWindows/CVI 2013 SP2 now includes the PID Control Toolkit as part of its Base and Full versions, and it is fully licensed with the same serial number used to activate the LabWindows/CVI development environement. The Readme linked below should provide more information.
    PID Control Toolkit: http://www.ni.com/download/labwindowscvi-pid-contr​ol-toolset-2.1/1037/en/
    PID Control Tookit Evaluation License Files: http://www.ni.com/download/labwindowscvi-pid-contr​ol-toolset-2.1/1038/en/
    LabWindows/CVI 2013 SP2 Readme: http://www.ni.com/pdf/manuals/374674a.html
    Thanks,
    Myriam

  • NI USB 8473s sous Labwindows/CVI

    Bonjours à tous.
    Je me rettrouves bien embeté par cette petite boite. En éffet je dois développer un programme exclusivement sous Labwindows CVI ayant pour but de tracer les courbes des informations reçues par ma CAN box et le hic est que je n'arrive tout bonnement pas à le faire à cause de l'incompatibilité entre Channel API et Frame API. Y à t'il une solution sous CVI pour réaliser celà? Peut on réaliser ce programme sous Labwindows sans utiliser les fonctions proposées par le constructeur?

    Bonjour,
    Je remonte un peu votre topic mais je ne sais pas si vous avez trouvé une solution entre-temps.
    Je ne comprends pas tout à fait où se situe votre problème. Pourriez-détailler un peu plus ? Pour l'instant, je ne vois pas trop d'où vient un potentiel problème d'affichage.
    Par ailleurs, qu'entendez vous par "sans utiliser les fonctions proposées par le constructeur" ?
    Cordialement,
    Mathieu P. | Certified LabVIEW Associate Developer
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    Journées techniques : des fondamentaux aux dernières technologies pour la mesure et le contrôle/comm...

  • Retour paramètre string par Labwindows/CVI pour Teststand

    Bonjour à tous,
    j'utilise Teststand 2012 Development System et Labwindows/CVI 2012 Development System sous Windows 7 professionnel.
    Le contexte : grâce à une DLL crée avec Labwindows/CVI j'appel la fonction "Traitement" par TS.
    Le prototype de la fonction est le suivant void __declspec(dllexport) Traitement (char message[256], car reponse[256]);
    Je passe en paramètre deux strings à cette fonction. Cette fonction reçoit un "message", effectue un traitement sur celui-ci et le renvois sous le tableau "reponse" à TS. Cette fonction a été testée et fonctionne sous CVI.
    Mon problème : J'ai vérifié ma fonction reçoit bien le message mais me retourne quelque chose d'erroné( cf. image) et n'est censé me retourner, dans"reponse", que les chiffres au début mais me rajoute des instructions en temps que string. Je ne comprend pas comment cette suite d'instruction ce rajoute et pourquoi?
    J'ai consulté tous les messages disponibles sur le forum et je n'ai pas réussi à trouver un problème équivalent et donc une solution.
    J'espère que vous aurez une idée, voir pourquoi pas une solution
    Dans l'attente d'une réponse,
    Cordialement,
    Erwan.
    Résolu !
    Accéder à la solution.
    Pièces jointes :
    message.png ‏74 KB

    Bonjour Akagi,
    Dans une chaîne de caractère, "Null" ou "\0", correspond effectivement à une fin de chaîne.
    Pour éviter ce comportement, vous pouvez changer le type de passage de paramètre dans TS en tableau de Numérique.
    Ce faisant, aucun traitement ne sera fait sur le caractère "NULL". pour rappel un char = 1 Octet, on peut donc utiliser un tableau de numérique U8 pour représenter une chaîne de caractère.
    En résumé, si votre chaîne de caractère = 3"Null"01, vous obtiendrez ainsi: tab[0] = 3, tab[1] = 0, tab[2]=1.
    Je suis désolé, mais j'ai du mal à saisir où est intégré le caractère "NULL" dans CVI, est-ce une entrée clavier saisie par l'utilisateur, autre?
    Est-il possible d'utiliser un autre caractère ou série de caractère(non spécial) permettant d'identifier cette transition/caractère spécial "Null"?
    EX: (\) = "Null", soit la chaîne 3(\)01 équivalent à 3"Null"01. Il suffit ensuite d'établir un algorithme permettant de changer (\) en "NULL".
    Cordialement,
    Rémi D.
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    >> Les rencontres techniques de NI - Mesures et acquisition de données : de la théorie à la mise en ...

  • LabWindows​/CVI Openings in MN!!

    A Fortune 200 Consulting firm is currently recruiting a talented LabWindows/CVI professional to play an integral role in the success of a high-profile project. 
    Experience and skills needed for this role:
    Solid and current knowledge of LabWindows/CVI
    Experience with Oracle and instrument data acquisition
    Technical Development experience
    Deep understanding of Labwindows/CVI
    Understanding of DIADEM
    User documentation knowledge
    Team player in an IT environment
    Knowledge of Oracle 10g
    Excellent communication and consulting skills 
    Experience with technical requirements gathering
    understanding of Software SDLC
    Qualified candidates please respond via email to [email protected]

    This depends on your CVI version... the full development version includes the advanced math library, which provides functions such as PulseMeas to evaluate waveforms.

  • VXI-MIO-64E-1 in LabWindows/CVI

    I am using VXI-MIO-64E-1 module for Data Acquisition of differential Signal of 0-10V. By default Module is configured in -5V to +5V. I have used  status = AI_Configure (deviceNumber, chan, inputMode, inputRange, polarity, driveAIS) function for configure module to 0-10V unipoler but  still module is taking -5V to +5V not 0-10V.  here is LabWindows/CVI code for configuration of analog input module.
        buffer = (short *)malloc ( NUMPOINTS * sizeof(short));
       status = Init_DA_Brds (1, &brd);
       if ( status != 0 )
        MessagePopup("Error","Error in initializing VXI device");
        exit(-1);
       status = SCAN_Setup (1, NUMMODULES, ChannelList, ChannelGain);
       if ( status != 0 )
        MessagePopup("Error","Error in configuring VXI device");
        exit(-1);
       status = DAQ_DB_Config (1, 1);
       status = DAQ_Config (1, 1, 0);
       status = Select_Signal (1, ND_PFI_7, ND_IN_SCAN_IN_PROG, ND_LOW_TO_HIGH);
       if ( status != 0 )
        MessagePopup("Error","Error in Configuring SCAN_START input Line");
        exit(-1);
       InitializeTimer1();
       /* Module 1 Initialization Over */
       /* Module 2 Initialization Starts */
       buffer1 = (short *)malloc ( NUMPOINTS1 * sizeof(short));
       status = Init_DA_Brds (2, &brd);
       if ( status != 0 )
        MessagePopup("Error","Error in initializing VXI device");
        exit(-1);
       status = SCAN_Setup (2, NUMMODULES1, ChannelList, ChannelGain);
       if ( status != 0 )
        MessagePopup("Error","Error in configuring VXI device 2");
        exit(-1);
       status = DAQ_DB_Config (2, 1);
       status = DAQ_Config (2, 1, 0);
       status = AI_Configure (2, -1, 0, 10, 1, 0);
       /* Module 2 Initialization Over */
    What mistake i am doing to configure module-2 to 0-10 Volt input range.

    Hello Vishnu,
    Unfortunately, the VXI-DAQ cards are no longer supported, but you can find information about using them in the manual.  The VXI-MIO Series User Manual  has details about setting the input range in Chapter 3 on page 3-4.
    Good luck with your application!
    Meghan
    Applications Engineer

  • Test NI cDAQ-9188 using LabWindows/CVI

    I am looking for help to create test for cDAQ-9188 with DIO and AIO modules.
    Would you please advise with information as follow:
    1. Adding device driver to a project.
    2. Sample of UI.
    3. Sample of test script for DO (AO) control.
    4. Sample of test script for DI (AI) acquisition.
    Thank you.
    Sincerely,
    Sam.
    [email protected]  

    There is a tutorial on using DAQmx with LabWindows/CVI here: http://zone.ni.com/devzone/cda/tut/p/id/2931. That is probably a good place to start.
    Another good article to check out is the NI Ethernet Data Acquisition Overview here: http://zone.ni.com/devzone/cda/tut/p/id/7374.
    As far as examples go, there are several text-based examples (as long as you have DAQmx installed) located at: Start Menu >> All Programs >> National Instruments >> NI-DAQ >> Text-based Code Support >> ANSI C Examples. 
    National Instruments

  • Introducing LabWindows/CVI 2009

    National Instruments released LabWindows/CVI 2009 on Friday, December 4th.
    LabWindows/CVI 2009 includes enhanced productivity tools and introduces a new toolkit for run-time analysis and optimization. LabWindows/CVI 2009 also includes support for new technologies such as the Microsoft Windows 7 operating system, 64-bit application development and deployment, and provides a new interface for communicating with NI PXI FPGA-based hardware including FlexRIO and R Series data acquisition modules.
    Visit the What's New  page to see a full list of the new features in LabWindows/CVI 2009 that will help users create more reliable applications in a shorter amount of time and take advantage of new PC technologies. You can also view the What's New webcast series to get a closer look at the new features in LabWindows/CVI 2009. Some of the new features include:
    The new Execution Profiler Toolkit, an application performance measurement and analysis tool
    Improved debugging capabilities  capabilities with extended information in the variables and watch windows
    Easier user interface development with the attribute browser
    Integrated support for 64-bit application development and deployment
    The C- Interface to LabVIEW FPGA, a communication interface for FPGA-based hardware
    Support for Windows 7, the latest Microsoft operating system
    Additional Technical Resources Just for LabWindows/CVI Developers
    Subscribe to the LabWindows/CVI Quarterly quarterly newsletter  to receive the latest product news, tips and tricks, and developer resources. You can also join the LabWindows/CVI user community  and start collaborating with users.
    Adri Kruger
    LabWindows/CVI Product Manager
    Message Edited by Adri K. on 12-07-2009 03:28 PM
    Adri Kruger
    National Instruments
    LabVIEW Product Marketing

    Turbo,
    There isn't a document that covers all the features from 6.0 to 2009, though there are documents that talk about individual upgrades. 
    http://www.ni.com/lwcvi/whats_new.htm
    Also this document covers the upgrades since 8.0  http://zone.ni.com/devzone/cda/tut/p/id/7995
    There have been quite a few upgrades, you can always download an evaluation version and test it out for yourself http://www.ni.com/lwcvi/try.htm
    Richard S -- National Instruments --Applications Engineer -- Data Acquisition with TestStand

  • 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.

  • 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.

  • How do I send e-mail to a distribution list using LabWindows/CVI?

    I need to be able to send e-mail to a user-defined distribution list using LabWindows/CVI? Has anyone done this? Any ideas where I could look?

    I commented on something similar to this awhile back.  My issue was that I had the base version and didn't have the Internet classes.  So this external app worked like a charm
    It has a lot of command-line inputer options to use as well.
    http://forums.ni.com/t5/LabWindows-CVI/Need-Help-for-Sending-Email-with-LabWindows-8-5-or-9/m-p/1095...

Maybe you are looking for