Hi, I have a Multifunction PCIe 6341 DAQ on a 64 bit machine with 64 bit Matlab 2014a. One of the DAQ Toolbox command is called the 'inputSingleScan', this command however is significantly slower than its 32 bit Matlab counterpart 'getSample'.
I like to know if this is an Matlab issue or the DAQ not playing well with Matlab. On my 32 bit machine a DAQ from MCC can achieve 1.4KHz frame rate and this NI DAQ can only achieve 190Hz.
I appreciate any input and solutions.
Matlab says it has support for NI PCIe DAQ, but NI didn't list Matlab as one of the compatible software for its products. So i like to know if NI optimized its product to be used with Matlab.
I am using Matlab 2014a, the software recognizes the card and is able to connect to it. However the speed for one of the commands i am using is extremely slow. This particular command is called 'inputSingleScan'. This commands' 32 bit legacy interface counterpart perfoms much faster, but with a MCC card instead.
Hello there,
I am trying to measure a signal using the DAQ assistant, aswell as a signal using a multimeter and a rs232 cable. The problem is: if I measure just the signal with the DAQ assistant it goes real time, measuring the signal from the multimeter at the same time gives a delay in the signal from DAQ assistant. I am kind of a rookie with Labview and was hoping one of you guys could help me out. I have attached the .vi.
Thanks a lot for your help in advance.
Kind regards,
Rudy
Hi everyone,
I use a niDAQmx solution in a custom MSVC application. Everything is fine in case of
a win32 build. However, in the x64 build, I can not find the import library.
I found a discussion with a solution for this problem with version 9.8 of the niDAQmx
installation software here:
http://digital.ni.com/public.nsf/allkb/0A58C96A9ECF3E27862577420050B500
Unfortunately, I do not have the folder
<Program Files>\NationalInstruments\Shared\ExternalCompilerSupport
on my system. The other post says that I need to activate "install ANSI C support" in the custom installation.
Well, I checked it multiple times, this option is active. As it seems, that is the default install option.
Nevertheless, no 64 bit library is present on my system.
Can anyone please help here?
Thank you and best regards
Hauke
Hello all,
I am trying to determine whether cDAQ or cRIO would be better to measure strain gauge, temperature (thermocouple), and accelerometer data from devices placed on a Formula SAE vehicle. Currently, I have both chassis (cDAQ and cRIO), as well as, all the modules needed (9237, 9213, and 9234) for the measuring devices. My concern comes from not having very much experience in determining which system is better in terms of counters/triggers, output, and device management. Also, where gathered data is stored and if a computer is always needed to be connected, etc. If anyone would be willing to share their experiences with either chassis in a similar senario that would be great.
Thanks,
Kevin
hello there
i wanted to generate pwm signal using NI 9263 voltage output module. it works properly when it is generating only one signal but i want to generate 4 signal simultaneously with different duty cycle.i have written a simple programme to generate only two signal but it is not giving me output. although it is not showing any error in programme and it runs contineously but there is no wave form on oscilloscope.
i have attached screen shot of my programme and configuration that i have selected......
please suggest me any different method or standard programme.
Thanking you!
regards
jay
I'm looking to record data from up to 100 thermocouples and batch log each one to an independent file. I need to be able to live trend them in groups. Sample rate is quite low, probably as low as 10 seconds, maybe less. Batch length would be about 12 hours. Data needs to be exportable to Excel. Does anyone have any suggestions on hardware/software for this.
Thanks in anticipation.
John
I updated my Win7 today (9/25/2014) with MS latest update KB2998527 that's supposed to just be a Russian timezone update.
Guys can i control firing angle of SCR using DAQ card and Labview?? If yes then how am i supposed to do the connection and how can i protect my DC (Low Voltage) DAQ card from High AC voltage so that it doesn't burn out. Is their any way to connect Labview and DAQ with an SCR of which i want to control firing angle using labview??
I am really sorry if my question seems stupid or isn't in the correct forum. I am new NI forums and i have just started out with Labview and Daq card. Please help me out people.
I'm trying to simultaneously start two processes AI and AO. AO is what I'm having issues with. It should output more samples that buffer holds (150000 in my example). That's why I have 'Write' block in a loop. I was not able to write exactly as many samples as I provide to the 'Daqmx base write' box. Using the code attached, it outputs about 143000 samples and stops.
Would appreciate any advice.
I write only 5V or 0V output. Like a TTL signal. When I tried to use digital output, I was getting error 200452 at the start digital edge block. If there is a way around that? Please let me know.
Could not figure out how to use counter for my output either. Need to output square wave duty cycle of which changes continuously.
Any advice apreciated
System: PCIe-6251 on an intel based MAC OS X, LabVIEW 2010 SP1 and I believe Daqmx Base 3.6
Hi,
I am trying to use my DAQ (PCI 6115) to count photon signals from a photon counting PMT.
What I have set up currently is
1. creating a gate pulse with a width of integration time with counter 1 on DAQ
2. creating a sencond counter to count the number of edges from the PMT within the given amount of time from #1.
as I change integration time the width of the gate pulse should change therfore giving me more or less counts from my PMT, but this does not seem to be working correctly. Is there a better way to do this with my daq or am I performing something wrong?
Thanks for any help.
We are using NI DAQ USB-6341 to achieve re-triggerable capture of 10 analog way, each with its own digital trigger input. Is it possible to have multiple triggered acquisition running at the same time (with different trigger) ?
Hello, I have trouble outputting data with a NI USB 6211 device using the Analog Output block from the Data Acquisition Toolbox on Simulink.
I have been able to acquire signals with the Analog Input block, which makes me think it sholud be possible to output the signals the same way. This is the model that worked fine and the configuration I used:
Anyway, I keep getting the following error whenever I want to run the simulation using Analog Output:
Error reported by S-function 'sdaqao' in 'DAQ_Analog_Output/Analog Output':
To run in a hardware-clocked output mode, this hardware requires that at least
2 samples be queued using PUTDATA. You must pad your output with additional
samples to use PUTDATA, or use PUTSAMPLE instead.
I have tried writing the following code in the command window and then running the simulation:
ao = analogoutput('nidaq','Dev1');
ch = addchannel(ao,0:1);
y = [1 1]';
putdata(ao,[y y])
But the same error keeps comming out.
I also tried using Analog Output (Single Sample), but I have problems with the timing. For example, I generate a sin of some frequence but on the osciloscope I see another frequence and the simulation does not last what I put in the model.
I could acquire and output data writing code in the Command Window, but for my work I need to be able to do it on Simulink. I am using Matlbab R2012b.
This are the images of the model and the configuration of the block for Analog Output:
How can I output data using the Analog Output block? I really need to do this so any help will be very appreciated.
Hi,
I have a PXI 1042 chassis, with an NI PXI-8360 controller, however, when I open NIMAX, the controller appears as unknown (see attached image).
I am using NIDAQmx driver version 9.9.0f0 on a Windows 64 bit machine.
The chassis is equipped with NI PXI-4461 and NI PXI-4462 modules, both of which are not recognized. I assume this is because the controller is unrecognized?
I am interfacing to the chassis through an NI ExpressCard-8360 - could that be causing the problem?
I have attached a screen capture of the issue.
I have also mode sure that I start with all PC's turned off, then turned on the chassis first then the PC. Any help is greatly appreciated
Thanks,
Wael Hemdan
The MathWorks
I am using the NI USB-6008 Analog Inputs. The spec says they have an input impedance of 144k-ohms. But it does not say what the termination voltage is. If you leave the AI's disconnected and measure voltage you will get 1.4 volts. So I'm assuming that this is the termination voltage, but it is not spec'd.
Does anyone agree that these AI's are terminatied by 144k-ohms to 1.4V? Is this in the documentation somewhere?
Hello,
I'm using NI DAQ USB 6363 with C++/Matlab.
I'm trying to do a pulse width measurement with a known finite sample size (on the order of 2000).
The problem is that some of these pulses might be very short, shorter than my clock.
I would like the DAQ card to simply report those pulses with width 0 and I know it works with other NI DAQ cards that some of my colleagues use.
However, for me, it simply returns an error saying that not all of the samples have been received.
I've searched the help but couldn't find anything about it...
Is it some configuration that can be changed?
If not, can anyone recommend me another similar DAQ card in which it works?
Thanks in advance.
Yoav
Hello,
the NI SCB-68A connector has several Analog Ground "A GND" and "D GND".
All Analog Grund are not connected to other Analog Ground, means when i try
to measure from one AGND to another AGND.
Does that mean that i must connect ALL AGND to my source ground or only one?
If so all AGND must connected to each other on my PCI-6225 internally. Is that the case?
Do i need to connect all digital grund or just one?
Hi,
I'm using a system based on a cDAQ 9178 (with 2 NI 9223 + 1 NI 9401) with a sampling frequency at 1MHz (the maximum rate).
Using USB3 ports, my application was not able to read the samples on time : buffer overwrite error
Using USB2 ports, everything was fine...
DAQmx version : 9.9 (delivered with the devices)
LV 2011 (run-time)
I don't find any information on NI website. Did anyone also notice this point ?
I didn't check the USB 3 performances, but just used the USB2 instead.
Best regards,
Adeline.
Hi,
According to the manual the 6259 device can use an external reference for analog output.
My problem is that I can't find the setting to select it. The NI-DAQmx help says: "The external reference voltage settings are available as a Channel property in the Analog Output»General Properties»DAC»Reference Voltage".
But where do I find this setting? I'm unable to find it in both MAX and SignalExpress. Do I need to use LabView to access this property?
Or is the external reference feature not available on USB-devices?
Regards,
Joacim
I have Labview 2011 32-bit (no toolkits), on Windows 7.
Hardware: NI USB-6251 DAQ board. I'm using analog in, analog out.
I am trying to collect data (read), analzye it (such as integrate or derivative) to make a new waveform (or data array)., and then output that new waveform. Just like this example:
http://zone.ni.com/reference/en-XX/help/370466V-01/mxcncpts/hwtimedsimio/
However, I don't have hardware timing.
I have tried many many things. One that worked temporarily, until the start task for write threw an error: http://i.imgur.com/as5ItdO.png
Another that works temporarily, but has a 7 second delay: http://i.imgur.com/VLbyZbo.png
Ends up having this error: Warning 200015 occurred
While writing to the buffer during a regeneration, the actual data generated might have alternated between old data and new data. That is, while the driver was replacing the old pattern in the buffer with the new pattern, the device might have generated a portion of new data, then a portion of old data, and then a portion of new data again.
Reduce the sample rate, use a larger buffer, or refer to documentation about DAQmx Write for information about other ways to avoid this warning.
Can anyone tell me what I'm missing? It seems very simple.
Thank you.
