Usb 6259

Hola,
Estoy trabajando con esta targeta de adquisición de datos y me gustaria saber si se pueden utilizar dos salidas analogicas a la vez. Es que lo intento pero siempre me sale el error 50103, alguien sabe que es lo que hago mal.
Gracias

Buenos días Bigalisco.
El error 50103 se produce cuando intentas a acceder al mismo recurso desde dos o más lugares a la vez. En este documento probablemente encontrarás la solución. Para otra vez, adjuntando tu VI sería más fácil saber donde está el error.
http://digital.ni.com/public.nsf/allkb/007B07166D9D2EBF862573ED00047B9D?OpenDocument
Un saludo,
Angel Marin
National Instruments
Applications Engineering
www.ni.com/support

Similar Messages

16 channels of data at 30kHz on the NI USB-6259 - is it possible?

Hello -- I would like to use the NI USB-6259 for electrophysiology. My application requires 16 channels of analog input digitized at 30kHz. This should be possible, as the listed aggregate digitization rate is 1MS/s. I've however run into several problems, all of which I believe may deal with how memory is handled in LabView (or maybe I'm just programming it wrong).
First off, if I pull in continuous voltage input using the DAQ assistant (DAQA) from anywhere from 5k to 30k samples at a time -- without any visualization -- things run alright. I record the data in binary format (TDMS) using the "Write to Measurement File (WTMF)" routine. However, I notice that the RAM used by LabView creeps up at a steady pace, roughly a megabyte every several seconds. This makes long-term recording unfeasible. Is there any way to avoid this? Basically I just have the DAQA and WTMF in a while loop that was automatically created when I set the acquisition mode to continuous.
Secondly, I would like to be able to visualize my data as I record it. If I set up 16 graphs -- one for each signal -- I need to raise the "Samples to Read" (STR) to 30k to ensure that the "Attempted to read samples that are no longer available" error [-200279]. This is annoying, as it makes the display look jerky, but is probably livable.
Now if I choose to display data in 16 charts rather than graphs (charts, as defined in LabView, display a bit of cumulative data along with the real-time signal), the amount of RAM used by LabView increases by several megabytes a second, regardless of whether or not I'm saving the data. After a short time, I get an "out of memory error".
Ideally I would like to be able to display 16 channels of 30kHz analog voltage data and save the data. As you see I'm having some level of trouble doing either of these things. Bare minimum requirements for my application would be to pull in the data with an STR of 30k, visualize the data in graphs, and save the data. Should this be possible in LabView 8.6 or 2009 (I use 8.6, but have tried these steps on the trial version of 2009 as well)? Even better, I would like to use an STR closer to 5k, and display the data in charts as it's saved. Should this be possible?
I'm using a reasonably powerful machine -- 32-bit Windows 7 with 3.24 gigs RAM, 2.4 GHz quad-core, etc.
Thanks

