Problem with NOR-DAQmx Base on Scientific Linux 3.4

Similar Questions

• 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.

• Firmware of switching of NOR-DAQmx Base on Linux to the USB-6221

  Our Windows machines are locked - even as developers, we without administrator privileges.  Which is updated from the impossible firmware via the Windows Device Manager.  On the other hand, we have total control on our Linux machines.

  Is it possible to download and check out the images of the firmware on Linux?  In particular, I need to move a USB-6221 to NOR-DAQmx Base.  I couldn't find all the instructions to do this on Linux.

  wlbaker

  I had a moment of complete Dyslexics your first post - powered external USB DAQ playback devices (USB-622 x, USB-625 x USB-628 x) are not supported under Linux (by DAQmx 8.0.1 or DAQmx Base 3.3), while DAQ USB (USB-621 x) bus-powered devices are supported by only DAQmx Base. The Readme files for the two drivers list the devices on which they based [1] [2].

  The USB-6212 case is the closest to the USB-6221 match, although if you don't have extenstive digital i/o in your application, the USB-6211 housing would also be a good fit.

  [1] DAQmx 8.0.1 Readme
  http://FTP.NI.com/support/softlib/multifunction_daq/nidaqmx/8.0.1%20Linux%20Only/Readme.txt

  [2] DAQmx Base 3.3 Readme
  http://FTP.NI.com/support/softlib/multifunction_daq/nidaqmxbase/3.3/Linux/Readme.txt

• Impossible to compile examples of NOR-DAQmx Base 3.4 installation of Red Hat

  By typing 'make' in/usr/local/natinst/nidaqmxbase/examples/I gives the following error: $ make gcc-I /... / include - O2 - lnidaqmxbase o acquireNScans/usr/bin/ld: /usr/local/lib/libnidaqmxbase.so incompatible to jump when you're looking for a lnidaqmxbase - / usr/bin/ld: cannot find lnidaqmxbase - collect2: ld returned 1 exit status is: * [acquireNScans] error 1 it seems that libraries are not compatible with my version of Red Hat/gcc. Are pre-built libraries are built during installation? Don

  In case anyone else has this problem, I managed to solve it by (1) adding - m32 for INDICATORS in the Makefile and (2) by following these instructions:

  «During the generation of the examples, the linker can point out that liblvrtdark.so»
  unresolved symbols in the Standard C++ library.  It is a known issue as the
  NOR-DAQmx Base 3.4 on Red Hat Enterprise Linux WS 4.  For good link and run
  examples, make the following changes to the Makefile.

  Add /usr/local/lib/LabVIEW-2010/patchlib/libstdc++.so.6 to nilibs.
  Add - Wl, - rpath, ' / usr/local/lib/LabVIEW-2010/patchlib "for flags. "since the README file:

  http://FTP.NI.com/support/softlib/multifunction_daq/nidaqmxbase/3.4/Linux/Readme.txt

  Don

• NOR-DAQmx Base on 18 Fedora i386

  I try to install NOR-DAQmx Base 3.6.0 - f0 on 18 Fedora i386.

  (I used so far with success OR-DAQmx Base on a Fedora 14 i386 3.6.5)

  When I run the installation of NI-VISA program in the nivisa subdirectory, I get this message:

  Pre Installation.
  After the Installation.
  Pre Installation...
  Préparation...                       ################################# [100%]
  the file/usr/local/natinst comes into conflict with the installation of nipxipfki attempts - 1.5.1 - f0.i386 and nimxdfi - 1.12.0 - f0.i386
  the file/usr/local/natinst comes into conflict with the installation of nispyi attempts - 2.8.0 - f0.i386 and nipxipfki - 1.5.1 - f0.i386
  the file/usr/local/natinst comes into conflict with the installation of nipxipfi attempts - 1.5.1 - f0.i386 and niapalerri - 2.1.1 - f0.i386
  the file/usr/local/natinst comes into conflict with the installation of niiotracei attempts - 3.0.1 - f0.i386 and nipxirmi - 2.7.3 - f0.i386
  Error when installing NI-VISA for Linux 5.2.0f0.

  So something was wrong with RPM in the next line of the SETUP file:

  $RPM - Uvh $RPMOpts $installPackageList

  It seems that there is conflict bewteen packages...

  Any idea?

  I have to install all of those packages to run the NI USB-6008 case?

  Yes, someone in this group could have fallen on the same issue.

  Hope this helps,

