USB-6009 with Labview 2014 on Windows 8.1

Hi,
I have trouble connecting USB-6009 OEM with my new laptop with windows 8.1. My USB-6009 OEM device is not shown up in NI Max. So when I check Device Manager, there is a question mark on "NI USB-6009 OEM FW". I tried to install Labview 2011 but still the same. When I tried to choose the driver in Device Manager manually, I can only find NI-VISA driver as the closest one. It is still not working when I open DAQmx to check my card. It is still not detected in NI Max and anywhere within labview. When I used NI-VISA driver, and try to connect the device in NI Max, I get timeout error. I think I need to see NI-USB driver instead of NI-VISA driver. Any help would be appreciated.
Cheers,

Hi Thoo,
You may also want to try reinstalling the DAQmx 14.5 driver first. DAQmx 14.5 is supported on Windows 8.1. Some of the driver files may have been corrupted and reinstalling the driver may solve the issue. If not, using the DAQmx Base driver could be a good option as Dennis suggested.
Thanks,
Frank
Application Engineer
National Instruments

Similar Messages

  • USB-6009 with "redy to run" datalogger SW

    To get a quick and low cost solution to my data logging need, I bought a USB-6009 which ships with "ready to run" data logger software, NI Data logger. Well, I guess this SW is nice to see if you data USB-6009 works, but for anything else it seems quite useless. It seems that I am only able to log one channel at a time. Whats the use then of having 8 channels? Or am I just missing the functionality in the undocumented SW?

    You can specify a series or group of channels in one of two ways:
    - A colon specifies a channel range (e.g. Dev1/ai0:7 for channels 0 to 7)
    - a comma seperates a group of channels in any order (e.g. Dev1/ai1,Dev1/ai4, Dev1/ai5 for channels 1, 4, and 5)
    This is the standard channel string for NI-DAQmx and NI-DAQmx Base.

  • Compile 9076 with LabVIEW 2014 Worked good with 2012 SP1

    An internal software error has occurred. Please contact National Instruments technical support at ni.com/support with the following information:
    Error 7 occurred at Open VI Reference in nirviOpenVIRefByNameOrPath.vi->niFpgaRemapObjsAndListIfUnderXNode.vi->niFpgaRemapObjsHandleXNodeSubErrors.vi->nirviMassageErrorList.vi->niFpgaErrorDialog_ParseErrors.vi->niFpgaErrorDialog_ReadErrorData.vi->niFpgaGenerateCode_ErrorDialog.vi
    Possible reason(s):
    LabVIEW:  File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.
    VI Path: C:\Program Files\National Instruments\LabVIEW 2014\rvi\CodeGenErrorUtilities\Diagram Constant
    All text parsed:
    <CodegenErrorList>
              <CodeGenErr>
                <ErrorCode>-64001</ErrorCode>
                <DynamicText>
                  <TreeLineInfo>
                    <TreeInfo>
                      <TreeID>1</TreeID>
                    </TreeInfo>
                  </TreeLineInfo>
                </DynamicText>
              </CodeGenErr>
              <CodeGenErr>
                <ErrorCode>-64001</ErrorCode>
                <DynamicText>
                  <TreeLineInfo>
                    <TreeInfo>
                      <TreeID>1</TreeID>
                    </TreeInfo>
                  </TreeLineInfo>
                </DynamicText>
              </CodeGenErr>
              <CodeGenErr>

    Hi Nieman,
    You have the right compilers for your FPGA targets, based on KB 609GUVBT.
    Error -64001 indicates that there is an issue with one of the nodes in your VI. Since you are able to compile a blank FPGA VI, then you should try to identify the node that is causing this problem. When trying to pinpoint this node, I’d recommend executing your FPGA VI with simulated I/O on the development machine, as described in KB 3W6EFRLX,
    Also, are you able to reproduce this issue when running one of the LabVIEW Example Finder FPGA VIs that targets your NI 9076? You can find these examples in the Example Finder's  Hardware Input and Output>>CompactRIO section.
    Regards,
    Tunde S.
    Applications Engineer
    National Instruments

  • Can I use USB 6008 with LabVIEW 6.1 RT?

    Hi there,
    I've been using LabVIEW 6.1 RT for my applications and so far I haven't felt the need to upgrade.
    However, I decided to try the USB 6008 and I'm learning the hard way that this device will only work with NI-DAQmx and apparently not with the latest NI-DAQ 7.4.2 (legacy)  In fact, I can't see the device in MAX 4.1
    Is there any way I can use the USB 6008 with my 6.1 RT version of LabVIEW ?  or should I send the thing back to NI ?
    I will appreciate your guidance on this issue.
    Thanks a lot,
    at

    Hi at -
    Allisso is right.  There is no way to use the USB-6008 with LV 6.1, because neither of its drivers (DAQmx and DAQmxBase) support that version of LV.  You'll have to either upgrade to a current version of LV or work with another device.  I recommend contacting your sales rep at NI for help.
    David Staab, CLA
    Staff Systems Engineer
    National Instruments

  • Sencore color pro USB drive with labview

    I have a Sencore color pro which measures lumens, Color temperature, Cx,Cy cordinates.
    If I want to measure these values using labview, how am I supposed to integrate this sensor
    with labview. It has a USB drive. I need to acquire these values and analyze them.

    HelloYesh,
    MikeS81 is correct. Yu can interface with your sensor using either ActiveX or Call Library Function Node.
    ActiveX and LabVIEW
    http://zone.ni.com/devzone/cda/tut/p/id/2983
    An Overview of Accessing DLLs or Shared Libraries from LabVIEW
    http://zone.ni.com/devzone/cda/tut/p/id/3009#toc1
    Andy Chang
    National Instruments
    LabVIEW Control Design and Simulation

  • When replacing Labview 2013 with Labview 2014, do I firstly need to uninstall Labview 2013?

    I have just recieved my latest version Labview 2014 CD.
    When installing this new version, do I firstly need to uninstall previous Labview versions?
    Solved!
    Go to Solution.

    Bob_Schor wrote:
    The reverse, however, is not true.  Once you install one version of LabVIEW, you cannot install an older version without uninstalling everything and "starting over".  Be warned ...
    Not exactly true.  You can install just an older version of LabVIEW.  I have had LabVIEW 2012, 2013, and 2014 installed on a computer and then installed 8.2.1.  It is all of the support drivers and what not that do not install side-by-side.  So the real lesson here is that if you install an older version of LabVIEW, pray that your current drivers support that version of LabVIEW.  You will need to reinstall the drivers to install the support for the older version of LabVIEW though.  Installing just the support takes hardly any time.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Labview 2014 crashing(windows 7)

    Hello for some reason my labview 2014 crashes when i try to open the labview application. It was working fine until yesterday but not having any luck today. Also i cannot see my labview software in the programs and feature section on the control panel even though i have administrative privileges in my computer. I have attached my error report below.Any help would be appreciated.
    Attachments:
    crash_report.PNG ‏109 KB

    Hi go_sa,
    In Programs and Features are you looking under National Instruments Software for LabVIEW 2014? If so, and LabVIEW is not listed, have you tried re-installing the software?
    If it is listed under National Instruments Software, it sounds like there may be some software corruption causing the error. The next step would be to try repairing the program. If this does not work, you can try force re-install the program (link below) or uninstalling and reinstalling it.
    http://digital.ni.com/public.nsf/allkb/ADD22E807D5A12AD862579EC00760F79
    Julia P.

  • Cannot print on a USB printer with Java PrintService in Windows 2000. Why?

    I want to print a simple ASCII file on a USB printer under Win2K and
    found 2 problems. Here is the 2nd one.
    Even though
    PrintServiceLookup.lookupPrintServices(<DocFlavor>, <AttributeSet>)
    returns nothing when I specify any AttributeSet, I can still print on the default printer, which I get by
    PrintService defServicedefService = PrintServiceLookup.lookupDefaultPrintService();
    but only on a parallel printer (HP Laserjet 4 Plus), either directly attached or over the network. When I try the very same code on a locally USB-attached printer, the printer is obviously reacting, but nothing is printed.
    In case of a Lexmark 730 (an ink printer), the driver even lies, it has printed 100%,
    on a Samsung CLP-510 (a color laser) the ready light flashes twice, that's all.
    The file to be printed has 5 lines and a "0C"X at the end in order to force a page eject at the end.
    I tried it with JDK 1.4.2 and with Java 6, same problem.
    I should mention that I can print that little file out of the editor Textpad without any problem.

    Thanks a lot for the quick hint, but it did not help.
    I used BasicPrint.java and PrintJobWatcher.java of the samples for testing.
    Printing a GIF file works both to a parallel printer and a USB printer.
    Then I changed only the DocFlavor from DocFlavor.INPUT_STREAM.GIF to DocFlavor.INPUT_STREAM.AUTOSENSE, and that one works with my parallel printer, but on the USB printer the Ready light flashes twice, that's all.
    The ASCII file must have a "0C"X at the end to force a page eject on the parallel printer
    Maybe it is a matter of the DocFlavor, but which one?
    DocFlavor("application/octet-stream", "java.io.InputStream") works like DocFlavor.INPUT_STREAM.AUTOSENSE.
    DocFlavor.INPUT_STREAM.TEXT_PLAIN_HOST and DocFlavor.INPUT_STREAM.TEXT_HTML_US_ASCII cause sun.print.PrintJobFlavorException, and with DocFlavor.INPUT_STREAM.TEXT_PLAIN_US_ASCII just nothing happens on either printer, not even an error message.
    I am getting the impression that nobody of the developers ever cared for testing such a simple thing as a plain ASCII file under Windows.
    My printers I am using for the tests are
    1. an old parallel-attached HP Laserjet 4 Plus and
    2. a borrowed USB-attached Samsung CLP-510 color laser

  • Cannot print on a USB printer with Java PrintService in Windows 2000

    I want to print a simple ASCII file on a USB printer under Win2K and
    found 2 problems. Here is the 2nd one.
    Even though
    PrintServiceLookup.lookupPrintServices(<DocFlavor>, <AttributeSet>)
    returns nothing when I specify any AttributeSet, I can still print on the default printer, which I get by
    PrintService defServicedefService = PrintServiceLookup.lookupDefaultPrintService();
    but only on a parallel printer (HP Laserjet 4 Plus), either directly attached or over the network. When I try the very same code on a locally USB-attached printer, the printer is obviously reacting, but nothing is printed.
    In case of a Lexmark 730 (an ink printer), the driver even lies, it has printed 100%,
    on a Samsung CLP-510 (a color laser) the ready light flashes twice, that's all.
    The file to be printed has 5 lines and a "0C"X at the end in order to force a page eject at the end.
    I tried it with JDK 1.4.2 and with Java 6, same problem.
    I should mention that I can print that little file out of the editor Textpad without any problem.
    Edited by: eSchobbert on Jan 24, 2008 11:34 AM
    By mistake I entered the same message another time after modifying the Subject instead of replacing the message. Sorry for that. If I knew how to delete it, I would. So please just ignore this one

    Thanks a lot for the quick hint, but it did not help.
    I used BasicPrint.java and PrintJobWatcher.java of the samples for testing.
    Printing a GIF file works both to a parallel printer and a USB printer.
    Then I changed only the DocFlavor from DocFlavor.INPUT_STREAM.GIF to DocFlavor.INPUT_STREAM.AUTOSENSE, and that one works with my parallel printer, but on the USB printer the Ready light flashes twice, that's all.
    The ASCII file must have a "0C"X at the end to force a page eject on the parallel printer
    Maybe it is a matter of the DocFlavor, but which one?
    DocFlavor("application/octet-stream", "java.io.InputStream") works like DocFlavor.INPUT_STREAM.AUTOSENSE.
    DocFlavor.INPUT_STREAM.TEXT_PLAIN_HOST and DocFlavor.INPUT_STREAM.TEXT_HTML_US_ASCII cause sun.print.PrintJobFlavorException, and with DocFlavor.INPUT_STREAM.TEXT_PLAIN_US_ASCII just nothing happens on either printer, not even an error message.
    I am getting the impression that nobody of the developers ever cared for testing such a simple thing as a plain ASCII file under Windows.
    My printers I am using for the tests are
    1. an old parallel-attached HP Laserjet 4 Plus and
    2. a borrowed USB-attached Samsung CLP-510 color laser

  • Can i build an application with Labview 2009 for Windows 7?

    Hello
    i use Labview 2009 SP1 and the application builder 2009 SP1. If i install the application on win7 this message is display:
    Labview Run Time Engine depends on pruduct with upgrade code (...) version 9.0.301, language {} which is not in distribution.
    Solved!
    Go to Solution.

    Is this an issue with Windows 7 having both installation folders for 32 bit (C:\Program Files (x86)) and 64 bit (C:\Program Files)?
    I had an application built on an XP machine and installed on a Windows 7 machine which was looking for files in C:\Program Files when they were actually installed in C:\Program Files (x86) - because it was 32-bit application.  After installation I had to move the files from 1 location to the other to make it work.

  • How do I control the motors in a third party usb toy with LabVIEW?

    Any suggestions?

    Hi, if you are only wanting to control motors than you have a lot of options. Use the parallel port with a current driver, use the serial port and a micro to control the motor. If you want to interface the USB device than this is where to get started.
    http://digital.ni.com/public.nsf/allkb/42B604435E3F9604862565E20043CD30
    http://zone.ni.com/devzone/cda/tut/p/id/4478
    LabVIEW 8.2,8.6,2009...still learning

  • PC Crash with Labview 7 and windows 2000

    Problem:
    the PC does reboot without any prompt when a LV 7 vi is running; the reboot seems to occur randomly (no time dependent); sometimes instead of rebooting, the PC switches to the blue screen with the following message:
    Stop: 0x0000001E (0xC0000002, 0x80419292, 0x00000000, 0x00000000)
    KMODE_EXCEPTION_NOT_HANDLED
    Xxx Address 80419292 base at 80400000, date stamp 3EE6C002-ntoskrnl.exe
    Starting memory download
    Configuration:
    Intel Pentium IV - 2.66 GHz - RAM 1 Gbyte - Video chipset Intel 82865G;
    OS: Windows 2000
    DAQ Board: PCI MIO 16 E1;
    Labview 7 express - NIDAQ 7.1
    Note:
    The VI that causes the reboot uses the DAQMX to generate an Analog Output with analog trigger.

    > The VI that causes the reboot uses the DAQMX to generate an Analog
    > Output with analog trigger.
    You probably want to post this problem to the DAQ message board as well
    since LV itself really can't cause either of these problems on a
    protected OS. Be sure to be very explicit about what HW boards and what
    DaqMX calls you are making along with which version of the driver you have.
    Greg McKaskle

  • Using USB-6259 with LABVIEW 8.0

    Hello,
    I currently have Labview 8.0 and am trying to use the USB-6259 DAQ device.  When trying to install the device I am told that the driver cannot be found.  I have looked through the knowledge base, forums, and reference this document: Device Drivers
    I have downloaded DAQ-MX 8.8 has shown by the previous link, but that version of DAQ-MX does not support Labview 8.0.  I am hoping someone knows a way I can make my version of Labview and this device work together.
    Thank you in advance...

    This is the document you are looking for:
    NI-DAQ & LabVIEW Version Compatibility (for Windows)
    And, you will find the drivers over here:
    Drivers and Updates
    Adnan Zafar
    Certified LabVIEW Architect
    Coleman Technologies

  • How to use USB interface with LabVIEW Embedded for ARM

    Hi everybody.
    I am developing an application based on the "LabVIEW Embedded for
    ARM". Now I am doing various tests using
    the evaluation board 2300 (with NXP LPC2378), but soon I will
    dedicate to program the micro used in my project (NXP
    LPC2148).
    During the tests, I have seen that "default" LabVIEW interface allows the use
    of CAN, I2C and SPI interfaces of the micro. I want to know how can I also use the
    USB interface that is on the micros -both LPC2148 and LPC2378- (pin USB_D + / D-, USB_UP_LED,
    USB_CONNECT, VBUS).
    Thanks in advance for your suggestions

    @chueco85
    If you've created an application in LabVIEW for ARM and you build it.
    you can go to tools >> ARM Module >> Show Keil uVision
    then go to he build options.
    the hex file will be created when you do a build.
    with flash magic :http://www.flashmagictool.com/
    you can program your device.
    Wouter.
    "LabVIEW for ARM guru and bug destroyer"

  • Print text file with labview 2011 and windows 7

    I am having some strange problem, hope someone out there knows the solution.
    We have a labview program running under windows xp, the program runs some test and print label from a local label printer. Last week, I have to upgrade the computer to windows 7 and all the sudden the printer will not print any more.
    The print vi is very simple. I am using the report function and I am attaching the diagram of that vi below. 
    If I use windows notepad to open that small text file, I can print fine. This means the printer driver itself is OK. However, if I print the same text file through Labview printing vi, from the printer's task list, I can see it does not recognize the char. From the attached png file, the top one is the task from notepad, it shows 2 pages and the bottom one is from the labview, it becomes 33 pages. 
    For the printer part, I use Generic / Text Only printer driver which comes from windows itself. And I am aslo attaching a sample of the text file, there are quite a lot of special char, it is for print bar code. When I tried to use labview print text vi to print general text from my computer to a regular printer, the vi works. So it seems Labview print can not handle the special char? Although it worked many years under windows XP in the past.
    Welcome to any suggestions!
    Thanks
    Attachments:
    print vi.gif ‏9 KB
    labview print bug.png ‏26 KB
    SerialLabel.txt ‏1 KB

    DGU wrote:
    where to check RAW or TEXT? the print report vi only asks for file name and printer name.
    When I print from notepad, everything just goes by default. This is a label printer, so I never need to specify printing parameter such as size, orientation, etc in the past
    Famous last words go something like this: "...never had to do that before."  Maybe you have to do that now.  It's worth at least comparing the defaults settings for bothe generic drivers.  It could save you a lot of headache if you notice something different.
    Bill
    (Mid-Level minion.)
    My support system ensures that I don't look totally incompetent.
    Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Maybe you are looking for