Dear Sir,

I tried to install DAQMAX 8.0.2f0 on Linux 2.6.29.6 to get my NI PCI-6509 card work. But It shows the error message: Class ff00:National Instruments Unknown device 7085 

Please help me.....

I have been using a BNC-2110 connected to a PCIE-6351 without trouble for over a year.

Today using an external DC power supply, an accidental 40 V and a current of ~0.1 to 1 A was applied to the channel AO-0. I heard a couple shocks and smelled something somewhere but I don't know where.

Now, all AI don't respond to input and AO dont change output. Using the Test Panel feature of NI-Max, the AI sit at -10.3 mV and the AO sit at around 1.0V and won't change based on settings.

Also suspicious is that the device says it is at -49 Celsius, which is certainly not the case.

How can I calibrate this device? How can I tell if the box or the board is fried?

Attached is a screenshot in case it helps. I removed the serial number from the image.

Thanks for your help!!

Dear Sir,

I installed DAQMAX8.0.2f0 on Redhat(kernel 2.6.96.6) and tried to use nilsdev to find my PCI 6509 Card, but nilsdev returns nothing,. Then I use ls -pci, and the system returns as: class ff00:National Instruments unkown device 7085 

Hi !

I have DAQPad 6016 unit but I am not unble to use, when I go on MAX it says that the device needs drivers. I have also installed DAQmx latest version, but it seems to me the device is not recognisable. It is my first time when I use such device, so not sure if I am doing right way...

Thanks for any help

Hello everyone. 

For a project Iam working on I need at least 120 analog channels. 

There is no need for a high sampling rate as it would be enough to read a channel every minute. 

As a DAQ with 120 single channels is extremely expensive I was wondering if it would be possible to connect a MUX before a more cheaper DAQ like the USB 6002 and if so what kind of hardware would be available for that? 

Thanks in advance, 

Kind regards, 

Michael 

Hello,

I update an application builded with .Net3.5/C# wich uses DAQmx 14.1.40; i do this software update using VS2015 and .Net 4.6. In the old projet of my application, i used references to NationalInstruments.Common.dll and NationalInstruments.DAQmx.dll. Unfortunately, installing DAQmx 16.0.1 installs NationalInstruments.Common.dll on my disk, but NOT NationalInstruments.DAQmx.dll.

Some one can tell what dll shall i use in place of NationalInstruments.DAQmx.dll, or if i must install other things?

Thanks i advance

Pascal

I'm working on a high performance scientific instrument for my laboratory.

I've build 4 identical silicon photodiode amplifier and I tested them using a NI PXI 5922 board. The test consist in powering the circuit and connecting it to the board without shining any light on the photodiode. The signal in this configuration is only the background noise generated by the circuit (resistance thermal noise and opamp noise), the so called "dark noise" of the circuit. This noise is analysed by computing its Power Spectral Density. The same is done with the noise generated by the board itself, by putting its input in short circuit.

Using the 5922, the circuit performed as expected. But when I did the same test using my NI PXIe 6124, I observed very strange behaviour, and I dont know what's happening. It looks like the DAQ noise receive some strange gain, or interact in a strange way with the circuit.

Configuration when using the 5922 :

 - circuit powered by a low noise linear benchtop power supply

 - board configured in high impedance input mode (1 MOhm in parallel to 60 pF, acording to the spec sheet)

 - circuit output connected to board BNC input using a shielded, twisted pair cable 1 meter in lenght

 - I dont remember the PXI chassis used, but I dont know if it's important. In all cases, in this configuration everything worked well

The result from this measurement is given in the attached figure "new circuit compare.png". The acquisition rate was 15 Ms/s.

Configuration when using the 6124 :

 - circuit powered as before

 - circuit connection to the DAQ described in the attached figure "capture shielded twisted pair"

 - The DAQ is the only board in a NI PXI 1073 chassis. Connection is made through a NI SCB 68 A connector bloc and a 5 meter long SHC-68-68 EPM cable. The total cable lenght is thus 6 meters.

 - The DAQ noise was measured with this cabling, but by replacing the circuit with a short circuit wire (a wire between the IN+ and IN- analog input, and a second wire between IN- and GND). Note that contrarily to the 5922, the 6124 have differential input.