Hello!
I will admit right now that I can't stand any of the "assistants" and never use them. I don't like to have any part of my code invisible from me. Therefore, looking at your code gave me a headache. :-)
So, what I did is rewrite your code using the DAQ functions (basically what you'd see if you selected "Open Front Panel" on the DAQ assistant icon). You can go in and put the DAQ assistant back in if you so desire. This is just to give you an idea of the approach you should take. I'm grabbing 15000 points per loop iteration, just because I happen to like 500msec loop rates. You can tailor this number to your needs.
I have two parallel loops -- one collects the data and the other displays it on the front panel and writes it to a file. (I used the "Write waveform to file" function -- you can put your assistant back in there instead if you like.) The data is passed from the DAQ loop to the display loop using a queue. I use the "index array" function to select out the individual channels of data for display. I show 3 channels here, but you can easily expand that to accommodate all 16. You can also add your filtering, etc.
I am using a notifier to stop the two loops with a single button, or in case of an error. If "stop" is pressed, or an error occurs in the DAQ loop, a "T" value is sent to the notifier in the display loop (and that "T" value is used to stop the DAQ loop as well). That will cause the display loop to receive a "T" value, which will cause it to stop.
I don't have a 6259 on hand, so I simulated one in MAX. I didn't have a problem with the processor running at 100% -- on my clunky old laptop here, the processor typically showed ~40-50% usage.
I've added comments to the code to help you understand what I'm doing here. I hope this helps!
d
P.S. I have a question...how are you currently stopping your loop? You have "continuous samples" selected, and no stop button.
Message Edited by DianeS on 12-30-2009 07:28 PM
Attachments:
16 channel waveform display and write.vi ‏31 KB

How do I connect my NI USB-6259 properly to SCXI?

I have
a NI USB-6259 DAQ Module
a SCXI-1001 Chassis
3 SCXI-1143 8 Channel Low Pass Filter Modules
and
a SCXI-1180 Front End Plate
I use a SH68-68-EPM Cable for Connecting the USB-6259(Connector 0) to a SCXI-1349.
Is it wise to use another Cable to connect Connector 1 of the USB-6529 to a SCXI-1349 mounted on the same chassis to get parallel operation?
Can I detect with my USB Module all 24(3x 8 Channel Lowpass) in Single Ended Operation with only one cable?
Thank you,
Alex

Hi Alex,
I'm sorry you had to wait for an answer for quite a long time.
To be honest, I don't really get your question.
One AI Input for the Cable on the USB 6259 has the range for 16 Signals.
So you can't send 24 Signals in one cable, as long as you don't add the signals in diferrent frequencies
and seperate them afterwards programatically..
But if you just want to get the Signal in the normal way you would need 2 cables for that.
Regards

Questions around calibration for USB-6259

Hi,
I
would like to do current measurements with the NI USB-6289 and NI USB-6259. I have several different boards to measure with low resistance resistors on them.
In my
understanding there are three calibration processes:
1) One done
by NI every two year
2) The automated
self calibration process done in the measurement and automation explorer.
3) And the
setup calibration done in the DAQ assistant where you must specify the
range used and calibrate the setup at several operating points.
Questions:
Can we
record the current calibration 3) into a file and reload it afterward by selecting the file with labview? (The
goal is to have one calibration file per device I want to measure)
Do we/can we
calibrate 3) for every range?
I am
not clear how to link the product specification accuracy with the DAQ
assistant calibration process: For instance what is the current drain
accuracy when using the 0.1V -01.V range and using a 1% 0.1ohm resistor
before and after DAQ assistant calibration? (same question for both NI USB-6289 and NI USB-6259).
Thanks in advance for your help
Best regards,
Jean-Marc

Hello,
I'm not an expert in calibration, but in regard to what you are trying to do I think you should take a look at this soft : Claibration Executive which allows you to manage calibration files.
Regards
Richard Keromen
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Découvrez, en vidéo, les innovations technologiques réalisées en éco-conception

Error - 200609 USB 6259

Hola estoy construyendo un VI para probar una planta lo importante es que yo necesito hacer un control PID para ello utilizo la DAQ USB-6259 en Labview 8.2 para Windows XP pero no me sale siempre me manda error 200609 o otros tengo el problema con tamaños de bufer que segun eso es pero no entiendo nada ya me arte, bueno yo quiero usar la DAQ en modo Continuo y tengo usando dos asistentes para in y out como le puedo hacer para que ya pueda ver mis datos.y que tantas muestras y frecuencia debo de poner por que ya probe con muchos valores y nada
Attachments:
escalon.vi ‏158 KB

Que tal Daniel;
El error 200609 normalmente sucede cuando el tamaño del buffer creado es muy pequeño, puedes realizar cambios programáticos en el buffer con los VIs avanzados de DAQ, te envío la liga a un documento que explica más a fondo como utilizarlo.
http://digital.ni.com/public.nsf/websearch/E1E67695E76BA75B86256DB1004E9B07?OpenDocument
Espero que la información te sea de ayuda.
Suerte
Francisco Arellano
National Instruments Mexico
Field Systems Engineer - Energy Segment
www.ni.com/soporte

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

Data aqusition of Vac with usb-6259

1.I am having problems with meaqsuring AC signal 400 hz. THe reading is juping all the time. When I conect a normal voltmeter every thing is ok.
2. I am having problem with reading of data flow from rvdt again the same problem. How can I buld a software signal conditioner or I need hardware one
our device is usb-6259.
Attachments:
153271.vi ‏2995 KB

Comparing DAQ readings with a meter can be tricky for a lot of reasons. To begin with, what is your sample rate and period? Because the signal you're reading is an AC source it's level is constantly varying (at a 400 Hz rate ). Hence, you need to sample enough of a waveform that you can calculate the appropriate AC parameter (peak-to-peak, RMS, or what have you).
Also remember that meters always have a certain amount of built-in hysteresis or dampening to make the output easier to read.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Le nom des ports de Ni USB-6259 afin de les implémenter en Cpp

