Retrigger AO finished on PCIe-6321?

Similar Questions

• constant output voltage DAQ NI PCIe-6321

  Good evening

  I am trying to output a constant tension there 10V DAQassist.
  However, as far as I know, when I want it to generate signals, it will only display waves.

  I'm relatively new to labview and can not fully use the modules of the individual drivers for DAQmx.
  Currently I use an external voltage source to power a set of scales that I'm trying out signals in LabVIEW.
  I've been somewhat successful, but a cleaner set would be to get an output of data acquisition to fully integrate the system
  I know that traditionally deplete you a game recommended by, OR like this:
  http://www.NI.com/white-paper/7138/en/

  However, I work with hardward existing on a limited budget.
  I have an acquisition of data NI PCIe-6321, with a block of connection BNC 20990.
  So, I work with BNC connectors.

  Change the AO writing single-channel > sample > DBL. That should give you a single value whenever you call the VI of Scripture. Also change the entry of data in a single digital control. Maybe call it voltage or something like that? You can probably remove the synchronisation screw DAQmx and the node property Regen as those who will be most relevant.

  A cell of 700 ohm load will draw 10 ohms = 14.3 V/700 mA, which is still well above the 5 limit my AO lines.

  A load cell is wired as a bridge. It is the equivalent of two voltage dividers. Without load on the output of the cell the two lines have equal tension: 5.00 V. When you have a 20 mV out of load cell tension on the two output lines will be 4,990 V 5,010 V (or 5,000 V and 5,020 V, according to the internal configuration). So your 6321 must be configured to accept 5,020 V (plus a bit of noise, mistakes and overload conditions). So, you will need to set it to 10 V range. On the 6341 (I happen to have the factsheet - the 6321 is probably very similar) which means a +/-10 V rank. Which translates a theoretical resolution of 0.3 mV. The output 20 mV full scale of the load cell, it comes down to resolution of 6 bits (6: 16).

  Two possible ways to improve: 1. use a preamplifier or a signal conditioner to amplify the 20 mV at a few volts. These usually have the differential amplifiers to reject common-mode 5 V. voltage They can also have hardware filters.

  2. use a power supply excitement split so that the load cell is excited by the + 5V and - 5V. This puts the common mode voltage to ~ 0 V and you can use the +/-0.2 V rank on the lines of HAVE it.  The resolution is then about 6 uV and the effective resolution on your signal is approximately 11 bits.

  Lynn

• OR PCIe-6321 custom PCB connection

  Hi you all,.

  I design a PCB custom at the interface between our sensors and our NI PCIe-6321.

  1 - can use a non shielded cable to make the connection? We work with low frequency shielded cable (less than 100 kHz) signal will cause trouble, because everything will be locked in a small space.

  2 should. what kind of receiver I use on the printed circuit to interface with cable (RC68-68)

  Thank you!

  Fabrice

  Hi Fabrice,.

  This document contains the set of our connection connectors Multifunction DAQ card.  You'll want to check out the section of connectors up 0.050 map 68 pins under the connectors and basket funds for SCSI connectors.  You can get either the right angle or vertical mounting of our website or a 3rd option part of the seller.  (We provide the part in this document number, if you want to buy it elsewhere).

  Kind regards

• error-10401 with pcie-6321

  Hello

  I have the error-10401 when I want to configure a port card PCIe-6321 (3 ports of 8 bits each).
  I use the sub - vi ' DIO-configure a port.
  I checked all the settings.
  I also tested the sub - vi 'Read a digital line' and I have the same error.
  The PC used for my tests is on Windows XP and using LabVIEW 2010 SP1 and NI DAQ MX (supplied with the PCIe-6321) 9.3.5.

  Sincerely,

  This function is part of the traditional DAQ driver obsolete. Use the DAQmx functions in your palette.

• Which DAQ driver I need to use for card PCIe-6321

  
  

  LabVIEW 7.1 is too old, 8.5, 8.6, 2009 maybe better. At the same time, you must choose the corresponding DAQ driver.

