Negative outputs analog of the PCI-6229

Similar Questions

• Measurement of the temperature with the PCI-6229

  I was announced in an old thread and do not receive and answer, so I thought I try a new.

  Link to the old thread: http://forums.ni.com/ni/board/message?board.id=250&thread.id=14920&view=by_date_ascending&page=1

  I'm trying to measure temperatures using thermocouples using the PCI-6229 and I use two SBC-68LPR to make the connection.  They are not reference on them joints.

  After moving down from enugh to careful reading of the old thread I mentioned above and I think I knew what I should do.  Here's what I do now:

  Create a task - DAQmxCreateTask

  Create a channel for this task - DAQmxCreateAIThrmstrChanVex thermistor

  Create a number of channels of thermocouple for this task (DAQmxCreateAIThrmcplChan) using the cjcsource DAQmx_Val_Chan option and specifying the string thermistor as the source channel

  Start this task - DAQmxStartTask

  Get the temperatures - DAQmxReadAnalogF64

  Stop the task - DAQmxStopTask

  Disable the task - DAQmxClearTask

  I have not yet hooked, but I doubt that it is the cause of the error.

  A few more details (pardon my Delphi):

  Create the channel of the thermistor

  TmPcName: = ' Dev1/IA.19 ";

  Secret: = DAQmxCreateAIThrmstrChanVex)
  TcTaskHandle, / / task handle
  @TmPcName, / / physical channel name
  @TmChName, / / name of channel
  -80,                                   // Min range
  80,                                    // Max range
  DAQmx_Val_DegC, / / units, ° C
  DAQmx_Val_ResistanceConfiguration_4Wire, / / 2-wire, 4-wire, etc.
  DAQmx_Val_ExcitationSource_External, / / source of excitement, external
  1, / / value of excitement
  9.376e-4,                         // a
  2.208e-4,                         // b
  1.276e-7,                         // c
  30000);                            Resistance of reference

  Creation of the channel of thermocouple:

  TcPcName: = ' Dev1/ai23;

  Secret: = DAQmxCreateAIThrmcplChan)
  TcTaskHandle, / / task handle
  @TcPcName, / / physical channel name
  '',                                     // Channel name
  0,                                    // Min range
  1000, / / Max range
  DAQmx_Val_DegC, / / units
  DAQmx_Val_DegC, / / type of Thermocouple
  DAQmx_Val_Chan, / / source CJC
  25, / / value of CYC, so DAQxm_Val_ConstVal
  @TmPcName);             CJC channel, so DAQxm_Val_Chan

  It looks like 4 scales is required for voltage excitement thermistor measurements.

  In addition, it seems that external excitation is necessary in my case, PCI-6229.

  Everything works if I use a CJCConstant.  When I do this I use the same code to create channels of thermocouple, but I spend creating the channel of the thermistor.  When I try to use a CJCChannel I get an error saying "value required is not supported for this property value," which occurs when I call DAQmxStartTask.  I don't have no idea of what this message refers to and the best I can tell the properties that I've specified sense.  The constant termistor are from actual thermistor, that I found on travailleursduweb.com.

  I could also use some help to know how to connect the thermistor.  Looks like I need to fab, a thermistor circuit myself, with a stable voltage to power the termistor and use a double-ended analog and reference to the channel.

  Thank you

  Mike

  The error of thermocouple type was a type-o in the post.   Thanks for catching it.

  I think I found the problem.

  I wrote a small program to test for Thermistors and I went to using the routine exctation of tension for a common routine of excitement (... IEX instead of... Vex).  I had been by specifying a minimum value less than 0.  I changed it from-80 to 0, and it works now.  However, I got an error in division by zero, intermittently, when you read a thermistor channel.  The error is not in my code.  It occurs when you call DAQmxReadAnalogF64 for the first time and I'm not all mathematical related to this call.  I'm still looking into it.

