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.

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....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 digital input

Dear All!!
With the following vi. I'm trying to receive a 5V signal in a digital input, using a usb-6009 device.
I would like to use the 5 VCC supply, available in pin 31 of the same device and send it to pin 17, representing line0 of port0. During execution, 'm physically connecting and disconnecting these pins in order to see the difference in a led indicator. Unfortunatelly, the led is always on, even if both pins are disconnected.
Could somebody help me? I would be very pleased.
Thank you very much in advance,
Miren
Attachments:
proof.vi ‏38 KB

Hi Miren,
"the led is always on, even if both pins are disconnected"
RTFM?!
They use open collector inputs with an internal pullup resistor of 4.7k, so you actively have to pull down the input to GND to see a difference...
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

USB-6009 digital input change detection

Hi,
I am trying to acquire digital signals from an ni usb-6009 device using daqmx on labview 8.0. I need to write the signals from a port of the device to an output file only when there is a change in the signals and I am not able to do this successfully. I created a digital task in MAX and was able to select acquisition mode as '1 sample (On Demand) ' only. Any other selection for acquisition mode would result in error 200077 with the following message -
Measurements: Requested value is not a supported value for this property.
Property: SampTimingType
You Have Requested: Sample Clock
You Can Select: On Demand
I selected '1 Sample (On Demand)' acquisition mode and was able to see the channel values on running it in MAX as I rotated a device connected to the usb-6009 device. As expected the hex values on MAX were showing up as FF,7F,3F,BF and this pattern was repeated everytime I provided the input by rotating the device.
Next, I created a simple vi to use the digital task I setup on MAX. I want to be able to record the signals only when there is a change in the digital pattern from the channels.That is when there is atransition from FF to 7F to 3F and so on, the vi should write to an output file and if no change happens, it should not write to file. To do this, I explored the Timing vi and tried using the 'Change detection' mode, but that produced the same error as above.
Can anyone please suggest a way to accomplish what I am trying to do ? Any guidance will be a hugely appreciated.
Thanks
~Sej

All of that effort with sample rates, timing, change detection, etc ciuld have been avoided if you had read the specs. As you finally found out, the device only supports sftware timed i/o and no change detection. You wll have to do your change detection in software this is done with a shift register/feedback loop.

USB-6009 Analog Waveform Output

I'm trying to create an analog waveform from a USB-6009 device through one of the analog output channels. However, through the DAQ Assistant, I can only select the 1 Sample (On Demand) setting. When I test the device, I can only push a constant voltage out. If anyone has any advice on how to create an analog voltage waveform using this device, I would like to know.

>I am only a novice at LabVIEW and data acquisition in general.
I don't use Labview (I write in C++) so I can't help you with that. I try to answer questions about C/C++ and general hardware questions.
>What did you mean by software-timed waveform generation?
That's where the software driving the device sends a sample to the DAQ device, waits for the prescribed time interval, then sends the next sample. So the timing of the waveform is driven by the software, using the computer's clock, instead of by the DAQ hardware. Software-timed is less reliable and has (often) lots more jitter because of competition for CPU resources.
>Does this mean that I cannot generate a waveform that is more than 150 Hz?
It's worse than that. It means you can't generate a waveform faster than 150/N Hz, where N is the number of samples (data points) that define the waveform.
John Weeks
WaveMetrics, Inc.
Phone (503) 620-3001
Fax (503) 620-6754
www.wavemetrics.com

USB-6009 Digital Output Current

You need to have all those grounds connected together - USB-6009 Digital Ground, ULN2003 GND, and the power supply ground. In this case it will not matter how they are connected. If they are not connected, then one of the devices could be damaged.
Lynn

Hi, I'm trying to increase the voltage of the digital outputs of USB-6009 device. I read a couple topics about using a relay but I could not manage it.
I was thinking to use 5V supply on the card since it has 200mA current on it, but when I use it with open-collector output, it can not switch the relay. When I measure the current between
5V and ground: 200mA,
5V and output, I read a value around 30-40 mA.
Why can't I use that 200mA with an output? This is the relay I'm using.
If this is not possible, can I use an external 5V supply (with more current) and a digital output to switch the relay without damage the 6009?

