Quantcast
Channel: Multifunction DAQ topics
Viewing all 6887 articles
Browse latest View live
↧

SC 2345 Not Communicating with PCIe 6320

October 17, 2020, 4:28 am
$
0
0

Hello All,

I have had four systems working well for over 15 years.  The systems were originally designed with the PCI 6221 DSP, the SC 2345 front end with 6 ACC01 modules and 1 AI01 modules.  With the advent of Windows 10, the PCI slots are gone and the new slots, PCIe called for an upgrade to the PCIe 6320.  I chose the 6320 over the 6321 because my systems do not require any voltage outputs.  

The system in question is the first to upgrade to Windows 10.  It also has a power supply for the SC 2345.  My problem is the PCIe 6320 card is working fine after finding it in NI MAX.  However, the SC 2345 block, after creating it, shows up in the Devices and Interfaces tree with a '0:' in front of it's name and it doesn't communicate.  When I try to test it, I get a communication error.  I'm sure the '0:' in front of the device name is trying to tell me something, but I don't know what that is.  Could it be I have the wrong selection for the PWR?  As I stated, this SC 2345 block has it's own power supply.  Any help is much appreciated.

Ron

 

↧
Search

High noise in NI 6353

October 17, 2020, 1:19 pm
$
0
0

I am using NI 6353 & NI-SCXI 1000 (1520) For Data acquisition analog input with differential signal. In SCXI-1000 there is no noise but in 6353 very high noise generated. And using 6353 with single ended the noise ratio exceeded. Any one help me for solution.? Plz

↧
↧

Could USB-6002, switching power supply, or another component cause oscillating measurements?

October 19, 2020, 8:14 am
$
0
0

In LabVIEW, the signal from the load cell is noisy and oscillates even when it's not being loaded. My question is: Is there a possibility it could be due to the DAQ or power supply?

 

The set up: 

NI USB-6002 DAQ

Omega DMD 4059 amplifier

Omega LCGB-10K load cell 

DC Power Supply (https://www.automationdirect.com/adc/shopping/catalog/power_products_(electrical)/dc_power_supplies/5vdc,_12vdc,_24vdc,_enclosed_panel_mount/pss24-050?gclid=Cj0KCQiA-8PjBRCWARIsADc18TKoW9XLoPfYWSc3WP8f9md6JB-7I79qh48up8OL8GNAhJeNR8MlcMgaAgh5EALw_wcB)

 

Ideally, we would have the NI-9237 instead of the UAB-6002. Could the USB-6002 cause this problem, or is there a greater likelihood that it's the switching power supply/something else? ANY help would be greatly appreciated!

 

More information on the project: https://stars.library.ucf.edu/cgi/viewcontent.cgi?article=7749&context=etd

 

↧

SC-2345 front end block connector not communicating

October 19, 2020, 9:31 am
$
0
0

Please help.  I recently had a test system rebuilt with a new PCIe 6320 DSP card that NI MAX found without issue.  However, when the SC-2345 block connector is added to 'Devices and Interfaces', the configuration menus all populate without any problems, but when it is finished, it shows up in the Devices and Interfaces with a '0:' in front of the name of the device and it will not communicate.  Instead of the label being 'NI SCC-2345 "SCC1"'  it says '0: NI SCC-2345 "SCC1"'.  There has got to be someone in National Instruments land that understands that error and can help me!!!  PWR02 was selected in the configuration because it does have an external AC universal power supply that was purchased with it.  What am I missing?  This is very frustrating and I am livid with National Instruments with not offering tech support after paying $700 for the new DSP board.  They throw you to the Message Boards like it's the Community's responsibility!  Pathetic.

Ron Brook

 

↧

NI 9205 with signal conditioner

October 19, 2020, 9:52 am
$
0
0

I have a 9205 connected to a model 126 signal conditioner and endevco full bridge accelerometers. The 9205 lowest range is +/-200 mV. The accelerometers are 400 mV full scale range but I will never need the full scale. I can't seem to get a reading from the accelerometers (no gain applied). I have tried two different accels to rule out the error on the sensor. I connected a 9 V battery and properly got reading with a correct voltage range. I noticed when I went down to a +/- 200 mV range I got a 0.215 mV reading which I also have gotten with my accelerometer connected at that same range so that makes me think that is some kind of out of range error reading. It seems I am not getting a reading in the range with the accelerometer. I had talked with NI before getting this DAQ so I think it should be able to work with this setup. 

↧
↧

Where does shunt cal/ offset nulling data get stored in NI MAX and when using a cRIO w) DAQmx