• Limit the audio via the acquisition of data, what is the analog output rate of the pci-6014?

  Hello

  I'm trying out audio buffers thanks to an acquisition of data pci-6014. Audio files normally have a sampling rate of 44.1 kHz, but I noticed that when I try to exit, at this rate, that I get an overflow error. I checked the datasheet and it shows a rate of output of 10 K samples per second, way too slow!

  This device 6014 is quite expensive but are still unable to a stereo sound output signal... ? Is there a way to bypass this limit? It is not sensible to pay $1000 one another.

  See you soon.

  I don't think there is a way to increase the analogue of rates. The 6014 is old enough. A better card and cheaper, would be the 6221.

• The drift in analog of the PCI-6221

  Hello

  The VI described below makes the measurement of three analog channels. Then it calculates (if - then)/ So B,

  where TR = Ai2 Ai1/channel channel

  and Bi = channel Ai0

  When TR = therefore, the average reading should be zero, but in fact what I get is the behavior showed in the chart below.

  I use PCI 6221, BNC-2110 and LabVIEW 7.1.

  This may be the cause of this drift? Could you help me fix this problem?

  Thank you

  Marcelo.

  You see on a derivative of uV ~ 40 on the map ±10V range?

  It would be nice in the care of the accuracy of the 6221.  However, it sounds like the drift occurs over time.  If you leave it plugged in long enough tensions continue to drift or they stabilize?

  It could very well be that the battery voltage is what is adrift.  However, if you add help polarization resistors so it is possible for you to accumulate small amounts of load on CDA - what values of resistance have you tried?  You can also consider CSR and connect the terminals of the battery (-) ground HAVE common to avoid having to use polarization resistors.

  Best regards

• The reference output analog of the PXI-67xx (AO GND) isolated or linked to the mass chassis/installation?

  I am trying to simulate a radiation of 3 mV/V power pressure transducers (excitement is + 10V, full range should therefore be 0mV at 30mV).  I am looking for a PXI analog output device high number of channels (PXI-6723, possibly) who doesn't have the down side of the analog output channels linked to the land of installation (differential channels of AO).  The plan was to use a voltage across the divider circuit of +/-10V output card AO to +/-50mV.  I use a card AO 16-channel, 12-bit which has all the Commons AO related to the mass of the PXI chassis and Earth installation.  The DC of the signal part I want it, but there are about 80-100mVpp of noise (from the ground connection) riding on it.  I also tried a PXI-6115 card we had at hand and its reference AO are related hard chassis-same result with the noise of the Earth.  Is PXI - 6723 AO GND isolated from the land of the chassis/installation?  Even if all GNDs AO are shared on the Board, this solution should be much better than having a noisy ground reference.

  Any ideas?  Alternatives to simulate a floating, the millivolt output device?

  Thank you!

  The reference of the AO of the 6723 relates to Earth; pages exit track to track analog insulation research, only a handful of AO devices have an isolated field (the business is a low channel count).

  -Ciao

• Slow outputs analog on the cDAQ-9178

  My control of the C language application calls the DAQmx API 200 times per second to update some AOs, using the following call:

  DAQmxWriteAnalogF64 (taskHandle,

  1, TRUE, 0.0, DAQmx_Val_GroupByScanNumber, data, NULL, NULL);

  On a system with a single chassis cDAQ-9178 and two modules OR 9264 AO, it works correctly with a task of up to 4 channels. If I add channels to the AO job, the flow slows down below 200 Hz (5 ms). Here are the times:

  Chans ms

  8 6.8

  16 13.4

  32 26.9

  How can I write 1 sample per channel, more than 32 channels, all 5 ms? It's a control application that meets the entries, so I can't write several samples per call.

  Thank you.

  
  

