replace this data generation... NOR-DAQmx

Similar Questions

• Data acquisition tool NOR-DAQmx with Matlab R2012a

  Hello

  I'm trying to control NI USB-6211 of Matlab 2012 using NOR-DAQmx Data Acquisition tool:

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

  I'm working on win7 64 bit. And I see the device AND Measurement & Automation Explorer.

  The tool does not work: DAQ_Demo_Browser do nothing. And I got the error "unexpected or unbalanced parenthesis or support" of AcqNUpdates_nonUI.m

  What is the problem?

  Thank you and best regards,

  Arthur Shulkin

  Hi Arthur,.

  Tools OR DAQmx for Acquisition of data with the Software Inc. MATLAB® from The Mathworks, supports up to the 2008 version of the MATLAB® software.  In order to use our products DAQ Multifunction with MATLAB® software, you could get back to 2008 or earlier, or instead use the Data Acquisition Toolbox provided by The Mathworks, Inc.

  Another option would be to import your ".m" files in a node MathScript in LabVIEW and use the functions of NOR-DAQmx everything in the LabVIEW development environment.  For more information on the Module LabVIEW MathScript, you can consult the information available on this link:

  Inside of the LabVIEW MathScript RT Module

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

  Katie

• New installation on this PC, but no functions > e/s measurement > NOR-DAQmx subpalette; How to put there?

  Just installed LV8.6 on a PC and things seem fine except functions > range of measures of e/s does not contain a subpalette NOR-DAQmx. It contains only the Configuration MAX subpalette. Without creating a task, Read Channel, Start, etc etc.

  I go through stages during the installation with the DVD drivers and thought that I was installing NOR-DAQmx. MAX said that NIDAQmx is installed on the system. And I can run test MAX on a NI USB-6009 case panels.

  What should I do to get access to all NIDAQmx vi? I miss something during the installation or something?

  Thank you!

  I heard a similar problem as well... Here's the article knowledge base that describes what to do. Let me know if this corrects the problem.

• 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

• How to choose destinations for counter/timer signals in NOR-DAQmx?

  In the document M Series DAQ
  M series user manual
  622 x, NI 625 x and the materials NOR x 628
  M series user manual
  July 2008
  371022K - 01

  appears on page 7-30:

  Counter/Timer default pinout
  By default, NEITHER-DAQmx routes counters/timers and outputs inputs to the PFI pin, shown in table 7-4.
  Table 7-4. 68 peripheral pins by default Counter/Timer pines NOR-DAQmx
  Counters/timers fail-safety connector 0 PIN (name)
  0 2 CTR (PFI 12)

  You can use these default settings or select other sources and destinations for the
  counters/timers of NOR-DAQmx signals. Refer to the connection counter signals
  in the NOR-DAQmx help or the help of LabVIEW in version 8.0 or later for
  more information on how to connect your signals for common counter
  measures and generations.

  I couldn't find any hint to the appropriate command of DAQmx in the "NOR-DAQmx C reference Help" to select other destinations for counter/timer signals in NOR-DAQmx.
  Please can you tell me the DAQmx command right? Thank you very much.
  I use the NI USB-6259 M material Series DAQ, BNC end unit.

  datafriend,

  If I remember correctly, you can "free" the output terminal of default counter by calling DAQmxSetCOPulseTerm and passing an empty string in the 'data '.

  Hope that helps,

  Dan

  Edit: You can also set this to any other valid terminal (IE... "Dev1/PFI0") and to send the output to.

• 5112 does not appear under devices NOR-DAQmx

  Why does not list MAX my 5112 under NOR-DAQmx devices, but it is displayed (undefinded) PXI system? Also, I can communicate with the map using the flexible Panel so I think that the device is correctly installed.  The main problem is that I can't use this card with my 5600 because MAX reports no digitizer.

  The 5600 must be coupled with a 5142 to form a DAA.  If you must use the 5112, you can use the 5600 on its own with the pilot DAMA downconvert only mode.  Then, it would be possible to manually use the OR-Scope driver with the 5112 to read in the data, but this is not recommended.  (It would be essentially the same using a third frequency step-down converter or digitizer).

  -Christina