Usb 6009 output changes

Hi, I'm using a NI USB 6009 device. I am using the analog output to drive very small currents (less than 1 micro Amp) through a 1 MOhm resistor. I find that the output often changes significantly when I begin to acquire data, or if the computer is doing something, such as fitting data, or even if I am simply opening other files or programs. Any advice?
Thanks!
Micah

Hi, thanks for the responses.
I'm outputing a DC voltage with values typically ranging from 0.1 V to 1 V. The signal goes through a 1 MOhm resistor in series with a coil for producing very small magnetic fields applied to an atomic magnetometer. It appears that the output changes by tens of millivolts, as recorded by a yokogawa oscilloscope with input impedance of 1 MOhm. The coil and scope are both grounded. I am using only a single input channel on the USB6009, coming from an SRS voltage preamp with output impedance of 50 Ohms
I can also infer that there are changes in the current when the computer "does something" by looking at the signal in the atomic magnetometer.
Perhaps it would help if I shunted the output with some smaller resistor, say 10kOhm?
I will look at the document you mentioned.
Thanks again.

USB 6009 and TDMS write

Dear all!
I'm using USB-6009 device to adquire data from a physical channel. In the following vi, the number of samples to be adquired is set to 1000, with a 100Hz rate. Therefore, as I understand, the number of samples that should be read inside the while loop where DAQmx read is placed should be 10 for each iteration. However, I've tried to store this information in a TDMS file and I'm getting less number of samples as expected. I wouldn't like to lose any data.
I've read overthere that the USB-6009 is a software-timed device, so, can this be the reason of this anomaly? Moreover, if I analyze the adquired samples using DIAdem software, I see some samples are being repeated. In this case, am I overwriting some data and reading past values?
If I need to replace my data adquisition device with a hardware-timed one, which one should I get?
Thank you very much in advance,
Miren
Attachments:
USB6009_TDMS.vi ‏25 KB

When you run the sample clock in "Continuous Samples" mode, the # of samples only determines the buffer size. This is outlined in the help for that function.
As a result, you have nothing pacing the internal loop: If there are samples available when it reaches the DAQmx Read, it passes out as many as are available in the buffer. You might get 1, 2, 100; it depends on how long the other operations in the loop take.
In general, DAQmx loops like this can be paced either by time or by # of samples. Looks like you want sample pacing: wire the number of samples you want to collect to the "# of samples per channel" input of the DAQmx read. Then the loop will wait at the daqmx read until that many samples are ready, and then it will proceed.
-Barrett
CLD

How do I set up a triggered analog output on a USB 6009?

Hi! I am very new to LabView and am working on the control portion of my senior ME design project. It is an anti-tip brake system for a bicycle. The goal is: When critical time to tip is reached (by reading values from a rear wheel normal force sensor, taking the derivative and calculating this critical time), my cheap DAQ USB-6009 device will put out an analog signal to a transistor, which will spin a DC motor (attached to a worm gear setup) for a certain length of time (...This will change a pivot location in the mechanical assembly which will decrease brake mechanical advantage).
I have been trying to work with LabView 8.5. I get bogged down in confusion when I try to use G-code and get unexplained errors in using Express VI's (they're rather black box-ish to me).
I think that all I need to do is set up an analog input channel, take derivatives and values and put them into a formula for critical time. Then if the result is a "True", I want to begin an analog out sequence for a certain period of time (to get the motor to the right position).
I would appreciate any help that I can get with this one.
Attachments:
ABScontrol1.JPG ‏43 KB

chowph,
You are
correct with your last statement about performing a comparison on your data.
1. Are there any error codes or messages in the
errors you are getting? Or if you have screenshots of the errors you could post
then that would work too. Knowing the
errors would help in understanding where to start.
2. In your previous
post did you have a chance to try the examples or Kent’s example code he
posted?
3. What were the results of those examples and
your experiment? Again screenshots would
work fine here.
Since you
new to LabVIEW make sure to take advantage of the online training material and
tutorials we have on ni.com. I have posted
a few that I think may be helpful.
Learn 10 Functions in
NI-DAQmx and Handle 80 Percent of Your Data Acquisition Applications
Complete Data Acquisition
Tutorial
How Can I Learn
LabVIEW?
I hope this helps!!
Message Edited by Ryan N. on 03-31-2008 11:52 AM
Ryan N
National Instruments
Application Engineer
ni.com/support

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