• Impossible to get CB-68LP play nicely with PCI-6229

  Hi, I am using a PCI-6229 for 4 analog outputs (call them AO0 - AO3) and 4 inputs analog (call them AI0 - AI3), where I have 2 blocks of connection are the BNC-2110 and CB-68LP.

  For now, they are wired like this:

  1 BNC-2110 inserted in slot 0 (HAVE 0-15) of the PCI-6229

  2 CB-68LP plugged into the connector 1 (HAVE 16-31) of the PCI-6229

  The BNC-2110 things part works perfectly. I use it with success for all 4 of the analog inputs and 2 analog outputs. The connection was intuitively simple, by choosing the PCI-6229 s AO0 and AO1 channel assignments in the DAQ Assistant of LabVIEW and simply by plugging in my wiring in terminals AO0 and AO1 BNC to BNC-2110 connector block.

  However, I can't understand how to wire the CB-68LP for analog output for AO2 and AO3 channels.

  My basic, stripped stable approach to used the NOR Measurement & Automation Explorer:

  -J' opened the dialog box indicating "Test panels: NI PCI-6229: 'Dev 1'.

  -I click the "Analog output" section and choose from the drop-down list "Channel Name"

  -J' I "Dev1/ao0" channels and "Dev1/ao1" working with terminals AO0 and AO1 BNC - 2110, respectively

  - but can't figure out how to wire the CB-68LP to work with the 'Dev1/ao2' and ' Dev1/ao3' channels

  I think at least part of my problem is that I can't find a pinout for the CB-68LP naming scheme.

  Never mind, figured out that list of pins of the PCI-6229 22 and 55 on connector 1 match 22-55 CB-68LP screw terminals, allowing an AO2 (i.e. physical channel "Dev1/ao2"). Similar to AO3 idea. In retrospect, quite simple really problem solved.

• DAQ + DAC... OR PCI-6143 + PCI-6731 vs only PCI-6229?

  Hi, I try to control a XYZ stage using a feedback program in LabVIEW and wonder about my computer card options for the acquisition of analog data (1) analog inputs and 2 digital outputs.

  One suggestion I've gotten is the NI PCI-6143 of data acquisition of analog inputs, more the NI PCI-6731 for digital output to analog.

  However, I wonder if the NI PCI-6229 can do the same thing that these 2 cards together can do and for a fraction of their price. The only question I can foresee is a slower rate with the PCI-6229. Other problems with this idea?

  Please notify.

  Thank you!

  Hello clas004,

  The PCI-6229 looks like it would be ideal for your situation.  According to the two connectors are concerned, the 6229 has two front end connectors.  If you check the 622 x specifications OR and look at the stitching down, you can see what is sent to each connector.  Since you need 3 analog outputs, you'll need a cable and a block of endings for the second connector as two of the AO signals are on each connector. For cost-efficiency, if the noise is less of a factor for the signals of the AO, you might consider the block of CB-68LP-unshielded endings for the second connection.

  As far as the compatibility of the PI functions are concerned, it is likely that they will work, but PI would be able to answer this question the best.

  I hope this is useful,

• Problem of clock sample e/s digital PCI-6229

  Hello

  I use PCI-6229. I need to use the digital output channel to generate pulses of 20 kHz 30% duty cycle.

  The datasheet shows the sample clock frequency can be 1 M Hz. But in may, only 100KHzTimebase may work to generate. But acctually I need at least 200K Hz.

  I've done the Vi is attached. Can someone help me with this problem?

  Thank you

  Hello ossoo,

  The PCI-6229 is not a timing engine digital to create a digital task which runs at 1 MHz, you must use an external sample clock.  However, one thing you can do is generate a pulse train at your desired frequency using a meter integrated 6229 and then using this output meter as the sample for your task digital clock.  Take a look at the attached amendment, I made to your VI which shows how to build your digital task to 1 MHz using the meter on board.  You can change the frequency of the train of impulses of the meter in order to change the frequency of your outputs digital.  Please let me know if you have any questions.

  Kind regards