What I've obtained Is given in the figure "CIRCUIT TO DAQ COMPARE". In this figure, the 4 spectra at the bottom correspond to the DAQ noise, while the 4 spectra at the top are what I obtain when I connect the circuit. The acquisition rate is vary, but the input range is always +/- 1V.

The DAQ noise change when its acquisition rate is modified, as expected. The DAQ noise level correspond exactly to the ones specified in its spec sheet. However, when my circuit is connected, everything look like the DAQ noise is multiplied by 200 (100 at 4 Ms/s), and I dont have the same result I had with the 5922. Note that the circuit noise level correspond to the DAQ noise level at 4 Ms/s, at least between low frequency and 100 kHz.

The DAQ noise also change with input voltage range. But stangely, if I change the voltage range instaed of the acquisition rate, the noise level remain the same...

What I've tried so far :

 - change the cabling between the circuit and the connector bloc: no effect

 - change the length of the cable between my connector bloc and the DAQ (from 5m to 2m) : no effect

so it is not a cabling problem

 - use a different analog input (the 6124 have 4 AI) : no effect

 - use a different copie of my circuit : no effect. Instead of this strange noise, the circuit behaved well.

 - add resistor's in parallel between the DAQ IN+ and GND, and also between IN- and GND (recommanded if you connect a voltage source with a high output impedance to the DIFF input) : the continuous background noise didn't changed, but It added spurious sin peak in the spectra.

 - add a resistor's in serie between the DAQ IN+ and the circuit OUT : It does change the noise level, but I also change the circuit bandwidth by doing this, so this is not a definitive solution. By looking at the circuit new bandwidth with this added resistor, it look like the resistor is forming a pole with a capatance around 1 uF. I dont know where this capacitance can come from.

Additionnal information : the circuit diagram is attached. The Opamp I used is the Analog Device AD8067. It have a very low ouput impedance, this is why I connected my circuit this way.

Any hypothesis or explanation about what's happening here would be appreciated. I dont know why my circuit and my DAQ dont like each other. The main difference I see between the 5922 and the 6124 is the DIFF input of the 6124, but I dont know how it can bring me trouble. I you want additionnal information just ask.

Please Help me !

hello everyone,

i was wandering which NI device i should use to acquire a torque shaft measurement from a RS-423 connector.

Hi There,

I've ordered a PXI-6704 board, and I would like to increase the current output range from 20mA to 40mA.  At the moment I'm thinking a simple opamp would do the job.  Thoughts?

Also, I'd like to know more about the analog current output signal.  Does it control current with voltage, duty cycle, or something else?  What is the voltage range?  If duty cycle, what is the voltage range and frequency of the pulse?  Are there any NI documents where I could read more about the details... the circuit, signal diagram, etc.

Andy

Hi,

I'm bacially trying to replicate a pulse generator using an NI 6602 driver + LabView software.  The problem I'm running into is that I can't seem to sync my separate channels.  Not sure why I can't get the DAQmx Start Trigger (Digital Edge) VI to work.  Without it, I can easily generate as many finite pulse trains as I have channels available (well, every other one since finite pulse trains require two channels), but they're not synced to the same start time.  And it's a difference of 8 microseconds, but I'd ideally like to generate pulses on the order of 20 microseconds, so that's a huge delay comparatively.

VI screenshot attached.  The top task doesn't work (it gets hung up on the wait until done and I get the error -200560; increasing the timeout doesn't work, and I can't figure out a good way to debug if the trigger just is acting funky, other than to say that other VIs using the same trigger work fine), but the bottom task chugs along just fine.

I haven't tried using another counter to sync these pulse trains, since I'm hurting for counter space.  As it stands, I'll probably need another slot in my DAQ to run another set of frequency outputs.  I'd like to be able to sync these using the internal clock, but that's not as intuitive as I think it should be.

Any help much appreciated.

Anna

Hello friends,

I have a task of acquiring continuous samples from two C series-NI9215 cards mounted on cDAQ-9171. The technique available on

http://forums.ni.com/t5/NI-DAQmx-Examples/Synchronize-Continuous-Acquisition-of-Multiple-Analog-Inpu...

does not include for the case for C series. Can somebody please help me regarding this. It would have been better if the logic behind using these blocks is also exlained as I'm a beginner in data acquisition.