• What DAQ for my project? USB or PCIe?

  Hello

  We want to make measurements with > 200 kech. / s for all about 5seconds maximum sampling rate.

  We operate a DMD that sends a trigger signal data acquisition at the beginning of the measure.

  Everything is done in C++, Windows7 64 bit.

  So my questions:

  What DAQ we should buy:

  • NOR-USB-6211
  
  
  • NOR-USB-6281
  
  
  • NOR-PCIe-6321

  And if the FiFo data acquisition memory is 4096samples does that mean? What happens if the memory is full? All data are transferred to the PC? Will there be a lack in action? Us are out of sync then?

  ben3000 wrote:

  What DAQ we should buy

  I would go with PCIe via the USB port on any day of the week.  USB has headaches when in a permanent situation.

  ben3000 wrote:

  And if the FiFo data acquisition memory is 4096samples does that mean? What happens if the memory is full? All data are transferred to the PC? Will there be a lack in action? Us are out of sync then?

  The stamp on the card is only 4096 sampels.  If the memory is full, you will get a buffer and data overrun error will be replaced before you get to it.  The solution is to continually read data (DAQmx Read) and store this data somewhere in your program (a table variable).  For example, read all the current data acquired every 100ms.  This will help keep the clear buffer.

• the last equivalent to the PCI-6024E

  What is the last product NOR equivalent to the PCI-6024E

  OR recommend the PCIe-6321.  It's a bit the connector is different.

• The PCIe for USB 6211 OEM replacement

  Hi you all,.

  We want to change our design to use PCIe card data acquisition, since we had a few USB driver problem in the past. Is the PCIe-6321 a good match to replace the capture USB-6211-OEM card

  Is there a better alternative?

  Thank you

  Fabrice

  Hello Fabrizio,

  Thank you for taking an interest in our line of PCIe cards DAQ. I took a glance at the USB-6211 OEM and PCIe-6321 to see if they are similar in specifications and capabilities. I would say the 6321 is a good match to replace your current USB card. As long as you intend to use no more i/o lines than expected or exceeds the designated sampling rate then it should be a good substitute.

  If you need high speed sampling or more i/o lines for various tasks, then another card can better meet your needs.

  The resources below compares several of our devices (USB and PCIe) X series.

  What is NI X Series? -1. Presentation of the product

  ---

  These links may also be useful during your upgrade:

  Major differences between series E, series M and material X NI DAQ series

  ---

  Guide to upgrade NI X series (USB to USB devices however)

  ---

  Kind regards
  Alex C.