bonjour je veux bien savoir le nom des Port Ni USB-6259 afin de parvenir à manipuler le materiel à l'aide de Programme en Langage C++. Merci de me répondre dans le plus bref des délais.

Alors déjà moi je n'ai mis aucun exemple, donc peux-tu me donner un lien, ou un fichier de l'exemple dont tu parles?
Ensuite, si ton exemple est fait pour du GPIB comme ton commentaire semble l'indiquer, tu es mal parti car l'USB-6259 est une carte d'acquisition DAQmx, elle n'utilise donc pas la communicaion GPIB, mais directement l'accès aux voies par les fonctionnalités du driver DAQmx.
Dis-nous quel est ton exemple, où le trouver, ou ce que tu cherches à faire et on pourra peut-être t'aider.
Sinon, tu vas dans le menu démarrer>>Tous les programmes>>National Instruments>>NI-DAQ. Tu y trouveras des guides d'utilisation du matériel USB, des guides pour comprendre ce qu'est le DAQ, et un guide pour le DAQ en langage textuel. Bonne lecture.
Olivier L. | Certified LabVIEW Developer

USB-6259 to capture the current waveforms

Hi all,
I am pretty new to LabView and data aquisition. Sorry to bother you all. I have a question:
"Can I use the USB-6259 DAQ device to capture the current waveform of electrical appliances e.g. electric kettle using current probes????? If yes, could you be very kind to guide me in this regard???"
Thanking in anticipation.
Best regards,
Haroon

Yes, you can do that. You need to do the following:
1. Put a shunt resistor (1ohm, high precision, high wattage) in series with your application.
2. Use one of the Analog input from your DAQ to measure the voltage drop across the shunt, and this will be your current waveform, since the resistor has 1 ohm.
Things to watch out for:
1. Power rating on shunt: make sure your shunt can handle the power.
2. Noise: you may need some filtering circuitry to get rid of the signal noise. If you are comforable with digital filtering, you can use some of the filtering function in LabVIEW.
3. Level at AI: maybe very low, since there are little drop across the shunt. If you don't mind a larger voltage drop, you can increase the value of the shunt to increase the level; if you just want to look at the pulse shape. Or, you can put an amplifying circuit for a little boost before you feel the signal to AI.
Yik
Kudos and Accepted as Solution are welcome!

Generate pulse frequency with usb-6259 on matlab

Hi,
I would like to create a pulse with the ni usb-6259 counter via Matlab (R2007b). As Matlab Data Acquisition Toolbox dosen't support the access to the counter/timer of the 6259, I call 'DAQmxCreateCOPulseChanFreq' from the library. However, it returns a negative status indicating that the channel was not created. Can someone tell me why I have a negative status?
Thanks,
Miko
Here is the code:
% %load libraries nicaiu.dll,nidaqmx.h if not loaded
clc
if ~libisloaded('myni')
disp('Matlab: Load nicaiu.dll')
funclist = loadlibrary('nicaiu.dll', ...
'C:\Program Files\National Instruments\NI-DAQ\DAQmx ANSI C Dev\include\nidaqmx.h', ...
'alias', ...
'myni' );
end
disp('Matlab: dll loaded')
disp('')
% Counter must be driven and read through 'c' function calls
% Define variable for taskhandle
taskh1 = uint32(1);
% Create task
[a,b,taskh1] = calllib('myni', 'DAQmxCreateTask', 'master', taskh1);
% Create channel name for counter input edge count
taskchans1 = ['Dev1/ctr0'];
%define required properties for pattern generation
DAQmx_Val_Hz = 10373; % a pre-scaled unit (aka DEFINE)
DAQmx_Val_Low = 10214; % resting state, pre-define unit
initialDelay = 0; % sec
freq = 16000; % Hz
dutyCycle = 0.5; % width / period. This ratio, combined with frequency, determines pulse width and intervals
% Create channel: specify duty cycle and frequency
nStatus = calllib('myni', 'DAQmxCreateCOPulseChanFreq',...
uint32(taskh1), taskchans1, '', DAQmx_Val_Hz, DAQmx_Val_Low, initialDelay, freq, dutyCycle);
if nStatus == 0 % channel created successfully
disp('Success')
elseif nStatus < 0 % error: channel not created
disp('Error')
elseif nStatus > 0 % channel created with warning
disp('Warning')
end
Miko

