DAQmx base missing tdms

Similar Questions

• DaqMX Base read like waveform missing ability for Mac installation

  Now I have a VI running a signal with an average of program using tables as data types and the program takes up some memory, I was curious to try it by sampling the data as waveform as opposed to a table data types.

  The drop-down list of the DaqMXbase Read has no option of waveform and for some reason any 'DAQmx Read (analog 1 Wfm NChan NSamp d) .vi"is missing from the installation.  How to add this feature, or where I can find this specific file?

  Thank you.

  DAQmx DAQmx base drivers different and are, therefore, have different features. Since you are using Mac, you can use the DAQmx Base driver that has limited compared to the DAQmx features.

• Difference between DAQMX and DAQMX base. Task list empty

  Hello

  Can someone please explain the difference between NOR-DAQMX and NIDAQMX base?

  I have recently installed Labview10.0 and NOR-DAQMX base on linux opensuse 11.4 3.4.0. Everythinng works very well. The device is recognized by labview and I put my controller and chassis using nipxiconfig. The DAQ assistant function is missing and also the drop down task and channels is empty, even if I create a new task using the basic NIDAQMX configuration utility.

  Can you get it someone please let me know where I'm going wrong?

  Thank you

  The DAQ Assistant is a Windows program only, DAQmx only.  It not Linux or with DAQmx Base.  DAQmx basic tasks and channels are a little different (I think) counterparts DAQmx.  The fall to the bottom of the list of basic parts, or is it only DAQmx?

  Lynn

