USB-6009 vs Non-traditional (e.g. 6001, 6002) Multifunction DAQ

Similar Questions

• OR USB-6009: Examples NIDAQmxBase hang in Ubuntu 10.04.1

  Hello!

  I installed NIDAQmxBase in Ubuntu 10.04.1 Server according to the various instructions in this forum. After a lot of trial and error, I managed to get the NI USB 6009 recognized in lsdaq.

  --------------------------------
  Detecting National Instruments DAQ Devices
  Found the following DAQ Devices:
  NI USB-6009: "Dev1"    (USB0::0x3923::0x717B::01586A5A::RAW)
  --------------------------------
  

  However the examples hang.

  These are my core modules:

  arc4                    1153  2
  bitblit                 4707  1 fbcon
  cfg80211              126528  2 rt2x00lib,mac80211
  crc_ccitt               1339  1 rt2800usb
  fbcon                  35102  71
  font                    7557  1 fbcon
  i2c_isch                3375  0
  led_class               2864  2 rt2x00lib,sdhci
  lp                      7028  0
  mac80211              205402  2 rt2x00usb,rt2x00lib
  mii                     4381  1 r8169
  Module                  Size  Used by
  nidimk                322759  2 nipxirmk
  nikal                  57594  1 nipalk
  niorbk                 95647  2 nipxirmk,nidimk
  nipalk               1220783  6 NiViPciK,nipxirmk,nidimk,niorbk
  nipxirmk              115018  1
  NiViPciK               79087  0
  output                  1871  1 video
  parport                32635  1 lp
  pata_sch                1963  0
  psmouse                63245  0
  r8169                  34364  0
  rt2800usb              31531  0
  rt2870sta             461971  0
  rt2x00lib              27541  2 rt2800usb,rt2x00usb
  rt2x00usb               9703  1 rt2800usb
  sdhci                  15654  1 sdhci_pci
  sdhci_pci               5502  0
  serio_raw               3978  0
  snd                    54180  6 snd_hda_codec_idt,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
  snd_hda_codec          74201  2 snd_hda_codec_idt,snd_hda_intel
  snd_hda_codec_idt      51978  0
  snd_hda_intel          22101  0
  snd_hwdep               5412  1 snd_hda_codec
  snd_page_alloc          7172  2 snd_hda_intel,snd_pcm
  snd_pcm                70918  2 snd_hda_intel,snd_hda_codec
  snd_timer              19098  1 snd_pcm
  softcursor              1189  1 bitblit
  soundcore               6620  1 snd
  tileblit                2031  1 fbcon
  usb_storage            39585  2
  vga16fb                11385  1
  vgastate                8961  1 vga16fb
  video                  17375  0
  

  What are the processes running (for clarity I have included only processes whose name starts with or):

  1222 pts/0    00:00:00 nipalps
   1234 ?        00:00:00 niLxiDiscovery
   1242 ?        00:00:00 nimdnsResponder
   1248 ?        00:00:00 nipalsm
  

  These are neither installed packages:

  ii  nidaqmxbase-board-support       3.4.0-1                         NI-DAQmx Base Hardware Support
  ii  nidaqmxbase-cinterface          3.4.0-1                         NI-DAQmx Base API (C version)
  ii  nidaqmxbase-common              3.4.0-1                         NI-DAQmx Base Common Configuration Utilities
  ii  nidaqmxbase-labview2009-vis     3.4.0-1                         NI-DAQmx Base API (LabVIEW 2009 version)
  ii  nidaqmxbase-labview2010-vis     3.4.0-1                         NI-DAQmx Base API (LabVIEW 2010 version)
  ii  nidaqmxbase-labview85-vis       3.4.0-1                         NI-DAQmx Base API (LabVIEW 8.5 version)
  ii  nidaqmxbase-labview86-vis       3.4.0-1                         NI-DAQmx Base API (LabVIEW 8.6 version)
  ii  nidaqmxbase-usb-support         3.4.0-1                         NI-DAQmx Base USB Device Support
  ii  nidimi                          1.10.0-f0                       NI-DIM
  ii  nimdnsresponder                 1.1.0-f3                        National Instruments mDNS Responder Service
  ii  niorbi                          1.9.3-f0                        NI-ORB
  ii  nipxirmi                        1.6.0-f0                        NI-PXI Platform Services
  ii  nirpci                          4.2.0-f0                        NI-RPC user library
  un  nis                                                      (keine Beschreibung vorhanden)
  ii  nivisa                          5.0.0-f0                        NI-VISA Runtime Engine -- Abtraction layer for access to NI-488, PCI/PXI, USB,
  ii  nivisak                         5.0.0-f0                        NI-VISA Runtime Engine Kernel Support
  

  These are dependencies of the sample program:

  linux-gate.so.1 =>  (0xb78df000)
      libnidaqmxbase.so.3 => /usr/local/lib/libnidaqmxbase.so.3 (0xb78d2000)
      libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb78b3000)
      libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7758000)
      libnidaqmxbaselv.so => /usr/local/lib/libnidaqmxbaselv.so (0xb774e000)
      /lib/ld-linux.so.2 (0xb78e0000)
      liblvrtdark.so.10.0 => /usr/local/lib/liblvrtdark.so.10.0 (0xb6529000)
      libstdc++.so.6 => /usr/local/lib/LabVIEW-2010/patchlib/libstdc++.so.6 (0xb6447000)
      libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xb6421000)
      libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb641d000)
      libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb6404000)
  

  I would appreciate your help to find out what makes the examples hang.

  Because of the size limitations post I'll post my gbd debug session in the next post.

  Martin Jukel

  Martin Jukel wrote:

  That is why it seems to me that there is a problem starting, because with acquireNScans the elapsed real time 9,671 s longer then that time consumed user is only 0.904 s longer.

  Yes and there is a work around. Please see my post in another thread:

  libnipalu.so, failed to initialize

  http://forums.NI.com/T5/Multifunction-DAQ/libnipalu-so-failed-to-initialize/m-p/1282246#M60196