• 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

• problem with loopback test base with NOR-6008

  I recently started to use DAQmx in c# .NET 4.0 with NOR-6008 USB DAQ. I tried a loopback test by connecting output to an analog input analog and tried readign the signal from the output to the entrance but did not send the signal (or maybe a problem with the code). The analog input readign reads a random value rather than the value entered by the user for the output. I connected ao0 and ai3 on data acquisition. Here's the code.

  private void button1_Click (object sender, EventArgs e)

  {

  Task analogOutTask = newTask();

  AOChannel myAOChannel = analogOutTask.AOChannels.CreateVoltageChannel ("Dev1/ao0", "myAOChannel", 0, 5, AOVoltageUnits.Volts);

  AnalogSingleChannelWriter writer = newAnalogSingleChannelWriter (analogOutTask.Stream);

  Double analogDataOut;

  analogDataOut = Convert.ToDouble (AnalogOut.Text);

  writer. WriteSingleSample (analogDataOut, true);

  }

  Private Sub button2_Click (ByVal sender As Object, EventArgs e)

  {

  Task analogInTask = newTask();

  AIChannel myAIChannel = analogInTask.AIChannels.CreateVoltageChannel ("Dev1/ai3", "myAIChannel", AITerminalConfiguration.Differential, 0, 5, AIVoltageUnits.Volts);

  AnalogSingleChannelReader reader = newAnalogSingleChannelReader (analogInTask.Stream);

  Double analogDataIn is reader. ReadSingleSample();

  AnalogIn.Text = analogDataIn.ToString ();

  }

  Hello

  I built an application using your code (with task.verify) and it works beautifully.

  Have you tried different channels of inputs/outputs?

  

  Curt

• NOR-DAQmx Base 2.0 and Win Mobile 5

  Hello

  Can someone tell me if NEITHER-DAQmx Base 2.0 is compatible with Win Mobile 5 devices?

  I try to capture analog voltages and my app very well builds and the charges for the PDA and the PDA does not see the DAQ (6062E) PCMCIA card that I use.

  I ran the installer of 'Base' which has copied the Base/s driver file in the PDA (and I have the basic task OK configuration in VI), but the PDA comes up with an error "unrecognized card". I deleted the driver/s of the PDA database and reinstalled them but without success.

  Is that all just because the Base 2.0 is not compatible with Win Mobile 5?

  Is there a way I can get 2.1 base to work with LV-Pro-8 and PDA - 8 or y at - it another way I can get the drivers on the PDA that handles the card under Win Mobile 5 6062.

  Any help would be greatly appreciated,

  Thank you

  Paul.

  Hi James.

  Sorry for my late reply.

  The problems are a combination of LV8.0, Base 2.0 and hardware failure.

  In the end I went with LV8.6, Base 3.2 and Win mobile 5 with 6024E PCMCIA card or 6062E.

  The basic hardware config utility is a bit different and took a little of violin to go. I also found some documents that lead me the wrong path re save for the project or unit basic tasks, but now I understand it's all good.

  I don't know if your customer still has problems, but I'm more than happy to help if I can.

  Thanks for your help as well.

  Best regards

  Paul.

• 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