• NOR-DAQmx 8.0.1 undefined reference

  Hello

  I'm new with NOR-DAQmx on Linux. After reading the posts in this forum, I was able to successfully install OR-DAQmx 8.0.1 on OpenSUSE 11.0. When you run "nilsdev", I get the following list of features:

  OR PXI-6255: "Dev4.
  OR PXI-6733: "Dev3.
  OR PXI-6733: "Dev2.
  OR PXI-6713: "Dev1".

  What is correct. However, when you try to compile the following program example, using "gcc main.c:

  #include "NIDAQmx.h".
  #include
  #define DAQmxErrChk (functionCall) if (DAQmxFailed (error = (functionCall))) goto error; on the other
  int main (void) {}
  error int = 0;
  TaskHandle taskHandle = 0;
  char errBuff [2048] = {'\0'};
  float64 data [3] = {1.0,2.0,3.0};
  /*********************************************/
  DAQmx Configure Code
  /*********************************************/
  DAQmxErrChk (DAQmxCreateTask("",&taskHandle));
  DAQmxErrChk (DAQmxCreateAOVoltageChan(taskHandle,"PXI1Slot4/ao0:2","",-10.0,10.0,DAQmx_Val_Volts,""));)
  /*********************************************/
  Starting code DAQmx
  /*********************************************/
  DAQmxErrChk (DAQmxStartTask (taskHandle));
  /*********************************************/
  DAQmx write code
  /*********************************************/
  DAQmxErrChk (DAQmxWriteAnalogF64(taskHandle,1,1,10.0,DAQmx_Val_GroupByScanNumber,data,,));
  Error:
  If (DAQmxFailed (error))
  DAQmxGetExtendedErrorInfo (errBuff, 2048);
  If (taskHandle! = 0) {}
  /*********************************************/
  Stop DAQmx code
  /*********************************************/
  DAQmxStopTask (taskHandle);
  DAQmxClearTask (taskHandle);
  }
  If (DAQmxFailed (error))
  printf ("Error");
  GetChar ();
  return 0;
  }

  I get several errors about undefined references:

  main.c.text + 0 x 90): refers to 'DAQmxCreateTask' the undefined
  main.c.text + 0xdc): refers to 'DAQmxCreateAOVoltageChan' the undefined
  main.c.text + 0xf0): refers to 'DAQmxStartTask' the undefined
  main.c.text + 0 x 140): refers to 'DAQmxWriteAnalogF64' the undefined
  main.c.text + 0x15f): refers to 'DAQmxGetExtendedErrorInfo' the undefined
  main.c.text + 0 x 171): refers to 'DAQmxStopTask' the undefined
  main.c.text + 0x17c): refers to 'DAQmxClearTask' the undefined

  I have already installed OR DAQmx on a Windows XP computer and got the same errors, but could (using this post) to create the libraries needed to link against. However, I have found no information similar to that in Linux (this message seemed to understand this problem, but unfortunately, the author does not share its solution). So far, I tried various options of connection with no success '-ldl ' etc. Obviously, I'm not bind properly.

  Any help would be greatly appreciated.

  Thank you

  Grine

  I solved step connects. (Why answers always come when you almost gave up? )

  As I suspected, a liaison simple number. Compilation with 'gcc /usr/local/lib/libnidaqmx.so o main main.c', did the trick.

  I have still some errors during execution of the program, but I can probably solve these on my own.

• DASYLab w / support NOR-DAQmx NI 9227, NI 9229 & cDAQ 9174

  I am trying to use DASYLab 11 w / NOR-DAQmx 8.5 to my configuration material of NI 9227, NOR 9229 & cDAQ-9174. After decommissioning of my PC Win7 for XP that takes in charge OR-DAQmx 8.5 (the OR-DAQmx last, supported by 11 DASYLab), I discovered that NEITHER-DAQmx 8.5 does not support the cDAQ 9174. Right now, looks like I'm watered except so use LABView. Is there any other way at this time to use this hardware configuration with DASYLab or any other application?

  DASYLab V11 supports Windows 7 when you install the Service Pack (see www.dasylab.com).

  Where are we going to say that it does support NOR-DAQmx 8.5? I installed the most recent NI.com last week, and it seems to work very well. I use only simulated devices so far, but DASYLab is data collection and display correctly.