• DAQmx Base 3.2 on Ubuntu for PCIe 6259

  I'm trying to install the package DAQmx Base 3.2 for card PCIe-6259 on Ubuntu with kernel 2.6.27 - 14-generic. I followed the suggestions of other messages to convert the *.deb packages software packages, install these and rpm install the original rpm on top packages. All this worked fine, and I can update the driver with updateNIDrivers, which prints the message as shown below. But when I try lsdaq, I get the error (as also reported by many others):

  --------------------------------

  Detect of National Instruments DAQ devices

  Find the following materials:

  libnipalu.so, failed to initialize

  Maybe you need to run updateNIDrivers

  / usr/local/bin/lsdaq: line 7: 25859 Aborted/etc/natinst/nidaqmxbase/bin/daqmxbase_listdevices

  --------------------------------

  As a note, I have NOT more than 4 GB of memory installed, and I use the mem = 4096M option at boot of the kernel.

  The logs show:

  Apr 24 00:25:43 xenomai daqmxbase_listdevices: [libnipalu.so.2.3] WARNING: source/lib/linux/linLoadKern.cpp:168 - libKernelDriverLoad: cannot open nipalk, errno: 2

  Apr 24 00:25:43 xenomai daqmxbase_listdevices: [libnipalu.so.2.3] WARNING: source/initcln/initcln.cpp:147 - Posix: Init kInitClnPackage: kernel: failure! status =-50204

  Apr 24 00:25:43 xenomai daqmxbase_listdevices: [libnipalu.so.2.3] WARNING: source/package/posix/ulibEntry.cpp:199 - initialize: unable to load OR-PAL. status =-50204

  For example, libnipalu.so does not load because of problems with nipalk. I added the niSystemReport output in this file.

  How could I continue debugging this issue? Any help would be greatly appreciated!

  -Stefan

  Print updateNIDrivers:

  ------------------------------------

  Configuration for linux kernel version 2.6.27 - 14-generic.

  ********************************* NOTE *********************************

  With the help of the kernel headers found in lib/modules/2.6.27-14-generic/build.

  If this does not match the location of the headers-2.6.27 - 14-generic,.

  Then set KERNELHEADERS in your environment to point to the location

  headers for the kernel to set KERNELTARGET as the version of the

  kernel for which compile and run him again. / configure.

  ********************************* NOTE *********************************

  A-team reparent_to_init(): no

  Number of arguments for do_munmap(): 3

  pte_offset function: pte_offset_kernel()

  Levels in the table on page: 4

  A-team remap_pfn_range: Yes

  Name altsetting USB: cur_altsetting

  A-team usb_get_intf(): Yes

  A-team intf_cache usb_host_config Member: Yes

  A-team members in usb_device ep: Yes

  Export kernel usb_set_configuration(): no

  USB_CTRL_GET_TIMEOUT units: msec

  A-team member owner in usb_driver: no

  A-team put_page_testzero(): Yes

  Kernel mutex method: Yes

  A-team kthread: Yes

  A-team config.h: no

  A-team ioctl32.h: no

  IRQ managers pt_regs: no

  A-team work_struct and delayed_work: Yes

  Core supports the fault method in vm_operations_struct: Yes

  Save the configuration to Makefile.in

  If the recorded values are incorrect, they can be changed before running make.

  Uninstalling OR KAL (nation): fact

  / bin/rm - rf Insertion objects

  Update OR-KAL:

  KAL-NOR up-to-date.

  Update of client modules:

  / usr/local/natinst/nation/SRC

  Updated NiViPciK.ko to date.

  / usr/local/natinst/nation/SRC

  Updated NiViPxiK.ko to date.

  Restart is necessary to ensure that National Instruments drivers

  have been updated.

  After a while of research and trying, I finally found a solution:

  (1) install Ubuntu 9.04

  (2) downgrade to kernel 2.6.24.2 source at http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.24.2.tar.bz2

  3.2 Basic 3) get NIDAQMX and NIVISA 4.5, convert RPM to deb with alien package, install the deb package, install RPMS on top (make sure that Ubuntu does not use the shell of dashboard (dpkg - reconfigure dash))

  (4) missing patch of symbolic links for additional modules such as in/usr/local/natinst/nation/etc/clientkdb, you will find:

  NICORE/nidimk - unversioned.o-> /usr/local/natinst/.nicore/src/objects/nidimk-unversioned.o

  NICORE/niorbk - unversioned.o-> /usr/local/natinst/.nicore/src/objects/niorbk-unversioned.o

  nipple/nipalk - unversioned.o-> /usr/local/natinst/nipal/src/objects/nipalk-unversioned.o

  nipxi/nipxirmk - unversioned.o-> /usr/local/natinst/nipxi/src/objects/nipxirmk-unversioned.o

  vxipnp/NiViPciK - unversioned.o-> /usr/local/vxipnp/src/objects/NiViPciK-unversioned.o

  (5) then the updateNIDrivers should compile fine and lsdaq works

  (6) as an aside, I could even patching this kernel with xenomai http://download.gna.org/xenomai/stable/xenomai-2.4.2.tar.bz2 , and the driver OR still works.

  A few minor corrections may be needed in this procedure to solve the problems of compiling because of the gcc - 4.3.3, but all errors may be google and trivially fixed by minimal changes in the makefiles or C-files.