• Is it possible to install a usb-6009 Dasylab box?

  I need to install a usb-6009 case in Dasylab, but Dasylab not recogise daqmx devices, or what it looks like.

  MAX, I see I have traditional NI DAQ installed (7.4.2f3), but the usb devices are listed as daqmx devices.

  Is there a a way to deceive Dasylab seeing my device?

  I usually work in Labview, but now I need to replicate a measure of a colleague from Ethiopia and Dasylab is confusing at first.

  Wouldn't be easier to use a pci card (we pci 6220 available)?

  Max version4.3.0f0

  8.6.1f0 DAQmx

  traditional OR daq 7.4.2f3

  DASYLab 8.00.00 since 2004, old, I know)

  LabVIEW 8.2

  If you create a task OR-DAQmx with the device, DASYLab should see it.

  There is a download for the driver OR DAQmx for DASYLab 8.00.04 to www.dasylab.com

  http://DASYLab.com/content/driver.php?action=filelist&SID=33

  We can only provide active support for current versions of DASYLab (V11 and V10), therefore, it is not much of help available.

• Reduce the period of sampling of the digital inputs of NOR-USB-6009

  Hello

  I need to read a line of digital input in the NI USB-6009 using NOR Express 2013 Signal box. I selected 1 sample (upon request) as acquisition mode. I need to define a smaller sampling period as 1 MS, but it gives error too short sampling period: "the current sampling period is too short.  Please specify a longer sampling period. ».
  I do not understand the reason for it and a way to slove this.

  Any help would be greatly appreciated!

  Thank you!!

  The 6009 doesn't have a clock that you can set for a sampling period. According to the specifications, the digital I/o is software programmed - sample on request you use now. I'm not at all familiar with SignalExpress but I don't think that you can find near a reliable khz sampling frequency on Windows or any other os non-deterministic.

• Using the NI USB-6009 case to generate a 12VDC output and output current of 300mA

  Hello

  I use the OR-USB-6009 my power supply for a 12VDC with drive current of 300 solenoid my. Initially, I used a non reverse Op-amp circuit and Inverter circuit operational amplifier to get the + 12V and - 12V output but I could not get the current I required. Should I use a transistor?

  Please find attached photos. Any input would be appreciated.

  Thank you

  Adam

  Well, really depend on your piercing circuit.  But I used most systems use the transistor to set the voltage of the device to 0V.  So when your DIO is high, the output is actually 0V (low).  So using a converter chip, your release of the DIO will be sort of the output circuit.  If you get the right IC, then the inverter will give you also a few extra current to drive your transistor.

