NOR-DAQ traditional to NOR-DAQmx

Similar Questions

• Conversion of a VI that uses OR-DAQ traditional to NOR-DAQmx

  Hello

  I'm trying to convert a VI that uses OR-DAQ traditional to NOR-DAQmx.  I'm almost there, but when I run my new rear version number 'read' and 'scan' are not the same.

  In the original version the "number read" always came back as 1 and "scan" backlog is always returned as 0.

  In the new version, "number readings" and "rear scan" could come back with any value.  It's sure to shake my recording of measures and VI the interaction with the rest of the program.

  I have attached a light version of the VI for the old OR-DAQ traditional and new OR-DAQmx that illustrate this problem.  The two VI is written in LabVIEW 2011 SP1.  I would be willing to upgrade to SP1 2013 LabVIEW if it would help solve the problem.

  I would be grateful for any guidance.

  Thank you in advance.

  I think I did.  Use-1 to erase everything in the buffer when the program is waiting for the countdown to the end and then just ask for 1000 measurements when the countdown reaches 0.  Do not need the Scan back or number reading.  Also don't need to add the measure in table 1 at a time because I get them all at once.

  I enclose a copy of my solution for all those who might need to do something similar in the future.

  Gary

• NOR-DAQ traditional vi not found in NOR-DAQmx

  Hello. We hope to control a detector via NI PCI-6533 (DIO-32HS). Our colleagues have implemented control programs in BT 7.1 to 7.3 of NOR-DAQ traditional. Now when we opened their programs on a PC installed with LV 8.6 and NOR-DAQmx 8.9, many vi was not located, including "DIO config.vi", "DIO wait.vi", "DIO clear.vi", "DIO read.vi", "Reset.vi Device", etc. We realized that they were supposed to come from vi.lib\daq\digital.llb and a few other .llb in the same folder. Apparently vi.llb\daq was installed by the traditional DAQ.

  We do not believe there is compatible with LV 8.6 traditional DAQ, which means that we need to replace those 'DIO *.vi' or 'Device reset.vi' with their counterparts DAQmx.  Could someone shed some light on how we should start working on that?

  Thank you very much.

  Xiaolan,

  Indeed, there is a traditional DAQ driver for LV 8.6. The installation can be found here.  I hope this helps.

• NOR-DAQ traditional (old) devices of measurement and automation explore 4.7 with LabView2010 under Windows 7.

  In measurement and Automation Explorer 4.7, with LabView2010 in Windows 7, peripheral OR-DAQ traditional (old) appears under devices and Interfaces and it allows me to create a chassis SCXI-1000, and she agrees "Reset for NOR-traditional DAQ.  However, it does not search the modules in the SCXI1000, and when I ask 'trial', he says 'Impossible to test the chassis at this time.'  The entrance of NOR-DAQmx devices for the SCXI-1000 chassis has no problem and detects the modules very well.  I need the Legacy DAQ to a popular former teaching tool that has no equivalent in NOR-DAQmx.

  Unfortunately, NEITHER-DQA traditional (old) for Windows Vista and 7 functions of the only driver on Windows 7 32-bit, as seen on the page of the driver at the end of paragraph 1 Solution. I recommend you move your program to DAQmx.

• MAX does not recognize NOR-DAQ traditional (old) devices * HELP

  I have a card PCIe-6259.  I want to use blocks of input-output in my program .vi (read Port DIO-DIO Port writing reading Digital Line), so I installed the version of NOR-DAQ traditional (old) devices 7.4.4.   But when I got to MAX (measures & Automation) and look on the left side under devices and Interfaces, I do not see the Tradional-NOR-DAQ tab; I see only the devices NOR-DAQ-mx, PXI, series and parallel system.

  Then when I go to run my program I get the error: error-10401 took place in a DIO Port Config Possible reason (s): NOR-DAQ LV: the specified device is not a product of National Instruments, the driver does not support the device (for example, the pilot exited until the device has been supported), or the device has not been configured using the Explorer Measurement & Automation.

  So, how do MAX to recognize that I have installed NOR-DAQ traditional (old) 7.4.4?

  Thanks for the reply!  I realized this too after going through the files for example... but thanks for the confirmation.

• 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

• Integration of material NI_DAQ and NOR-DAQmx software on the same system PCI-DIO-96

  Hello

  We have a great system that is developed in VB and uses the traditional inherited NOR-DAQ system. The system controls the controller PCI-DIO-96. We would like to upgrade to some parts of the system to NOR-DAQmx and use VB.Net and we know that you can install both systems together on the same computer.

  We have a few questions:

  (1) once the legacy of NOR-traditional DAQ OR DAQmx software can be integrated in the same system. Some parts of the system will always use the VB and the other parties will use VB.Net.

  (2) if the answer to the first question is Yes. Are there hardware or software limitations? Is there a recommended way to integration?

  (3) are there articles based on the knowledge about it?

  Thanks Jeremiah

  There are a number of limitations to the use of NOR-DAQmx and NOR-DAQ traditional at the same time.  First of all, only one of the drivers can access the device at a time.  To switch between the drivers, I recommend that you read this knowledge base Article: that I can use OR-DAQ traditional (old) and NOR-DAQmx simultaneously?  You will need to use the equivalent functions of VB .NET to switch between the pilots.

  In addition, the system should use Windows XP or an earlier version.

