Acquisition continues using NOR-traditional DAQ

Similar Questions

• NOR-traditional DAQ will work with a USB-6008?

  Hi guys,.

  I have ordered a USB-6008 and I would use it with the NOR-DAQ traditional 7.4.4 instead of MX. Is this supported?

  Thank you

  Jim

  LV 8.6

  LV 8.01

  LV 7.1

  TS 4.1

  Jim,

  No, traditional DAQ isn't USB compatible, 6008.

  You can use DAQmx base instead, but I wouldn't recommend it.

  hope this helps,

  Norbert

• Question about the Acquisition continues through NOR-DAQmx

  I'm a bit new to NIDAQmx methodology and I was wondering if someone could could give me some advice on accelerating certain measures of tension that I do with a case of DAQ NI USB-6363.

  I have a python script that controls and takes measurements with a few pieces of equipment of laboratory by GPIB and also takes measurements in the area of DAQ OR DAQmx via (I use a library wrapper called pylibdaqmx that interfaces with the libraries C native).  As I do with the data acquisition unit is 32 k samples at 2 MHz with a differential pair to AI0.  An example of code that performs this operation is:

  from nidaqmx import AnalogInputTask
  
  # set up task & input channeltask = AnalogInputTask()
  task.create_voltage_channel(phys_channel='Dev1/ai0', terminal='diff',       min_val=0., max_val=5.)
  task.configure_timing_sample_clock(rate=2e6, sample_mode='finite',
        samples_per_channel=32000)
  
  for i in range(number_of_loops):  < ... set up/adjust instruments ... >  task.start()  # returns an array of 32k float64 samples  # (same as DAQmxReadAnalogF64 in the C API)  data = task.read(32000)  task.stop()  < ... process data ... >
  
  # clear task, release resourcestask.clear()del task< ... etc ... >
  

  The code works fine and I can all the 32 k spot samples, but if I want to repeat this step several times in a loop, I start and stop the job every time, which takes some time and is really slow down my overall measure.

  I thought that maybe there is a way to speed up by configuring the task for continuous sample mode and just read from the channel when I want the data, but when I configure the sample for the continuous mode clock and you issue the command of reading, NOR-DAQmx gives me an error saying that the samples are no longer available , and I need to slow the rate of acquisition or increase the size of the buffer.  (I'm guessing the API wants to shoot the first 32 k samples in the buffer zone, but they have already been replaced at the time wherever I can playback control).

  What I wonder is: How can I configure the task to make the box DAQ acquire samples continuously, but give me only the last 32 samples buffer on demand k?  Looks like I'm missing something basic here, maybe some kind of trigger that I need to put in place before reading?  It doesn't seem like it should be hard to do, but as I said, I'm kinda a newbie to this.

  I understand the implementation of python that I use is not something that is supported by NEITHER, but if someone could give me some examples of how to perform a measure like this in LabView or C (or any other ideas you have to accelerate such action), I can test in these environments and to implement on my own with python.

  Thanks in advance!

  Toki

  This is something I do a bit, but I can only describe how I would do it in LabVIEW - I'm no help on the details of the C function prototypes or the python wrapper.

  In LabVIEW, there are accessed via the 'DAQmx Read property node' properties that help to implement.  One is the Mode "crush" which I'm sure must be set before performing the operation.  The other pair is known as "RelativeTo" and "Offset" and they allow you to specify what part of the CQI data buffer to read data from.   If you the config to "RelativeTo" = 'most recent sample' and 'Offset' =-32000, then whenever you read 32000 samples, they are the very latest 32000 which are already available in the buffer of data acq.  Between the readings, the task is free to overwrite the old data indefinitely.

  Note that you will need to do this continuous sampling mode and that you can explicitly set a buffer size smaller than the default which will choose DAQmx based on your fast sampling rate.

  An excerpt from LV 2010:

  

  -Kevin P

• Labview2009 and NOR-traditional DAQ

  Hello friends NOR!

  I am running LV2009 on a machine with win7 32 bit with a DAQ PCI-MIO-16-1 card.  We have a program for the calibration of pressure transducers, but he wrote with the NOR-DAQ traditional.  I plan on writing a new program to make the calibrations, but until then, I would use the old.

  I see that some DAQ hardware can support two pilots, including the device that I mentioned above (http://download.ni.com/support/softlib//multifunction_daq/nidaqmx/7.4/readme.html). I also found the location to download the traditional NOR-DAQ driver for 32 bit Win7 (http://digital.ni.com/public.nsf/allkb/8EC9E81C3DE4E619862573930083BD7A). Based on the information I have at the moment, it seems that it will work.

  However, I remember seeing something that says that if I install a different driver, the current will be replaced (I can't find the original source).  I also met this warning: "NOR recommend not to install NOR-DAQmx on the same machine that the driver beta OR-DAQ traditional (old). (http://digital.ni.com/public.nsf/allkb/8EC9E81C3DE4E619862573930083BD7A)

  I'm not interested in screwing up this machine because I'm not the only person who uses it.  I don't have enough experience NOR the appeal without checking first with those who do it here on the forum.

  Thanks for the help.

  Darren

  You have a deployment problem.

  my strong recommendation would be not to change the drivers on the computer that works and develop your code of replacement to new hardware.

  Yes, you might get away with developing a new solution on a working machine but it's almost garunteed to cause some conflict somewhere with a driver.  Unless you know what everyone does with a system that works AND you really understand NOR drivers and what changes exactly where and in what version you ask some "educational" by developing a functional system necessary.

• Problem with traditional DAQ passage to DAQmx using NOR-6534

  I'm moving the traditional following of DAQ code to DAQmx:

  

  This code is used to send data to program a FPGA using a PCI OR-6534 DIO.  This code works like a charm, but when I try to write the equivalent code using DAQmx (in LV 8.6 as well) it does not work.  I don't get any errors, but the FPGA do not program.

  The General procedure is as follows:

  The value of all the lines on the Port exit 0

  Set up the mode of transfer to low Active

  Write the data in the buffer

  Send the data using the internal clock of 10 MHz of the 6534 (6533 is no longer used, but the code was never updated)

  Wait until the output is made

  Disable the task

  In DAQmx I configured as such:

  

  Any ideas on what has changed in DAQmx or what I am doing wrong?

  Looking at your code traditional DAQ once more, he is actually setting up handshaking vs just a straight sample clock.  The Config VI Mode with the "clock polarity" setting is not a sample generated at a certain rate clock, but instead, it's a protocol handshaking attack or the trailing edge.  TDAQ had much more flexibility with what DAQmx and some handshaking protocols are not transferable to DAQmx completely.

  So when you say the configuration of your device in TDAQ bass Active transfer mode, I don't see what is happening in the code TDAQ.  It's really a negotiation protocol of unknown polarity (given that you use a control and I don't see the default value in the public Service).

  You can try to determine which protocol handshake TDAQ you use first, then determine if there is an equivalent for DAQmx.  The three modes that cannot be transferred are level ACK, tip, or long pulse modes.  These have ACK leading REQ, which is not possible for DAQmx to manage.  You can read more in the user guide for the 6534 and starting on page 3 and 4 are the comparison of the different modes of handshake.

  Then move forward options are do not migrate or to download a beta driver TDAQ, if you perform the migration for the purposes of the compatibility of the OS.

  Hope this helps, let me know what other spawn of this.  Thank you.

• Data before release for NOR-6133 trigger material and acquisition continue?

  I use the pxi of NOR-6133 can acquire data on 7 channels continuously with ai0 as the trigger without problems. The acquisition is triggered. What I have to do is collect a finite amount of data before triggering immediately until the trigger is detected.

  Is it possible to do without the help of a software solution. I watched go over acquisition and using the integrated trigger reference but that is not suitable for my needs because it just seems to change the first section of data to be 'post trigger' to 'pre trigger.

  A software solution that I already know how to do is the last resort to try to reduce the demand for processor and keep the hardware triggering.

  Thank you

  By using the "reference trigger" is the right solution.

  So can you please explain a little more in detail why it does not work in your case?

  Christian

• Determine the number of traditional DAQ hardware using Labview.

  Hello

  Anyone can answer the question:

  Regarding materials traditional DAQ, for example the DMM OR-4060, how

  can I programmatically determine the number of device which can be seen in MAX?

  With the help of Labview 8.5, I looked into the following function libraries:

  NOR-DMM

  VISA

  NOR-ModInst

  None of the libraries above seem to provide access the number of traditional DAQ hardware

  property, which is automatically assigned.

  Background:

  I have a 18 PXI chassis containing 2 DMM, in housing 3 and 14.

  The DMM may be a mixture of type OR-4060 or NOR-4070.

  The system is controlled by a Teststand sequence employing IVI - DMM

  steps.

  When you set the IVI logical name step, I am referring to IVI device defined Sessions

  Max - rutime determined.

  Labview VISA functions using I can determine the model, i.e. 4060 or 4070.

  Because the DMM just locate into the slots 3 or 14, then the devices NOR-4070

  are accessible using the following descriptors of resources: PXI1Slot3 or

  PXISlot14.

  (The 4070 is compatible DAQmX.)

  So for devices OR-4070, I can predefine 2 Sessions of IVI device, knowing

  It will be sufficient for all occasions, when I run my Teststand sequence, which will be

  determine what device session to use at run time.

  But I'm stuck for the NOR-4060.

  At the Session of the device, I have to give a descriptor of resource the following

  format: DAQ::x (where x is the device number)

  I could create device 18 sessions each reference to a different DAQ::x, but to select

  the good pair during execution, I would need to programmatically determine the device

  number, i.e. the value of x.

  Where my question.

  The closest I came to a solution was an entry of the Knowledge Base that said that the

  Assigned device number would be the same as the slot number, providing the

  Number of the device had not previously configured manually.

  Unfortunately, our device numbers have been changed manually and maybe in the future.

  All popular solutions.

  Gary.

  Hi Gary,.

  Good afternoon and I hope that your well today.

  Thanks for your post and I want to help you solve your problems.

  I don't think there is just a function that you can use to identify and collect information on all cards with your. For traditional DAQ devices in particular I suggest using the Information.vi of DAQ devices get.

  If you look at this link,

  SAL posted an example VI entitled, find dev trad.vi.

  You can get information such as serial number, Dev name and the Base address.

  The assistance of the respective drivers to collect information you could generate an array of strings with the information that you need all the slots.

  Please let me know if this is useful at all,

• Problem to stop the task of continuous using API C DAQMx data acquisition

  I'm doing the acquisition of data in the PCIe-6536 continuously using DAQMx C API. But whenever I try to erase the task and put end to my application, program stops and it is not completed by the Task Manager and task killer applications. Can someone help me with this?

  Sameer

  Hi John,.

  Thank you for your concerns. the example attached also created the same problem. Then I run the test of the device to the MAX and it failed. Then I realized that there is something wrong with the installation. I simply uninstalled the card and installed on the other PCI-e slot. This time, self test has been successful and so did my request.

  So my problem has been resolved

  Again thank you for your quick response.

  Sameer

• Synchronize two E-card with traditional DAQ series

  Hello

  I have a PCI-6052E and a PCI-6071E and I have a Matlab program that interacts with traditional hardware DAQ driver cards.

  It is possible to synchronize the two cards use RTSI or something? If so, what should I do in matlab to achieve?

  I'm a bit confused, because I don't know if this is only possible using DAQmx.

  Thank you!

  Hi zlyhere,

  Using DAQmx would definitely be the best choice.

  In terms of using C vs the Data Acquisition Toolbox for The MathWorks Inc. Matlab® Software, I would recommend the Toolbox for ease of use.  The MathWorks develops the Toolbox, so they must have documents on how the maps can be synchronized.

  If you find that you need more features, you can fall back to C.  Documentation is available at

  "" "" Start menu"all programs" National Instruments "NOR-DAQ" support textual Code ' using NOR-DAQmx C reference

  MATLAB® is a registered trademark of The MathWorks, Inc.

  See you soon!

• Why do my pci-6052e configured as traditional daq and daqmx in MAX?

  I have an old computer of three year with 1 GB of RAM and a 3.00 GHz running Windows Server 2003.  It has already been used for experiments of movement control and has a 7333 motion control card and a PCI-6052E.  Now all I want to do is sample data of a pressure sensor and a flow meter using the PCI-6052E, but for some reason, this card is configured in MAX as a DAQmx device and a traditional DAQ (Leagcy) deivce.  Unfortunately, when I write the LabVIEW 8.2 VI, the only available data acquisition tools are DAQmx and Max my two instruments are installed in traditional DAQ.

  If there is only one card PCI-6052E in the computer, why MAX card PCI-6052E called dev3 DAQmx and a card PCI-6052E dev1 in traditional DAQ?  How can I fix?

  Cpesko,

  I am happy here, you have a few things working under Windows Server 2003.  We do not however have any software under this OS except what is listed here.

  DAQmx and TDAQ are 2 different drivers and this is the behavior expected that devices that support both would be present in the title of each driver.

• How can I configure a PFI to high on a 6602 traditional DAQ board

  Dear all,

  I'm using LabVIEW 8.5 on 32-bit Windows XP with a data NEITHER the 6602 acquisition Committee. In the past, I used DAQmx but for compatibility with older software, I need to do a few simple things using traditional DAQ, which I never used. Specifically, I want to make a simple VI which affects 5 PFI high when the user presses a button and then low when they press a second time. How do I put 5 PFI for output and then write faithful to her?

  Thank you

  Ed

  Dear all,

  Apparently its also simple to use digital writing line VI. However, the non-obvious thing is the width of the Board 6602 32 port is not the default value 8. Buried in the LabVIEW help files is a list of widths of physical port to fall on. As the cave of bats. In the picture as an attachment to the super simple VI, I did the 16 designated PFI 16. Good to know.

  Best,

  Ed

• Determine the number of channels selected for traditional DAQ

  The blocks 'DAQmx task' and "Traditional DAQ Channel" look pretty similar (see attachments). The DAQmx block ist an individual selection of channels and I am able to determine the number of selected channels.

  Now I am trying to determine the number of selected channels to a traditional DAQ, but the property DAQmx block does not work here. I already tried the trad to some form of blocks. Range of data acquisition, but failed.

  Any idea?

  

  In traditional DAQ, there are several ways of specifying the list of channels. Assuming that your picture shows how you use your channel list is just a string of delimited by commas. Wire a constant to a string array node worksheet and specify "comma" as the separator and the number of columns must tell you the number of channels.

  Ben

• Difficult to see the details for the traditional DAQ functions

  I'm migrating a Tradtional DAQ to DAQmx applications and manage to LV 8.6 to see 'details' for traditional data acquisition functions.  I looked to the traditional manual online user DAQ & a few other pubs and impossible to find a good explanation, parameters of entry and exit to functions.  Can someone help me?

  Thank you... PacMan

  In talking with Kent Lau, an applications engineer at NOR, told me I was missing the file nidaq.chm for a reason any.  Even after trying it from reinstalling drivers traditional DAQ of Q4, 2008 software distribution, it is still missing.  So, I installed an older version of the driver on a computer that has never had LabVIEW, then copied the file nidaq.chm in the folder 8.6\Help of LabVIEW & was able to then see the traditional DAQ work details.  Thanks Kent!

• Acquisition of data NOR usb 6008: a strange problem: mxwcgoutrunsilent.VI is not respected

  Expensive OR

  Today, I bought an acquisition of data NOR usb 6008

  and I'm using labview in 2011
  the problem is appear when after I end the process of configuration of the i/o data acquisition Wizard

  the following image shows the mxwcgoutrunsilent.VI is ignored and an error has occurred

  

  someone can help provide this VI for me

  What is the complete labview modules can also so I could do a real time data acquisition

  Best regards

  mangood,

  You received an error code? If so, what is it? What version of NOR-DAQmx driver you have installed? It seems your driver potentially incorrectly installed, and you may need to reinstall the driver.

  Here is the link to the latest version of the NOR-DAQmx driver: http://www.ni.com/download/ni-daqmx-9.8/4297/en/

• Find the difference of pressure between the two transducers using a NI DAQ 6008

  Hello

  First of all, I'm a relatively inexperienced LabVIEW Developer, so my apologies in advance if this message does not have something, or otherwise lacks clarity.

  I try to develop a VI as follows the pressure difference between the 2 EME 3100 pressure sensors (4-20 my), related to two different pressure lines, using a NO-DAQ 6008. I would like for the acquisition of data to read the two transducers, then have him find VI the differential and write this differential in an Excel file.

  The data sheet for these sensors may be found at: http://www.gemssensors.com/Products/Pressure/Pressure-Tranducers/Sputtered-thin-film/~/media/GemsNA/...  It is a 3-wire system, with a voltage between 8 - 24V. I use an external power supply of generic brand to power sensors, which provides a maximum of 24V @ 4A.

  I drifted my physical connection (for the two transducers) this thread http://forums.ni.com/t5/LabVIEW/I-am-having-trouble-Omega-PX4200-Pressure-Transducers-to-where-I/m-p... and am relatively certain of the accuracy of the information. For purposes of signal conditioning, I use a 500 Ohm resistor between the signal of each transducer and the Earth wire.  On the side of software, I use the latest version of LabVIEW (2011) as well as MAX on a Windows 7 64-bit machine.

  In an ideal world, the sampling rate would be as high as possible, but 4 samples per second would suffice for all purposes useful.

  Given this goal, are there any sample of VI (especially for MAX, which I have not yet used) who would be similar/applicable to this project, specifically, regarding setting a sampling frequency, calibration of the transducers or affecting the pins/channels appropriate? All resources would be greatly appreciated.

  Kind regards

  MG Wilkinson

  Measure the voltage between the two resistance (resistance by probe 4-20 MA) using the differential inputs of the x 600.

  When you configure the task, you can read several entries at once, by entering in "Dev_ / AI0:1" in the physical channels and using the "several channels / {unique |}". multiple} samples"polymorphic instance.

  600 x can read 1kS/sec.

  Do maths/conversions on the table, and then simply subtract the two tables.

  Could also take some samples (10-100) at 1 kHz and their average together, give you a smaller rate effective sampling but with less noise.

  A loop of producer-consumer would be good architecture here, let the daqmx reading live in a loop and sends the data via a queue to a 2nd consumer that performs mathematical operations and write to a file.