Thanks Peter!
It indeed proved useful, thanks to the last comment (slastuka p.10).
It seems that the input and output type depend on NIDAQmx version.
Here is the code (that works for me), in case help someone else:
clear all, close all
clc
if ~libisloaded('myni')
disp('Matlab: Load nicaiu.dll')
loadlibrary('nicaiu.dll', ...
'C:\Program Files\National Instruments\NI-DAQ\DAQmx ANSI C Dev\include\nidaqmx.h', ...
'alias', ...
'myni');
end
disp('Matlab: dll loaded')
% libfunctionsview('myni')
% Counter must be driven and read through 'c' function calls
% Define variable for taskhandle
Taskh1 = [];
% Create task
[a,b,Taskh1] = calllib('myni', 'DAQmxCreateTask', 'Counter', Taskh1);
Taskh1 = libpointer('voidPtrPtr',Taskh1);
% Create channel name for counter input edge count
Taskchans1 = libpointer('cstring','Dev1/ctr0');%Counter name
NameChan = libpointer('cstring','');%Channel name
%define required properties for pattern generation
DAQmx_Val_Hz = int32(10373); % Units: Hz <-> 10373
DAQmx_Val_Low = int32(10214); % Resting state: Low <-> Terminal is at a low state at rest. Pulses move the terminal to a high state.
InitialDelay = 0; % Delay (sec) from the start call to the beginning of the pulse train ; this is currently set to 0.0 by default.
Freq = 16000; % Hz
DutyCycle = 0.5; % width / period. This ratio, combined with frequency, determines pulse width and intervals
% Create channel: specify duty cycle and frequency
nStatus = calllib('myni', 'DAQmxCreateCOPulseChanFreq',...
Taskh1, Taskchans1, NameChan, DAQmx_Val_Hz, DAQmx_Val_Low, InitialDelay, Freq, DutyCycle);
if nStatus == 0 % channel created successfully
disp('Success')
elseif nStatus < 0 % error: channel not created
disp('Error')
elseif nStatus > 0 % channel created with warning
disp('Warning')
end
I don't know for the following, but at least I can create the channel.
Miko

Connect usb 6259

i need to connect ni usb 6259 with the network analyzer and i don't even know what are the programs i need for this. is there any way i can test if the niusb 6259 is working or not. your comment will be highly appreciated.
thank you

I wish you were consistent. Now you are saying that you have a signal generator and not a network analyzer. Are you really sure of what instruments you have?
For the 33250A, there is an instrument driver here. You will obviously need to connect the instrument to the pc in some manner. The instrument supports GPIB, Ethernet, USB, and RS-232. You need to find out what interface the actual instrument has. If it's only GPIB, you would need a GPIB controller for the pc. For information on what a driver is and how to use one, check the links on the Instrument Driver Network page.
I already mentioned that you use DAQmx functions to control/read the DAQ card. See the DAQmx Getting Started page for explanations of waht DAQmx is and how you use it for NI DAQ cards.
For learning LabVIEW basics, see these tutorials. There other training resources available.
You have not mentioned the type of analysis you need to do. If you have trouble, you need to provide these details. And why do you continue to not provide the details that have been constantly asked for? Whether or not you understand LabVIEW, you need to be able to do a technical description of your task. That's a basic skill that you need to have.

NI USB-6259 and labwindows Interface

Hello Everyone,
I am new to Labwindows and dont know much about the interface between NI USB-6259 and Labwindows. I want to make a simple user interface by which i can sense few sensors and plot their data with time. I want to use these sensor's values to estimate parameters (i have laser sensor which is telling me stroke of a piston, and i know the cross section area, i can plot volume, and stuff like that). I tried to find out some material but could. Can anyone help me?

A good starting point can be the Example finder, which is run using Help >> Find Examples... menu option.
The example finder can be instruted to search either on the local disk or on NI site for examples related to a specific hardware: see the help for the finder.
Just as an example, this is the aspect of the finder searching for examples of analog measurement for your board (note the highlights):
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

SignalExpress and the usb-6259

We are trying to use SignalExpress and the USB-6259 to generate digital outputs without success. Do all the digital I/O lines on this module require an external sample clock to work correctly. Any information would be appreciated