• I don't see the icon of NOR-DAQmx in measurement window in Labview 2013 (student Edition)

  Hi all:

  I installed the driver NOR-DAQmx and Labview 2013 (Student Edition). I connected an acquisition of data NI USB-6008 and tested using NOR-DAQmx and that it works correctly.

  Now, I tried to make registration of data of this device using the software Labview installed but as I open a new project and go to the block diagram and show the measure menu I can't NEITHER-DAQmx icon in the window (Menu) measurement in Labview 2013 (student Edition).

  Any suggestion?

  I enclose two screenshots.

  Help, please.

  Thank you

  In what order did you install software?

  You must install LabVIEW first, followed by DeviceDrivers!

• Clock and hw external trigger with USB-6210 on Linux with NOR-DAQmx Base?

  I have two devices USB-6210 I need to synchronize so that they both collect data exactly at the same time. I was told by support OR I can send the clock off Dev1/PFI4 and have the two USB-6210 s read the clock in through their own PFI0. I also want to trigger data collected for each device by sending a trigger off Dev1/PFI6 and have two devices to receive the signal on PFI2.

  All my attempts to try this are filled with error messages and my research online seem to say that's not possible with USB devices on NOR-DAQmx Base 3.4.0f2 on Linux.

  I "ve tried using example AI programs and those who do not seem to work either for external clocks. Here is the code I tried:

  #include "NIDAQmxBase.h"#include 
  
  #define DAQmxErrChk(functionCall) { if( DAQmxFailed(error=(functionCall)) ) { goto Error; } }
  
  int main(void){    // Task parameters    int32       error = 0;    TaskHandle  taskHandle = 0;    char        errBuff[2048]={'\0'};    int32       i;
  
      // Channel parameters    char        chan[] = "Dev1/ai0";    float64     min = -10.0;    float64     max = 10.0;
  
      // Timing parameters    char        clockSource[] = "/Dev1/PFI7";    uInt64      samplesPerChan = 1000;    float64     sampleRate = 10000.0;
  
      // Data read parameters    #define     bufferSize (uInt32)1000    float64     data[bufferSize];    int32       pointsToRead = bufferSize;    int32       pointsRead;    float64     timeout = 10.0;
  
  printf("Calling CreateTask...\n");    DAQmxErrChk (DAQmxBaseCreateTask("",&taskHandle));printf("Calling CreateAIVoltageChan...\n");    DAQmxErrChk (DAQmxBaseCreateAIVoltageChan(taskHandle,chan,"",DAQmx_Val_Cfg_Default,min,max,DAQmx_Val_Volts,NULL));printf("Calling CfgSampleClkTiming...\n");    DAQmxErrChk (DAQmxBaseCfgSampClkTiming(taskHandle,clockSource,sampleRate,DAQmx_Val_Rising,DAQmx_Val_FiniteSamps,samplesPerChan));printf("Calling StartTask...\n");    DAQmxErrChk (DAQmxBaseStartTask(taskHandle));printf("Calling ReadAnalogF64\n");    DAQmxErrChk (DAQmxBaseReadAnalogF64(taskHandle,pointsToRead,timeout,DAQmx_Val_GroupByChannel,data,bufferSize,&pointsRead,NULL));
  
      printf ("Acquired %d samples\n", pointsRead);
  
      // Just print out the first 10 points    for (i = 0; i < 10; ++i)        printf ("data[%d] = %f\n", i, data[i]);
  
  Error:    if( DAQmxFailed(error) )        DAQmxBaseGetExtendedErrorInfo(errBuff,2048);    if(taskHandle != 0) {        DAQmxBaseStopTask (taskHandle);        DAQmxBaseClearTask (taskHandle);    }    if( DAQmxFailed(error) )       printf ("DAQmxBase Error %d: %s\n", error, errBuff);    return 0;}
  

  When I run the resulting program, I see this:

  $. / acquireNScans-ExtClk
  The CreateTask call...
  Call for CreateAIVoltageChan...
  Call for CfgSampleClkTiming...
  Error-89136 DAQmxBase: route specified cannot be satisfied, because the hardware does not support it.

  For example, a clock and a trigger can be imported via one of the PFI lines by using a USB-6210 on Linux with NOR-DAQmx Base? A clock and a trigger exportable via one of the PFI lines?

  If so, does anyone have the code example illustrating how to do this, or can you at least tell me the names of the lines ("PFI0/Dev1" or other) so I can try again?

  Clues or suggestions would be helpful.

  Thank you

  -Tom

  The clockSource in the example specifies an output rather than an input channel channel. Change source "/ Dev1 / PFI0" solved the problem.

  Please close this post.

