Requirements of DAQmx

I discount code of a member of my company, when I try to load the code into my LabVIEW System I see:

""Convert 1DWfm to DDT.vi"file not found". There are also a host of other material objects DAQ, it cannot find

This would lead me to believe that DAQmx is not insalled, however, if I look at a list of all the objects that I can use the following objects ARE available:

Traditional DAQ channel

DAQmx Switch

DAQmx Terminal

DAQmx task name

Name of the DAQmx scale

DAQmx device name

Global DAQmx Channel

Physical channel DAQmx

When I insert the disc of "Device drivers" and try to install the device drivers I ammet with the error message following 'error of 1921. Service 'National Instruments LXI discovery suites' (niLXIDiscovery) could not be stopped. "- even though I have administrative privileges on this PC.

Please can someone help me! I'm using LabVIEW 2009 (Note: the code I'm upgrading is LabVIEW 7.1)

At the end of the day, I opened the Task Manager and ended the process of 'niLXIDiscovery '. Don't know why I didn't that at first.

Thanks for your help!

Tags: NI Software

Similar Questions

  • Minimum requirements of DAQmx PCI 6229

    I am currently converting our are configured to use a PCI-6229 for the analog inputs.  We have LABView 7.1 on a Windows XP operating system.  I looked at the latest version of DAQmx that would work with LABView 7.1 and found it DAQmx 8.9.  When I run the DAQ Assistant I gen an ERROR of INITIALIZATION:

    Some components required for publishing are missing.  For more information, please contact National Instruments.

    Article OR suggest that I put to update to the latest version of the software driver, DAQmx 9.3, to solve this problem, but I do not think that this version works with LABView 7.1.

    Does anyone know if the PCI-6229 will work with DAQmx 8.9?

    Any newer version of DAQmx will work with LABView 7.1?

    And if there is another way to fix the DAQ Assistant error?

    Thank you Ahead of time,

    WindResearcher


  • CVI 8.0 OR-DAQmx 8.9.5 compatibility?

    New laptop, installed CVI 8.0.1 then NOR-DAQmx 8.9.5 driver provided with acquisition of data USB-6211. Unit works very well with the help of MAX.

    When you select tools/create/edit the CVI DAQmx tasks... a pop message says: "this feature requires NEITHER-DAQmx. Please install OR-DAQ from device drivers CD OR or check your installation. »

    However, NEITHER-DAQmx appears in libraries.

    The sample program compiled Acq-IntClk, but some error message is displayed when the application is run:

    "Procedure entry point not found SetEnableResourceTracking in cvirte.dll.

    "Unable to load nicvidu.dll, check your installation.

    If I continue through errors, the application seems to work.

    Any installation or compatibility obvious problems here?

    CVIRTE to version 9.0.1 update fixed everything.

  • Distributions

    I am building a distribution that requires DAQmx.  When I get an error "Cannot find distribution" OR DIAdem 11.0.

    Where would this file be?

    You provide the drive NOR DIAdem 11.0. Some software has been installed on the system of this distribution, and at least one component of it (i.e. the shared component also required by DAQmx or NOR Installer framework) should be copied from this disk.

    A. Mert

    National Instruments

  • NOR-DAQmx on an Asus eeepc 900?

    Did someone already used an eeepc 900 with DAQmx drivers? I would use this ultra compact pc for CQI data.

    PC will be running a lite version of XP.

    Programs could be compiled Labview 8.5 or Visual Studio 2005 with soul Studio.

    Material would be USB-6211 or 6212 which all require two pilots DAQmx.

    M is concerned that the pc has a limited memory and the DAQmx isn't the lightest eater. There is no way I could install the driver as a whole package. Is there a way I could install enough the DAQmx to spin these two DAQ cards? There will be no development program on this machine. Just race programs compiled.

    You probably want DAQmx 9.4 Core Runtime, which includes only drivers DAQmx and support libraries. It does not include things like support of environment of LabVIEW Development, documentation, or measurement and Automation Explorer.

  • The USRP CSD requires the LabVIEW Communications?

    I recently installed LabVIEW 2013 on my machine, as well as a whole bunch of toolboxes:

    LabVIEW English 2013
    VI Package Manager
    Module LabVIEW Control Design and Simulation 2013
    2013 LabVIEW Datalogging and Supervisory Control Module
    2013 LabVIEW MathScript RT Module
    NI LabVIEW 2013 LEGO (R) MINDSTORMS (R) NXT Module (in English)
    Module OR Vision Development 2013
    Module LabVIEW FPGA of 2013 (English)
    Xilinx toolchain 14.4
    Module time real LabVIEW 2013 (English)
    2013 LabVIEW Touch Panel module
    2013 LabVIEW Robotics module
    Software OR SignalExpress 2013
    LabVIEW Sound and Vibration Measurement Suite 2013
    Module LabVIEW Statechart of the 2013
    LabVIEW 2013 for myRIO Module
    Toolkit OR run real time Trace 2013
    2013 LabVIEW System Identification Toolkit
    LabVIEW Toolkit 2013 Digital Filter Design
    4.3.4 for LabVIEW Modulation Toolkit
    2013 LabVIEW VI Analyzer Toolkit
    2013 LabVIEW Database Connectivity Toolkit
    2013 LabVIEW Report Generation Toolkit for Microsoft Office
    LabVIEW Spectral Measurements Toolkit 2.6.4
    2013 LabVIEW Advanced signal processing Toolkit
    LabVIEW 2013 PID and Fuzzy Logic Toolkit
    Kit filter LabVIEW Adaptive, 2013
    Toolkit LabVIEW DataFinder of the 2013
    2013 LabVIEW Desktop Execution Trace Toolkit
    LabVIEW 2013 Multicore analysis and matrices hollow Toolkit
    LabVIEW 2013 power electric Suite
    Toolkit LabVIEW 2013 GPU analysis
    Biomedical Toolkit LabVIEW 2013
    Module LabVIEW 2013 OR SoftMotion
    NEITHER Motion Assistant 2013
    NEITHER Vision Builder for Automated Inspection 2012 SP1
    OR DIAdem Professional 2012 SP1 (English)
    LabWindows/CVI 2013 development system
    Module time real LabWindows/CVI 2013
    LabWindows/CVI Spectral Measurements Toolkit 2.6.4
    Spectral measures of LabWindows/CVI DURATION 2.6.4
    LabWindows/CVI SQL Toolkit 2.2
    Toolkit for processing Signal of LabWindows/CVI 7.0.2
    LabWindows/CVI PID Control Toolkit 2.1
    Execution of LabWindows/CVI Profiler 1.0
    Measurement Studio Enterprise Edition for Visual Studio 2012 2013
    General safety NI Patch 2nd quarter of 2013
    NEITHER TestStand 2013
    NEITHER ELVISmx 4.5
    NOR-DAQmx 9.7.5
    Xilinx 10.1 Compilation tools (requires the build tools additional Xilinx DVD)
    Device drivers or - February 2013

    I tried to follow this tutorial with the USRP 2932, coming soon, but I found out later that I have seem to have none of the LabVIEW Communications. No not those who prevent me from using the USRP radio? If not, then is there any restrictions on what I can do with the radio without communication?

    Hi BreadLB,

    The link to the tutorial you posted is based on LabVIEW Communications System Design Suite, a new software environment designed to accelerate the prototyping of the algorithm and stable air.  It is a completely separate and independent of LabVIEW environment.  See my post here for more details.  You can also download a free 30 day trial copy here.  Your hardware is supported with LabVIEW and LabVIEW Communications.

    The 2932 NOR is a network based USRP, and there a small on-board FPGA.  For this reason, the FPGA on that specific product is not a target of LabVIEW FPGA.  The NI 294 x / 5 x family has a large Kintex 7 FPGA and can be programmed using LabVIEW FPGA and LabVIEW Communications, as in the tutorial you posted.  The 2932 OR can be used with your host PC and LabVIEW for a variety of applications.  Unfortunately the tutorial that you have linked to your post requires the NI 294 x / 5 x hardware and Communications of LabVIEW.  If you have questions about a specific application for your 2932, please post more details and we would be happy to help you.

  • Frequency measurement of analog input using DAQmx C APIs on SMU-6341 map

    Hello

    I use Linux DAQmx and attempt to measure the frequency of analog input using the map DAQ SMU-6341.

    There is an ANSI-C frequency measurement example:

    / usr/local/natinst/nidaqmx/examples/ansi_c/Analog_In/Measure_Frequency/Cont_Freq-Int_Clk-SCXI1126

    However, the call to DAQmxCreateAIFreqVoltageChan results in the following error:

    DAQmx error: selected physical channel does not support the type of measure required by the virtual channel you create.

    Create a channel to a type of measure that is supported by the physical channel, or select a physical channel that supports the type of measure.
    Property: DAQmx_AI_MeasType
    Required value: DAQmx_Val_Freq_Voltage
    Possible values: DAQmx_Val_Current, DAQmx_Val_Resistance, DAQmx_Val_Strain_Gage, DAQmx_Val_Temp_BuiltInSensor, DAQmx_Val_Temp_RTD, DAQmx_Val_Temp_Thrmstr, DAQmx_Val_Temp_TC, DAQmx_Val_Voltage, DAQmx_Val_Voltage_CustomWithExcitation

    Task name: _unnamedTask<0>

    State code:-200431

    DAQmx does support the function of the frequency on the map 6341, or should we use examples of voltage and calculate the frequency manually?

    Frequency of HAVE it is a type of channel that has been supported only on the SCXI module name of the example.

    You will need to use a voltage input channel and calculate the frequency manually for your device.

  • With a sampling of the data with DAQMX, error-200279 occurs when making 2d array dbl

    Hello

    I did a system of simple analog voltage with DAQMX data acquisition.

    It is made for reading of capacitance, where output capacitance value out of a circuit in the periodic voltage signal.

    What I want is to get data from four capacitors simultaneously through four channels, using samples n n (dbl 2d).

    The structure of my VI is almost similar with examples of continuous sampling of voltage in LabView, with the exception of a few other calculations in the loop.

    And for the synchronization of the trigger, I've corrected the edge of release with the external signal from the capacitance reading circuit.

    Version no. 1 has a channel for data input voltage. Version n ° 2 has four channels for the input data.

    While ver.1 can get accurate reading of four capacitors circuit data each (a single channel at a time),.

    ver.2 acquires four channels of data, with a single thin data channel, all the others were wrong.

    I saw a 200279 error occur in the DAQMX read part 2d dbl, so I tried increasing the buffers by changing the sampling frequency or the number of samples, but it wasn't everything.

    I rose for most of the forums with the 200279 error, but the solution would not work on mine.

    Anyone can find the problem? I will attach my screws it may include a bit of Korean language, but most of them are in English, shouldn't be too hard to recognize. Sorry for the inconvenience.

    Oh I forgot, my DAQ is NI USB-6259, and it works in Win XP sp3 and LabView 8.6.

    Thank you.

    Hello Azurenight,

    The 6259 is a DAQ card of the M Series Multiplexed, which means that it is not possible to sample each signal at the same instant, rather the channels are all sent through the ADC even and must be sampled in order. More information on this can be found here:

    LabVIEW Help: Multiplexing compared with simultaneous sampling

    http://zone.NI.com/reference/en-XX/help/370466W-01/mxcncpts/multisimulsamp/

    It may still be possible to get the data you need with the card you have - could you give more information about the maximum eligible period between samples on different channels?

    If you require * real * simultaneous sampling, you will probably need different hardware.

    Kind regards

  • Update of LabVIEW, which updated 9.8 DAQmx. SMU-8101 to 9.4 DAQmx. Difficult how?

    I am trying to use MAX to navigate up to a DAQ SMU-6363 connected to my SMU - 8101 RT connected to my local network, but encounters an error: "error-88716 occurred at communication·entre·dispositifs·de·sante·personnels, or the possible reasons: the requested operation failed because a driver on the local and remote system versions are different."  Updated the driver for versions on both systems are the same.  "Remote system: 172.17.2.65, Incompatible driver: NI - DAQmx Device Driver 9.4.0f0.

    This problem occurred recently when I've updated LabVIEW on my development computer to the latest version (2013 f2), which updated DAQmx on my development for v9.8 machine.

    While I'm not quite there, I intend to analyze an audio signal using the SMU-6363.  I guess I'll need to have all the properly information in MAX before I have a hope of implementation in LabVIEW.

    I am now updating the drivers / firmware on the SMU help system full of communication between my development system and the SMU system and having problems.

    During an attempted 'Select all to install' for 'NOR-DAQmx 9.8.0"in the" Add/Remove software"on the SMU-8101 thanks MAX system, I get the error:

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

    Cannot continue following unresolved dependencies:

    Acquiring dynamic signals 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
    Acquiring dynamic signals 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
    Counter/Timer 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
    Counter/Timer 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
    NOR-DAQmx 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
    NOR-DAQmx 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
    Multifunction 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
    9.8.0 multifunction data acquisition requires Intel 8254 x Ethernet Driver 5.0
    CompactDAQ 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
    CompactDAQ 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
    CompactDAQ 9.8.0 requires LabVIEW time real 12.0.0
    E/s digital industrial 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
    E/s digital industrial 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
    Analog output series 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
    Analog output series 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
    OR-653 x 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
    OR-653 x 9.8.0 requires Intel 8254 x Ethernet Driver 5.0
    SC Express 9.8.0 requires linguistic support for LabVIEW RT 1.0.0.3
    SC Express 9.8.0 requires Intel 8254 x Ethernet Driver 5.0

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

    This dialog box does not offer an option to automatically try to download or to locate the missing packets.  Research online revealed no obvious statement upgrade for my particular case.

    I downloaded and installed v9.8 DAQmx as well as RealTime 2013 module on my development machine, and am trying to download the 4 GB device drivers.

    Is there a suggested method for the SMU-8101 software update / firmware must match that of my development machine that does not require me trying decrypt and download the packages manually?

    I've never worked with the SMU (or any remote system) with LabVIEW front and wait it would be an easy fix for someone more experienced in this.

    Owen

    AHA!

    OK, that explains it.  You actually have LabVIEW 2011 on target (SMU-8101) but you have LabVIEW 2013 on the host.  You have all the required software installed on the host computer, but there are conflicts between the required versions of the software on the controller itself compared to what you're trying to install now.  You have 3 ways to do this:

    (1) the cleaner to proceed is to keep track of all the software components that you have installed (version is not important) and then UNINSTALL all the controller software, and then REINSTALL your software (leaving MAX select the latest versions of everything).  This ensures that you'll get the latest components of software.

    (2) the 'simpler' wat to proceed is to pass by and "update" symbolizes all the components with an icon 'Bang' (yellow triangle with an exclamation point) to upgrade/reinstall the latest version found on the host - the icon of 'bang' software currently installed on the target, but more recent versions exist on the host computer.  Version does not update without user intervention, even if the other components require more recent versions.  This lump all your versions later, that's what want the latest version of DAQmx.

    (3) nuclear option - reformat your controller and reinstall all software.  This is not recommended, but this option always exists.

    -Danny

  • The substitution of DAQmx writing?

    Hello

    In my project, I am required to constantly acquire an analog input of 2 sensors and den generate the desired to 2 devices using use-cases(already done) output.

    The question now is whether it is possible to substitute the DAQmx writing so that I can ignore the use cases and just generate the output I want

    Put a case statement in the case statement, you already have? Is the point to jump DAQmx writing or have a control to set up the output?

    And clean your diagram. The wiring is horrible.

  • I'm trying to reference NationalInstruments.DAQmx in my application c# but build error

    I'm trying to reference NationalInstruments.DAQmx.dll in my c# application but get error of next generation. No idea how to solve this problem?

    WARNING 1 the referenced assembly 'NationalInstruments.DAQmx, Version = 9.4.40.50, Culture = neutral, PublicKeyToken = dc6ad606294fc298, processorArchitecture = x 86' cannot be resolved because it has a dependency "System.Web, Version = 4.0.0.0, Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a", which is not in the current target framework". NETFramework, Version = v4.0, profile = customer. Remove references to assemblies not in the target framework or consider retargeting your project. NITesting

    Julien,

    If you have the same error message, such as noted above, it seems that the problem was that the project has been configured for the profile of the Client .NET 4.0. The .NET 4.0 Client profile is a lighter version of the .NET framework, but the assemblies of National Instruments require the .NET 4.0 framework. You can set up your project (even after its creation) to use the full version of .NET in the project properties > Application > target framework in c# and project properties > compile > Advanced Options of compilation... > target in VB .NET framework.

    If this isn't the same error message that you receive, or if this does not resolve the problem, could you please put the error message in your response?

  • NI DAQmx 9209 sampling rate

    Hello! I need to monitor 8 channels of analog input with a NI 9209 module inserted into a unit of the cDAQ. I have 5 channels with CSR terminal config channel + 1 also as CSR but different range and 2 channels with differential terminal config. I'd like to try these 8 channels with a frequency of 5 Hz. The maximum speed I can get is now slightly below 2 Hz above, unless I change the DAQmx ADC synchronization in high speed Mode. In this way, I get the required speed. I would like to know what is the compromise of accuracy how much I lose? I was able to check the accuracy of my sensors, and it is easily possible that I'm still OK with lower accuracy of DAQmx ADC. How can I get this information? Is there a whitepaper, or the property DAQmx node to read? Thank you!

    Check the voltage (of events) - example of continuous input, you can find it in the Finder for example of OR. The vi has changed my life DAQmx, . Using a version heavily modified VI I could permanently acquire 8 channels each 2MSa/s continuous with a portable 10 year old.

    In any case looking at the datasheet, it probably not will help you with the Mode high resolution. The data sheet gives time to conversion by channel for mode high speed as 2 ms, or his 500s. For 8 channels, gives you a 62.5 Sa/s max speed. For high resolution, the conversion time is 52 ms per channel or 19.2 Sa/s. For 8 channels, it gives its 2.4 Kbps, or what you saw earlier.

    The moral of the story, you know, so if you want 5 rate of Sa/s while you need mode high speed.

    See you soon,.

    McDuff

  • DaqMX wait the next sample causing slow down Clock.vi

    Hello

    I have a question about the proper use of DaqMX wait for next sample clock.

    I read channels analog voltage on a map or pcie-6259.

    I would like to read as soon as possible make your comments between each of these points of single data points.

    I wish I had an error generated if I miss a data point.

    From reading the forums, I've gathered that the best way to do it is using the Timed Single Point material.

    A simplified program that I use to test this is attached.

    If I remove the DaqMX wait for next sample Clock.vi, my program seems to work.

    I added a counter to check the total time is as expected.

    For example, the program seems to work at the speed appropriate for 120.

    However, without that vi, it seems that the program does not generate a warning if I missed a sample.

    So I thought that the next sample clock waiting vi could be used to determine if a single data point has been missed using the output "is late."

    However, when I add inside as shown in the joint, the program seems to slow down considerably.

    At high rates as 120000, I get the error:-209802

    14kHz is the approximate maximum rate before you start to make mistakes.

    My question is: is this the right way to check a missed sample? I don't understand why the wait next sample Clock.vi is originally a slow down. Without this vi, the program does just what I want except that I do not have strict error control.

    My confusion may be based on a lack of understanding of real-time systems. I don't think I do 'real time' as I run on an ordinary pc, so maybe I use some features that I wouldn't.

    Thank you

    Mike

    Mike,

    You should be able to read to return delays errors and warnings by setting the DAQmx real-time-> ReportMissedSamp property.  I think that if you enable this, you will see errors or warnings (according to the DAQmx real-time-> ConvertLateErrorsToWarnings) in the case where you use read-only.  I'm a little surprised that you have measured your application works at 120 kHz without waiting for next sample clock (WFNSC), although I'm not surprised that it would be significantly faster.  I think if you call read-only, you'll read the last sample available regardless of whether you would of missed samples or not.  When you call WFNSC, DAQmx will always wait for the next, if you are late or not sample clock.  In this case, you will wait an additional sample clock that is not the case in read-only.  Once again, I expect that, in both cases, your loop would not go to 120 kHz.

    Features real-time DAQmx (hardware Timed Single Point - HWTSP) are a set of features that are optimized for a one-time operation, but also a mechanism to provide feedback as to if a request is following the acquisition.  There is nothing inherently wrong with using this feature on a non real-time OS.  However, planner of a non real-time OS is not going to be deterministic.  This means that your app 'real time' may be interrupted for a period not confined while the BONE died in the service of other applications or everything he needs to do.  DAQmx will always tell you if your application is to follow, but can do nothing to guarantee that this will happen.  Thus, your request * must * tolerant bet of this type of interruption.

    There are a few things to consider.  If it is important that you perform the action at a given rate, then you should consider using a real-time operating system, or even with an FPGA based approach.  If it is not essential to your system, you might consider using is HWTSP, where you do not declare lack samples (DAQmx simply give you the most recent example), or you could avoid HW timing all together and just use HAVE request to acquire a sample at a time.  What is appropriate depends on the requirements of your application.

    Hope that helps,

    Dan

  • Error 200088 using the DAQmx reading VI in a case structure

    Main problem: I'm writing a VI that will read data from a data acquisition and write to a text file when I hit a button "registration". To do this, I use the VI of reading DAQmx in a while loop, which is located in a case statement (I hit the 'Save' button for the case of true), which is in another while loop. My DAQmx create Virtual channels screws are outside of the loop, so a wire goes through three structures to connect these screws to the VI DAQmx Read.

    After clicking on 'Save', my VI works until I hit the "Stop" button, how I get error 200088: ' specified is not valid or does not exist. " If anyone can help me get rid of this error, that would be greatly appreciated!

    I enclose my VI and an image of the error.

    Secondary problem: currently, I use two different DAQmx read live: one mentioned above, which lays down: after clicking 'Save' and the other who reads data continuously to display on maps. I want to combine these two, but I don't know if this is possible given the case statement.

    Thank you!

    Hi Alexwright,

    I made some quick changes to demonstrate the producer consumer loop that would be effective in your case. You want to loop of producer in the first while loop so that you use and the same closing DAQmx task. Moving a forwardthis will require some trial and effective change for your application. Please also make sure you use our debugging tools: http://www.ni.com/gettingstarted/labviewbasics/debug.htm.

    I hope this helps.

  • Data channel read name DAQmx without installed DAQmx

    We have data files, including a header with the names of channels in the DAQmx channel name format.

    Now, we want to send a Labview application to our customer by which they can open these files and just seeing the names of channels in the form of text. Can we make such an application without requiring the customer to install DAQmx. We use Labview 7.1.1 and after installing the application, it asks for nivaiu.dll, nipalu.dll nipalut.dll and so on. Change the simple arrays of strings file header gives compatibility on old data problems.

    Concerning

    Dan Larsson

    Problem solved!

    Control of channel name DAQmx can serve as a binary file read model without installing DAQmx separately. I found a Subvi calling "DAQmx unflatten string. After the removal of this call everythings working.

    Sorry for all you mind!

    / Dan

Maybe you are looking for