Reset Ni-DAQmx tasks

Hi,
How do you reset the NI-DAQMx tasks in dasylablab 12.0?
I have tried to do a reset in MAX but the tasks doesn´t disappear in Dasylab, even after I removed Dasylab an installed it again. I am using the Task timebase several places in my worksheet, and if i have made changes in MAX the only place it works is at the input module, not in generators ect.
As you can see in the attached files there are more than one task with the same name, and after creating the "Noise test" task in MAX, synch Dasylab with MAX, the generator module still selects the wrong task as timebase.
Rgds.
Per Skov
Attachments:
Time base new task - generator.pdf ‏14 KB
Time base - generator.pdf ‏14 KB

It is not possible to copy the worksheet because i am using a lot of black boxes, so that options can´t be used.
I have tried saving as DSA, and it was quite easy to locate the time base settings, and I succesfully removed the unwanted time bases.
After editing I saved the file again (same name), and loaded it into Dasylab. The worksheet worked, but it had lost information about several global strings.
The missing strings are all calculated ones like this one:
strfmt ( ${VDMEAN}, 5, 2) +";"+strfmt ( ${VDMIN}, 5, 2)+";"+strfmt ( ${VDMAX}, 5, 2)+";"+strfmt ( ${VDSTD}, 5, 2)
After editing the DSA file and loading it into Dasylab it looks like this:
'strfmt ( ${VDMEAN}, 5, 2) +"
In the DSA file it is still:
Expression[42] = 'strfmt ( ${VDMEAN}, 5, 2) +";"+strfmt ( ${VDMIN}, 5, 2)+";"+strfmt ( ${VDMAX}, 5, 2)+";"+strfmt ( ${VDSTD}, 5, 2)';
Apparently It is the quotation marks that confuses Dasylab when loading DSA files. The solution is to export the global strings/variables from the original worksheet, do the edit of the DSA file load it into Dasylab and then import the strings/variables, save the worksheet with an new name.
Problem solved, but I think that it should be possible to remove unwanted tasks directly in Dasylab.
Thank you for you help:-)