• Why using the driver NOR-DAQmx ANSI C functions in a thread causes a deadlock?

  Firstly, apologies if this is bad advice, but it seemed the closest fit.

  I use MSVC 2008 Express with the library in ANSI C NI DAQmx for some analog output with a box USB-6009. I create a thread to handle the signal generation is based on fixed time. My main thread running the user interface. I found that I get intermittent blockages in release, so that libraries mode NOR are responsible (in the second thread) and I use MSVCRT features (on the main thread). My test code is attached as "deadlock2.cpp".

  I used WinDbg to try to find the cause of the deadlock. Traces of the battery of my two sons are attached as t1_stack.txt and t2_stack.txt.

  It seems that the MSVCRT localtime() function uses a lock when it is called for the first time and then went to lock the Windows DLL loader lock. At the same time libraries NOR (or less libraries mxs) are responsible for locking the charger DLL is being held. The mxsutils library uses getcwd() which seems to try to block something the MSVCRT and therefore my two sons are now deadlocked.

  I can probably work around this by calling the localtime() and the NOR-DAQmx functions before I spawn my second thread so that the DLLs are already loaded in the process. However, I have no guarantee of this to continue working if something changes in the future, and if there are any locks going on finally having the DllMain() calls for a thread hanging may still cause a deadlock. If my results are correct, is it likely that NEITHER would fix the dll for not trying to make something complex in their DllMain()?

  According to NI Measurement and Automation Explorer, I'm under DAQmx libraries v9.3.5f2. I download the latest version now to try, but it will take time.

  Hi dmcminn,

  Thank you for the comprehensive and detailed bug report. I was able to reproduce the problem with NOR-DAQmx 9.6 using the code you posted. I reported it to the R & D team suitable as CAR #366538.

  I agree with your analysis of the problem. Getcwd() so the first call to __tzset() acquired _ENV_LOCK, which Microsoft has documented as the "lock for environment variables. __tzset() also called GetTimeZoneInformation(), which can load additional libraries, that you have demonstrated.

  Here are a couple more possible solutions, but they are not great:

  • Link to the static version of the CRT (/ MT instead of /MD). This would bind a separate copy of the lock of the CRT table in your program, and DAQmx would continue to use the lock to MSVCR90.dll table. They use more of the same _ENV_LOCK.
  • Build using a different version of Microsoft Visual C++ (for example 2005 or 2010). MSVCR80.dll MSVCR90.dll and MSVCR100.dll own separate copies of the lock of the CRT table.

  Whatever it is, it does not eliminate the fact that mxsutils called the CRT while now the loader lock, and this function CRT acquires another lock.

  Furthermore, the forum Multifunction DAQ is a better place to ask questions DAQmx.

  Brad

• How to calibrate the PCI-6110 with NOR-DAQmx

  Hello

  I am a new user of the PCI-6110 Council tries to run the calibration using LabVIEW procedure. I look at the document "Calibration" on the page of the manuals for the Board of Directors,

  http://sine.NI.com/NIPs/nisearchservlet?nistype=psrelcon&NID=11888&lang=us&q=FQL: 28locale % 3Aen % 29 + AND + % 28phwebnt % 3 A 1081 + OR + phwebnt % 3 A 7075% 29 + AND + 28nicontenttype % 3Aproductmanual % 29 + AND + % 28docstatus % 3Acurrent % 29% 20RANK % 20nilangs: en & title = NOR + PCI-6110 + manual

  One of the first steps in the document is to call the AI_Configure command to set the input mode, beach, etc. I'm using LabVIEW 8.5 with the NOR-DAQmx software, and I can not find the command (which, in LabVIEW, seems to be "AI Config.vi") anywhere. The calibration paper was written in 2003, and I gather from Google searches (please, correct me if wrong) that this command is actually a part of NOR-DAQ traditional, who was replaced by driver OR DAQmx.

  My question is this: what is the equivalent to AI_Configure command in the latest software? Is it perhaps a subsequent document describing how to calibrate using NOR-DAQmx?

  Thanks much for any help.

  Tom McLaughlin

  Hi Tom,

  The calibration Procedure series B, E, M, S, which is also linked from this page, describes how to calibrate the PCI-6110 with NOR-DAQmx.

  Brad

