Installing labview with DAQmx

I am trying to install labview 2009 on a new
computer with windows xp but am having some problems. I installed labview and the f3
patch.Everytime i try to install Ni-Daqmx 9.1 I get an error saying
that 
The system cannot read from the specified device
This
happens when it tries to install support for  labview 1.13.0. Any
suggestions on how to rectify this would be helpful
Thanks
Priam

Hi Prima,
Where are you installing this driver from a DVD or a folder?
I suggest that you download it from here and run it on your machine from a
folder on your desktop. It might be a corrupted download or a bad Disc/Drive if
you are using a Media. You might want to try to copy the disk to your desktop
and trun it from there as well.
Thanks and have a great day.
Esmail Hamdan | Applications Engineering | National
Instruments  

Similar Messages

  • Installing LabVIEW with WINE (?)

    So my primary computer runs Ubuntu64 Linux (8.04).  I purchased a LabVIEW Developer Suite (8.5.1) for Windows as the programs I will build will be for Windows primarily.  I don't plan on interacting with external hardware in any of my VI's, only parsing data files and displaying graphs and other such things. 
    I'm trying to install this Windows version of LabVIEW under WINE (1.0-rc2) and I'm receiving this error message: "You have a different language edition of LabVIEW 8.5 already installed.  You must unistall that edition before you can install the English edition."  But here's the thing, I've not installed any version of LabVIEW ever on my system.
    What is the deal here?

    jjrev wrote:
    So my primary computer runs Ubuntu64 Linux (8.04).  I purchased a LabVIEW Developer Suite (8.5.1) for Windows as the programs I will build will be for Windows primarily.  I don't plan on interacting with external hardware in any of my VI's, only parsing data files and displaying graphs and other such things. 
    I'm trying to install this Windows version of LabVIEW under WINE (1.0-rc2) and I'm receiving this error message: "You have a different language edition of LabVIEW 8.5 already installed.  You must unistall that edition before you can install the English edition."  But here's the thing, I've not installed any version of LabVIEW ever on my system.
    What is the deal here?
    LabVIEW 8.x depends on so many Windows thingies like ActiveX, .Net and whatever that it will  not likely run at all or at least not very well. Also the Installer is a very complex MSI installation that is likely to push the Wine implementation of MSI beyond it's capabilities despite their great efforts in MSI support in the last one or two years.
    I've tried LabVIEW 6.1 under Wine several years ago and got it working quite fine but at that time LabVIEW was a rather self contained package. Nowadays it integrates with so many things under Windows and installs many extra components to support the different editions like RT, FPGA, embedded, etc. that it is almost certainly not going to run.
    I guess it would be an interesting test case for Wine and someone with
    a lot of free time could help Wine quite a bit in making LabVIEW
    install and run under it but since there is a Linux version of LabVIEW for a long time already I have never bothered to make newer LabVIEW versions install under Wine anymore.
    Rolf Kalbermatter
    Message Edited by rolfk on 05-30-2008 12:07 AM
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Labview winxp 64bit *VI coding only* with DAQmx

    We have a few workstations in our lab, with a labview 8.2 license for each. One of our machines (few months old dell) has windows xp pro 64bit installed as the operating system. It is not used for data aquistion of any sort, but we do want to be able to write/fix/code VIs involving DAQmx.
    The official NI line is that winxp 64 is not supported, but since i don't want to do data aquisition on this machine, there should be some way to create VI with DAQmx.
    I have tried an install of labview then a manual install of DAQmx 64bit components manually from the Drivers CD, but it remained invisible to Labview.
    Can anyone give me any help with this?
    thanks.

    Hi
    FieldKam,
    The first thing i tried was the labview install, which of course did not install DAQmx. I then tried to install the NI-DAQ resource disk onto the pc, which resulted in the installer terminating upon the discovery that is was winxp 64.
    I then took a closer look at the contents of NI-DAQ's folders, and found 64 bit installers in locations such as \NIDAQ861-1\Products\NI-DAQmx\.
    These individual installers appeared to run without issue, but the ability to write VI's in labview with DAQmx assistant and other components would not show.
    Now since, data acquisition would not be done on this machine, i pondered a 32bit install. Win xp 64 does run 32 bit applications as well, but i could not fool the installer to install for win xp 32. I attempted to copy a 32 bit install from another machine by folders and registry keys. This made DAQmx - Data acquisition icon under Measurement IO subpalette, but it lacked components such as DAQmx assistant.
    Next i tried a brute force approach: i overwrote the folders with those of a 32bit install, which provided all the DAQmx tools in labview, but then was confronted with the problem that Labview could not find the dll (& other libraries) dependencies. I haven't been able to progress past this point.
    thanks for any tips you may have!

  • Installing LabVIEW 8.2.1 with DAQmx 8.0 on Suse 10.2 for Linux.

    We recently installed LabVIEW 8.2.1 on Opensuse 10.2 for Linux.  After some work, my advisor was successful at getting the install to work with DAQmx 8.0 and NIKAL 1.5.  I thought I would post the install notes for anyone who finds them useful.  Everything seems functional thus far.
    Jeff Hay
    Attachments:
    installnotes_2007aug13.txt ‏12 KB

    Jeff,
    Thanks for the extremely detailed post.  I have actually been experimenting with this combination of software for the past couple weeks (i.e. OpenSUSE 10.2, DAQmx, LabVIEW 8.2.1).  Your steps match mine very closely.  I did have a one thing to add, and one question about your steps.  First, I just want to mention that NI-KAL 1.6 has been released and it fixes several issues when installing NI-KAL with newer kernels.  This is available at:
    http://joule.ni.com/nidu/cds/view/p/id/850/lang/en
    I would highly recommend using NI-KAL 1.6.
    Second,  I wanted to ask about step #2 where you modify the modpost.c file.  When I ran updateNIDrivers I was not required to make this change.  However I did have to increase the allowable symbol length.  I changed the line:
    #define SZ 500
    to
    #define SZ 1024
    in modpost.c.
    I then proceeded to follow the steps you mentioned and was able to run updateNIDrivers without error.  Could you test to see if changing the allowable symbol length fixed the problem without having to ignore the "parse error in symbol dump file."  I don't exactly know what the read_dump function does but it always makes me nervous to ignore errors.  Since NI-KAL uses modpost to install a kernel module, this failure may be important, although I don't know for sure.
    Once again thanks for your awesome post.
    Regards,
    Neil S.
    Product Support Engineer
    Multifunction Data Acquisition
    National Instruments

  • New Hardware / DAQmx Install, LabView 7.1 Now Missing DAQmx VI's?

    Hello -
    I've been running Labview 7.1 and some applications we've built with it for some time now.  Due to an old DAQ board failure, we had to upgrade.  Upon receiving the new (PCI-6225M) DAQ board, we had to update DAQmx (to 8.9.5) in order for this new board to be supported.
    In doing so, it appears that the DAQmx VI's I had for Labview 7.1 were actually removed from the system.  When I try to load my 7.1 applications, I get errors saying that it can't find various DAQmx VI's (like the DAQmx Create Task and Read VI's).  Since it allows me to browse for them, I browse to the directory structures that *do* have them now (intended for LV 8.2+, which we don't have).  If I select these VI's they seem to be found okay, but then I get an error for each VI saying that it's only for a newer version of LabView, not v7.1.
    So what gives?  What can I do?  Why on earth would a newer DAQmx installer actually go in and remove already existing files from my previous install that previously worked fine?  I am not impressed.  What should have been a simple board upgrade now appears to be setting us back some significant time.
    Thanks,
    Brett

    Hi Dennis,
    I also have common issue.  I am using labview 7.1 with DAQmx version 8.8.  Recently, I just bought the cDAQ-9178, which requires me to upgrade my DAQmx to version 9.4.  After installation completed, I discovered all my DAQmx missing.  My question is:
    1. Do you have any patch to let me stay @ LV version 7.1 with the new DAQmx 9.5 without missing DAQmx vis?  I need the new DAQmx to be able to connect with cDAQ-9178.
    Thanks you for your time, Dylan

  • LabVIEW 8.2 can't work with DAQmx program written using LabVIEW8.0 ?

    My old LabVIEW program is using the DAQmx sub-vis  from folder: C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\DAQmx
    e.g. C:\Program Files\National Instruments\LabVIEW 8.0\vi.lib\DAQmx\create\channels.llb\DAQmx Create Channel (AI-Voltage-Basic).vi
    After I installed LabVIEW 8.2 and NIDAQ831.zip (~600MB), there isn't a folder called DAQmx in folder:
    C:\Program Files\National Instruments\LabVIEW 8.2\vi.lib\
    When I load my old program, it need I specify the location of, e.g. DAQmx Create Channel (AI-Voltage-Basic).vi,
    I copied DAQmx folder from \LabVIEW 8.0\vi.lib\ to \LabVIEW 8.2\vi.lib\
    After I copied the DAQmx folder, right click on "block diagram" under "measurement I/O" the folder "NI-DAQmx" comes out and I can pick all the vis inside "NI-DAQmx"
    However, all the vis are not executable.
    My old program find all the vis needed to load; however, the vis are not executable, e.g. DAQmx Create Channel (AI-Voltage-Basic).vi, please see the attachment.
    Anyone know how to solve this?  Thanks.
    ------- LabVIEW 2009, So Easy, Even a Therapist Can Do It -------
    Attachments:
    DAQmx_Error.JPG ‏97 KB

    You should make sure that in the installer options of DAQmx the support VI's for LV 8.2 are installed.
    Ton
    Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
    Nederlandse LabVIEW user groep www.lvug.nl
    My LabVIEW Ideas
    LabVIEW, programming like it should be!

  • How to solve the error "The specified resource is reserved" when running with DAQmx And LabVIEW?

    How to solve the error "The specified resource is reserved" when running with DAQmx And LabVIEW?

    I hate "J term"
    OK I love the learning the students get.   And, I like helping them out!  But, as a former man who's got the varicose viens to prove he's spent time "behind the podium" (yeah, "behind the podium" puts 'em to sleep- songs and dances for the young'uns) come on! USE the tools you teach!
    Instructors invited to engage in the forums
    Jeff

  • Just Installed Labview, it won't recognize previously loaded DAQmx

    Just Installed LabView 7.0. Previously had Evaluation version working, even using DAQmx.
    Now DAQmx is not recognized by Labview 7.0 (no DAQ assistant express VI at Functions>>Input palette).
    Device Driver CD won't load because it's already there... Should I punt by removing all and reload or what?
    SIDE NOTE:
    Also tried to register this new S/W (purchased from NI last week) but web site (ni.com/register complains that this S/N is already registered... which is not likely as I opened the package myself)

    Try running the Driver CD again to get the DAQmx support for LabVIEW 7.0. It is quite possible that when you uninstalled, eval copy, DAQmx support went away because you don't have LabVIEW anymore.
    Now that you have LV 7.0, run the DAQmx installer to get the support files.
    A Rafiq

  • Problem with DAQmx and Real Time PCI-7041/6040E.

    Problem with DAQmx and Real Time PCI-7041/6040E.
    I have a problem with the Real Time card PCI-7041/6040E, I think it is properly installed because my software run with the traditional NI-DAQ. When I try to use the new DAQmx to acquire one signal, Labview doesn't see any device for de DAQ card 6040E.
    Information, I work on Windows XP and LabView v7.0.0 (NIDAQ RT v7.0.0, NI-Serial RT v2.5.2, NI-VISA v3.0.1 and NI-Watchdog v2.0.0).
    Could Labview RT run with new DAQmx ?
    What can I do to use DAQmx with PCI-7041/6040E?
    Thanks for your help !

    Hello,
    I refer to your posts because i am using the PCI 7041/6040E card as
    well but without any success to make it work. The problem I have
    already described in the following thread:
    http://forums.ni.com/ni/board/message?board.id=170&message.id=120198
    Would be nice if you had a look on it, maybe you can help me. BTW, the
    thread starts with a problem of someone else, the difficulties I
    encountered are to be found a little bit to the bottom of the thread's
    page.
    Thank you!
    Dirk Völlger
    Darmstadt
    Message Edited by ratschnowski on 07-28-2005 07:14 AM

  • Blue screen after installing labview 8

    I recently installed Labview 8 Professional Dev. Suite on to a Win. XP SP2 system.  The image before installation was stable.  After the installation and reboot, the system blue screens (I have been unable to read the exact message on the blue screen) and reboots.  I was able to boot if I selected "using last know configuration" option in the Windows XP boot options, indicating that the problem is driver/registry related.  After I use the last know configuration, I get an error message "nidevmon.exe - Application Error.  The application failed to initialize properly (0xc0000142).  Click on OK to terminate the application." 
    I tried to repair all of the installed NI products without any success.
    Device manager shows all devices installed properly without any conflicts.
    Please advise on how I can resolve this installation conflict.
    Thanks.
    --Jeff

    Hi, I am experiencing the same problem.  When my system boots up I receive the "nidevmon.exe could not be initialized" error message.  When I try to manually start the program after startup, I still get the same message.  I am running Microsoft Windows XP [Version 5.1.2600] and have also updated my system with the latest patches.  I have the ni USB-6008 device.  My system is an IBM Thinkpad T40, 1.5Ghz Centrino, with 512MB ram, and 80GB hd.  I have installed labview 7.1 and then NI-DAQmx 8.0 that came with the card.
    Furthermore, the hardware does not succesfully install on my system.  After I install the software, reboot and plug the usb device in, the hardware wizard pops up.  However, in the end, I get "Windows cannot initialize the device driver for this hardware. (Code 37)".  I suspect this has to do with the nidevmon.exe not initializing.  The ni hardware appears to be fine, I have successfully installed the devices in another system.  I uninstalled and reinstalled the ni-daqmx 8.0 software several times, and even downloaded version 7.5 from the web, however this did not solve the problem either.  I would appreciate any suggestions..
    Thanks,
    Arash

  • SCXI 1001, SCXI-1102 and SCXI-1303 not working correctly with DAQmx

    I have recently upgraded from Labview 6.5 to Labview 8.2 and now my SCXI 1001 with a SCXI 1102 and SCXI 1303 terminal block no longer reads the correct voltage.  Using the old version of labview thermocouple measurements are correct at 0.5mV; however using the new version of labview and DAQmx the thermocouples are reading 5V.  Everything is installed correctly as it still works with the older version of Labview, is there something that needs to be reset or change so that teh SCXI will function properly with DAQmx?

    Hello ilabtech,
    From my understanding you are using an SCXI 1001 chassis with an SCXI 1102 and 1303 terminal block to perform thermocouple measurements.  You are upgrading to LabVIEW 8.2 and DAQmx.  I am assuming you were using LabVIEW 6.1 since there isn’t a LabVIEW 6.5.  You mentioned that are able to get a correct reading of 0.5 mV with LabVIEW 6.1 but you see a rail of 5V with LabVIEW 8.2 and DAQmx. 
    My first suggestion is that you ensure that the SCXI is set at the appropriate range and for the correct thermocouple type.  You can also configure these settings in MAX as detailed on page 27 of the SCXI 1102 User Manual and Specifications Guide. 
    My second suggestion is for you to start off using an example program to see if you see the same error.  When you are in a LabVIEW 8.2 VI you can go to Help>>Find Examples to open the NI Example Finder.  You then choose Hardware Input and Output>>DAQmx>>Analog Measurements>>Temperature>> Cont. Acq Thermocouple Samples-Int CLK.vi.   This example program is supported by your hardware and is a good resource to use to troubleshoot.
    If these suggestions aren't helpful please answer the following questions in your reply.
    1.        I would like to know what range you have set the SCXI 1102 to read. 
    2.       What version of DAQmx are you using?  You can find the version my opening Measurement and Automation explorer (MAX), expanding the “Software “and clicking on NI-DAQmx.
    3.       What operating system are you using?
    4.  Does your Traditional DAQ program work in LabVIEW 8.2?
    Regards,
    Ima
    Applications Engineer
    National Instruments
    LabVIEW Introduction Course - Six Hours
    Getting Started with NI-DAQmx

  • Problem with DAQmx Physical Channel control

    Dear LabVIEW community!
    I have installed LabVIEW, v13.0f02, 32-bit on my PC. The problem, which I face, is that DAQmx Physical Channel controls, which are used in VIs inside the LV projects, sometimes don't show me the list of DAQ devices - I can't expand the list at all. I push the button to expand the list, but nothing helps.
    But when I create VIs outside the project, and put there DAQmx Physical Channel control - everything works well.
    Note: devices are simulated via MAX.
    Is it some kind of bug in 2013 vesrion of LabVIEW? Because while using LV 2012 I didn't have such headache.
    The only thing that helps now - is to restart PC (laptop) several times; b/c restart of LV doesn't help.
    Can anyone suggest, what it can be, and how to fix this problem?
    Thank you very much in advance!

    Thank you for your answer!
    The point is, that this bug is independent from the code. DAQmx Physical Channel controls don't work even when I'm trying to use NI examples - for instance, Strain - Continuous Input.vi; Voltage - Continuous Input.vi, etc.
    I have such simulated via MAX devices: NI USB-9213, NI USB-9201, NI cDAQ-9172 with NI 9217, and 4 NI PXIe-4331 modules.
    Also, what I have noticed - front panel doesn't visualized fully (I send you the screenshot). When I'm moving mouse pointer over it, those part, which were under the mouse pointer, became clearly seen. And when I minimize, and then restor FP, it becomes fully clear visible.
    And also, this story happens when LV project is open. If I close opened projects, and open only single VIs, everything works smooth.
    Thank you very much, I hope, that this information will be useful to solve this problem.
    Attachments:
    Screen 1.PNG ‏87 KB
    Screen 2.PNG ‏107 KB
    Screen 3.PNG ‏129 KB

  • Installing LabView 6.1 Runtime on Win 7 64 bit

    Hi,
    I have LabView 6.1 based program which I want to install and run in Windows 7 64bit. I tried to install LabView 6.1 Run time Engine. It looks like it starts loading then hang on for long time.
    What is the issue here?
    Regards

    Fair point, I hadn't forgotten XP Mode, but simply chose not to suggest it as a solution at this point.  Not all versions of Windows 7 support XP Mode, so that isn't necessarily an option for the OP.
    NI-DAQmx devices aren't supported in virtualised OSes like XP Mode, this is due to the nature of USB communication handling in virtualised OSes.  Typically, they are optimised for HMI devices or Mass storage, but not higher performance devices such as USB DAQ.  We don't know if the OPs application requires USB, another reason that XP Mode isn't necessarily a suitable option to suggest at this point.
    Another noted issue with XP Mode is that it can brick certain USB devices for, as yet, unknown reasons.  This is not limited to NI Hardware specifically, but with USB devices in general that do not fall under the HMI or MS categories and is a problem that Microsoft are actively working on.  So rather than suggesting the use of XP Mode that could potentially cause problems with his hardware, if he is using any (which we don't know at this point), it is better to ask some more questions about the particular application and the OPs needs.
    If the information from my last post was sufficient for the OP, then he/she needn't reply, if however, they require more information, then we can begin to explore other solutions such as XP Mode if it's appropriate.
    When using older versions of LabVIEW, it is also a good idea to ascertain why/if an older version is required.  It is possible to open VIs from certain older LabVIEW versions in current versions, which I'm sure you are aware, so it might be that the OP isn't aware of this and might be under the impression that he must use the same version to work with his VIs.  Which isn't the case.  Hence my last question regarding why LabVIEW 6.1 is required.
    For the sake of the post, this information is available here.  You can open LV 6.1 VIs in LV 2011.
    I am completely aware that a simple search would have turned out those resources, that's exactly what I did to get the links to them.  However, not all LabVIEW users are aware that there are extra sources of information available by searching ni.com in addition to the forum search, so it could be helpful to point this out just in case.  Not all of the information I have sourced would necessarily be found by simply using the forum search bar, it might, but then again it might not.
    Yes, I agree with you that there are other posts asking similar questions and Yes, I agree that in this instance searching for the issue at hand would probably have negated the need for this post to have been made, but whilst it is true that the OP might not have searched to see if he/she could resolve his/her issue, at least now he/she is aware of the resources that are available to him/her and can continue to be proficient and successful in the future.
    hants1984: Having just read your last post, you should find the information you require in the above links.  The question on LabVIEW 8.5 in Windows 7 64 bit has come up in the past a lot on these forums, the official answer is no.  LabVIEW 8.5 is not supported in Win7 64, however, as discussed in the above post, XP Mode may be an appropriate solution for you.
    Oli
    LabVIEW Student Ambassador
    National Instruments UK

  • Old VI, new LabView and DAQmx Driver

    I was given a VI that was made with LabView 2012 and DAQmx drivers 7.0. I am in LabView 2013. Would this VI still work if I installed new drivers (drivers that are compatible with LabView 2013)? Do I have to install LabView 2012 or can I just install new drivers?
    Solved!
    Go to Solution.

    DAQmx 7.0 was not compatible with LabVIEW 2012.  In fact, it was barely compatible with 8.1.  Perhaps you meant 9.7?
    Just use the new drivers and save the VI(s) in LabVIEW 2013.  You shouldn't have any issues.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • How can i install labview in a AMD64Linux machine?

    Hello:
    I'm a linux user, I have Debian installed and maybe changing for Suse or Mandrake due to the NI's preference on those two OS. But I have only one question: is it possible to install LabVIEW in a linux that's native AMD64, this means, that if there's a 64-bit Linux Version of LabVIEW?
    Thanks for reading this.

    Hi panthell, your concerns have solid bases. If you want to Learn LabVIEW and get full functionality, I will suggest using Windows. But if you want to use Linux you will find less trouble with the  32 bit OS.
      The 32 bit Suse can work with 64bits as if there were 32. So it could work, but you won’t have all the functionality or will have to deal with more small problems.  Also there is a version of 64 bits of Suse, it has some compatibility mode to run programs as 32 bits systems. Using this final option you may have the core functionalities running but might have trouble with NI drivers. Still using Linux 64 bit will have some of the limits the Linux and the 64bits.
    http://www-uxsup.csx.cam.ac.uk/pub/doc/suse/suse9.0/adminguide-9.0/node14.html
     LabVIEW as it works on a Runtime can be used in many platforms the officially supported are the ones that we had made tests and are confident they will work
    Benjamin C
    Senior Systems Engineer // CLA // CLED // CTD

Maybe you are looking for

  • Error  in Km when submit for approval.

    Hi In Km once in a while we are having error when we submit a document to be approval. If I restart the application, the error will disappear. This is the error log I receive when I submit. Anybody have an idea. Thank you Could not create command wit

  • Error uploading in host directory

    Hi I've seen different topics on this but I still can't seem to fix my problem. Whenever I put a host directory (in my case: www) I get an error message. Please check out the two files below for more insight. This used to work before so it's a total

  • Stocktransfer after UD doesn't work

    Hi experts, following problem: Creation of a inspection lot (04) by release of a work order. Inspection lot was created without inspection lot stock, because GR from WO wasn't done. After WO confirmation, GR with MB31 (Mv-Typ. 101) was done. Material

  • Remove line breaks within a xml element

    Hi, I have a xml element that contains a long text string with multiple line breaks. something like this: text text text text text text text text text How can I remove all line breks except one, i e I still want a line brek after each text line: text

  • Mass change of component in Task list

    Hi Experts I have thousands of material and there are changes done for them to use them in maintenance order task list as stock or nonstock. The task is to change the item category (from L to N or from N to L) of those materials used as components in