• USB-6009 not recognized after the blue screen of death

  I have two devices USB-6009, used with NOR-DAQmx and Labview to make some analogue simple analogue input and output.  The USB box - two 6009 were previously works very well on this PC.  Recently, I got a blue screen of death, associated with a different USB device to (non - OR) connected to the PC.  I not save the information of the blue screen of death.  When I restarted the computer, the USB-6009 devices were no longer recognized by Labview / MAX.  The Green LED on the USB - 6009 s do not come.  The USB - 6009 s appear in the Device Manager of Windows with a yellow exclamation point ("Windows cannot load the driver for this hardware device").  If I connect the USB-6009 case to another PC, MAX recognizes them on this PC, and I get the usual flashing green LED.  If I connect another USB-6009 (never connected to this PC), I get a green LED solid, and, says Windows cannot load the driver.

  I am running Vista, Labview 8.5 and NOR-DAQmx 8.9.  I rebooted 5 - 6 times, I tried disabling and the reactivation of the USB-6009 by windows Device Manager, I tried the options "update driver" in Device Manager.  Any advice on how else to solve it?  Thank you!

  The driver update and turn do nothing to the main driver - DAQmx. Reinstall or repair that.

• remove the casing usb-6009 floating voltage

  Hello

  I created a VI that records 6 6 different battery voltages, and everything is fine, until I disconnected a battery and it stills sees about 1.4 volts. How can I remove this offset (?)

  It is present on the readings connected?

  Concerning

  Steven

  The USB-6009 case has a non-standard input circuit which ends in ~1.4 V through the ~ 144000 ohms. Consult the manual for a schematic representation.

  As long as your source has a much lower than the 144000 ohms impedance and can sink current (if the source voltage)< 1.4v),="" then="" you="" should="" be="" ok.=""  batteries,="" even="" nearly="" discharged,="" should="" not="" be="" a="">

  Lynn

• USB-6009 stops working

  Hi all

  My apologies in advance if this has already been asked, but I couldn't find it in a search.

  USB - 6009 s allows us to measure an analog signal.  We recently bought the latest model of the laptop that we use, and with this new laptop model, we observe that the USB - 6009 s stop working after a short period of time (usually less than an hour) of data taking.  Although the down time is variable, once the USB-6009 case stops working, it does not work until we UN-plug/re-plug USB cable to the laptop.

  This behavior is compatible with the device is not enough power through USB?  Is there a way to check whether what is happening?  We wonder if the new laptops are not up to the task and will try a hub powered as an experiment.

  Thank you

  Bruce

  It seems therefore that the main cause of our problem was an old DAQmx.  We used v9.2.3

  I waited until the entered 6009 in the non-plus-acquisition mode and then tried to use a panel of Test able & Automation Explorer.  It gave me an error on buffer overruns.  When I checked the DAQmx (especially to v9.4and v9.6 ) release notes I found several fixes specific 6009 overruns buffer and compatibility with Windows 7-related, so I installed the last DAQmx, v9.9.

  Although I did successful tests, the problem that I saw seems to have disappeared after installing the latest version of DAQmx.

  Why this happens on our new laptops (Dell 5540) and not the old ones (Dell 5530) by using the same Windows image?  I don't know, but can only assume the old drivers OR don't play well with the new systems chipset/USB drivers.

  Thanks for all your help!

  Bruce

• USB-6009 + LabWindows

  Muy buenas:

  Tengo una targeta digital y Necesito UN that por esta targeta me salga por un menor peso bit 1 el y por el puerto 0. El he found a programa en OR sober cual me estoy basando para crear esta condition pero no programarlo problems can forma deseada. A c editor el programa para as the hecheis a look. MUCHAS gracias.

  Muy buenas:

  Estoy realizando el proyecto final of carrera. ESTOS momentos estoy trabajando con una targeta DAQ USB-6009 y en OR he found a programa me works very well don't put con ideas pero el problema what I have that none be como el puerto salida Québec. Targeta en TR works como entrada salida analogica digital o o y yo just need the part digital of the targeta. El programa Québec en he sown OR, as editor a c lo, me slightly para x values of entrada salida o y los puertos, y lo no puedo are to get there has the config of los puertos para as estos no varien. Alguien sabe como if is you can hacer Québec me heche a cable por favor? Gracias.

• Default settings for digital lines? USB-6009

  Hi all

  I use the digital lines on my USB-6009 to control normally open SSRs.  When I turn on the system, I would like to have the digital lines on the USB-6009 case to automatically configure themselves to be output digital lines put in position "Low", so I don't spend on my SSRs until I gave the command.  Is there a way to do this?

  Thank you.

  Cannot set default on 600 x Renault States, unfortunately.

  Do a genius on the hardware side, knowing the lines are pulled high on the acquisition of data is initialized. and if certain combinations of outputs produced a dangerous situation, you must stop to happen in hardware.  Good practice to do so anyway.

  Another option is to use an analog output, those can pump a little more power than otherwise to 1V, and do what is usually not sufficient to turn of SSRs.