Hello Greenies
Thank you for your posts, as I have said on your other message, I hope it is ok for me to contact you on just the one page as it saves repeating ourselves. I would also like to mention that in future it is better to post on one board so that other users can search discussions with more ease.
As I understand you have queries regarding the digital I/O of the USB 6259, I firstly recommend looking in the manual for your device to see if this is already documented.
"Each DIO and PFI signal is protected against overvoltage, undervoltage, and overcurrent conditions as well as ESD events. However, you should avoid these fault conditions by following these guidelines:
• If you configure a PFI or DIO line as an output, do not connect it to any external signal source, ground, or power supply.
• If you configure a PFI or DIO line as an output, understand the current requirements of the load connected to these signals. Do not exceed the specified current output limits of the DAQ device. NI has several signal conditioning solutions for digital applications requiring high current drive.
• If you configure a PFI or DIO line as an input, do not drive the line with voltages outside of its normal operating range. The PFI or DIO lines have a smaller operating range than the AI signals.
• Treat the DAQ device as you would treat any static sensitive device. Always properly ground yourself and the equipment when handling the DAQ device or connecting to it."
This information was taken from chapter 6 of the manual, there is also information about connecting signals for DIO on page 10 of chapter 6.
Specifications
Manual
Here are some articles which discuss DIO functionality, these may also help you with your development.
DIO benchmarks
DIO
Please let me know if your questions are answered in these documents, if you still have outstanding queries, please reply so I can continue to offer you support.
Regards
Stephanie L
Applications Engineer
National Instruments UK and Ireland

USB 6259 support?

Hello,
Is the USB version of the M series 6259 supported by the MH DDK? The FAQ says that the PCI ansd PXI versions of M series boards are supported, but gives no information regarding the USB version.
Thanks,
Steve C.

USB communication is not currently supported by the MHDDK. The method of communication is completely different than PCI/PXI. Can you tell me more about your application and why you want to use USB? Why are you wanting to use the MHDDK?

Mirroring input to output on NI usb-6259 (with or without DSP)

Hi, I'm new to Labview and I am looking to make a vi that reads a digital waveform in and echoes that waveform out on another pin, preferrably after having undergone some logical switching for channel selection purposes.
I have tried looking through and modifying the example vi's (e.g. Multi-Function-Synch AI-AO.vi ) with little luck. It seems that the best I can do is to generate a square/triangle/sine wave at a frequency that is governed by my external clock trigger... No data echoing for anything complex.
Can anyone offer me some pointers on where to start with this IO stuff?
Ideally from a "block diagram" point of view, I'd like to have my external waveform generator running an external trigger to a DAQ pin, use that to trigger sampling on another (digital) IO pin, send that data to the DSP blocks, and then finally echo the data out to another IO pin...
I've tried constructing this setup in all the "intuitive" ways I can think of, and have sort of struck out.
Please help?

Hello Godzilla,
In order to do synchronized digital input and output you will need to route your external trigger through a "dummy" analog input task. The reason for this is that the digital I/O tasks do not support start triggers. By using the analog input sample clock and starting the digital tasks before the analog input they will be started at the same time and thus be synchronized.
I would recommend starting with the Multi-Function-Synch AI-Read Dig Chan.vi example program. This example does everything you need to do for the digital input; the only thing you need to change to the source input of the DAQmx Timing VI for the analog input task. Right click the source input and create a constant, then choose the PFI line you want to route your external trigger in on.
At this point you'll have a program that uses your external sample clock and you have the ability to add a digital output task that will be synchronized with your input. To add this digital output task I would suggest the Cont Write Dig Port-Ext Clk-Non Regeneration.vi example. If you copy this example into the other one and merge the two while loops you'll only have a few modifications to make.
Here are some things you'll need to change:
1. Route the same analog input sample clock to the source terminal of the DAQmx Timing VI for the digital output task.
2. Buffer the output with the data you want by changing the data input to the DAQmx Write VI.
Non-regeneration keeps the digital output from looping previous data. This will allow you to know if you are buffering output data fast enough. If you have trouble running this loop with your analysis then I would recommend implementing data pipelining. For an overview of what pipelining is please see this article: http://zone.ni.com/devzone/cda/tut/p/id/6425
In general control loops are not recommended on Windows operating systems. However, depending on the analysis you're doing, your computer, and what loop rate you're looking to get it can be possible with good programming techniques. The fastest I would recommend trying to execute your loop on a Windows OS is on the order of 10ms (give or take depending on your computer and analysis). If you need to execute this control loop faster than 1ms I would recommend considering a Real-Time operating system. We have benchmarked PID control loops on Real-Time operating systems at more than 30 kHz.
I hope this helps get you started, and if you'd like to talk with someone at National Instruments about Real-Time control loops feel free to contact us directly using the information at www.ni.com/contact.
Have a great day!
Brooks

Usb 6259

Similar Messages

Maybe you are looking for