CVI 2009 + NIDAQMX ?

Bonjour,
J'ai installé une version d'essai CVI 2009 et lors de la compilation d'un ancien projet (historiquement sous 8.0) j'ai des problème de link sur la bibliothèque NI-DAQMX ...
Cela vient-il d'un problème de compatibilité avec mon ancien NI-DAQ ? Si oui quelle version dois-je utiliser avec CVI 2009 ?
Merci d'avance 
Résolu !
Accéder à la solution.

Bonjour,
J'ai besoin de quelques informations supplémentaires pour vous aider. Quelle version de NI-DAQ, NI-DAQmx utilisez-vous ? Sur quel OS êtes-vous? Quelles sont les problèmes de link que vous avez rencontré, pouvez-vous copier les messages d'erreurs ?
Avez-vous encore la version 8.0 de CVI installé en même temps sur le pc ? Si oui, ce document peut vous aider :
Installing DAQ Support for Multiple Versions of LabWindows/CVI
Cordialement,
Charlotte F. | CLAD
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;}
>> "Du 11 octobre au 17 novembre, 2 sessions en parallèle : bien démarrer - approfondir vos connais...

Similar Messages

  • How to use CVI 2009 with CVI 2012 installed

    I have TestStand 2012 / CVI 2012 installed. 
    I need to also test using teststand 4.2.1 / CVI 2009.
    I installed teststand 4.2.1 / CVI 2009 and can activate teststand 4.2.1 but I cannot access CVI 2009. 
    Is there any way to have CVI2009/2012 both available on the same computer? 
    Is there a way to compile CVI 2012 to work with TestStand 4.2.1?

    Hi HMRJ,
    You can have multiple versions of CVI installed on the same computer. Can you explain in detail what you mean when you say that you cannot access CVI 2009? Do you mean that you can't open it or can't activate it?
    I am not sure I understand what you mean by compiling CVI 2012 to work with TestStand 4.2.1. You should be able to create a DLL from CVI 2012 and call this code module from TestStand. Are you receiving any errors when you try to do this?
    Regards,
    Anjelica W.
    National Instruments
    Applications Engineer

  • LabWindows CVI 2009 Word_Rpt routines: Document is corrupted: Error reported: The MSWORD.OLB file cannot be opened.?

    Using WordRpt support routines with a C application in LabWindows CVI 2009 to format Word files, an error sometimes occurs resulting in the document format being corrupted.  An error  is generated: The MSWORD.OLB file cannot be opened.  I don't know why or how to correct this problem.
    Any help you can provide would be appreciated!

    Hi LPR1,
    Do you have an application that reproduces this.  If so, do you mind posting it?
    Regards,
    Hassan Atassi
    NI Community Project Engineer

  • Can't open .prj files CVI 2009

    Running CVI 2009 and everything had been running fine for weeks.  Shut down test program that was running.  Installed my license device and went to my .prj file to open it up in debug mode.  When I double clicked on it, Windows says it can't find the file, even though it is sitting right there in explorer, it will not open it.  Tried several other .prj files and it does the same thing.  Tried opening CVI by itself and then loading the .prj file, but the splash screen comes up and then it never does anything else.  Rebooted several times (running XP SP3), then finally tried to do a repair of the CVI install.  This didn't help and it did the same thing.  Then deleted everything and did a fresh install...it still says it can't find the .prj file.  It seems like something has gotten corrupted in my Windows install maybe??  Probably going to try and re-image the machine, but trying to figure out what happened.  Anyone seen anything like this ever before???
    Thanks for any info...
    EDGE

    Hi EDGE,
    I haven't run into a similar error in the past but keep us posted on if reimaging the machine resolves the issue.
    Best Regards,
    Swathi B

  • CVI 2009 Very slow installation of distribution kits

    I'm having an issue with distribution kits built with CVI 2009 taking a long time to install on some PCs.  In the installer, the progress bars will both be completely full, with the top one displaying "Overall Progress" "Currently Installing [application name].  Part 1 of 1."  The bottom bar displays nothing.  During this time, there is usually a few instances of msiexec.exe sucking up considerable CPU time according to Task Manager, and the disk does not appear busy.  If I wait several minutes (sometimes 10 minutes or more), it will eventually move on, with the next step displaying "Validating Install..." on the bottom progress bar.  This only happens on some PCs, other ones install in a reasonable amount of time (less than a minute).  Once the installation is complete, everything appears to have worked and the installed software runs fine.  The only pattern I've noticed that the PCs that show this problem tend to be older models.  One is a P4 3.2Ghz desktop with 1.5GB of ram, and the other is a Core Duo (not sure about speed at the moment) Dell laptop with 2GB of ram.  Both are running Windows XP SP3.  
    Any insight into this would be appreciated, as some of the PCs that show this are ones used for testing software packages and often having things installed onto them.  Thanks.

    Hi tstanley,
    I was wondering what you were running distribution kits from - hard drive, CD, network or USB stick?
    Charlie Rodway
    Test Design Engineer
    Rolls-Royce Controls and Data Services Ltd

  • Timer( ) resolution in CVI 2009 SP1

    In the CVI 2009 SP1 Contents Help for Timer() function I find
    The resolution is normally 1 microsecond. However, if you set the useDefaultTimer configuration option to True, the resolution is 55 milliseconds.
    But if you click on the useDefaultTimer hyperlink, a new page is opened, where you can read that the resolution is 1 millisecond if you set useDefaultTimer to False.
    Which is the right resolution?
    I wrote my application considering 1 microsecond, but I found strange problems, and I think it is 1 ms.
    Vix
    In claris non fit interpretatio
    Using LV 2013 SP1 on Win 7 64bit
    Using LV 8.2.1 on WinXP SP3
    Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
    Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

    Hi vix,
    Thanks for bringing those documentation problems to our attention.
    1. There does seem to be a problem with a lot of the function prototypes in the .chm help in the CVI 2009 SP1 and 2010 versions, where an extra asterisk seems to have been added to a number of output parameters. We'll fix this and post a corrected version of the affected .chm files as soon as possible. In all these cases, the parameter data type as it appears in the Parameters section of the help topic is correct, as is the prototype in the corresponding function panel.
    2. Concerning the timer resolution issues, the async timer resolution is in fact 1 millisecond, as confirmed by the GetAsyncTimerResolution function. But note that asynchronous timers are a library in and of themselves, and are not covered by what is discussed in the documentation of the Timer() function or the useDefaultTimer option.
    The resolution of the Timer() function should be 1 microsecond, as of CVI 9.0 and later. The function documentation is correct. When that change was made, however, the documentation of the useDefaultTimer option was incorrectly not updated. It should say that "the performance counter timer provides a resolution of 1 microsecond".
    You mentioned that you didn't think that the resolution of the Timer() function was 1 microsecond. If you run the following code, what do you see?
    int     i;
    double  time[10];
    for (i = 0; i < 10; i++)
        time[i] = Timer();
    for (i = 0; i < 10; i++)
        DebugPrintf ("timer = %f\n", time[i]);

  • SqlToolkit Problem with CVI 2009 and Windows7

    Hello,
    I'm using the test version of CVI 2009 and have a problem with the sql toolkit which works fine under CVI 8.5.
    DBNewConnection()  returns always -100 and the error message is NULL.
    Did you have any ideas what causes this problem and how it can be solved?
    Thanks in advance
    Inomed1

    Hello Inomed1
    have you tried to reinstall the SQL Toolkit?  I found some cases in the past where this has been helpful. 
    For further investigation it would be interesing witch DBMS is used?
    Regards
    Moritz M. 

  • Unable to use external compiler support in CVI 2009 with VC++ 2005

    The compiler gives me this error message:
    cvisupp.lib(setprec.obj) : fatal error LNK1103: debugging information corrupt; recompile module
    Solved!
    Go to Solution.

    Well, I do call InitCVIRTE  in my main, but it doesn't find it in cvisupp.lib, it finds _InitCVIRTEEx@12   this way:
    00404808      _InitCVIRTE@4                                    initcls.obj
    00404818      _InitCVIRTEEx@12                              initcls.obj
    004048FC      _CloseCVIRTE@0                                initcls.obj
    The identifier  cvisupp.lib is no where in the map of my project.
    I do see this library in the NI folders on the PC however.
    I think we may be crossed up here in what we're doing - I am building the application from the LabWindows 2009 framework in release mode using the VCPP 2005 compiler as an external compiler ... are you building from Visual Studio or from CVI 2009?
    Menchar

  • CVI 2009 Base Package won't activate CVI 8.1

    I own a license for CVI 2009 Base Package, which is activated and works correctly.  A customer of ours requires that we use CVI 8.1.
    When I launch CVI 8.1, I first got an evaluation period, but now I'm unable to launch at all since the evaluation is expired.
    I already tried removing my cvi_base_pkg_080100.lc and downloading the new one from NI's site (http://joule.ni.com/nidu/cds/view/p/id/78/lang/en).
    License manager shows that the license is installed correctly:
    What should I do next?
    Josh W.
    Certified TestStand Architect
    Formerly blue

    Louis,
    Thanks for cluing me into how NILM works with NI software.  I didn't realize that it was linked as a static library.  I had seen in the past when NI moved to WinVista-compliant paths that licenses didn't need to be in the old folders and that software pre-change and post-change worked equally well with the new folders, so I had guessed that it was all handled by the NILM runtime.
    Nick,
    This may not be a reproduceable case.  I wish I could tell you my install order...but unfortunately this machine isn't that clean.  I think the order goes something like this, but I'm not completely certain:
    Install CVI 7.1 (eval)
    Install CVI 2010 (eval)
    Install CVI 8.1 (eval)
    Install TestStand 4.2.1 (eval)
    Install TestStand 2010 beta (beta license)
    License CVI 2010 & CVI 7.1
    Install LabVIEW 2010 (full)
    Uninstall TestStand 2010 (after beta expires)
    Uninstall TestStand 4.2.1
    I originally had all of the usual license files for CVI, but I removed the extraneous ones (full/debug/etc.) as part of my debugging to make sure they weren't interferring in some way. I still have those licenses, they're just in a subfolder called 'old' within the Licenses folder.
    My UAC is set to "Notify me only when programs try to make changes to my computer (do not dim my desktop)".
    I'm logged in as "VIRGINIA\Josh" (VIRGINIA is the name of our local domain), and I'm an administrator.
    If you can't reproduce this, and it's not immediately obvious what's causing it, don't spend too much time at it. I'm worried it's an interaction between the TestStand beta license expiring, and the CVI license being in eval at that time.  I can work around it for now (I can write the code on my machine where I have better monitors and then compile it on a test machine where it licenses correctly).  We're also considering moving to Win7 x64 by the end of the year, so I'll have to re-install everything then anyway.
    Josh W.
    Certified TestStand Architect
    Formerly blue

  • CVI 2009 and C99 variadic macros

    I've read in the help that "Variable arguments macro" (or variadic macro) is one of the C99 extensions supported in CVI 2009 (since CVI 8.5 if I' right).
    So I declared the following variadic macro
    #define ERR_MSG(x, ...)    printf(x, ##__VA_ARGS__)
    using the ## token to swallow the preceding comma in case the variable-argument list is empty (the ## token is a GCC extension of C99, but also other compilers implement it).
    Unfortunately CVI doesn't and I get a compiler error if I call
    ERR_MSG("Message");
    with an empty variable-argument list.
    Would it be possible to implement the ## token also in CVI?
    Vix
    In claris non fit interpretatio
    Using LV 2013 SP1 on Win 7 64bit
    Using LV 8.2.1 on WinXP SP3
    Using CVI 2012 SP1 on Win 7 64bit, WinXP and WinXP Embedded
    Using CVI 6.0 on Win2k, WinXP and WinXP Embedded

    We'll try to implement this for a future release. Thanks for the feedback.
    Mert A.
    National Instruments

  • Labwindows CVI 2009 compatible issue with VISA 4.4.1?

    Hi,
    I would like to understand is there any compatible issue for Labwindows CVI 2009 with NI VISA 4.4.1? If so can you please direct me to the right document where this is document.
    Can you also tell me what is the version of NI VISA for Labwindow CVI 2009. Please reply at the earliest.
    Regards,
    Usha

    Apparently HP has stopped updating that application for Firefox. It wasn't available for Firefox 3.6 last year and now - not for 4.0 either.

  • CVI 2009 - Instruments loaded in project lost when CVI shutdown/restarted

    Steps to duplicate:
    1. Start CVI 2009; load a project with no instruments loaded.
    2. Load instruments into project (the test case in which this problem was observed loaded niScope.fp and FieldPoint.fp; NI-Scope version was 3.5.1, Field Point was 6.0.4).
    3. Compile/build project.
    4. Shutdown CVI; restart (project will be reloaded by default).
    Observed behavior:
    1. Instruments loaded into project in prior iteration will not be loaded and need to be reloaded before project can be compiled/built.  This behavior was not observed in prior versions.

    This is the expected behaviour, I think. At list it was up to release 8.5 (I can't test more further). See here.
    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?

  • [CVI 2009] Unexpected trailing tokens on directive line ignored.

    Hello
    We use CVI 2009 and we have this warning :
    Test.prj(Debug) - main.c - 1 warning
    1, 1 Warning: Unexpected trailing tokens on directive line ignored
    The first line of the main is just a comment.
    Have you ever seen this? Do  you have any idea to wich line is ignored?
    Regards
    Etienne RABY

    Hello
    I have more information about this and the problem is probably not with the code:
    Unexpected trailing tokens on directive line ignored.
    Compile Warning
    Preprocessor line contains harmless trailing tokens that the compiler ignored.
    Nacer M. | Certified LabVIEW Architecte

  • CVI 2009 menu bar resize problem

    In CVI 2009, if you have the 'scale contents on resize' attribute set for a panel with a menu bar on it, the menu bar font resizes with the panel.
    Unfortunately, there is a rather severe bug in this. If you do the following repeatedly:
    (a) Load a panel with 'scale contents on resize' set and a menu bar
    (b) Enlarge it
    (c) Display it
    (d) Hide it
    (e) Discard it
    then the menu bar font gets progressively bigger and bigger each time the panel is displayed. Below is an example from the test project attached to this posting (four successive display iterations). To say this is inconvenient is understating the truth: It actually breaks many of my applications. Is there any way to stop this behaviour?
    Martin
    Certified CVI Developer
    Attachments:
    TestMenu.zip ‏6 KB

    Hello Martin -
    I'm very sorry for the inconvenience this bug has caused.  Another workaround that may be a little simpler would be to update the font of the menubar with a newly created metafont immediately before showing the panel (and after resizing).  This also has the added benefit of the menu retaining it's original size instead of being scaled.  You could accomplish this with code similar to the following:
    int hNewPanel, hMenuBar;
    hNewPanel = LoadPanel (0, "TestMenu.uir", MENUPANEL);
    hMenuBar = GetPanelMenuBar (hNewPanel);
    SetPanelSize (hNewPanel, 600, 800);
    CreateMetaFontEx ("NewMenuMetaFont", "NIMenuMetaFont", 13, 0, 0, 0, 0, 0);
    SetMenuBarAttribute (hMenuBar, 0, ATTR_MENU_BAR_FONT, "NewMenuMetaFont");
    I also just wanted to add why the behavior of scaling menus with "Scale Contents On Resize" changed in LabWindows/CVI 2009.  The problem was that when using scale contents on resize, all fonts are supposed to scale proportionately to the scaling of the panel.  However, menu fonts did not scale, and this led to the problems seen in this forum.  Because of the inconsistenty and to fix the bug reported on that forum, bug report 134165 was created and then fixed in LabWindows/CVI 2009.
    Once again, I'm sorry for the inconvenience this has caused,
    NickB
    National Instruments

  • LabWindows CVI 2009 9.1.0 - Build 64-bit Apps?

    I have LabWindows/CVI 2009 (version 9.1.0 427).  Can I build my apps as 64-bit apps?  Do I need a service pack upgrade to do this?  Or do I need to upgrade to a higher version of LCVI?
    Thanks

    LabWindows/CVI 2009 introduced the ability to create and distribute 64-bit executables, DLLs, and static libraries, see e.g. here

Maybe you are looking for