Thank you all in advance,

Gajanana Abhyankar B

Hi,

I am working on a VI for frequency response analysis. The test should consist of two rounds. In each round different analoge output should be used. So I need to change the physical channel for analoge output task in the second iteration of the loop. I tried to do so by using DAQmx Channel Property Node. However the "PhysicalChanName" element of the node only accepts input channels! Furthermore, the "ChanType" element reads as "Analoge Input" and the "Change To Write" option is deactivated for this element. Any idea how can I fix this?

I am using NI PXI-4461 and LabView 16.0 64-bit.

Hello,

I have a pressure transmitter that I would like to read with PCI 6289 DAQ. I assume I have to connect the transmitter's signal line to one of the channels but I am a little confused because I can't find the data sheet for AIchannel and Gnd combination.

And how do I map that to the Analog Input on the DAQ? For example, I have thermocouples connected to SC modules where I know which channels I connected and I can create a DAQmx task with the channels to read. 

The pressure transmitter has 2 power lines, a signal line and a cable screen line

I have a 2 way 12 VDC NC Valve that I want to control with PCI 6289. Which Module would I need to connect the valve so that I can write a DO value from Labview. I have a CB 68LPR. Is it capable of DO?  and how do I map the connection to a specific DO line on the PCI 6289 in order to create a DAQmx task?

Thanks

Using PXIe-6363, DAQmx C API on Win64

I'm trying to get DAQmxRegisterEveryNSamplesEvent to work with both AI and AO, on each sample.

My AI task works, which means my callback gets called with every sample.

My AO task waits until it's finished, then calls the callback very quickly.

For example, for 50 AO samples, the analog voltages appear on my scope, then after the 50th sample, my callback gets called 50 times all of a sudden.  This happens even if the output rate is very slow, like 0.5 or 1.0 Hz.

The behavior is the same as if I had asked for DAQmxRegisterEveryNSamplesEvent with an argument of 50 instead of 1.

How do I get my AO to call back with each sample as they are written out?  I think I encountered this a year or two ago, and the workaround was to set up the timing so it does only one sample instead of 50, then stop and restart the task in the callback for each sample.  I can live with the resulting extra few ms this adds with each cycle, but it's ugly.  I'd like my code to be called either at the beginning or the end of each analog voltage physically sampled out on the wire.

Below is the abbreviated code.

// Set up common channels
char aoPhysNames[100], aiPhysNames[100], doPhysNames[100];
strcpy_s(aoPhysNames, sizeof(aoPhysNames), "Dev1/ao3,Dev1/ao2,Dev1/ao1");
strcpy_s(aiPhysNames, sizeof(aiPhysNames), "Dev1/ai16,Dev1/ai17,Dev1/ai18");
strcpy_s(doPhysNames, sizeof(doPhysNames), "Dev1/port0/line8:31");
char aoNames[] = "XDRIVE,YDRIVE,ZDRIVE";
char aiNames[] = "AUX X,AUX Y,AUX Z";
DAQmxErrChk(DAQmxCreateTask("Analog Output Task", &hAOtask));
DAQmxErrChk(DAQmxCreateTask("Analog Input Task", &hAItask));
DAQmxErrChk(DAQmxCreateAOVoltageChan(hAOtask, aoPhysNames, aoNames, -10.0, 10.0, DAQmx_Val_Volts, NULL));
DAQmxErrChk(DAQmxCreateAIVoltageChan(hAItask, aiPhysNames, aiNames, DAQmx_Val_NRSE, -10.0, 10.0, DAQmx_Val_Volts, NULL));

// ANALOG OUTPUTS
DAQmxErrChk(DAQmxRegisterEveryNSamplesEvent(hAOtask, DAQmx_Val_Transferred_From_Buffer, 1, 0, DAQ::_everyNWriteCallback, this));
DAQmxErrChk(DAQmxRegisterDoneEvent(hAOtask, 0, DAQ::_doneWriteCallback, this));
double outRate = <some formula, about 100 Hz>
DAQmxErrChk(DAQmxCfgSampClkTiming(hAOtask, "", outRate, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps, numSamples /*+1*/));