Similar Messages

  • Is it possible to maintain the last AO value after the DAQmx task is done on device DAQ USB-6341 ?

    Hi all,
    I use the device DAQ USB-6341 to generate the desired voltage waveform by the "finite samples" sample mode.
    I notice that the channel resets to zero volts after the DAQmx task is done and the DAQ USB-6341 does not have 
    the property AO.idleOutputBehavior to select "Maintain Existing Value".
    How can I maintain the last AO value after the DAQmx task is done on device DAQ USB-6341 ?
    Thanks.
    Godel

    How many computers do you have in the network?
    What is the IP address and default gateway number on your computer?
    In order to connect to the wireless network, WVC80N should get valid IP address from the access point.
    If the access point has capacity to assign a private IP address to the computers and devices then I think you can use WVC80N.

  • Would you Open and Close DAQmx tasks within a function or Globally

    Hi Guys,
    This should start something.
    The subject is DAQmx Tasks.
    If you were writing a function that is called many times, say MeasureVolts (double *Value) to obtain a reading from an Analogue Input Channel.
    Would you.
    1. open and start the task inside the function, do the measurement and then close the task inside the same function.
    or
    2. open the task globally and later do the measurement inside the function using the global task then close the task only when the application is closed.
    I am mostly concerned with the overhead of task generation and closing, what do you guys and girls out there do?? and what is the general opinion?
    I would appreciate your views.
    Regards
    Paul.

    I would definitely NOT keep configuring and clearing (I think that's what you mean by open and close) the same task over and over.  I would configure once, read many times in my main app, then stop & clear once.
    I typically like to package such data acq into an "Action Engine" that keeps track of its own DAQmx task id so I don't need to sling that task id wire around into multiple parallel loops / vi's.  Attached is a very stripped-down example for Digital Input. 
    I would typically do more with error testing and would make the "Action" enum into a typedef custom control, but this gives you the basic idea.  The action engine approach works very nicely when there's a small # of different kinds of input parameters and output info needed to support all the necessary action cases.   When you start needing a large number of differnent kinds of inputs and outputs to support the desired actions, then you start having difficulty with (1) having enough terminals to wire and (2) remembering which inputs and outputs are meaningful for which actions.
    -Kevin P.
    Attachments:
    DI Action Engine.vi ‏75 KB

  • How to Measure Frequency to RPM NI-DAQmx Tasks

    Hello,
    I am trying to measure frequency using NI DAQmx task and then convert this to an RPM if at all possible.
    I have the following hardware options at my disposal.
    I have SCXI 1126 Module along with a SCXI 1327 terminal, as well as a PXI 6289 Multifunction DAQ.
    I have wired in a mag sensor to ai7 on my 1126 and when I pass a metallic object I get a amplitude of 6  - 8  so I am able to read the mag sensor.
    What I am trying to do is to somehow convert this analog measurement into a RPM while only utilizing the NI DAQmx task.
    Any help would be appreciated.
    Tim
    Solved!
    Go to Solution.
    Attachments:
    Freq Set Up.jpg ‏2993 KB

    So I would select new in "Custom Scaling"
    Then would I select linear?
    Your calculations are simple but I am unsure if this would give me the desired result.  From my attachment I am seeing an input amplitude of 6 Hz for each pulse.  What I mean by this is that every time I bring a ferrous object near my mag pick up I get a pulse, this is what I was trying to illustrate in the attachment.  The analog pulse comes in a 6 Hz so I would simply multiple this pulse by 60 (assuming I get one pulse per rotation) to get RPM?
    How would this make sense if I only input one pulse for a long duration of time? 
    I have notice the amplitude of the pulse input increases with increased pulse frequency.  Does this mean the lowest RPM I can record is 360 RPM?  
    Tim

  • Creating a new DAQmx task after building to EXE

    Should I be able to create a new DAQmx Task while running a VI containing the DAQmx Task control that was built as an EXE?
    I can't but would like to know if there is a work around or if I am doing something wrong. See the attached screen shots.
    When I am not running the VI, I can right click the Task front panel control and select "New NI-DAQmx Task" -> "Project" or "MAX", but when it is running or I am using the VI built as an EXE (running or not) I can't. In the EXE I am able to click the Task drop down box -> "Browse..." -> "Create New..." -> "MAX Task" but nothing happens when I click on "MAX Task".
    I would like to be able to create a new task in the software to use different channels and signal types on the fly. The goal is to build a program setup similiar Signal Express but include some on off controls for some machinery and scale it down and customize it so that it is easier to show people how to use it.
    Thanks
    Attachments:
    block diagram.png ‏30 KB
    front panel.png ‏25 KB
    exe front panel.png ‏26 KB

    When running your exe, you'll be able to select from tasks created in MAX.  Instead of right clicking on the task control, try creating the tasks you want directly in MAX (under Data Neighborhood right click on DI-DAQmx Tasks to create a new one).  Tasks that you've saved in MAX will be selectable in the DAQmx Task Name control.

  • NI-DAQmx task works in MAX or DAQ Assistant test panel but not in LabVIEW

    I am attempting to read a single AI channel from a PCI-6024E card via an SCB-68. I have created a NI-DAQmx Analog Input Voltage Task in MAX for this channel, sampling in contiuous aquisition mode at 100 kHz, 10000 samples at a time, with RSE terminal config. If I use the Test feature from MAX, the channel acquires data as expected.
    In LabVIEW, I call this task using an DAQmx Task Name Constant. If I right-click this constant and select "Edit Task", the Daq Assistant opens and I can use the Test feature from the DAQ Assistant to see that the data is still being acquired as expected.
    However, when I try to programmatically read this channel in LabVIEW using the VI "DAQmx Read (Analog Wfm 1Chan NSamp).vi", the VI returns a constant DC value of 500 mV, which I know is incorrect (I can monitor the signal across the two terminals in the SCB-68 with a DMM to know that the signal coming in varies as expected, and as I read using the test panels). This erroneous reading occurs even if I make a new VI, drop the task name constant on the diagram, right-click the task name constant and select "Generate Code - Example" and let LabVIEW create its own acquisition loop (which is very similar to what I already set up, using the "DAQmx Read" VI).
    Any ideas why the Test Panels work correctly but the LabVIEW code does not?

    Hello bentnail,
    I'm not sure why the test panels are readin the value correcly but the LabVIEW code does not, but there are a couple of things we can try.
    1) What happens if you just use the DAQ Assistant and place it on the block diagram? Does it read out the correct values?
    2) Try running a shipping example that comes with LabVIEW. "Acq&Graph Voltage-Int Clk.vi" should work well.
    3) What kind of signal are you expecting to read (peak to peak voltage, freqeuncy, etc.)?
    Thanks,
    E.Lee
    Eric
    DE For Life!

  • Where is the DAQmx Task informatio​n saved in MAX

    I currently had a computer crash which resulted in a complete reformat of my Windows computer system.  When the system was rebuilt, the IT professionals made a backup of the reformatted drive before reformatting.  Since I had a computer rebuild I now have to reconfigure DAQmx task in MAX but was wondering if there was a file (such as a task or configuration file) from the old system backup that would allow me to import the DAQmx task information in without having to reconfigure the task.  The hardware on the system is unchanged.  Thanks, Jeff

    From Max select File>import or Export.  Export will create a *.nce file that contains the MAX information you select and Import prompts you to selet the *.nce file you want.
    Its a pretty good idea to save your config information frequently so that you can restore to a known good configuration if something bad happens (like a rebuild of the PC)
    Jeff

  • Why can I not use the channel name, which is obtained from the function of DAQmx Task, as the input of the channel name for the function of Get Channel Information of DAQ?

    Why can I not use the channel name, which is obtained from the function of DAQmx Task, as the input of the channel name for the function of Get Channel Information of DAQ?

    Not a lot of details here, but my guess is this isn't working for you because you are wiring in the task to the Active Channels Property and not the actual Channel Name. I have attatched a screenshot of what I believe you are trying to do. The Task has 2 channels in it, so I need to index off one of the channels and wire it into the active channels input of the Channel Property node. Then I can read information about that channel
    Attachments:
    channel_name.JPG ‏69 KB

  • How do i pass a daqmx task from labview to matlab using the math interface toolkit?

    I want to use DAQMX functions from Matlab using the Math Interface Toolkit (MIT). How can I have a labview function output (return) the DAQMX task to matlab via the MIT?
    I want to do this so I can start a DAQMX task in Labview from a matlab function and return control to matlab without losing the task.

    Hi Mark,
    (I already posted this answer in your other thread, but let's keep THIS thread alive - it makes more sense here in the LabVIEW forum than in Instrument Control forum.)
    Since the DAQmx Task is not a native data type that can be passed directly to MATLAB from LAbVIEW, try flattening the DAQmx Task to a string before passing to MATLAB. However, I doubt that you can access the task from within MATLAB, but feel free to give it a try.
    Good luck!
    - Philip Courtois, Thinkbot Solutions

  • How to get running Daqmx task handles

    HI,
    We are creating a TestStand module using CVI 8.5, in that module we have to close all the running Daqmx tasks, please provide help on how to get running Daqmx task handles. We could not find any API function which can return list of running Daqmx task handles so that we can close one by one.
    Thanks in advance for the help

    I just had a similar issue.  Stumbled on this forum in the hopes of getting an answer and found no reply to the original message.  I think this is what we are both looking for DAQmxGetSysTasks.  
    I havent used it yet.  Still in the excited I found something stage.

  • How to create a DAQmx task in LabVIEW ?

    I want to create a new DAQmx task in LV. I've used 'create new task' VI in LV. Bt I want to see the created task in MAX task list also.
    There is no hardware device connected. Its just simulation.
    Solved!
    Go to Solution.

    Here's a driver we use.  The design intent is to make sure the software provides the tasks that we need so it's not dependant on resources already existing.
    Jim
    You're entirely bonkers. But I'll tell you a secret. All the best people are. ~ Alice
    Attachments:
    DAQDIO_InitializePorts.vi ‏34 KB

  • DAQmx task does not start on RT target

    I cannot programmically start a DAQmx task on an RT target.  The PXI-8140RT controller hangs on either the DAQmx Start Task.vi, DAQmx Read.vi, or the DAQmx Create Timing Source.vi, depending on the level of complexity I try to use.  Any suggestions on what would cause this?
    The vi running on the target is based upon the wizard created target-multi rate-variables-fileIO.vi.  I cannot stop the vi once it hangs; I can only close it.  I have to restart the controller to reestablish communication.    I have tried DAQmx tasks created using MAX, created programmically, and created from a front panel task control.  The tasks test ok using the MAX or the DAQ Assistant.  For now I am trying to measure one RTD channel. 
    The RT system consists of the PXI-8140RT,  a PXI-6259 M-series controlling a SCXI chassis, and the SCXI-1102B and SCXI-1581 pair capable of measuring 32 RTD's.  There are two other modules in the SCXI chassis which aren't being used yet; a SCXI-1162HV and SCXI-1163-R.  The target and host are running LV Real-Time 8.01 and NI-VISA 3.5.  The host has NI-DAQmx 8.0.1f while the target has V8.0.0, apparently the lastest available.

    The VI didn't generate an error message.  Nor was there a message in the RT error log.  I guess it froze before an error could be generated.  I used the DAQ Assistant Express vi in a totally new project.  I have since converted this to code and added features to make it more like my original project.  The new project is working.  I suspect something went wrong with the original project.  I've tried to edit the original project to more closely match the new one and it still dies.  Guess it's time to put it to bed.

  • Design Suggestions for Multiple DaqMX Task Streaming App?

    I'm working on a LabVIEW application in which I'm streaming high-speed data to disk from multiple PXI devices simultaneously.  Each device has its own DaqMX task, and all tasks stream to the same file.  The PXI device configuration (which devices are in the chassis, which slots they're in, and which channels to read from each device) is determined at runtime.
    Does anyone have a suggestion for a design model for this?  To make matters worse, I'd like to be able to specify a channel to monitor its data during the streaming.  I'm thinking the Producer-Consumer model is the basic approach, and I'm at the point where I have an array of DaqMX tasks, one for each device.  I could probably extend that array to be an array of clusters containing:
       1) DAQ Command (e.g. Initialize, Start, Stop, Acquire, etc)
       1) Task ID
       2) Control reference to 2-D array (where each DaqMX read can be stored)
       3) Array of channel names (to allow selection of channel to be monitored
    This could be passed as notifier data, to a data collection subVI, but the part I'm struggling with is finding the best way to run X number of tasks in parallel, where X is not known until runtime.
    Any suggestions would be appreciated.

    Thanks for the input.  With regards to the file format, the decision has been made by my superiors not to use TDMS - unfortunate, but NI hasn't provided the information to write a MatLab file reader, which is a requirement.  So, I've created a custom file format tailored to the needs of my application, but generic enough to be used for other apps. With it, I've been able to stream 8 channels at 800KHz (4 channels each from 2 PXI-6120s) without breaking a sweat.  However, the performance varies greatly depending on which slots the cards are in (but that's a whole different discussion - see the PXI forum for that one).  Once NI solves that one, I'll feel a lot more comfortable.
    I have already made reentrant subVIs that can perform a specific DAQ task.  The problem with a for loop is that the VI sits and wait for a start trigger, then acquires the streaming data.  I can't start the next VI because I'm in the first one.  I thought about creating a data collection VI, and this VI would start up to 6 other VIs in parallel, based on how many and which cards were present.  It's a bit messy, because each slot can contain one of two devices, so I'd need to check which type it was before calling it.  I'm thinking I'll have to create the task list and the references to the data in the main GUI loop, and then pass this using a notifier or queue to the data collection loop. 

  • Full information about DAQmx Task Name - How get?

    Labview 7.1 (information required for solve problem)
    I put in my application a DAQmx Task Name for fast configuration but i want put all information about task in a txt or spreadsheet file. But in Labview 7.1 haven't VIs like (http://zone.ni.com/devzone/cda/tut/p/id/3079):
    - DAQmx Info Query
    - General DAQmx channel Info
    - General DAQmx TEDS Info
    I'm using Analog Input (Voltage and Accelerometers) with several configurations and I need register all data of configuration to re-execute in the future or know about how acquisition data were gotten.
    I think that solve is in property nodes(DAQmx Task, DAQmx Channel, DAQmx Timing), but I believe will be hard work to make. Somebody has this working?
    Leonardo de S. Cavadas
    Maintenance Engineer and Inspection - Bureau Veritas do Brasil
    Engineer Metallurgist with emphasis in Advanced Materials
    Technologist in Computer Science

    Sorry about that, I haven't checked if they were made only for LV 8 and later. Attached is a zip file with all the VIs converted to the version 7.1.
    Some of them were not successfully converted and are presenting fatal errors when opening, probably because they have something not available in 7.1. But I'm sending you anyways, because the three VIs you mentioned in your first post that you wanted, are working fine in LabVIEW 7.1.
    - DAQmx Info Query
    - General DAQmx channel Info
    - General DAQmx TEDS Info
    Please let me know if this is of any help for you or if I can do anything else in this case.
    Best Regards
    Andre Pereira
    Attachments:
    DAQmxTaskInfoQuery.zip ‏586 KB

  • Is it possible to create a list of NI-DAQmx tasks used in a VI in LV7.1?

    Hello,
    I was wondering if there is a built in function for Labview 7.1 that would allow me to generate a list of DAQmx tasks or global channels that are being used in the VI.
    Thanks,
    Steve

    Welcome to the Discussion Forums,
    Steve!
    Since I’m a visual person, I wanted
    to make it clear where these properties are found by posting a picture.
    I also wanted to clarify and say
    that these properties show the global channels and tasks saved on your system.
    They do not indicate which are used by a specific VI. This is because global
    channels are not bound to any particular VI. Any indicator you could include in
    your VI would just return the names that are being assigned as inputs. So the
    best way to know what’s being used in your VI is to look at what the inputs
    are.
    I hope this helps. If this isn’t
    exactly what you’re looking for, will you please post again and clarify your
    application?
    Message Edited by Mark E on 11-07-2007 09:29 AM
    Mark E.
    Precision DC Product Support Engineer
    National Instruments
    Digital Multimeters (DMMs) and LCR Meters
    Programmable Power Supplies and Source Measure Units
    Attachments:
    System_node2.JPG ‏106 KB

Maybe you are looking for