Problems with creating a USB boot device for Windows 8.1

My iMac (late 2012) running OSX Mavericks is encountering problems creating a Windows 8.1 install disk via a USB thumbdrive. The drive has 8gb of space available, which is enough to fit windows. But when I choose my ISO image and select the drive I recieve an error message. The error is 'Bootcamp only supports 64-bit Windows installation on this platform. Please use a ISO file for 64-bit Windows installation.
I'm certain this ISO definately contains 64-bit, so I'm slightly confused.
I've followed instructions found in other discussions talking about adding an extra line of information to 'info.plist' found inside the Package Contents for bootcamp, but that has also not worked. If I try that, Bootcamp crashes upon being clicked every time.
Any help is appreciated

First up: a question. How did you fix the crashing Bootcamp Utility? It would help out this guy: https://discussions.apple.com/message/23523783?ac_cid=tw123456#23523783
Next up: A possible solution (also posted here:https://discussions.apple.com/message/23523783?ac_cid=tw123456#23523783)
=====================
It's possible you have a Windows ISO for both 32- and 64-bit. In this case it's probably detecting the presence of the 32-bit installer and forgets to look for another 64-bit version.
A way to work around this is to not use the Bootcamp Assistant utility by following the listed steps:
The way installing Windows should work either way using the Legacy BIOS mode:
- Get a Windows ISO or DVD and copy the contents over to a freshly fat32 formatted USB stick of at least 4GB.
- Download the Apple Bootcamp Support Software (4.x or 5.x, 5.x only supports 64-bit, get that if you are going 64-bit);
- Copy the content of the Support Software folder over the the same USB stick from the first step. It should fit just right (it did on my 4GB stick with 2MB te spare!);
- Use disk utility to partition your disk. Make sure the partition for Windows is Fat32 and at least 30GB;
- Reboot your machine while holding Option/Alt at the chime;
- You should be able to select either your OSX HDD or your USB stick labeled "Windows" -> Select Windows and press enter or click the arrow;
- The Windows installer should now load, format the previously made Windows partition to NTFS;
- Continue on your way.
Can you try what I typed above? If it doesn't work, can you let me know at what step things go differently than described?
Edit: This is based on the logical conclusion that any Mac that was shipped without ODD should be able to boot from USB.
Edit2:
One other note is that Mac's have trouble booting from USB when multiple USB storage devices are attached. So make sure you connect only one storage device.
=====================
Best of luck to you!

[solved] USB storage devices problem

Hello everyone. I have MSI Wind U270 and recently I've moved from Ubuntu 11.04 to Arch. I really like Arch so far but I have one quite big problem and I can't find any solution, so I hope someone here could help me.
After I'd installed Arch, I tried to copy some file from/to USB flash drive. After just few seconds, transfer failed with information about I/O errors and USB flash drive disappeared along with any other USB drives connected at the same time but logitech usb mouse and keyboard continue to work.
My first thought was that it's simply broken USB drive, but same thing was happening also when I tried to move some files from/to any other USB storage device that I have.
Here is sample dmesg output after I connect device:
[ 4799.189720] usb 1-2: new high-speed USB device number 4 using ehci_hcd
[ 4799.369911] xhci_hcd 0000:06:00.0: PME# disabled
[ 4799.369935] xhci_hcd 0000:06:00.0: setting latency timer to 64
[ 4799.399707] ehci_hcd 0000:00:13.2: BAR 0: set to [mem 0xfeb48000-0xfeb480ff] (PCI address [0xfeb48000-0xfeb480ff])
[ 4799.399754] ehci_hcd 0000:00:13.2: restoring config space at offset 0x1 (was 0x2b00000, writing 0x2b00013)
[ 4799.399800] ehci_hcd 0000:00:13.2: PME# disabled
[ 4799.399819] ehci_hcd 0000:00:13.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[ 4799.426731] ohci_hcd 0000:00:12.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 4799.520213] ohci_hcd 0000:00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 4799.690262] usbcore: registered new interface driver uas
[ 4799.704107] Initializing USB Mass Storage driver...
[ 4799.704420] scsi7 : usb-storage 1-2:1.0
[ 4799.704959] usbcore: registered new interface driver usb-storage
[ 4799.704966] USB Mass Storage support registered.
[ 4801.166512] scsi 7:0:0:0: Direct-Access JetFlash Transcend 8GB 1100 PQ: 0 ANSI: 0 CCS
[ 4801.168550] sd 7:0:0:0: [sdc] 15826944 512-byte logical blocks: (8.10 GB/7.54 GiB)
[ 4801.169401] sd 7:0:0:0: [sdc] Write Protect is off
[ 4801.169411] sd 7:0:0:0: [sdc] Mode Sense: 43 00 00 00
[ 4801.170332] sd 7:0:0:0: [sdc] No Caching mode page present
[ 4801.170340] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 4801.175736] sd 7:0:0:0: [sdc] No Caching mode page present
[ 4801.175747] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 4801.176962] sdc: sdc1
[ 4801.181454] sd 7:0:0:0: [sdc] No Caching mode page present
[ 4801.181465] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 4801.181471] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[ 4801.388155] xhci_hcd 0000:06:00.0: PME# enabled
[ 4801.439601] ehci_hcd 0000:00:13.2: PCI INT B disabled
[ 4801.439657] ehci_hcd 0000:00:13.2: PME# enabled
[ 4801.519628] ohci_hcd 0000:00:12.0: PCI INT A disabled
[ 4802.346484] ohci_hcd 0000:00:13.0: PCI INT A disabled
and when I start to copy some things to/from USB device this is what's happening:
[ 4981.389262] ehci_hcd 0000:00:12.2: force halt; handshake ffffc90000c1e024 00004000 00000000 -> -110
[ 4981.389271] ehci_hcd 0000:00:12.2: HC died; cleaning up
[ 4981.389377] usb 1-2: USB disconnect, device number 4
[ 4981.399810] sd 7:0:0:0: [sdc] Unhandled error code
[ 4981.399820] sd 7:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
[ 4981.399826] sd 7:0:0:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 1f b4 7e 00 00 08 00
[ 4981.399840] end_request: I/O error, dev sdc, sector 2077822
[ 4981.399850] Buffer I/O error on device sdc1, logical block 259720
[ 4981.399854] lost page write due to I/O error on sdc1
[ 4981.404451] sd 7:0:0:0: [sdc] Unhandled error code
[ 4981.404461] sd 7:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
[ 4981.404467] sd 7:0:0:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 20 34 7e 00 00 f0 00
[ 4981.404481] end_request: I/O error, dev sdc, sector 2110590
[ 4981.404489] Buffer I/O error on device sdc1, logical block 263816
[ 4981.404493] lost page write due to I/O error on sdc1
[ 4981.404500] Buffer I/O error on device sdc1, logical block 263817
[ 4981.404504] lost page write due to I/O error on sdc1
[ 4981.404509] Buffer I/O error on device sdc1, logical block 263818
[ 4981.404512] lost page write due to I/O error on sdc1
[ 4981.404517] Buffer I/O error on device sdc1, logical block 263819
[ 4981.404521] lost page write due to I/O error on sdc1
[ 4981.404525] Buffer I/O error on device sdc1, logical block 263820
[ 4981.404529] lost page write due to I/O error on sdc1
[ 4981.404534] Buffer I/O error on device sdc1, logical block 263821
[ 4981.404537] lost page write due to I/O error on sdc1
[ 4981.404543] Buffer I/O error on device sdc1, logical block 263822
[ 4981.404546] lost page write due to I/O error on sdc1
[ 4981.404550] Buffer I/O error on device sdc1, logical block 263823
[ 4981.404554] lost page write due to I/O error on sdc1
[ 4981.444899] usb 1-4: USB disconnect, device number 3
Next I thought – computer is broken. But it simply couldn't be true because in Ubuntu it's working.
I wanted to test if USB transfer is working in other distros, so I downloaded few and tried:
Ubuntu 11.04 – everything is working
Ubuntu 11.10 – it's not working, exactly same errors as in Arch
Ubuntu 12.04 Alpha 2 – it's not working
Mint 11 – it's working
Mint 12 – it's not working
So one thing in common that I can think of is fact that USB transfer is working in distros using kernel <3.0 and is broken in those using kernel >=3.0.
In dmesg output I can see ehci_hcd errors. When I remove this module before moving files, than everything is working fine apart from very slow transfer but it's obvious.
I really hope that someone will be able to help with my problem. I don't know if it's some bug or it's just some configuration error.
EDIT: problems were caused by rts5139 module (card reader). Blacklisting that module solved all the problems.
Last edited by wpb (2012-07-01 08:37:02)

