USB 6009 - mysterious problem

Have mysterious problems with my new USB 6009.
I'm using LabView 7 on MacOS-X 10.3.8.
All vi's of DAQmx show "ERROR 15 - Ressource not found".
Then I tested:
- "lsdaq" shows the device
- "nidatalogger" works
- "mxbaseconfig" doesn't recocgnize it!
I realy have no idea know what to do now?
Thank you for helping.
Greetings,
Stephan

I happend to stumble over the same issue and found a solution.
The problem really seems to be the firmware in the USB-device. There is
only one way (I think) to make USB600x devices work with linux:
You have to start MAX (on a Windows-box) , go to tools - NI-DAQmx configuration - NI-DAQmx USB Driver Selector.
Press "Switch" and select the BASE-Driver for your USB-Device. This
seems to write something into the device's flash memory. After this
procedure you can use the device with linux and DAQmxBase
Funny thing is, mxbaseconfig still can't see it, but nidatalogger finds it.
Hope that helps, even though this thread seems to be rather old...
-DB

Similar Messages

  • USB-6009 device not found problem

    Hello all,
    So my VI and USB-6009 have been working fine until recently.  I noticed the VI was not reading or graphing information from the analog input channel correctly.  My firmware is up to date, but I noticed a problem.  In Isdaq, it will recognize that the USB-6009 is connected, then when I run my VI and stop it, i check Isdaq for my device again, and it does not recognize any device.  I have to unplug the daq and replug it for Isdaq to recognize the usb-6009 again.  But each time I run my VI, it does not seem to collect any data, and it makes the device unrecognizable.  Do you know what the problem might be?  Attached is the VI I have been running in case you want to look at it.  Its been working fine until now.  
    btw, I am running Labview on a Mac OS X
    Thanks for the help!
    Solved!
    Go to Solution.
    Attachments:
    AO:AI Data Aquisition.vi ‏39 KB

    Hello Solis,
    I would recommend making changes to the parallel tasks to use the error cluster to force the order of execution, since NI-DAQmx Base is not multi-thread safe (review NI-DAQmx Readme). Please verify if this alleviates the issue.
    Best regards,
    Ali M
    Applications Engineer
    National Instruments
    www.ni.com/support

  • Usb - 6009 Device Recongition Problems

    Hi,
    I just got a USB-6009 DAQ. I have labview 7.0, drivers software and the supplied software installed with no problems. In the measurment nad automation explorer (MAX) the device is recongnised and declared problem free. I tried to test the device in labview using help tutorials which suggests the DAQ assitant block. After selecting Analogue input and then voltage I am told that no device is detected i.e. Where I should be selecting my terminal(s) I am not giving any options.
    If anyone has had the same problems or know how to fix them I would be thankful of your help.
    Kyle

    Hi Kyle,
    The USB-6009 device works on DAQmx base. This is a restricted version of NI-DAQmx which is used on some of our products. Unfortunetly it is incompatible with DAQmx and the DAQ Assistant uses DAQmx. Therefore you can't use the UDB-6009 with the DAQ Assistant.
    To use the device, load up the USB-600x Interactive Control which should be located in the following directory.
    C:\Program Files\National Instruments\LabVIEW 7.0\examples\daqmxbase
    Take a look at this and figure out how the code works. If you want to configure it to do your own specific functions then I would suggest that you use this program as a base and customise it for your purposes.
    Best regards,
    Peter H.
    Applications Engineer.
    NIUK.

  • Setup Problem in Measure 2.0 with USB-6009

    I purchased a USB-6009 for my laptop (running XP Pro), and installed the NiDAQmx vers. 7.5 that came with the unit. I opened NI explorer, and tested the unit in there (using Test Panel). It worked nicely there, though the indicator light on the DAQ board  was blinking. I then added my copy of Measure to the computer, but when starting MS Excel, I get the error message "Measure unable to detect a valid installation of NI-DAQ. Please install NIDAQ before using Measure for Windows Data Acquisition Add-In."
    Is there a step I missed? or is there something wrong with my applications?

    Hello dlclough,
    Measure 2.0 is a Legacy application that works only with our Traditional NI-DAQ Legacy driver, not NI-DAQmx which supports the USB-6009.  The blinking light on the USB-6009 simply indicates that the device is receiving power.  However, if you go to this section in the Readme file for NI-DAQmx 7.5, you can look at your numerous options for programming NI-DAQmx.  You can also use VI Logger Lite which is installed with the driver for simple data logging applications.
    Regards,
    Laura

  • USB 6009 lock-ups?

    Hello,
    I'm having a strange problem with my newly aquired USB 6009. I've written an app to read the temperature from a temperature controller using the 6009 and that all works fine. However, the problem comes when I port this code into another application. The code is intended to run in a parallel loop to the main execution loop, to continuously read the temperature whilst other data is captured and process (all done in the main loop). Both applications run quite happily when separate. When I bring them together the applications sometimes, but not all the time, refuse to quit and just lock up. I have no idea what is happening as it is not a case of one loop remaining running (I've tried separate stop buttons) and they will run together quite happily. The problem only comes when I hit the button that terminates the main loop (this also triggers the other loop to stop - I'm sure this bit works as I've used the same method in another vi).
    The main loop should, in theory, just close. The loop with the USB reads (using DAQmx Base) will stop and then clear the task (DAQmx Base Clear I think). Sometimes the DAQmx Base Clear runs and the program stops fine, other times it runs and the program locks, other times it locks as soon as I hit the quit button.
    Any thoughts as I'm completely stumped on this one? Like I say, apart from the one button triggering both loops to terminate there is no link between the two loops.
    My only thought is it could be a USB issue as the PC also has a USB keyboard and mouse. I know from my home experience, when for instance plugging in my camera, it can cause the USB to lock if, say, my USB modem is running.

    See the thread
    http://forums.ni.com/ni/board/message?board.id=250&message.id=13722
    John Weeks
    WaveMetrics, Inc.
    Phone (503) 620-3001
    Fax (503) 620-6754
    www.wavemetrics.com

  • USB-6009 Sine Wave

    Hi,
    I am new to LabView and am having some trouble. I need to input two sine waves into a USB-6009. I have a voltmeter that should read the output. Two of the problems that I have had thus far: I can only use "On Demand" in DAQ Assistant and even when I throw the DAQ Assistant into a while loop I still do not get a readout on my voltmeter. Any suggestions? Thanks for the help.

    That is confusing. You say you need to input 2 sine waves into a 6009 and that to me implies that you are doing a DAQmx Read. Then you say you have a voltmeter to read the output. That implies you are doing a DAQmx Write. If you are really doing a write from the 6009, then on demand is, of course your only choice. As the specs clearly indicate, the output of the 6009 is strictly software timed so you would need to pass a sine wave point by point and then you would have very little control over the frequency. And, again as the specs clearly state, the fastest output rate you could expect is 150Samples/sec.

  • Usb 6009 acquisition fall after 15min

    Hello,
    Like it's said on the name of my post i have some problem with my new usb 6009. When i start it all work good but after a while my two AI fall to 0V. I put my code in joint pieces. I use AI0 and AI1 with a 220ohm resistance.
    Thank you
    Samuel Rioux
    Attachments:
    test.vi ‏30 KB

    Hi skling,
    DON'T use an additional Wait function when you have set your DAQmxRead to use a certain sample rate!
    It will wait on it's own and after some time you will miss to read samples in time...
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Usb-6009 high-speed continuous acquisition for slow control loop application

    Hi,
    After watching a few Youtube videos, I successfully built a control loop in LabVIEW using my USB-6009. Currently, this loop is limited by the speed my actuator can take and respond to commands, topping out at 200 Hz. This is completely sufficient for my application. My question is more regarding the wasted potential of the USB-6009 to acquire samples at a much higher rate than what would be obtained if I used a simple single sample-on-demand during every iteration of the loop.
    It seems to me that having the USB-6009 continuously acquire samples and having my control loop periodically check in for the latest data when it is ready to execute would have the advantage of allowing me to average groups of samples together to lower the overall noise associated with the measurement process (I am reading voltages from an amplified photodiode).
    1) Does anyone know how I would instruct the USB-6009 to continuously acquire at say 10 kHz, so that on each loop I will have 50 or so samples that can be averaged together for a more accurate measurement of my control variable? Unfortunately, I'm new to this and not too familiar with DAQmx Timing.vi.
    2) I've heard that reading into a buffer can increase latency for moving data into the computer. Given the low speed of my control loop, I don't foresee this as being a problem. Is this a correct assumption? I can probably live with an extra millisecond of latency.
    3) I goofed around briefly with DAQmx Timing and managed to see a buffer overflow error. Certain rare events will by necessity cause my control loop to take much longer to execute, so I cannot guarantee that occasionally during normal operation I will not overflow the buffer. Can I suppress this error so that the dialog box does not pop up and the program continues to run uninterrupted? If the buffer overflows and old data gets overwritten it isn't a big deal for me since the control loop is only concerned with the latest data anyway.
    Thanks for any info!

    Howdy Patrick!
    Here is a picture of the front panel:
    Here is the block diagram:
    And I've attached a copy of the VI saved for LabVIEW 7.1.
    Regards,
    Barron
    Applications Engineering
    National Instruments
    Attachments:
    most recent samples.vi ‏73 KB

  • USB 6009 thermocouple noise

    I'm using NI-DAQmx 7.5, Labview 7.0, and a USB-6009.
    I'm trying to get a more accurate reading from my j-type thermocouple.  It is now distorted with noise and jumps rapidly +/- 20 degrees around room temp without any heat being applied.  When heat is applied, it climbs as it should but with the same variation.  I haven't moved to the labview side of it yet, I'm still trying to get a usable reading in MAX.  I have it wired as a differential input with a floating signal source.  I've installed 10k ohm resistors for bias current return as instructed.  Installing the resistors helped but still leaves me with the readings shown in the attached pic.  I've also tried grounding my USB 6009 with no results.  Please help. john
    Attachments:
    thermocouple reading.jpg ‏41 KB

    Hi John,
    What you are running into is a problem with the actual voltage resolution of your USB-6009.  This device has 14-bits of resolution over a minimum range of +/- 1V.  That means that the voltage resolution is (1 - (-1))V / (2^14) = 2V / (16384) = 122uV.  While this is an excellent resolution for such a low cost USB device, you will still notice problems when trying to make a thermocouple measurement.  The reason for that is that Thermocouples make a very small output voltage (see image below).
    Common thermocouple types have the following response:
    K type: 41 microVolts per degree Celsius
    J type: 56 microVolts per degree Celsius
    T type: 52 microVolts per degree Celsius
    There are a few options for ways to get around this limitation.
    Good: You could read the signal in as a voltage and then manually convert that voltage into a temperature.  This would be the least accurate method, but it should allow you to average out your signal and then use the Convert Thermocouple Reading.vi to show the voltage as a temperature.
    Better: If you want to keep using the USB-6009 to measure thermocouple, what you really need to do is first amplify your signal before you connect it with your device.  This should increase your resolution of the thermocouple allowing you to get more accurate temperature specs.  This will require some more complex programming to properly scale your measurements, but it will give you more accurate readings for relatively little cost.
    Best: Opt for getting a USB device that is designed for taking temperature measurements such as the USB-9211A.  This device would give you a voltage resolution of 160mV/2^24 = 9.54 nV!  That's over 12500x the resolution of the USB-6009 that you currently have.
    Hopefully the above information helps you better understand what is going on and why.  If you have any other questions feel free to post them here.
    Message Edited by Otis [DE] on 01-13-2006 11:37 AM
    Message Edited by Otis [DE] on 01-13-2006 11:38 AM
    Otis
    Training and Certification
    Product Support Engineer
    National Instruments
    Attachments:
    761029-Thermocouple_Voltages.GIF ‏10 KB

  • USB-6009 labview 7.1

    Hi can anybody tell me if they have had any problems running USB-6009 with Labview version 7.0? I can't get it to recongnise my device and it's behaving as if there is nothing there. Do I need version 7.1 or is there a more sinister problem afoot?
    Kyle

    What version of DAQmx Base are you using? The latest version, 1.4, is supported on all versions of LabView 7.0 and higher. It can be obtained using the following link:
    http://digital.ni.com/softlib.nsf/websearch/941677622E793A2686256F8C0083641A?opendocument&node=132050_US

  • USB 6009 - Calibration of Analog Input (Mac)

    Hi,
    I have recently acquired a NI USB 6009. I'm using it under labview 7.1 on Mac OS X 10.4 (Tiger).
    I can run the software examples and the datalogger without problems. However, the device seems
    not to be properly calibrated, and I can't figure out how to do it from the manual. When I connect
    pin 1&2 (analog in 0) to pin 32 and 31 (GND and 5V ref voltage) the software claims that the
    measured voltage it ~3.7V (a multimeter confirms that it is in fact 5.0V). Can anyone help
    trouble shooting this ?
    Thank you in advance,
    Niels

    A little update : After thinking some more I realized that it's because
    the USB 6009 is in differential mode, and I hadn't connected one pin. Now
    however, I have trouble figuring out where to change/set this. None of
    the programs (e.q. Acquire One Voltage.vi) seems to define this, so where
    is this defined ?
    Thanks,
    Niels

  • USB 6009 Data Acquisitio​n noise

    When I acquire the voltage from USB 6009, It gives some fluctuation/Noise (Please check the image, green color).
    What is the reason for that?. How to overcome this noise? One way is averaging, is there any other ways to do or overcome this problem
    Could you please suggest me?
    Thank you,
    Best Regards,
    Rathan
    Attachments:
    Noise.GIF ‏16 KB

    Dear Rathan
    The correct Terminal configuration depends on if your power supply is floating or grounded. Please have a look at tabel below.
    As to the filter, which type of filter to use depends on the frequency of your signal. If your frequency (or frequencies) is low a lowpass with a cutoff frequency a bit over your frequency would be best. Conversly if your frequency is high a highpass with a lower cutoff frequency would do the job. If you are interested in only a single or small spann of frequencies a bandpass could be used.
    You can filter your signal either via a hardware filter before you acquire it via your DAQ, but that would require that you have or can build a hardware filter that fits your needs. Else you can filter the signal in software after you've aquired it. The filters in LabVIEW can be found in the functions palette under Signal Processing -> Filters. I think a butterworth filter would do nicely. You can find an example through the LV Help.
    Best Regards
    David
    Message Edited by DavidEk on 07-29-2009 05:03 AM
    Attachments:
    Connection Configs.PNG ‏66 KB

  • Usb 6009....mx base....and other musings

    I've recently received a few usb-6009 devices, and, like most of the other people here on the boards, have had my share of problems getting the things up and going.
    If I understand correctly....
    I can create an empty task in LabView with a VI.  This VI however doesn't give me the option of choosing differential or single ended analog in measurements.  To do this, I need to use the config utility to create a task, and then import it into my program. 
    What isn't clear is HOW I get the task I create in the config utility into my program.  Thoughts?
    I will admit that I'm a bit disappointed that the devices, while convienient in size and price, have so many idiosyncrasies in the software.  Not having the full arsenal of VI's or compatability with MAX makes getting these up and going a bit painful.
    Brandon

    Hi
    I've been trying to get a USB-6009 to work for a few days now. I was using DAQmx 7.4 and DAQmx Base v 1.4. Max Explorer would show the device  under USB Devices but I couldn't get any of the Tasks from the DAQmx Task Configuration Utility to show up in Labview. If I used the intermediate vi's to create a task and a physical channel name I did get to take measurements with the device.
    Since I realy needed to use global channels and tasks set up in Max Explorer I was hoping that the new upgrade to DAQmx 7.5 would solve the problem. I removed DAQmx Base and DAQmx 7.4 and loaded 7.5. Unfortunately I'm still unable to use the 6009 device. Again the device shows up in the USB devices and I'm now able to give it an alias but when I try to set up a global channel it says I have 'No supported devices found'. If I look at 'NI-DAQmx for USB Devices Getting Started' which I think was included with the 7.5 update that suggests that it should be seen in the DAQmx devices, but in my case it doesn't.
    I guess I've missed out some crutial stage but as yet I can't figure out what that might be. Has anyone been able to use the USB-6009 with DAQmx 7.5 (or v7.4 for that matter)?
    Ian S

  • Usb 6009 freeze

    Hi all,
    When using the USB 6009 interface for reading out two sensors (temperature and pressure, using the Voltage they generate) and sending signals to valves, my program keeps working.
    But after a while the USB module crashes.
    Most of the time both input and output don't seem to work anymore. I don't get any error, it just doesn't work anymore. When I pull out the USB device and insert it again in the USB port, it works again perfectly
    FYI (It happened once or twice that the outputs still worked, but I got no input from the devices.)
    Does anyone have similar problems or knows how to fix this?
    Thank you in advance.
    Regards,
    Bart
    Solved!
    Go to Solution.

    Here is the code.
    Attachments:
    Leakage_test_v1.1.vi ‏355 KB

  • USB 6009 DAQ to use in Simulink at External mode with DAQ toolbox

    hi
    Currently I am using usb 6009 daq board for data acquisition in using simulink. I have created a model with taking analog input from data acquisition toolbox. Then when i want to run in external mode and try to connet to target, the following error is coming up:
    Could not execute target data map file 'untitled_rtwin_win32\untitled_targ_data_map' or it does not exist. Stop the target, delete the untitled executable, rebuild the code,and try again. Note that execution of external mode requires the build directory to be present...
    How can I solve this problem? For your info, I am using 32-bit matlab, version: 2012a
    For your info, a snapshot of the error is attached,
    Any help would be appreciated Thanks
    Attachments:
    Untitled.jpg ‏130 KB

    Hi Mahmudur,
    what does MathWorks say about this error message?
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

Maybe you are looking for