• Need help to convert DAQ traditional subvis DAQmx configuration

  I need to convert these screws (of NOR-traditional DAQ) to be used with a new data acquisition card that supports only NI-DAQmx.

  Please help me in this...

  Can I use the same traditional NI DAQ VIs with the NI PCI-6221?  If so, how? This device can be configured for NI DAQ traditional?

  NOR has several resources to help move tradtional DAQ DAQmx. A good place to start is the getting started page. There is a tutorial on how to transition. There is also the compatibility screws which replace certain traditional DAQ functions with wrappers around functions DAQmx. The DAQ example you posted is pretty trivial and really shouldn't take a lot of time to convert once you get a basic understanding of the DAQmx.

• Runtime error example NOR-DAQmx ANSI C in the Windows 7 virtual machine

  I am under a guest Windows 7 system with a host of Ubuntu 14, using VirtualBox and have encountered a problem running even the simplest examples provided by National Instruments, using the ANSI C API for NOR-DAQmx.

  The first time that the DAQ hardware is turned on, I can run a single measure, and after that, any other indicator displays the following error message:

  Attempted to read samples that are no longer available.
  
  The requested sample was previously available, but has since been overwritten.
  
  Increasing the buffer size, reading the data more frequently, or specifying
  
  a fixed number of samples to read instead of reading all available samples
  
  might correct the problem.
  
  Property: DAQmx_Read_RelativeTo
  
  Corresponding Value: DAQmx_Val_CurrReadPos
  
  Property: DAQmx_Read_Offset
  
  Corresponding Value: 0
  Task Name: _unamedTask(0)
  
  Status Code: -200279

  In order to start a new measurement, I have to restart the DAQ hardware, probably in order to clear the internal buffers that are in the process of substitution.

  I am interested in a measure of continuous tension in basic by using a callback function. (The example of ContAcq_IntClk provided by OR)

  The exactly the same setup, same version of NOR-DAQmx (9.7.5) and running on Visual Studio 2012 smoothly on a computer that is running Windows 7 directly.

  I suspect that the problem is with the internal buffer being somehow messed up because of the connection with the Virtual Machine, but do not find an elegant solution to fix it.

  The camera I use is NI USB-6289.

  Hello fromm8

  Thank you very much for your help, I managed to locate the problem.

  He was not the actual code, or something like that, it was a problem of communication between the VirtualBox machine and the physical device.

  Kept launches MAX test panels a comparable as error the program C.

  I fixed the problem by opting for VMWare, which seems to have the best compatibility with USB devices.

  See you soon!

• 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

• HAVE Start.vi - number of buffers to acquire - equivalent in NOR-DAQmx

  Hello

  I'm trying to convert a VI above NOR-DQA traditional to NOR-DAQmx.  I'm unable to find the equivalent of some inputs to the AI Start.vi

  number of scans to acquire

  number of buffers to acquire

  Also it HAVE buffer Read.vi which is equivalent to the

  time limit

  I would be grateful for any guidance.

  Thank you in advance.

  He mailed examples for DAQmx Analog Input tasks in LabVIEW.

  In the toolbar, go to:

  Help > find examples (this will open the Finder of example of OR).

  Select:

  Material input and output > DAQmx > input analog (then select the type of task you did.)

• 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

• NOR-DAQmx C to run two cards USB M series

  Hello

  I am a newbie in working with DAQmx system and need help on the synchronization of multiple USB DAQ devices. The goal is to start the collection on two USB DAQ for M-series card, and we use C codes (via the DAQmx ANSI C library) to do this. I read and resources OR more guides: "Several hardware DAQ synchronization" (http://www.ni.com/dataacquisition/videos.htm), and examples of code on the dev box NOR: "NOR-DAQmx: HAVE / simultaneous in CVI AO" (http://zone.ni.com/devzone/cda/epd/p/id/879).

  My understanding is as follows:

  1. set the first card as the master and export the signal 'StartTrigger' and 'SampleClock' PFI1 and PFI2 (the physical axis).

  2. connect physically with pin PFI1 and PFI2 (sources) of MasterCard wire on pin of PFI0 and PFI1 (destination) in the slave card.

  3. set the task of the slave to use the beginning of digital dashboard using PFI0 and configure the sample clock of the slave task to use the clock of the source of the exported signal from main task to PFI1 (the slave PIN).

  So far the result does not work. The error still shows as if the physical connection is not recognized (I have not yet found a way to check if the signal exported successfully or not).

  I have attached the instant routing table to the map created in the MAX and the code snippet I used.

  Any help is welcome. Thank you!

  Hi kusg.

  DAQmx unclear that some PFI terminals on your two devices are interconnected, and you can't tell him that they are connected because DAQmx only supports connections inter-appareils for chassis PXI, not PFI terminals and cables of the RTSI. So export terminals PFI of Dev2 Dev1 task signals won't work.

  However, you can export terminals PFI of Dev1 Dev1 task signals. Try to do this instead, and the error should go away (as I think it is to assume that it is error-89124).

  In addition, when you use PFI, I recommend committing the master task before you begin the task of the slave, to start the master task does not generate unwanted edges digital:

  DAQmxTaskControl (masterTask, DAQmx_Val_Commit);

  DAQmxStartTask (slaveTask);

  DAQmxStartTask (masterTask);

  Brad

• 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

• 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