Ok, so here is part of /var/log/messages.log with failed USB transfer:
Feb 28 20:21:40 localhost kernel: [ 117.263584] usb 3-2: new high-speed USB device number 4 using ehci_hcd
Feb 28 20:21:40 localhost mtp-probe: checking bus 3, device 4: "/sys/devices/pci0000:00/0000:00:12.2/usb3/3-2"
Feb 28 20:21:40 localhost kernel: [ 117.470130] ehci_hcd 0000:00:13.2: BAR 0: set to [mem 0xfeb48000-0xfeb480ff] (PCI address [0xfeb48000-0xfeb480ff])
Feb 28 20:21:40 localhost kernel: [ 117.470251] ehci_hcd 0000:00:13.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Feb 28 20:21:40 localhost kernel: [ 117.546266] ohci_hcd 0000:00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
Feb 28 20:21:40 localhost mtp-probe: bus: 3, device: 4 was not an MTP device
Feb 28 20:21:42 localhost kernel: [ 119.687034] usbcore: registered new interface driver uas
Feb 28 20:21:42 localhost kernel: [ 119.692675] Initializing USB Mass Storage driver...
Feb 28 20:21:42 localhost kernel: [ 119.693029] scsi7 : usb-storage 3-2:1.0
Feb 28 20:21:42 localhost kernel: [ 119.694285] usbcore: registered new interface driver usb-storage
Feb 28 20:21:42 localhost kernel: [ 119.694294] USB Mass Storage support registered.
Feb 28 20:21:43 localhost kernel: [ 120.353657] ohci_hcd 0000:00:13.0: PCI INT A disabled
Feb 28 20:21:43 localhost kernel: [ 121.110815] scsi 7:0:0:0: Direct-Access JetFlash Transcend 8GB 1100 PQ: 0 ANSI: 0 CCS
Feb 28 20:21:43 localhost kernel: [ 121.115125] sd 7:0:0:0: [sdc] 15826944 512-byte logical blocks: (8.10 GB/7.54 GiB)
Feb 28 20:21:43 localhost kernel: [ 121.117132] sd 7:0:0:0: [sdc] Write Protect is off
Feb 28 20:21:43 localhost kernel: [ 121.125243] sdc: sdc1
Feb 28 20:21:43 localhost kernel: [ 121.130244] sd 7:0:0:0: [sdc] Attached SCSI removable disk
Feb 28 20:21:44 localhost kernel: [ 121.570240] ehci_hcd 0000:00:13.2: PCI INT B disabled
Feb 28 20:21:44 localhost ntfs-3g[1936]: Version 2012.1.15 external FUSE 28
Feb 28 20:21:44 localhost ntfs-3g[1936]: Mounted /dev/sdc1 (Read-Write, label "", NTFS 3.1)
Feb 28 20:21:44 localhost ntfs-3g[1936]: Cmdline options: rw,nosuid,nodev,uhelper=udisks,uid=1000,gid=1000,dmask=0077,fmask=0177
Feb 28 20:21:44 localhost ntfs-3g[1936]: Mount options: rw,nosuid,nodev,uhelper=udisks,allow_other,nonempty,relatime,fsname=/dev/sdc1,blkdev,blksize=4096,default_permissions
Feb 28 20:21:44 localhost ntfs-3g[1936]: Global ownership and permissions enforced, configuration type 1
Feb 28 20:22:11 localhost kernel: [ 148.692914] usb 3-2: USB disconnect, device number 4
Feb 28 20:22:11 localhost kernel: [ 148.756937] sd 7:0:0:0: [sdc] Unhandled error code
Feb 28 20:22:11 localhost kernel: [ 148.756947] sd 7:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
Feb 28 20:22:11 localhost kernel: [ 148.756954] sd 7:0:0:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 1e 2f f6 00 00 18 00
Feb 28 20:22:11 localhost kernel: [ 148.756983] lost page write due to I/O error on sdc1
Feb 28 20:22:11 localhost kernel: [ 148.757000] lost page write due to I/O error on sdc1
Feb 28 20:22:11 localhost kernel: [ 148.757016] lost page write due to I/O error on sdc1
Feb 28 20:22:11 localhost kernel: [ 148.761894] sd 7:0:0:0: [sdc] Unhandled error code
Feb 28 20:22:11 localhost kernel: [ 148.761905] sd 7:0:0:0: [sdc] Result: hostbyte=0x01 driverbyte=0x00
Feb 28 20:22:11 localhost kernel: [ 148.761911] sd 7:0:0:0: [sdc] CDB: cdb[0]=0x2a: 2a 00 00 1e 2f ae 00 00 08 00
Feb 28 20:22:11 localhost kernel: [ 148.761939] lost page write due to I/O error on sdc1
Feb 28 20:22:11 localhost kernel: [ 148.914173] usb 3-4: USB disconnect, device number 3
Feb 28 20:22:24 localhost ntfs-3g[1936]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Feb 28 20:22:24 localhost ntfs-3g[1936]: Reading $BITMAP failed: Input/output error
Feb 28 20:22:24 localhost ntfs-3g[1936]: Failed to allocate clusters: Input/output error
Feb 28 20:22:24 localhost kernel: [ 161.862408] quiet_error: 2 callbacks suppressed
Feb 28 20:22:24 localhost kernel: [ 161.862424] lost page write due to I/O error on sdc1
Feb 28 20:22:24 localhost kernel: [ 161.862436] lost page write due to I/O error on sdc1
Feb 28 20:22:24 localhost kernel: [ 161.862446] lost page write due to I/O error on sdc1
Feb 28 20:22:24 localhost kernel: [ 161.862457] lost page write due to I/O error on sdc1
Feb 28 20:22:24 localhost kernel: [ 161.862466] lost page write due to I/O error on sdc1
Feb 28 20:22:24 localhost kernel: [ 161.862476] lost page write due to I/O error on sdc1
Feb 28 20:22:24 localhost kernel: [ 161.862485] lost page write due to I/O error on sdc1
Feb 28 20:22:24 localhost kernel: [ 161.862495] lost page write due to I/O error on sdc1
Feb 28 20:22:24 localhost kernel: [ 161.862505] lost page write due to I/O error on sdc1
Feb 28 20:22:24 localhost kernel: [ 161.862514] lost page write due to I/O error on sdc1
Feb 28 20:22:24 localhost ntfs-3g[1936]: Unmounting /dev/sdc1 ()
and here is complete /var/log/messages.log - I just started system and then tried to copy some files to USB drive:

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

Problem with two USB-gaming devices

I have a weird problem on the K8T Neo FIS2R. I have two USB gaming devices plugged in (Saitek X45, Thrustmaster Force Feedback GT). The Saitek is "on" every time since it does not have an external poer supply. The Thrustmaster I have to turn on, since it has Force Feedback. Both of these devices work perfectly when the othe one is inactive (Thrustmaster in off-position or X45 unplugged). But if I want to use the wheel with the X45 plugged in it just does not work right. If I check under the windows devices both of them work fine. But when it comes to ingame action the wheel is al f***** up. It seems, that the X45-axis is colliding with the wheel. I was using this combo on my former nForce2 board without any problems. Any clues?

Hi
Quote
it's almost as if a certain % of these boards have usb problems and half don't :(
Well then, lets find out which USB drivers are being used
The XP original 1.1
The XP updated 2
or the VIA driver from Companion CD.
Are they all on same Bios?
If Ports are reacting differantly, it is more likely to be a driver or Bios issue
Cheers
jocko

Usb - 6009 Device Recongition Problems

Similar Messages

Maybe you are looking for