// Set up N input samples as slave to when AO starts, at same frequency as pulse
DAQmxErrChk(DAQmxCfgSampClkTiming(hAItask, "", pulseDef.frequency, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps, pulseDef.count));
DAQmxErrChk(DAQmxRegisterEveryNSamplesEvent(hAItask, DAQmx_Val_Acquired_Into_Buffer, 1, 0, DAQ::_everyNReadCallback, this));
DAQmxErrChk(DAQmxSetStartTrigRetriggerable(hAItask, TRUE));
DAQmxErrChk(DAQmxSetStartTrigDelayUnits(hAItask, DAQmx_Val_Seconds));
DAQmxErrChk(DAQmxSetStartTrigDelay(hAItask, AI_TRIG_DELAY));
DAQmxErrChk(DAQmxCfgDigEdgeStartTrig(hAItask, "ao/SampleClock", DAQmx_Val_Rising));

// Later on, after other non-DAQ stuff....
DAQmxErrChk(DAQmxStartTask(hAItask)); // AI is slave to AO
int32 aoWritten;
DAQmxErrChk(DAQmxWriteAnalogF64(hAOtask, numSamples, FALSE, -1, DAQmx_Val_GroupByScanNumber, (float64 *)outData, &aoWritten, NULL));
DAQmxErrChk(DAQmxStartTask(hAOtask)); // AO starts regardless



int32 CVICALLBACK DAQ::_everyNReadCallback(TaskHandle taskHandle, int32 everyNsamplesEventType, uInt32 nSamples, void *callbackData) {
    // This is called correctly at the proper times, with nSamples == 1
	return 0;
}
int32 CVICALLBACK DAQ::_everyNWriteCallback(TaskHandle taskHandle, int32 everyNsamplesEventType, uInt32 nSamples, void *callbackData) {
    // This is called the correct number of times, but only after the DAQ has physically
    // written out all the voltages, as seen on the o-scope.
    // nSamples == 1 each time, which is correct
	return 0;
}

I'm trying to output some basic waveforms with USB-6003 using a DAQmx analog output channel in regenerative mode. In the VI, when a timeout event occurs, task is stopped, timing settings and sample data is updated and task is restarted. I'm expecting the device to continuously output the available samples until another timeout event occurs and new samples are written. Most of the time device does this. However, sometimes the regeneration does not work and newly written data is outputted only once or twice.

Here is an example simplified block diagram generating the problem,

An example output signal captured with the same device,

The flat lines above are the problem. They should be square waves instead.

I'm also getting an internal software warning after a short time the program starts. I don't know wheter it is related to the problem or not.

I would be very glad if anyone can point out the cause of the problem.

Hi,

I have a PCI-6289 DAQ that's connected to a SCXI-1000 chasis. I have 2 modules in it. SCXI 1102-C with SCXI 1303 and SCXI 1180 with SCXI 1302. I have connected 16 thermocouples connected to 16 channels of SCXI 1102C. I am not sure about how to use SCXI 1180( I didn't build the system). Is it a 50 pin connector like a scb 68. I also have a CB 68LPR that I have connected to a Pressure Transmitter. I was wondering if it could be coonected to the analog input of 1302.

Thanks

Hi,

A part of the system accepts TTL trigger and generates 2 pulse trains which are connected to 50 Ohm inputs. It there USB module (due laptop) which handle 50 Ohm?

Thanks, Andrey.

Hello,

I'm trying to send sawtooth AO signals at certain frequency and at each rising or falling edge, would like to send DO trigger signal out. I wired AO channel into AI channel and set DO to wait on AI signal as a trigger. I searched forum and read manual but it wasn't clear how to achieve this (it seems USB-6211 doesn't support Analog trigger). Any suggestion would be appreciated (been stuck for awhile with this problem).

Thanks in advance.

I am measuring temperature with thermistor sensor using NI 9219 AI module on a cDAQ 9178 chassis. There is no issue when measurement is done using 2-wire mode and displayed result is in complete agreement with calibration report provided by Thermistor manufacturer. However we want to take measurement over a long distance. To get accurate result, we used 4-wire resistance measurement scheme. But the displayed result shows Zero resitance (short). The connections are proper and checked multiple times. I am not able to figure out the error. Whether NI 9219 cannot measure Thermistor resistance in 4-wire mode.

At 25 deg C, Rthermistor = 10k.

Need help.