DAQmx uninstalled?

I have the Labview professional development system installed on my computer
 (version 8.5) including DAQmx. I used the same machine to run my
application(executable) which uses an SCXI chassis and a number of cards. It ran fine,
butwhen I tried opening up the source code later it seems that DAQmx had been
uninstalled. The VIs cannot be found and DAQmx is no longer on the user
palette. Can you tell me why this happened and what the solution is? Do Ineed
to re-installDAQmx? Should I be running executables on the same machine that I have
installed the development system?

Did you use an installer for your executable?
There is a strange feature/bug whereby if you run an installer that has a cut down version of DAQmx (e.g. just the runtime + MAX) on a system with the full DAQmx package installed, it will remove the additional features that were not included in the installer.
A way around this is to not use the installer on your development machine (it shouldnt be necessary anyway as you will already have any appropriate runtime drivers)
Shaun 

Similar Messages

  • Uninstall LabVIEW but leave run-time engine and DAQmx

    Hoping there is an easier way to do this, basicall we are developing software on a customers computer that we buy and will eventually ship to them. However we can't ship them LabVIEW so we make an executable and just keep the run time, DAQmx and MAX. Is there anyway to do this easier than uninstalling LabVIEW and reinstalling everything else?
    Windows 7
    LV2013

    Under Windows, try going to Control Panel | Programs and Features and find National Instruments Software. You might be able to select all except the run-time, DAQmx and MAX, then select uninstall. If not, then perhaps consider just making a full installer for your LabVIEW executable solution, this will clearly install only the necessary components for your code to work (if it's LabVIEW 2013).
    Thoric (CLA, CLED, CTD and LabVIEW Champion)

  • Uninstall daqmx 8.8 before installind LV 2009?

    We're just starting to deploy applications built in LV 2009.  We have a program that was written in 8.6 and distributed as an executable.  The installer for that old program also installed DAQmx 8.8 and the LV 8.6 RTE.
    Now we are building an updated version in LV 2009.  It's installer uses DAQmx 9.0.1.  Previously, when an installer needs to update DAQmx, it just does so, right on top of the current version.  (At least for minor revision numbers...)  But when we try to run this installer (built from a LV2009 project), it says it can't run until you manually uninstall DAQmx 8.8.  You have to exit the installer, run the NI add/remove to get rid of DAQmx 8.8, then run the installer again.  This is rather inconvenient for our customers who are trying to upgrade our program in the field.  Worse yet, when you manually uninstall DAQmx 8.8, it says that the old version of our program is a dependency and forces you to uninstall it too, along with the LV 8.6 RTE!  Once DAQmx 9.0.1 and our new program are installed, you can reinstall the 8.6 RTE and reinstall our old program, which then works with DAQmx 9.0.1.
    Our old and new versions are side-by-side compatible, so forcing the customer to uninstall everything to get a new version of DAQmx installed is incredibly inconvenient.
    Has anyone else noticed this issue?  Is there something we're missing on running these installers that would prevent this?
    Thanks,
       DaveT
    David Thomson Original Code Consulting
    www.originalcode.com
    National Instruments Alliance Program Member
    Certified LabVIEW Architect
    There are 10 kinds of people: those who understand binary, and those who don't.

    The reason for this is due to certain changes we made to how DAQmx runtime engine is divided in DAQmx 9.0.
    Prior to DAQmx 9.0, the runtime engine consisted of 5 parts and a full version.  Each of the runtimes could upgrade the previous version.  However, because of the complexity of building 5 runtime engines and one full version, not all 5 REs would be released each time the full version was updated.
    With DAQmx 9.0, we simplified the runtime scheme to have a Core, Config, and Full version of DAQmx.  The Core version only includes the necessary components to run a built executable.  The Config version includes all of the components of Core, Measurement and Automation Explorer (MAX) and the necessary components to use DAQmx functionality in MAX.  The full version includes everything in the Config version, but also all of the components necessary for development.  We now build all three of these versions each time we update the full version, allowing us to continually provide smaller runtime engines with each DAQmx release.  This also allows for just the Core or Config component to be updated without having to completely update the API in many cases, leading to better modularity with regards to distributing DAQmx with built installers.
    However, because the way that runtimes were mapped changed with 9.0, in order to prevent a number of upgrade/downgrade issues we had to disable upgrading from a runtime engine of a version older than 9.0 to any version after 9.0 or upgrading any full version prior to 9.0 to any runtime after 9.0.
    Put simply, when crossing the DAQmx 9.0 line, only a full installation can be upgraded, and only to a full version.  Any other upgrade across the 9.0 boundary will require an uninstallation.
    Now that this change has been made, however, once you are past the DAQmx 9.0 line, all upgrades should go smoothly for you.
    Seth B.
    Staff Test Engineer | National Instruments
    Certified LabVIEW Developer
    Certified TestStand Developer
    “Engineers like to solve problems. If there are no problems handily available, they will create their own problems.”- Scott Adams

  • NI-DAQmx 1.0.1 for PocketPC over NI-DAQmx 1.4 for XP

    Hi,
    On my development system I have LabVIEW 7.1 + PDA add-on. The other day I installed NI-DAQmx 1.4 in order to use a USB-6008 device (which took me 2 hours to finally find a posting about switching the DAQmx driver to make it work). But now I'd like to use the CF-6004 card in my PDA and test it but I find that DAQmx 1.4 does not support PDA and I need to install DAQmx 1.0.1 to make it work.
    However when I try that then the 1.0.1 installer won't install because "a higher version of this product already is installed on your computer".
    Please do not make me uninstall DAQmx 1.4.
    Thanks,
    Remco Breen

    I'm getting a very similar result trying to run  updateNIDrivers  on a 2.6.12 kernel (see my post on Re: NI DAQmx Base on Debian). Does this have to do with a specific kernel version or configuration?
    I posted my error message here
    - I'm getting the same error for the patched kernel that came with the
    linux distribution (ubuntu) and a vanilla kernel. I tried gcc version
    2.95, 3.4 and 4.0 but - as mentioned - with the same result. Any ideas? Thanks in advance,
    -ingmar-

  • NI-DAQmx 8.8 does not work properly after upgrade to LabVIEW 8.6

    Hi,
    I just upgraded to LabView 8.6 from version 7.1 and found out that the NI-DAQmx 8.8 drivers do not install correctly, since there is not Measurement I/O tab in the Functions palette (see attached document). The curious thing is that I can see all my NI-DAQmx devices in the MAX, and they all test correctly, i.e., they are working correctly. The sales representative for my area recommended me to uninstall , and reinstall LV8.6 and then reinstall the NI-DAQmx 8.8 drivers, but it did not work. I still do not see the Measurement I/O functions and my application says that it "cannot compile" the NI-DAQmx vi's. Thanks in advance for your help.
    Peter
    PS. Someone reported a similar problem back in 2003, but the final solution was not posted. Thanks again.
    Attachments:
    LV8.6.doc ‏116 KB

    Dear Mallori,
    Thanks for your help. You are right, I uninstalled and reinstalled LabVIEW 8.6 (update from LabVIEW 7.1) and reinstalled DAQmx 8.8. I still continue to have some problem that seem (to me) beyond compatibility issues. Here are the answers to your questions:
    1.  Before you reinstalled DAQmx 8.8, did you
    uninstall it? If not, then I  believe that the installer would see the
    driver already present and not actually make any changes.
    REPLY: No, I did not uninstall DAQmx 8.8. What do you recommend? Should I uninstall BOTH LabVIEW 8.6 and DAQmx 8.8 and then reinstall everything again? 
    2.  When you say that the VIs are not responsive,
    could you describe this a bit better? Perhaps post one of the error
    messages about compiling that you mentioned in your first post?
    REPLY: I am having a lots of "This SubVI is not executable" error messages in many of the library VI's not even mine. See the attached file.
    3.  If you open the NI Example Finder (Help»Find
    Examples) and the expand Hardware Input and Output»DAQmx»Analog
    Measurements»Voltage, are you able to run one of the example programs
    and see the correct values that you see in the Measurement and
    Automation Explorer Test Panels?
    REPLY:  I tried to runa couple of the examples for continuous voltage acquisition (internal clock) and both open with errors (see attachement).
    Thanks again for your help. I am looking forward to your recommendation.
    Regards,
    Peter
    Attachments:
    LV8.6-3.doc ‏43 KB

  • NI-DAQmx Run-time Engine

    Is a run-time version of the NI-DAQmx v8.6 driver available yet? I'm distributing an application from LV 7.1 that requires DAQmx and want to include this as part of the installation. I found run-time packages for v8.3 but I'm using v8.6 in my development work so hate to switch to an older version. Are there any compatibility issues in using v8.3? Thanks.
    Art

    HI Paul,
    Thanks for your suggestions. Just prior to receiving your response, I had in fact tried to build just an installer for the daq driver from LV 8.5. The problem is that it forces the project to be saved before it will create and installer and then proceeds to include the empty project and the LV runtime engine. In my case, I named the project test and the installer created c:\test on the target and installed the LV runtime as well as the daq driver. I also ended up with a regiestered application - test. Once I manually uninstalled test, I had the result I wanted, but too long a path to get there.
    I bit the bullet and migrated the code from LV 7.1 to LV 8.5 so that I could build a comprehensive installer. Generally, things turned out well. My biggest question is why the application builder / installer insists on putting both LV 8.2 and 8.5 RTE on the target. I want, and expect, only LV 8.5 RTE. I'm have installed and am running off of the 3rd Q release for the NI developer suite. Why is 8.2 RTE loading and how do I correct this?
    Another strange result is that my daq device and channels do not show up in MAX. I included the level 5 daq driver and MAX in my installer as well as the hardware configuration. The application works ok, and if I manully import from my *.nce file then I get a warning that my device will be replaced. Is this normal? The GPIB controller shows up as normal. The only thing that seemed odd during installation was that the daq driver didn't complete installation after restart because I forgot to plug in the daq device cable. Afterward it seemed ok.
    I also have a couple of bugs with the application builder / installer. I converted my LV 7.1 build script and made needed changes. I see the following behaviors.
    1) I have setup a file to install into a subdirectory. Every thing works ok except when I subsequently go back into the Installer Properties window and go to the Source Files. I see two problems. First, in the Project View my files are in the correct locations, but the icon for the one in the sub-directory is switched with the very last one in the list. Second, in the Destination View the next-to-the-last file from the Project View is the one shown in the sub-directory while the file that should be in there is listed directed below it in the list (but not in the sub-directory). Everything installs to the correct location, but this maked it very confusing to edit the installer.
    2) Whenever I use the Build All command, the application builder fails with the following error. If I start the build individually from the Properties window, then the build completes successfully.
    Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
    Error 1 occurred at Copy in AB_Engine_Copy_Error_Files.vi->AB_Application.lvclass:Copy_Error_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
    Possible reason(s):
    LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
    =========================
    NI-488:  Command requires GPIB Controller to be Controller-In-Charge.
    C:\Program Files\National Instruments\LabVIEW 8.5\user.lib\errors\McPherson-errors.txt
    Thanks again for help.
    Art

  • NI-DAQmx 8.3.0f0 installed but Found New Hardware Wizard shows up when plugging in a USB-6008

    I have NI-DAQmx Device Driver 8.3.0f0 installed with LabVIEW 8.2 but when I plug in a NI USB-6008 I see the "Found New Hardware Wizard" in Windows XP.  Since the DAQmx driver is installed shouldn't Windows recognize the device immediately?
    I cancel the driver and I get the taskbar message "A problem occurred during hardware installation.  Your device may not work properly."
    The USB-6008 does not appear under Devices and Interfaces in MAX. 
    Help would be appreciated.
    Thanks,
    Dave

    Ahh, I thought Windows performed an automatic search after cancel is clicked. 
    I clicked next and allowed Windows to search and it says:
    "Cannot Start this Hardware"
    There was a problem installing this hardware: USB-6008
    The device cannot start.  (Code 10)
    I tried uninstalling and reinstalling the device but the results were the same.
    Any ideas?

  • Missing DAQmx folder in vi.lib

    I tried installing LabVIEW 8.2.1 and its requested device driver disks on a computer without any DAQmx device, and no DAQmx folder is placed inside vi.lib.
    As a result, one of my LabVIEW programs won't compile. Is there a way to trick the installer into putting the DAQmx folder into vi.lib even though there is no DAQ device there? Simply copying the DAQmx folder from another computer doesn't work.

    There is no requirement to have hardware installed. I have no DAQ devices on this pc and and DAQmx installed just fine. I've done the install on many computers without any hardware. Was this a fresh install and what OS are you using? Does MAX indicate that DAQmx is installed? If it does and it's listed in the National Instruments section of Add/Remove programs, try doing a repair first and if that does not work, uninstall and do the DAQmx install again.

  • How do I downgrade from NI-Daqmx 9.0 to 8.1?

    So my ni-daqmx drivers decided to die off and my programs would no longer run.  I could see my daq card (6024e) in the device manager for windows but in MAX there was nothing.  So I installed the ni-daqmx 9.0 drivers and all the software that comes with the nidaqmx900f2.exe in order to fix the problems I was having.  The computer once again recognized my boards and through MAX it was good to go.  
    However I have labview 7.0 and ni-daqmx 9.0 does not work with labview 7.0, however ni-daqmx 8.1 does.  I've been trying everything in the world to downgrade to 8.1. 
    I have removed the ni-daqmx drivers from within the labview add/remove software program, however when I run the 8.1 installer everything is red x'd.
    How do I uninstall nidaq-mx 9.0, everything that came with it and downgrade to the 8.1 package?  
    Thanks,
    -Whil 

    This thread was continued and resolved here.
    Regards,
    h_baker
    National Instruments
    Applications Engineer
    Digital Multimeter Resources

  • Does the DAQmx drivers include LVRun-Time Engine?

    Does the DAQmx drivers include LVRun-Time Engine?
    1. I first installed LVRun-Time Engine 7.1.1 on a new PC.
    2. Then i ran the installer once again and selected remove to uninstall the program.
    3. Next I installed DAQmx drivers 8.0.1
    4. After this I tried to run my compiled labview.exe and it works fine(!)
    When I look in control panel - add/remove programs and select National Instruments software and press change, I can see that NI LabVIEW Run-Time Engine 7.1.1 is installed.
    Now why would version 7.1.1 be included in DAQmx 8.0.1?
    Question1: Was perhaps the LVRTE install refreshed by the DAQmx install?
    Question2: Is it not possible to completely remove installed software with the regular uninstall? I am trying to verify the install procedure as it will be on a fresh PC.

    The run-time engine is included with DAQmx. If you look at the distribution, there is a Products folder that has it. My guess is that it's included for something like VI Logger or even the test panels in MAX.

  • I can not create an Installer, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...

    I can not create an Installer on LabView, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...
    Solved!
    Go to Solution.

     Hi Shada this can happen if you are including additional installers to your installer for example DAQmx. When you are doing this the installer has to include other files like MAX (Measuremente and Automation Explorer). Probably when you installed Vision Builder it updated MAX, so when your installer is trying to Include MAX, its asking for the source where it was installed in your computer in this case Vision Builder.
     Here you can cache the information so its not asked again, or you can download a newer version fo DAQmx, so it will update MAX and change de dependecy.
     You can find more details about this issue in this KB:
    KnowledgeBase 3S88PJMY: Why Do I Get A "Missing Distribution" Error When Trying to Build an Installe...
    And for keeping a copy here is more info:
     How Do I Stop the Missing Distribution Notification Each Time I Build An Installer?
    Best Regards
    Benjamin C
    Senior Systems Engineer // CLA // CLED // CTD

  • Missing DAQmx Create Task.vi among others

    Hi all,
    I'm trying to run a .vi made in Labview 8.5 using Labview 2012. I have the most recent version of DAQmx (9.5) installed, but it's unable to find the file DAQmx Create Task.vi, and if I chose to ignore it about 6 other files pop up that it is also unable to find. I have uninstalled and installed DAQmx on both my computer and two other computers running Labview 2009 to try and get this to work, but nothing seems to be solving the problem. Any ideas what might be going wrong here?
    Thanks!

    Are you trying to open the VIs using 8.5 or 2012?  Are the DAQmx VIs in the palette?
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Erratic behaviour/results using DAQmx

    Hi!,
    One of our PXI based automation systems is not working as expected.
    The errors we are observing:
    1) Timed while loop hangs and is unable to read the clock source. The clock source is TTL pulse train coming from encoder and fed to Counter 0. When we reset the loop (or force a timeout) it continues to read the pulse correctly. The vi used for this test is attached. We tested with a hardware counter running in parallel to ensure pulse availability.
    2) Wrong readings of various digital I/O. For e.g. even when a proxy is in OFF state, the software reads it as ON
    3) MAX (version 3.1) got corrupted and we had to repair the same.
    Pointers:
    1) The above mentioned errors occur at random. There is no pattern or frequency of occurance.
    2) When the hardware was first shipped to us, the controller showed erratic behaviour (while booting) which seemingly resolved when we changed the onboard BIOS battery.
    3) Do you think reinstalling the OS will help? We have already uninstalled and reinstalled NI-DAQmx 7.2 without any success.
    4) We have Service Pack 4 and IE 6.0 (for Win2K) installed. Are there any known issues with SP4 and IE 6.0?
    System Specs:
    OS is Win2000 Professional.
    Development environment is LV 7.1
    Chassis / PXI-1031
    Controller / PXI-8184
    Multifunction / PXI-6025E
    Serial / PXI-8423
    Connector Boards / SCB-68 (two numbers)
    Any help will be appreciated
    - Gurdas
    Gurdas Singh
    PhD. Candidate | Civil Engineering | NCSU.edu
    Attachments:
    TimeoutTesting_VI.zip ‏199 KB

    Sean,
    I have not tried the 100KHz timebase but what I did try yesterday was using the encoder pulses to simultaneously run a counter and trigger the time loop.
    My VI for this is attached. Sequence 0 and 2 in my VI are used to powerup and powerdown the motors and can be excluded from our discussion.
    I have inserted a note in the blockdiagram that explains VI results and behaviour.
    To restate: The encoder pulses (at PFI8) were being edge counted by Counter 0 and simultaneously acting as source of timing for counter 1 which in turn was the tick for timeloop. What was observed is that while the time loop went into an infinite wait (if my timeout was -1) or continuous timeout (if say timeout was 50ms), counter 0 continued to successfully count encoder pulses.
    This, to me, strongly points that either the timing source for the timeloop is failing to do its job OR the timeloop is failing to read the ticks coming from timing source OR both are failing to do their job.
    What inference can draw from this?
    I guess we can rule out encoder pulses to be the issue since counter 0 does not fail. Do you think something is wrong with my PXI-8184 controller? Is this a bug?
    Eagerly awaiting some answers that can help me resolve this deadlock.
    Thanks,
    Gurdas
    Gurdas Singh
    PhD. Candidate | Civil Engineering | NCSU.edu
    Attachments:
    Test_Counter_TimeLoop.zip ‏128 KB

  • DAQmx support for Labview 8.0

    I am having a problem with the current DAQmx Drivers,
    The system used to run perfectly when using labview 8.0, however, after the installation of labview 2009
    The DAQ library in the labview 8.0 folder is missing.
    I tried to install the older version of the DAQmx (Legacy) but i still can't get the library back in labview 8.0 folder.
    Would it possible to get those files ?
    Thanks,
    Ahmad Aladdasi
    Mechatronics Engineer
    Solved!
    Go to Solution.

    Hello again,
    I tried to uninstall everything related to labview on the computer using msiblast, but still having the same problem, even after removing every labview newer than 8.0 files.
    When I try to install DAQmx 8.6 it says a newer version is available.
    I deleted the registry stuff to.
    I had to keep labview 8.0 because it is the version i want to use plus i don't have the CD to install it, so i kept it and it's support files.
    Can anyone send me the DAQmx library for labview 8.0?
    Makesure it is the Vi files not the installation setup because that one will give me the same problem, " Newer Version is installed" problem.
    Don't refer me to any extra links about installing, cuz honestly i have seen them all....
    Thanks,

  • SCXI - Error when creating virutal channel in Daqmx

    Hi All,
    I am in the process of upgrading our measurement system to labview 7. I uninstalled Labview 6 and then installed labview 7. In MAX our SCXI is verified and confirmed.
    In my program when I try to create a virtual channel using the DAQmx Create Virtual Channel.vi I get the follwoing error:
    Code: -200220 - Device Identifier is Invalid.
    I use the following physical channel string:
    SC1Mod1/ai0
    I can't find any information on the error code. Please Help!!
    Regards,
    Setu.

    Setu,
    Indeed, this is quite puzzling. I have a few items to try. To use the DAQmx Create Virtual Channel.vi, your chassis needs to be verified under "NI-DAQmx Devices" (NOT Traditional NI-DAQ Devices) in MAX. Once you have confirmed that, the "physical channels" input should self-populate with a list of available channels. Check the filtering of the names if it does not show up. Hope this helps.

Maybe you are looking for