October 19, 2020, 11:23 pm
$
0
0

Hello,

 

I am developing an application for 8 cRIO-9056 units, for a structural health monitoring application.  We plan to use LabVIEW RT and DAQmx.  Prior to developing the software, my client used NI MAX to install a base of LabVIEW RT 19.5, and then used NI MAX to create a DAQmx task on every cRIO, and create scales and perform calibration of each strain channel.  We used the Device --> Strain Calibration feature to perform offset nulling and shunt calibration on each channel (as shown in image below). This task was repeated for all 8 cRIOs.

 

Ozfarmboy_0-1603174745342.jpeg

 

The issue is however, is that this calibration process was performed on one PC that we don't have access to, and we now are trying to access the cRIOs from a different PC.  So we need to understand the calibration status of the cRIOs and the channels.

 

This poses the following questions regarding using NI MAX / DAQmx / cRIO:

1) When you use NI MAX to create tasks/channels/scales/calibration data (ie Device Calibration such as offset nulling and shunt calibration) and then save these configurations for a cRIO, where does this data get stored on the cRIO?  I presume it gets uploaded to the cRIO and stored somewhere?  What format does it get stored on the cRIO as?  An "nce" file? How can I find/access this data?

2) If I then try to access the cRIO from a different PC, can I pull down the aforementioned configuration directly from the cRIO into NI MAX on the different PC? Or is the only way to do this by first - on the original PC - exporting to an nce file, and then on the 2nd PC - importing the nce file back into NI MAX?

3) When using the Strain Calibration feature (for strain input devices like the NI 9237), you can perform offset nulling and shunt calibration.  Does this data get stored as part of the DAQmx task inside NI MAX?  And if you export it, will it get stored in the nce file?

4) How can one export the shunt calibration and offset nulling calculated data?  Is the only way by exporting to an nce type file? You can export other calibration data, but not the shunt cal and offset nulling as far as I can see.  Any reason for this?

5) Is there a document that describes the correct process to follow for this?

 

Thanks in advance for any guidance/tips you can share!

↧

Upgraded system with PCIe 6320 not communicating with SC-2345 front end terminal block

October 21, 2020, 6:06 am
$
0
0

Good day!

I have had a system operating successfully for 15 years using the PCI 6221 DSP board and the SC-2345 block terminal with 6 ACC001 accelerometer modules and one AI01 analog voltage input module.  It has worked with Windows XP and Windows 7.

I recently had a computer die and had to go with a new Windows 10 computer with the new PCI e slots.  I upgraded to a PCIe 6320 DSP board, since I do not require any voltage outputs.

I downloaded DAQmx15 and ran NI MAX.  The PCIe 6320 DSP board was recognized and says it is functioning properly.

When I create the SC-2345 block terminal, the creation is straight forward.  The PCI e 6320 digitizer shows up, the PWR is correct (factory provided Universal Power Supply), the modules are populated, etc.

I finish and the SC-2345 shows up under Devices and Interfaces, but there is a '0:' in front of the name and if I test it, I get a communicating error.  The name of the device should be 'NI SC-2345 "SCC1"', but it shows up as 

'0: NI SC-2345 "SCC1"'.  There is no explanation in any documentation for this change or the error I get.  Can anybody help?!!!

Regards,

Ron Brook

rbrook@ips.us

↧

Multichannel analog output (Voltage and Current)

October 21, 2020, 4:17 pm
$
0
0

Dear all, 

 

Could you share any thoughts or recommendation for 16 channel AO? 

I want to have 16 channel AO with NI PCIe board, but I can only find 32 channel AO for voltage but no AO for current(PCIe-6783). I can find PCI card (PCI-6704), 16 channel AO for both voltage and current but I don't have PCI slots on my computer. Any comment would be appreciated.

 

Thank you.

 

↧
Search

DAQmxGetWriteTotalSampPerChanGenerated returns wrong value for NI USB - 6001

October 22, 2020, 2:01 am
$
0
0