• Switch firmware DAQmx/DAQmx Base 6009

  I installed the driver NOR-DAQmx base v3.2 on Ubuntu 8.10.  Thanks to all the previous posters for the detailed instructions!

  lsdaq is not the 6009, lsusb shows that it is connected.

  I understand that I have to re - join the 6009 'DAQmx base' by updating the firmware.  I ran the FWUpdate provided with 3.2, but like the lsdaq, he does not see my 6009.

  I installed DAQmx v8.8 on my windows xp machine and is seeking to swap the firmware by following the instructions in the KB 3NE7GJMY as shown below:

  Solution:
  NOR-DAQmx 7, 5-8, 5 (recommended method)

  Switching of NOR-DAQmx Base

  1. Open the Windows Device Manager:
     • Right-click on desktop and select Properties.
     • Select the hardware tab and click Device Manager.
  2. Find the USB-6008 box under data acquisition devices.
  3. Right click on the USB-6008 box and choose Update driver...
  4. In the context menu which appears, select install from a list or specific location and click Next. (Note: this isn't the default selection)
  5. In the next window, choose do not search. I will choose the driver to install and click Next. (Note: this isn't the default selection)
  6. Select IO multifunction NI USB-6008 and click Next.
  7. This will put the USB-6008 housing in a mode of reception of the NOR-DAQmx Base firmware. The device should now appear in the device under Device USB of NI-VISAManager. If he does not appear or appears with a yellow exclamation mark, please disconnect the USB cable from the device and plug it in again. This should make the device list again properly.

  Steps 1-5 works well, but my options for the selection in step 6 is "USB-6009' not ' NI USB-6008 multifunction IO.

  I select "USB-6009" but when I hit "Next", it updates the driver immediately and said the "end of the upgrade wizard to update material.  Then, it tells me that "the wizard has finished installing the software for USB-6009" when I click on 'Finish', the wizard closes and I'm right back where I started.  I never have a chance to go to the step 7 above.

  The Alternative in KB 3NE7GJMY method suggests using MAX and do the following:

  "" Select Tools > Configuration of NOR-DAQmx > Driver NOR-DAQmx USB selector ".

  When I do a popup appears that reminds me of 491FPHB9 KB that points then back to KB 3NE7GJMY and again, I am right where I started.

  It was supposed to be the easy part.  The KBs reference DAQmx v8.5 and low.  I have 8.8.  If something has changed?

  Thanks in advance,

  Mike

  Hi Mike,.

  I just want to confirm that with Windows Xp
  SP3 DAQmx 8.9 (latest version installed) and DAQmx Base 3.2 I could
  to get a USB-6009 to a DAQmxBase device.  I was able to
  re - associate the driver so that the device show in Device Manager
  as IO NI USB-6009 multifunction.  I just followed the directions in
  3NE7GJMY KO OF #.  My only recommendation at this point would be to check your version numbers on DAQmx and DAQmx Base.  It doesn't sound like DAQmx base was not installed correctly, because we do not see the second driver in Device Manager.  I suggest you to re-setup DAQmx Base (note there is no need to uninstall DAQmx for this).   Let's try and see if we can get the second driver is displayed

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

• Error 200428 creating task in DAQmx Base

  I wrote a basic program that captures a voltage signal, plots and written to a file, but when I run it, I get this error message:

  "Error-200428 occurred at the value passed to the control task/channels is not valid."

  I enclose a copy of my VI. At first, I do not have the VI 'DAQmx Base create a task' in the block diagram, and I was getting the above error. After a search through some documents, it seems that the problem was that I had to put the VI to "Create a task" in when you use DAQmx Base. Unfortunately when I did, I kept getting the same error.

  Y at - it something I'm doing wrong here?

  Here is my software/hardware information:

  Operating system: Mac OS X 10.11.14

  Material: NEITHER myDAQ

  Software: LabVIEW 15.0 (64-bit)

  Drivers: DAQmx Base 15 OR 15.5, 15.5 OR-488 VISA. 2 NOR-DAQmx for myDAQ on Mac OS X (all for OS X)

  AliMoradi wrote:

  I wrote a basic program that captures a voltage signal, plots and written to a file, but when I run it, I get this error message:

  "Error-200428 occurred at the value passed to the control task/channels is not valid."

  Here is my software/hardware information:

  Operating system: Mac OS X 10.11.14

  Material: NEITHER myDAQ

  Software: LabVIEW 15.0 (64-bit)

  Drivers: DAQmx Base 15 OR 15.5, 15.5 OR-488 VISA. 2 NOR-DAQmx for myDAQ on Mac OS X (all for OS X)

  Hi Ali.

  You encounter this error, because NEITHER-DAQmx Base does not support unit OR-myDAQ . You have NEITHER-DAQmx for myDAQ installed, however, that supports this feature.

  See the instructions here to confirm that the device and the pilot communicate properly:

  Get started with NOR-DAQmx for myDAQ on Mac OS X

  http://www.NI.com/Tutorial/52345/en/

• Problem with NOR-DAQmx Base on Scientific Linux 3.4

  Hello everyone.

  I'm trying to install the driver OR-DAQmx Base 3.4 on Scientific Linux 6.0, but I got these errors:

  

  On this text said that Scientific Linux 5.4 and 5.5 is supported.

  Can anyone help me or 6.0 is not supported?

  Hello decadence,

  Thank you for posting.  Your post, it seems that the problem occurred while trying to install NI VISA 5.0.  Unfortunately, the only versions of Linux that are officially supported by our pilots and implemented to date are those listed in the Readme of each product.  In the Readme for NEITHER VISA 5.0, Scientific Linux versions 5.x are supported, but Scientific Linux 6.0 is not in this list, nor in the Readme for DAQmx Base 3.4.  I hope this helps.

  Kind regards

  Joe S.

• Installed OR-DAQmx Base 15.0 for Device Manager (PCI-MIO-16-4 & PCI 6713) Watch always point of exclamation on both cards.

  There are two cards I have installed on this computer. The two cards are PCI-MIO-16-4 & PCI-6713. They all have two cable connecting to each other on top. The current operating system is Windows 7 64-bit with 4 GB of memory.  I went to the drivers OR support and typed in the serial number for these two cards. The two cards came back with the same drivers. That is NEITHER-DAQmx Base 15.0. Installed the driver NOR-DAQmx Base 15.0, but shows Device Manager always the exclamation point on those two cards. So, I tried to search for new hardware and get a message saying cannot install driver. I also tried to restart. Help, please.

  Thank you

  hms168

  Drivers install successfully. Thank you!

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

• 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

• Problem DAQmx Base Examples

  Who what to compile the Mac DAQmx Base examples?

  I get a lot of errors. See annex.

  Hi Ben_01880,

  It is a known issue with Mac OSX and DAQmx Base. It happens when OS x starts in the 64-bit kernel instead of the 32-bit kernel which requires DAQmx Base. Here is a workaround in the DAQmx Base Help file:

  "Xcode 3.2 or later by default to 64-bit (x86_64) architecture at the call of the GCC on 32-bit OSX 10.6 If the 64-bit system hardware." This will result in errors during compilation. To resolve these errors, force gcc to use the 32-bit (i386) architecture in OSX for 32-bit installations by adding "-arch i386' for flags in your Makefile:"

  "Flags =-O2-arch i386 '.

  There is also an article on Mac support site that shows how to force OS x to start the 32-bit kernel on a basis of by-boot:

  http://support.Apple.com/kb/ht3773

  Finally, there is a forum OR discussion about this problem and how people were able to solve it. I link you to it because it's a good resource:

  http://forums.NI.com/T5/Multifunction-DAQ/NIDAQmxbase-compatibility-with-Mac-OS-X-10-6/m-p/1433896#M...

  I hope this helps, let us know if you still have problems!

• 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

• Waveform 1 d for daqmx base

  Hello.  I have a USB of NOR-9233 key I aquire card with.  I'm under Opensuse 10.3, Labview 8.5 and Daqmx Base 3.1.   Using DAQmxBase Read, I noticed that there isn't an option for 1 D Wave, only 2D DBL, under the analogue of the multiple samples.  This option is available on another configuration using DAQmx.  I guess it's a difference between software.  The 1 d waveform seems to include the timestamp while the 2D DBL does not.  Is anyway to read the timestamp of DAQmxBase?  I could write artificially the time based on the sampling frequency, but I'm afraid that's not precisely correct. Thank you

  Jeff

  Hi Jeff,

  That's correct - DAQmx Base does not currently provide the ability to enter data in a form of wave.

  You will need to write the times artificially.  The type of waveform data consists of a data table, a value of timestamp t0 (you would get this bone) and a delta t (based on your sample rate).  You would use the function create a waveform to convert the data in the waveform type, if desired.  I hope that helps you out, let me know if you have any questions.  Thanks for posting!

  -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