• Minimum requirements of DAQmx PCI 6229

  I am currently converting our are configured to use a PCI-6229 for the analog inputs.  We have LABView 7.1 on a Windows XP operating system.  I looked at the latest version of DAQmx that would work with LABView 7.1 and found it DAQmx 8.9.  When I run the DAQ Assistant I gen an ERROR of INITIALIZATION:

  Some components required for publishing are missing.  For more information, please contact National Instruments.

  Article OR suggest that I put to update to the latest version of the software driver, DAQmx 9.3, to solve this problem, but I do not think that this version works with LABView 7.1.

  Does anyone know if the PCI-6229 will work with DAQmx 8.9?

  Any newer version of DAQmx will work with LABView 7.1?

  And if there is another way to fix the DAQ Assistant error?

  Thank you Ahead of time,

  WindResearcher

  
  

• problem setting daq virtual channel to PCI-6229

  Hello

  I have trouble to set up a virtual channel to PCI-6229.  It comes to LABVIEW 7.1.  I am updating a VI in LABVIEW 6.1 to 7.1.  When I go through the Assistant of MAX, I get it configured how exactly it is about the version of LABVIEW 6.1, but then under device, there are not listed, although MAX recognizes the labview map in the NOR-DAQmx devices section.

  Please help me on this one, as I'm new to labview and cannot find another way for this VI to work but with virtual Renault.

  Thank you

  Hello

  The PCI-6229 is a map of series M and it is supported only by DAQmx Device Driver

  Since you MENTIONED that it is the virtual channels in LabVIEW 6.1, your old VI must use of the API OR-DAQ traditional (old)

  Howerver the transition from the traditional DAQ in the DAQmx will certainly not be a major concern for you

  Since you're new to LabVIEW, you can quickly adapt to the use of DAQmx

  The following links should help you to learn and get into programming with DAQmx

  http://zone.NI.com/DevZone/CDA/tut/p/ID/3021

  http://digital.NI.com/public.nsf/allkb/BB06D0620FDD7ADB86256D2700557BFC

  http://zone.NI.com/DevZone/CDA/tut/p/ID/5375

  http://zone.NI.com/DevZone/CDA/tut/p/ID/2744

  http://zone.NI.com/DevZone/CDA/tut/p/ID/4342

  No matter what other assistanceyou seek, let us know

  Kind regards

  Dev

• Map of the AREA-6229

  I have the PCI-6229 of data acquisition card. I want to work with the card without LabView or Measurement Studio but with Visual Studio Express 2010 - c# and... What do I need other

  and how to get it?

  When you installed the DAQmx driver, do you really watch what has been installed to support code or simply leave it by default? Do a repair on installation and I think you should be able to explicitly select to install the .NET support.

• What is the analog input of the NI PCI-6229 impedance?

  I am trying to determine the effect of a 12 K resistor that is in series with an analog input of an NI PCI-6229 data acquisition card.  Resistance of 12K seems to be part of a RC filter.  I have a 0-10 VDC source this supply circuit.  What is the impedance of the analog input of the NI PCI-6229 data acquisition card?  If it makes any difference, the analog input is connected in differential mode with a 180K resistor to Gnd AI.

  Thank you

  RWB

  Hi, RWB,.

  The input impedance is classified in the specifications 10 GOhm.  So, the effect of your k 12 resistance should be relatively low.  Take care!