Steps:

 

The Write Buffer is filled to 1000 Samples before Start.

After starting DAQmxGetWriteTotalSampPerChanGenerated is called immidiately.

 

Issue:

DAQmxGetWriteTotalSampPerChanGenerated for NI USB - 6001 return 1000 samples.

But, for other devices such as NI PCIe - 6363 (X series) and NI USB - 6211 it returns the actual value generated somewhere less than 10.

 

Attached:

6001_checkWriteTotalSampPerChanGenerated.nitrace - Output of NI USB 6001

6211_checkWriteTotalSampPerChanGenerated.nitrace - Output of NI USB - 6211

test.c - Code to reproduce

↧
↧

USB-4431 has started generating Error -200361 on system that has worked for years

October 27, 2020, 9:11 am
$
0
0

I have a USB-4431 that has been working for years using two analog input channels. It just recently started intermittently generating Error -20061 Onboard device memory overflow errors. It seems to work about half the time. The system is running Windows XP with LabView 2009 and DAQmx 8.9.5. The system is not connected to the internet, so no software has been updated for years and no hardware changes have occurred. I can of course get rid of the problem if I drop the number of samples below the buffer size or reduce the sample rate significantly. We have a spare 4431 and the problem also occurs with the spare. The system has been able to read the buffer at the desired rate and sample size for several years without problem. Do you have a suggestion as to why the system is suddenly unable to dependably avoid this error?

↧

Edit Buffer Rate

October 27, 2020, 10:53 am
$
0
0

I am working with a NI USB 6353, sending analog data out of the board into third part software (Optirack Motive 2.2).

 

I am not using LabView with this hardware. 

 

Is it possible to control the data output buffer size if I am not using LabView? I don't see anything specific to this in the Measurement and Automation Explorer. I would like to see if I can reduce the buffer size as I am looking at a real-time data measurement application.

 

Thanks for the input.

↧

PCI-6224 779067-01

October 28, 2020, 2:13 am
$
0
0

Hello,

we were using a NI DAQ card PCI-6224 779067-01 in a workstation at a hydraulic test bench since 2005 (with Windows XP and a LabView 8.2 software app).

The workstation failed recently and we have to replace the PCI-6224.

We would like to know if a new card is a plug and play change or

if we will run into compatibility problems with a new card.

We've tried to ask NI support that question but didn't get an answer.

Thanks!

↧

Securely Mounting USB-6002

October 28, 2020, 6:18 am
$
0
0

Hi all,

 

The 6002's predecessor, the 6009, had 3 screws on the outside. Unscrew those and you could simply discard the plastic case and work with the board itself. Then, importantly, the board had 3 holes to be able to be securely screwed into a test fixture. 

IMG_2392.jpg

 

 

With the 6002, the case is completely seamless, which looks great. But how am I supposed to mount this into a fixture? First thought was Velcro but some of our test fixtures go through extreme temperature variations. And the terminal labels are printed onto the case, so even if I did manage open up this seamless case to work with only the board, that would be the next issue.

 

Thoughts?

↧
↧

How to estimate RELATIVE adc accuracy

October 28, 2020, 7:24 am
$
0
0

For an application we are using a NI 6289 DAQ which uses aggregate sampling for multiple channels. In the spec sheet a description is given how to estimate absolute measurement accuracy (see attached image). However, I am interested in the relative accuracy between multiple channels. Since the device uses an aggregate sampling method, I would assume the same circuit is used to perform the analog to digital conversion and therefore a large part of the absolute error must be equal between inputs.

 

Is there a way to estimate what the relative error will be? Or is there maybe a general rule I could apply, like taking a certain percentage of the absolute error? 

 

 

image.png

↧

DAQmx 20.0 not working with LV 2014

October 29, 2020, 3:17 pm
$
0
0

 I up dated to MAX 20.0, but after that, LabVIEW2014 no longer sees my USB-6009, but DAQ does.

Do I remove DAQmx.  Runtime engine 6.1 

Thanks for helping

Gene

↧
Search

Different reading from two different devices

October 30, 2020, 9:44 pm
$
0
0

Hello,

 

I hope you are well during these times.

 