• acquisition of continuous data from Ni-DAQmx

  Hello

  I use LV 8.0 and am acquire signals of an ecg machine using the NOR-DAQmx with a sampling rate of 1000smpls/s... the thing I want to do is, get the table with the complete information and move on to another VI for analysis... But the problem I am facing is, as the sampling rate is 1000 and my DAQmx is a while loop I get just 1000 values in the table and not the complete table with the record for more than 60 seconds...

  Can someone tell me please a method to get all the values in the table, I mean for the session of any acquisition (maybe 5 minutes)...

  Kind regards

  Nitzy...

  Hello!

  Use something like this:

  

  But the DAQ Assistant, putting your own code DAQmx (for something as simple as buying 1000 samples, DAQ Assistant is good!)

  Make sure the Array function to build is set to concatenate entries, also convert Dynamic Data has the value table 1 d of scalars-automatic (but this is only important with the DAQ Assistant)

  I hope this helps!

• NOR-DAQ traditional to NOR-DAQmx

  I am a neophyte of LabVIEW.  I inherited a previous employee long gone from the company, so that I work a LabVIEW project.  The project has been written using NOR-traditional DAQ and I need some update OR-DAQmx so that it is 64-bit capable.  Of course, I ran into trouble with the VI first that I try to put in level.

  This VI was built with LabVIEW 2011 SP1 and I need to replace the Config AI, I start, I Read, Index channel, control and HAVE clear screw with their equivalents of NOR-DAQmx.  Upgrade to SP1 2013 LabVIEW is possible if that makes things easier.

  Now here is the tricky part.  I want to keep the terminals on this VI even if possible.  This VI is used in several places and a few different programs and I want to make the change as minimally invasive as possible.  If possible, I want the changes must be made within this VI.

  I am looking for any help and or advice. Thank you.

  First, abandon all hope to keep the same connector components.  It is possible, but it's foolish to try. (Just trust me, OK?)

  Read these articles in the knowledge base

  http://www.NI.com/white-paper/3021/en/

  http://www.NI.com/white-paper/4342/en/

  What you're trying requires skills usually not developed in a neophyte of LabVIEW. (And you start with the 'Spaghetti' code - this is not 'Fun') Do an internship of audit and meet with your representative local of NOR.  Chances are that some local expert advice will point you away from some serious mistakes.

  Take care

• Maximum latency to read/write for PCI-DIO-32HS with NOR-DAQmx?

  I was asked to evaluate using the PCI-DIO-32HS and NOR-DAQmx on MacOS X to essentially close a control loop.  My first concern is whether or not it can run fast enough.

  So my questions are: what is the maximum latency from the moment of receiving a signal strobe reading data from external hardware, then read a single 16-bit sample and sending it upward by NOR-DAQ to a user space application?  And, similarly, what is the maximum latency of sending a unique 16-bit value from a space application user down through NOR-DAQ, then write a port and affirming a strobe signal of external-data writing material?

  Thank you.

  Hi AliasMe,

  Thanks for posting and welcome to the Forums EITHER!

  Do you need to process the data in the software and generate a value on this basis?  DIO-32HS (alias PCI-6533) offers in the buffer of inputs and outputs, but you'd have a latency in your control system relying on the OS to do treatment.  Since this period is dependent on the system, I can't give a specification for the amount of time it would take.  However, integrating data in memory, processing and writing back to the card would likely be on the order of several milliseconds.

  Generally, we recommend FPGA in situations of control like this, so you can do all the processing in hardware.  However, if provide you more details on your request we can look into all the options available.

  -John