• 6259 analog integrated Output error with the sample clock

  I run into some problems outputing a sinusoid of analog output with my acquisition of data using the sampleclock aboard. At one point, I was able to get the vi works pretty good and repeatable. When revisited however, I started to see error that the driver could not provide the unit with the points quickly. I was running at 250 k 1 k sampling rate a tone to one, but it seems only to be able to get about 20 k, sampling frequency. This creates a pretty rough signal, expecially when the rate fell to 8 k. I produce only 1 second of data.

  See attached bmp. The I/O moved references aren't channels of tasks. Could be the problem? I'm a little frustrated because he has to be a very simple to create vi and I'm having all sorts of problems with it.

  Hi klessm1,

  I want to stress that the behavior you're seeing is atypical - under normal circumstances, DMA transfers must take place fast enough to keep the data in the FIFO embedded permanently until at least the max (2.86 MHz single channel) sampling rate.  After saying that the error you receive indicates that we get no data for the 6259 fast enough for some reason - there are a few options at this point, it should get you operational:

  Remove the need to transfer data to the device.  As Sarah suggested, you can do so by regenerating the on-board FIFO.  The FIFO output on the 6259 is 8 191 samples (shared between the channels), so if you build a periodic signal and this is a sufficient number of samples to characterize a period then this should be a viable option.

  Try using interrupts instead of DMA.  This may seem paradoxical since DMA is generally the fastest method of data transfer on our DAQ hardware, but something rings the Bell with the DMA transfer from your computer to the 6259.  I imagine that you will actually have a faster rate using interrupts if that is the case.

  You can configure the appliance to use only the quantity of memory onboard or interruptions using a channel property node DAQmx (Analog Output > General Properties > advanced > memory and data transfer)

  Implement a delay between the start of the task and the first sample.  If the problem is with the first DMA transfer latency (and not the total throughput on the PCI bus), then adding a delay before attempting to write the first sample should solve the problem.  Some motherboards have been found to have a latency higher than the others (so the question of Sarah #3).

  You can configure the delay with the property node Trigger DAQmx (start > more > Delay / delay units).  This applies even if you do not explicitly have a configured start trigger.

  I think the three above are good ideas to try depending on what you need exactly.  I would also check for updates to the BIOS available for your motherboard that could address the issue (but it would be something that the manufacturer would be more known).  I hope this help - made - know us how it goes!

  -John

• Blocking of blue screen with the analog voltage (WinXP, PCI-6251)

  Hello

  I'm looking to solve a problem of blue screen with my measure blocking
  application, which I am developing with C++. Blocking seems manifest
  a little random after a variable amount (500-50 000) of voltage analog
  measures. My application needs to make a huge amount of these digitally
  trigger voltage measures after a certain period of time, and I'm using a
  unique
  task to do. The task is stopped and started after a single measure
  is
  which is done around 10 000 - 100 000 times per second. For this
  because I do synchronized with the PCI-6251 map data acquisition and
  one
  Ztec oscilloscope card. It seems that the probability of blocking could be
  associated with
  the frequency of measurements of voltage that I perform.

  The
  the app itself is multithreaded, but I'm blocking concurrent access
  TO
  the card with lock - all access to the card are behind a single mutex

  lock, so simultaneous access is blocked. In any case, all data acquisition
  access
  o the map is initially a single thread, which is dedicated to the acquisition of data
  operations.

  I also did stress tests with Ztec scope map, which does not
  result
  in all the problems. I also disabled in order of acquisition of Ztec map data
  TO
  Make sure that it wasn't the card scope, the origin of the problems - the problem
  persistent, so this seems to point towards the direction of the nidaq map.

  The deadlock appeared when I used the original supplied with drivers
  the
  card. I installed the latest drivers (removed the device from)
  ' Windows
  Device Manager and your application Measurement & Automation, reinstalled), but the blue screen still appears.

  Blue screen gives me a few debug data, but it does not mention any

  files .dll or something that would be of course point to a specific file (driver). I enclose at least partially matching code snippets.

  Hello again! I've been in contact with a local support person, who suggested that I have use DAQmx_Val_FiniteSamps instead of DAQmx_Val_HWTimedSinglePoint. I don't have any other changes, but this (see below) and the problem disappeared, so this seems to be an acceptable solution, because I don't see at all why not do this way. (Thanks Henry!)

  DAQmxErrChk (DAQmxCfgSampClkTiming (task_reader, NULL, 100000.0, DAQmx_Val_Rising, DAQmx_Val_HWTimedSinglePoint, 1));
  DAQmxErrChk (DAQmxCfgSampClkTiming (task_reader, NULL, 100000.0, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps, 2));