We have a PXIe-6363 and a NI 9234. We fabricate devices and input different waveforms and measure the output. The device itself functions as a form of a resistor. We used to use NI 9234 and a function generator to measure our device performance. Since we got the PXIe-6363, we thought we could use the PXIe as both input and output. We started using PXIe because we wish to simultaneously measure 32 outputs, which was impossible using NI 9234. We made a program to generate the waveform we required and used it to feed in the input while measuring the output simultaneously.

 

Now here is the problem; when we use the NI 9234, we instantly read behavior changes. But with the new program and device, we have a problem; the input looks exactly like the output. When we use the PXIe as the input source and NI 9234 as the recorder, everything is fine, but it fails when we do both with PXIe. I believe the issue arises from the internal coupling, but I can't be sure, and I don't really know how to overcome this issue.

 

Basically, the program is the same, and as long as I use NI 9234 as the AI port and PXIe as the AO, everything goes well, but the moment I switch to PXIe for both AI and AO, everything goes south. By the way, the sampling rate and clock are the same during all measurements.

 

I appreciate any constructive comments.

 

Regards

↧

simple analog output using USB 6009

October 31, 2020, 8:15 am
$
0
0

I want to generate a triangle wave to control a programable power supply.  I want a triangle waveform of various frequency and amplitude such as, 1 cycle every minute to 1 cycle every 20 minutes. I want to set a time for repeating the cycles continuously for hours.  ex. 1 cycle every 15 minuities for 6 hours.

The Triangle Waveform .vi looks like it is exactly what.  It has offset frequency and amplitude.  Similarly, the DAQ assistant will control my 6009.

My request is how do I put these together to make a functioning control for a power supply?  I don't want someone to code this vi I want to learn how to.  I have LabView 2014 sp1 and DAQmx 17.6 Thanks to the community forum multifunctional DAQ.

Can someone help me with a general outline or plan?

I am  returning to LabView after several years, I can use labView and I'm sure that I can do this but I need a point or two in the right direction.

btw if this post belongs in a different place please let me know.

GeneL

↧
↧

Failing to write a 2 byte number to DAQ (USB 6212) using .net

November 1, 2020, 6:48 am
$
0
0

Hello,

I am failing to write a 2-byte-number to my USB 6212 DAQ in a single port+line (for example – port1/line7).

The 2 closest things I tried:

 

  1. I tried to do that using the function “WriteSingleSamplePort” from a “DigitalSingleChannelWriter”.
    I provided the function with the boolean value “true” for its auto start parameter, and an int (that I hoped will be sent bit by bit through the DAQ’s specified port+line) for its data parameter.
    The output I received from the DAQ was only the most significant bit of the least significant byte of the number (only 1 bit).
  2. I tried to do that using the function “WriteMultiSamplePort” from a “DigitalSingleChannelWriter”.
    I provided the function with the boolean value “true” for its auto start parameter, and an array of bytes (that I hoped will be sent as is through the DAQ’s specified port+line) for its data parameter.
    The output I received from the DAQ was only the most significant bit of every byte in the array.

What am I doing wrong? How can I send a number – bit by bit – through a port+line of the DAQ?

Thanks in advance,

Dolev.

↧

How to write a square signal to a single port+line in a USB 6212 DAQ?

November 1, 2020, 7:14 am
$
0
0

Hello,

 

How can I write a square signal to a single port+line in a USB 6212 DAQ?

I am writing my conde in .net.

I also need to be able to choose the frequency of the square signal.

 

Thanks in advance,

Dolev.

↧

ContWriteDigChan_Burst example throws and exception.

November 1, 2020, 7:23 am
$
0
0

Hello,

 

When I try to run the ContWriteDigChan_Burst example I get the following message from an exception trying to call this function "ConfigureHandshakingBurstExportClock":

[

"Requested value is not a supported value for this property. The property value may be invalid because it conflicts with another property.\n\n
Property: NationalInstruments.DAQmx.Timing.SampleTimingType\n
Requested Value: NationalInstruments.DAQmx.SampleTimingType.BurstHandshake\n
Possible Values: NationalInstruments.DAQmx.SampleTimingType.OnDemand\n\n
Task Name: _unnamedTask<0>\n\nStatus Code: -200077"

]

 

How can I solve this problem?

 

Thanks in advance,

Dolev.

↧
Viewing all 6887 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>