• You can use DDK?

  Hello

  I apologize if this is a duplicate message - I sent a similar yesterday but can't find it on the forums.

  I am a complete newbie and would like some advice on how to connect our PCIe-6321 on a Linux system.  Currently, we use several features of the PCIe-6321, including outputs analog and pulse finishes train.mode.  We use DAQmx on Windows 8.1, but try to Red Hat Enterprise Linux real time get more consistent results.  Is this an accurate description of our State?

  * NOR-DAQmx supports the X-Series cards, but does not support Linux.

  * NOR-DAQmx Base supports Linux, but does not support the X-Series cards.

  * MI-DAQmx Base supports two cards M-series PCIe, PCIe-6251 and PCIe-6259.  However, the file readme.txt for immediate release 15.0 (http://download.ni.com/support/softlib//multifunction_daq/nidaqmxbase/15.0/linux/README.txt) says that the pulse train finish M-Series cards feature does not work as expected, so we cannot use it.

  Is there a better alternative than writing a driver Linux and using DDK & NI_VESA to provide functionality?

  Thanks for your time!

  Dan

  ddavies wrote:

  Is this an accurate description of our State?

  * NOR-DAQmx supports the X-Series cards, but does not support Linux.

  * NOR-DAQmx Base supports Linux, but does not support the X-Series cards.

  * NOR-DAQmx Base supports two cards M-series PCIe, PCIe-6251 and PCIe-6259.  However, the file readme.txt for immediate release 15.0 (http://download.ni.com/support/softlib//multifunction_daq/nidaqmxbase/15.0/linux/README.txt) says that the pulse train finish M-Series cards feature does not work as expected, so we cannot use it.

  Is there a better alternative than writing a driver Linux and using DDK & NI-VISA to provide functionality?

  The DDK is the only way to get the Linux support for the X series devices.

  For starters, you can consider to explore the demonstration DAQ for NIWeek 2012.

• Synchronization of analog and digital output with the external sample clock

  Hello

  First of all sorry for my English, I will try to explain what I want to do.

  I want my PCIe-6321 to send two custom signals (modification sawtooths) on a mirror controller. I would also like to generate output with my card at the beginning of each tooth of saw. Everything must be synchronized with an external k-clock signal of 100 kHz. The idea is that whenever the PCI receives a trigger to external clock, it sends two analog output voltages and when he received 1024 clock ticks it will also send a pic of triggering TTL. What I do is first prepare the map and after that in a loop sending and modifing the output values of the two signals and at the same time send a digital signal Boolean in each arch, so when's done it 1024 iterations of the loop I send an event to the digital port. Attached you can see.

  The problem is that I don't know how to synchronize both. Can I use the sample clock just to the analog output? I can use sample for the two outputs clock, or do I need to use the output of the meter? If don't know how to use it here.

  If I do nothing else bad/wrong, I would be grateful for feedback.

  Thanks in advance,
  Pablo

  I don't know how but I find the solution. I'm generating more than a positive value (as I was triggered maybe very fast the oscilloscope has been absent there). If I put the sample clock of digital output to use the sampling/ao/Dev1 clock that it doesn't, but if I put to use the same source as the OD (terminal where my external clock is connected), but the trigger to start the DO to be Dev1/ao/StartTrigger this works. I don't really know why, but it does.

  Thank you for your patience and your help. I put here the final code.

• AI sample clock using to Trigger counter samples

  My basic question is: the ai\SampleClock signal is active only during the execution of a task of analog input?

  The details are:

  I have a multifunction data acquisition card series X PCIe-6321.  It is controlling an SCXI chassis and has a module SCXI-1180 and SCXI-1302, so I can control the analog inputs of the chassis but also access to the meter 4 on the map.  My application requires that I use all 4 meters to measure a frequency input signal and synchronize the samples for the analog input signals.  I created 5 tasks, 1 for AI and 1 for each counter.

  I'm using LabVIEW 8.6.1 with the latest NOR-DAQ drivers on and the operating system 64-bit Vista

  1 are there drivers or hardware restrictions that cause this solution does not work?

  2. can I use the ai\SampleClock as sample clock of entry for each task frequency?  If I do this the beginning of sampling will be synchronized?  I.e. If I each task frequency first starts, they will wait until that task to HAVE it is started before you start sampling?

  3. If this does not work, do I need to send the sample clock of the task of the AI to a line PFI (PFI1) and then use it as the special frequency sample clock input?

  I used to do option 3 when the synchronization of two cards in PXI chassis and use only the beginning of the task of the software instead of synchronization on a digital departure, given that the sample clock will control samples anyway.  I need to know if the same behavior works with the above scenario.

  Thank you

  Bob

  Prolucid Technolgies Inc.

  Hi Bob,

  I can confirm that the AI/SampleClock is available only during the execution of the task to HAVE it.  As far as other issues go:

  1. you must provide more information on what you seek to do exactly, but there is no problem with the clock of the task of analog input sampling to be used with routing counters.  I had read through the section of the X series operating manual which deals with the measures of frequency clocked at sample (see page 7-16) for more information about what really happens during this configuration to make sure that it suits your needs.

  The frequency of the signal to be measured must be at least two times faster than the sample of your task clock to HAVE.

  2. you can indeed pass the signal on all four tasks at the same time (you can check the page peripheral routes in MAX to ensure the routing restrictions).  Sampling will be synchronized four counters are started before the task to HAVE it, but counters will be armed at different times unless you configure a trigger to begin arms (see page 7-45 series X operating instructions).  I would consider using the AI/StartTrigger if you want to do.

  The effect of not to arm the counters at the same time would be a different number of periods on average on each counter for the first sample (assuming an average is enabled).  Maybe it's not a major concern, but I just wanted to point out.

  3. the itineraries are available inside the Board of directors so external routing is not necessary, you can simply specify to use the sample clock of the AI for each meter clock and roads will be done for you.  If you want to export the signal on a PFI line and new route on another line PFI, this option is also available for you, but shouldn't be necessary.

  I hope this helps you get started.  I'll make sure to take a look at Chapter 7 of the X series user manual, if you have a chance as he described how all configurations of meter of working more in detail.  If you have related questions do not hesitate to post in return.

  Best regards

  John

• Need a new acquisition of data USB multifunction device

  Hello

  Currently I use a PCIe - 6321 Multifunction DAQ hardware to control my stepper motor. I need to change the PCIe - 6321 and use the engine with a device for the acquisition of data USB multifunction bit PCIe - 6321. I'm not sure which USB model to select. Can I please get help about the choice of the right MIO USB data acquisition device that works similar to the PCIe - 6321.

  Thank you

  Bharath J S

  The 6212 differs from the 6321 somewhat on the digital side, which probably you use to control your stepper motor.  For example, it was only software DIO timed tasks and has only 2 counters with a set of features (e.g. no output meter in the buffer).

  Best regards

• How to generate two different analog signals in two different screws

  I use a card PCIe-6321 and a block of connection SCB-68. As it has two analog outputs, I use one of these outputs in a Vi to generate a square wave, and the other in an another VI to generate a sinusoidal output waveform. Each VI perfectly work separately, but if I run one then the other, the other sends no signal. Because I don't want to merge the two screws (it is more convenient to use them separately), how can I find out so that they work together (sometimes).

  Of course, independent maps with timing motors, controlled by the works of independent screws.

  Christian

• Rate for the low number of County Digital events

  Hello

  I'm trying to use the example of digital counting examples DAQmx Events.vi to count the pulses of a photon counter.  As long as the light level is high enough, it works very well. But, when the light level is below a threshold, no count is read. I checked that's not because of the photon counter by testing with an independent instrument.

  It seems like it might have something to do with the rate at which counted events are unloaded (PCIe-6321) hardware in the computer, that is, there is a minimum threshold of count indictment before such a transfer of data occurs. I'm voting for the number of levels of every 100ms.

  Any help would be appreciated.

  Thank you

  Alex

  
  

• PhysicalChannel.DIChangeDetectionSupported not correct

  Hello

  I have a PCIe-6321 with 24 digital lines. Only the first 8 specifications (port0/$line0... (7) can be used for change detection. Also when I try to use...

  myTask.Timing.ConfigureChangeDetection (up, down,

  SampleQuantityMode.ContinuousSamples);

  ... of channels do not support detection of changes (port1 and port2) I get an error on the audit.

  In my program, the user can select which device to use. I fed to the user a list of all the DILines who have the the PhysicalChannel.DIChangeDetectionSupported set to true, like this...

  PhysicalChannel physicalChannel = DaqSystem.Local.LoadPhysicalChannel("\dev1\port1\line5");

  If (physicalChannel.DIChangeDetectionSupported)

  {

  inputTerminals.Add(("\dev1\port1\line5");

  }

  However, all digital 24 for return true on PhysicalChannel.DIChangeDetectionSupported that should not be the case.

  Is this a bug or am I missing something?

  Hi Holland,

  I think it's a bug, but it is also a kind of gray area. Here is the description of this property by using LabVIEW (I guess using .NET said the same thing): "Indicates if the calendar type of change detection is supported for the physical digital input channel".

  You can use the calendar type of detection of change with port1 and port2? In normal use, the answer is no. However, there is one case where you can: detect changes without buffer. If you set the size of the buffer entry to 0, then it is possible to have lines of port1 and port2 in the task without mistakes, as long as they are not included in the side up/down lines property. (In other words, port1 and port2 may not lead the task of detection of change, but memory buffer is off, they can come along for the ride). Di ChangeDetectSupported returning true may be technically correct, but it is not particularly useful, because you need to configure additional properties to make it work.

  M series also supports detection of changes without buffer, and DI, it returns false. ChangeDetectSupported on port1 and port2. So no matter what the correct behavior is, this property does not always behave on the series of M vs X-series. I just filed a request for corrective measures, CAR #298171.

  As a solution, if your code does not work on the materials NOR 65xx, perhaps you could use DI. ChangeDetectSupported & DI. SampClkSupported? Di SampClkSupported returns false to port1 and port2 on M and X series.

  Brad