• Simulate signals wired to the DAQ assistant for USB-6009 device

  Hello

  I'm trying to send a signal to the DAQ Assistant Express VI.  I watched the movie "Generating a Signal" on the Web site of NOR (www.ni.com/academic/students/learnlabview/generate.htm) and I have my Signal simulate connected directly on the DAQ Assistant, as shown in this film.  In my case, the DAQ Assistant sends the signal to a device USB-6009.

  However, I received this message:

  Error-200077 occurred to the DAQ Assistant
  Possible reasons:

  Requested value is not supported for this property value. The value of the property may be invalid because it is in conflict with another property.

  Property: SampTimingType
  asked the value: Sample clock
  You select: On-demand

  If I select 'On Demand' in my DAQ assistant and run the vi everything works beautifully.  However, I need my DAQ assistant to be configured to generate a waveform AC continuous, not output a single alternating current rippling.

  What happens here?  I did not have this problem before on other devices of NOR. I am using LABView 2010.

  Please answer.

  Thank you.

  double post

• OR USB-6009 and Tek TDS2024C comparesment

  My apologies if this topic was already discussed, but I searched through the forum and manuals and can't find anything.

  I have a problem with measurements in parallel with TDS2024C NI USB-6009 and Tek.

  I measured the noise high frequency on 10 s window.

  I used the data logger with a frequency of 40 kHz connection in parallel with TDS2024C (which reached 250 Hz on 10s window) and got very different results.

  On the attachment figure, first signal comes from screenshot of scope data and the second of the NI USB-6009 islogged.

  Can someone explain to me why are these so different results?

  Different sampling frequencies could easily explain it.  Try to run the USB-6009 case at the same rate as the scope and see what you get.  I also think that the TDS2024C has fewer bits in the ADC, which could also cause differences.

• With the help of MAX to configure digital input levels on a USB-6009

  Hello

  I use a USB-6009 box in a Windows environment. MAX allows me to configure the 8 bits in the port 0 as inputs or outputs. However, when I put the bits for all entries, their default level is high, and the "ALL LOW" button is grayed out. Is there a way I can turn this button to set the bits all low entry and therefore be configured to read a + 5V input pulse?

  Concerning

  Geoff Hammond

  When you set up the pins as inputs, you can read 0 or 5 volts. It makes no sense to set then high or low. No PIN disconnected feel of course a logic 1 because of pull-ups on the device.

• Current output digital USB-6009

  Hi, I'm trying to increase the voltage output digital device USB-6009. I read a few topics on the use of a relay, but I couldn't get it.

  I was thinking of using power 5V on the map because there current 200mA on it, but when I use it with open-collector output, it cannot change the relay. When I measure the current between

  5V and ground: 200 ma,

  5V output, I read a value around 30-40 my.

  Why can I not use this 200mA with output? It is the Relay that I use.

  If this is not possible, can I use an external power supply 5V (with more current) and a digital output to pass the baton without damage the 6009?

  Outputs digital of the USB-6009 confined to 8.5 my. Your relay coli requires much more than that. Even if the power source can provide enough current for the relay, digital output can not put.

  The solution is to use a buffer of extermal. The ULN2003 can switch currents up to 500 my and voltage up to 50 V while being controlled by digital output.

  Lynn

• Methods of protection for NI USB-6009

  Hello

  I developed a tester to measure 8 outputs varies between 1-5 V to a power supply Board. But suddenly the meter 6009 got damaged since the problems with rectifier circuits of UUT that caused the volt of entry (230 v AC) to reach the limits of measurement.

  Could someone help me to design/introduce certain protection measures between USE and DAQ unit to avoid happening again?

  It would be really helpful for me if I can solve this problem before the transfer of the tester at the end of production.

  Thank you.

  The USB-6009 is supposed to be a bottom of the line test solution and is not really designed for quality of production systems. As you have discovered, it doesn't have its own internal protection products OR more expensive. I used it before production systems and I killed one like you did it (a week before delivery, no less).

  My only advice is to make sure that all of your grounds are connected and your system is melted, but there is not a lot you can do other than that. Maybe an EE here can provide more wisdom.