• NOR-DAQmx Base: Thermocouples

  Hello. I use NEITHER-DAQmx Base for mac on LabVIEW 8.2 and I struggle to get the differential voltage for thermocouples type k of data acquisition that I use. The conversion is easy using the thermocouple vi, but somehow the pressure readings seem not just.

  When using CQI. example of samples vi continuous or acquire it only sample vi, the measured voltage I get just a regular temperature thermocouple are 0 and - 0.00048 (especially remains on 0 if); which for me, is not look right. The tension of the CJC reading also reads about 0.3 V (I don't really know how it works yet, but here it is if it helps).

  A sales engineer field came the other day and seemed to have it. When tinker around with the example vi, he kept getting small positive values that seem to work. In addition, when it is combined with LabVIEW 6.0, the data acquisition system works very well.

  Please, any help would be appreciated.

  K type thermocouples have a maximum temperature of-200 to + 1250 ° C.  The output goes to about-6 mV to + 51 mV for this temperature range.  If you need to use the 0 to 100 mV or + / 50 range mV on your data acquisition card, regardless of the better matches the actual temperatures you will be measuring.

  If you don't you not explicitly connected resistances of polarization, they aren't there.  Look at page 4 to 6 of the user's Guide of SCB - 68 for the advanced features for more information on the connection of thermocouples.

  Lynn

• Trigger with NOR-DAQmx in Ansi C/C++ and OR USB-6210

  Hello

  We need to read an analog signal each time a trigger signal it is does not know how to get the trigger to work. Here is the code that we have found so far:

  ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

  ...
  DAQmxErrChk (DAQmxCreateAIVoltageChan (analogInputTaskHandle, "Dev1/ai0", "AI0', DAQmx_Val_Diff,-10, 10, DAQmx_Val_Volts, NULL));

  Int32 numSampsPerChan = 20;
  uInt64 sampsPerChan = numSampsPerChan;
  float64 timeout = 0; Time in seconds to wait for the function read String-> 0 try to read only once; -1 wait infinitely;
  bool32 fillMode = DAQmx_Val_GroupByChannel; Reading non-interlaced channel
  const uInt32 arraySizeInSamples = 20; Number of samples that are read
  float64 analogValuesFromDevice [arraySizeInSamples];
  sampsPerChanRead of Int32;
  bool32 * reserved = NULL;

  char startTrigger [256] = ' / PFI0/Dev1;
  int startEdge = DAQmx_Val_Rising; rising edge

  DAQmxErrChk (DAQmxCfgSampClkTiming (analogInputTaskHandle, "", 10000.0, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps, 10));

  DAQmxErrChk (DAQmxCfgDigEdgeStartTrig (analogInputTaskHandle, startTrigger, startEdge));

  DAQmxErrChk (DAQmxStartTask (analogInputTaskHandle));

  DAQmxErrChk (DAQmxReadAnalogF64 (analogInputTaskHandle, numSampsPerChan, timeout, fillMode, analogValuesFromDevice, arraySizeInSamples, & sampsPerChanRead, reserved));

  DAQmxErrChk (DAQmxStopTask (analogInputTaskHandle));

  Frees the memory of the task
  DAQmxErrChk (DAQmxClearTask (analogInputTaskHandle));

  ...

  ////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////

  This is the error message we receive.

  DAQmx error: relation to the outbreak of the reference or the beginning reading
  position of pre-trigger samples before the acquisition is completed.

  Wait until the acquisition is complete before reading or increase your reading timeo
  UT. Additionally, make sure that the equipment is set up and wired correctly, the signal for
  the reference trigger is correct, and that the reference trigger occurs during th
  e device is data acquisition.
  Property: DAQmx_Read_RelativeTo
  Value: DAQmx_Val_FirstPretrigSamp

  Task name: ReadAnalogInput

  State code:-200281

  Can you tell us how to expect the acquisition supplement or increase our reading timeout? We think these are the problems we face.

  Thanks for all your help.

  Update:

  We use is no longer a trigger, so it's resolved.

  We believe that we receive at the origin of the mistake because we weren't using a TTL signal.

• problem with card wireless & sound in mandriva linux 2008

  
  

  The audio driver will be a HD audio then try to install the ALSA driver and intel driver wireless driver can be downloaded from the website maintained by Intel. To find the site just google it.

  See you soon

• 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

• Why the basis of NOR-DAQmx for LabVIEW options are grayed out using a custom installation (with Action: Skip)?

  I try to install NOR-DAQmx Base 3.7.0 LabVIEW 2013 (LV is installed). When I try to install Standard, it does not settle for LabVIEW (only the tools common and C and USB), but gives a successful installation message.

  

  When I try to custom installation, all the "...". for LabVIEW 20XX"options are unchecked, dimmed and Action says 'Skip '.

  

  I try this on a 2011 MacBook Air 11 '' running OS 10.9. LabVIEW works very well.

  Thanks for your suggestions.

  Hello

  DAQmx Base gray if poster LabVIEW Installer is not detected on the LabVIEW support system. Did you install LabVIEW and then move it to another location?

  The LV location controls DAQmx Base is...

  / Applications / National Instruments/LabVIEW LabVIEW.app

  Thank you

  Steven T.

• 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.