Export DAQ Task created in Labview to MAX

Hi,
Is it possible to export a DAQ Task that was created in labview so that it appears in "Data Neighborhood / NI-DAQmx Tasks" in MAX?
Thanks,
James
Solved!
Go to Solution.

Never mind...
Found it as "DAQmx Save Task"

Similar Messages

Problems saving a DAQ task in Labview and running elsewhere

I am attempting to use DAQmx Save Task.vi in LabView to save a simple signal generation task, so I can open it later / elsewhere. The problem I am having, though, is when I attempt to open the task in MAX. The task is brought into MAX, but when I attempt to run the task error -200552 occurs at DAQ Assistant.
Error -200552 occurred at DAQ Assistant
Possible Reason(s):
Specified string is not valid, because it contains an invalid character.
Position of Invalid Character: 4
Invalid String: Dev1/port0/line0
It looks as though the problem has to do with the '/' character, but I am not sure how to create an output line in LabView that does not include the '/' character. Is there anyway around this problem in either LabView or in MAX?
I have attached my LabView program. Thank you for your help and patience.
Solved!
Go to Solution.
Attachments:
saving_generation_task.vi ‏19 KB

Where is your program where you are trying to run the task? I don't understand what an existing task has to do with the DAQ Assistant. You would simply have to wire the task to a DAQmx Write.

How can I combine these two DAQ tasks???

I am using LabVIEW 11, Windows XP, cDAQ-9174 chassis, two NI-9205 modules.
Please see my code for reference. I am very new so i will accept all suggestions.
I am acquiring 12 volatage signals in a producer/consumer structure giving me a queue of 1-d array of waveform(dbl). Then I am acquiring 12 voltage signals in another loop giving me 2-d array of waveform(dbl).
There is an issue creating the channels. How can I combine these two tasks?
Thanks,
~Chris
Attachments:
WaveTest_6.2.vi ‏558 KB

Hello chrisbe723,
When you say that there is an issue creating the channels, are you getting a specific error message when running your code? Also are you referencing the same set of channels for the two DAQ task you are configuring?
Paul-B
Applications Engineer
National Instruments

How can i delete a DAQ Task

Hi,
As i see the list of NI DAQ tasks growing into infinity, Im starting to wonder how I can delete these tasks, as many have become irrelevant. Is there any easy acces to them? I've Tried to use MAX, but that didnt do anything for me. It terribly easy to add these tasks but seemingly impossible to delete them, or to copy them from one computer to another, hence my frustration.
Could anyone help me out?
sincerely,
Bart de Vries

Boob wrote:
[..], thats why I went the hard way around.
Well, it is not a "hard way", it is just "another way". Both ways (MAX vs. LV created task) have their place.
The advantage of MAX tasks is that you can change settings (e.g. different hardware/channel, ...) without modifying the software. Disadvantage is that you have to provide those configurations together with your application, so you require a more worksome deployment procedure....
just my 2 cents,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

I can not create an Installer, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...

I can not create an Installer on LabView, After install the Vision Builder Demo and then uninstall it. I can not create a Labview installer anymore, it asks me for a Vision Builder Installer, even if My Labview program does not have nothing to do with it...
Solved!
Go to Solution.

Hi Shada this can happen if you are including additional installers to your installer for example DAQmx. When you are doing this the installer has to include other files like MAX (Measuremente and Automation Explorer). Probably when you installed Vision Builder it updated MAX, so when your installer is trying to Include MAX, its asking for the source where it was installed in your computer in this case Vision Builder.
Here you can cache the information so its not asked again, or you can download a newer version fo DAQmx, so it will update MAX and change de dependecy.
You can find more details about this issue in this KB:
KnowledgeBase 3S88PJMY: Why Do I Get A "Missing Distribution" Error When Trying to Build an Installe...
And for keeping a copy here is more info:
How Do I Stop the Missing Distribution Notification Each Time I Build An Installer?
Best Regards
Benjamin C
Senior Systems Engineer // CLA // CLED // CTD

Using APT ActiveX methods to create a labview program for BPC 203 3 channel Benchtop Piezo controller

Hi Everyone,
I am really very new to Labview and i am in great need for some help.I am assigned a task where i am supposed to create a labview program to control or moniter a BPC203 3 channel benchtop Piezo controller. I created a program with the help of the instructions provided in the APT-Labview guide provided by Thorlabs.But th program doesnt run . Whenever i try to run it i get the same error which says that "Control HW Communications disabled".I have attached a snapshot of the error message.So i tried to create a small program in labview which would read the volage output.Even there i got the same error message.I suppose there is some mistake on my part which i am not able to correct due to the lack of proper knowledge.Could anyone please help me to solve this problem.A slight elaboration would be highly appreciated.Also i think the error lies in the use of invoke node with the get Voltage output method. I am not sure whether the parameters i have provided to the invoke node are correct.Any help of any sort would be highly appreciated.
Attachments:
Front Panel with error message.PNG ‏202 KB
Block diagram.PNG ‏101 KB

Hi
I had the same problem today. However, I noticed that the piezo controller has 3 channels with separate slots and they are packaged in the same box. Therefore the whole box has a serial number, probably something like 71822280, and this is written with large letter. Now, in order to communicate with any of the channels, this does not help, but one needs to communicate directly with the interested channel and they have thier OWN SERIAL NUMBERS.
For example channel 1 (my X direction in the nanoMax stage) has serial 91822281, Y has 91822282 and Z has 91822283. So try looking if you have the right serial number Hopefully you found out this yourself but this might help others, I took me3 hours to get this thing working when I started to plug-in the cables and everything.
Lasse

Which tablet/s can run executables created in LabVIEW 8.5?

Background: I have created a VI that acquires data over bluetooth from a specific DAQ device. The VI is created in Windows 7 and LV 8.5. The VI is tested to work on the development machine. I'd like end users to be able to install and run an executable version of this VI from a tablet that has bluetooth capability.
Question: Which tablets can run executables created in LabVIEW 8.5? I think tablets running Windows 8.1, such as Surface Pro and Dell Venue Pro, should be okay but need a confirmation before I purchase one. Also, how about tablets that run other operating systems, such as Windows RT or Android?
Extended Question: What tablets in the market can run LabVIEW 8.5 VIs (or in other words allow LabVIEW 8.5 to be installed)?
Gurdas Singh
PhD. Candidate | Civil Engineering | NCSU.edu

Well since LabVIEW 8.5 isn't officially supported on Windows 7, or 8 you may have issues.
http://digital.ni.com/public.nsf/allkb/B972242574D4BB99862575A7007520CB
Of course many on the forums have stated being able to run older versions of LabVIEW on new operating systems without issue but know that from NI's perspective you should not be running LabVIEW 8.5 on Windows 7. Which means no modern tablet.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Vision builder AI 2011 incompatible with Vis created by Labview 2011 ?

Hi,
I have some issues to drive some motor by a Vi created under Labview 2011 using an inspection built under vision builder AI 2011
The step for running a Labview Vi said me that it only support 2010 VIs or earlier ? How two NI softwares 2011 can be incompatible ?
So I try to save under a old version but this vi is part of a huge LLB...Is it possible to save this LLB as a 2010 version without saving all subvis .ctl etc.. ? I am a little confused...
Thank you for your help

You should be able to save the top level VI for previous to LV 2010, and all VIs from that LLB will also be saved to a LV 2010 version LLB that can be used by VBAI. There is a restriction that any VIs from a toolkit that you have to pay for (i.e. Vision), even if they are in your LLB will not be saved for previous, but driver VIs (i.e. Motion, DAQ, NI-IMAQ) if they are in your LLB will be saved in the resulting LV 2010 LLB.
I realize this isn't ideal and VBAI will be supporting LV 2011 or a future version later. Another option will be to use the VBAI API in LV 2011 to have VBAI do just the image processing portion of your control system and do Motion, or other functionality in LV environment and control VBAI from LV using the VBAI API (this allows you to load inspections, run them, get images, and results, etc.), which does support LV 2011.
Hope this helps,
Brad

DAQ Task in Project is incorrect in distributed copy

Greetings all,
I have a question that I can't find the answer to w/ the search. This is odd, but I've generated a DAQ Task in Project in LabWindows that reads a thermocouple and displays temperature in F. It works well until I created a distribution disc & installed it on the computer where it will live. The task works properly, except it displays temperature in C... how can this be? Have I missed something in the distributions section, or is there something else I have to do to the destination machine?
I will add, I have 2 of the DAQ cards, both 6036E. Would it be that I'm using a different card in the destination?
Thanks,
Rob

Rob,
There should be an option in one of the Advanced Tabs when you are building the distribution CD/installer for Including your hardware configuration with the installation. (It should be something along the lines of "Include my Hardware Configuration"). Ensure that this is checked when you are building the distribution so that the hardware configuration can be associated with the program and not just the card. It sounds like moving the 6036 over with the system worked because it was already configured to read in F whereas a different card might now have been without the program storing the hardware configuration information.
Timothy
Timothy S.
PXI & VXI Platform Product Support Engineer

Is it possible for a DAQ task to just stop responding to commands?

The software I am working on controls a NI USB-6501 digital I/O device using the NI-DAQmx library. When the software initializes, it attempts to create 10 "tasks" (for different I/O lines of the device) using DAQmxCreateTask(). If any of the tasks cannot be created, the software should close with an error message.
if ((!CreateTestModeTask(&TestModeTask, USBdevname)) &&
     (!CreateChooseDUTTask(&DUTSelectTask, USBdevname)) &&
     (!CreateChargeStatusTask(&ChargeStatusTask, USBdevname)) &&
     (!CreateInitLinesTask(&InitLinesTask, USBdevname)) &&
     (!CreateChargeEnableTask(&ChargeEnableTask, USBdevname)) &&
     (!CreatePassFailEnableTask(&PF_EnableTask, USBdevname)) &&
     (!CreatePassFailResetTask(&PF_ResetTask, USBdevname)) &&
     (!CreatePassFailStateTask(&PF_StateTask, USBdevname)) &&
     (!CreatePassFailWriteTask(&PF_WriteTask, USBdevname)) &&
     (!CreateResetDUTTask(&ResetDUTTask, USBdevname)))
     continue running the software
else
     show error message and close software
Once the tasks are created, the software goes on to use them to manipulate the I/O signals of the NI USB-6501 device with DAQmxWriteDigitalLines() or DAQmxWriteDigitalU8(). The software does not check whether these functions return an indication of success or not... The assumption is that it works every time.
This is my question:
At run time, is it possible for a successfully created DAQ task to simply stop responding to commands? This is what I believe happened. I observed it only once out of hundreds of trials, but it is still a great concern. Only 1 task stopped properly controlling the NI USB-6501. All of the other ones continued to work properly. It continued to misbehave until I closed and re-started the software (thus re-creating all tasks).
And if it is possible for a task to simply stop responding, is there any way to prevent it?
-Mike

Your assumption that instructions will work every time without facing errors is excessive in my opinion. I never observed a daqmx task simply stopping responding to commands: every time it happened, an error condition was raised explaining the misbehaviour.
I would add some error checking where you are manipulating the daq board and look into the informations the error message gives you.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

How do I increase the precision of a timestamp acquired with a DAQ task?

Hi
I am using a DAQ task to acquire multiple channels of analog data. The waveform data already has timing information incorporated into it. I wanted to know if there was a way of increasing the accuracy of this timestamp information - (Its currently in seconds with a default ms offset for each sample).
Thanks
Brinda

Hello Brinda,
From your posting, it sounds like you are acquiring some waveform data and plotting it to a LabVIEW graph. Unfortunately, the ability to increase the timestamp of your acquired data is going to be a limitation of using a non-real time operating system such as Windows. You may have a device which can sample to some very small precision of accuracy, but if your OS is not able to transfer the data fast enough and timestamp it, then you will see a less precise timestamp than you were hoping. A workaround to get around this would be to use a real time environment and the LabVIEW Real Time module. If this does not seem to be an option, you may also want to consider trying to use a counter to perform the timestamping, or take a look at the LabVIEW exam
ple program I have linked to below.
Timestamping Analog Input Data Using a Counter (DAQ-STC)
Precise Current Timestamp with Milliseconds
Best of luck.
Jared A

Choose the task create in nidatalogger

Hi;
I try to get my new task create with NI-DAQmx Base Task Configurationbut i don't ind it in nidatalogger?

Hi,
NI Data Logger is set up to use physical channels, not tasks.
When you configure tasks, you only can use them in LabVIEW with "DAQmx Task Name Constant".
Hope this help.
Isabelle
Ingénieur d'applications
National Instruments France

LV 8.21: strange behavior with DAQ tasks, parallel running VI's and shift registers

Hello,
I have made a VI using DAQmx vi's. The VI uses shift registers to store DAQ tasks and other (internal) information. I have implemented several modes of operation (enum control with a case structure) like 'init', 'read AD', 'config AD' etc. If I use this multi mode VI in a single main VI everything work as expected. I have attached a jpg that shows one example where the DAQ VI is called from 2 parallel running while loops. One loop aquires the data (LOOP 1) while the other loop configures the aquisition task (LOOP 2). If I implement the same thing by putting LOOP2 in a different VI that runs seperately from the first VI I get an error message (200428):
Possible reason(s):
Measurements: Value passed to the Task/Channels In control is invalid.
The value must refer to a valid task or valid virtual channels.
Task Name: EasyDAQ_AD
Of course, the second VI is started manually after the 1. VI has passed the initialization part. The error message is triggered from the 1. VI that executes the DAQ task. From my understanding of the LV execution system this seems like a bug to me. Does anyone have an idea what could go wrong here?
klaus
Attachments:
problem.jpg ‏30 KB

1. In general, this kind of technique is something I've been using successfully for years. (Ben recently wrote up a very nice treatment of these "Action Engines" as a "Community Nugget.") So I don't start by expecting this to be a bug in the LV execution system.
2. Your description of the problem sounds almost backwards. You say you manually start the 2nd vi ("Config AD") *after* running the 1st vi ("Read AD"). Seems like you'd need to do the Config 1st and then do the Read, right? I kinda suspect you actually did it in the right order, but described it wrong.
3. The next likely scenario is that the Config failed, but you didn't trap the error and were unaware of it. Then it makes sense that the Read would also fail.
4. A couple issues I regularly deal with in these DAQ Action Engines is internal error handling. I often keep a shift register inside to store errors generated inside the Action Engine. But it can get a little tricky doing sensible things with both the internal error and any other error being wired in as input.
I said all that so I can say this: if you have complex nested case statements, or lots of different action cases to handle, double check that the task wire makes it from all the way from left shift register to right. Sometimes they get lost if they go through a case statement, the output tunnel is set to "use default if unwired", and 1 or more of the cases don't wire the output.
-Kevin P.

Task created to stop and start Health service not working.

We have multiple servers being grayed out so we created a task to stop and start the health service on SCOM 2007 R2. We have created two tasks one to stop and another task to start. The STOP task works but the START tasks keeps running but there is no result
as well as when i check in Services.msc it is still stopped. Below are the screen shots .
Task created to STOP the health service which is running.
Screen shot of service start task creation which is NOT working
The same was created for another service windows audio. Which worked for both stop and stop (Created separate tasks).
We also tried the recycle health service and chche which is also failing.
Can any one please help. The issue is on both SCOM 2007R2 and 2012 R2 both. Is there any other way to touch the health service.
We are facing the issue only with Healthservice.

Hi All,
Thank you for all your answers.
@ dktoa -
You are right we have to concentrate on the servers to determine why do they go grey (all in one site). But before we do that i felt i find a temporary solution. Then go deep investigation to solve the issue.
@Yan LI: As per the likn provided above you. I overrided the servers but still the health services were not starting or restarting. When i created a custom group and added the servers to that group in that site and then enabled the override on Restart
Health Service for a specific group and pointed towards that group then it worked.
Thanks All.

Export Project Tasks to Excel using VBA by Custom Field

Question referring to the link:
http://social.technet.microsoft.com/Forums/projectserver/en-US/9c46458c-893f-41ba-bd46-bdb59c533f4a/export-project-tasks-to-excel-using-vba-by-custom-field?forum=project2010custprog
Help needed. I have inserted my question at this address for Andrew or anybody else to reply. Hope to hear from you.
Regards,
Chuck

Thank you Andrew for getting back to me and I have found somewhere on the net the following macro that would do the job for the version 2007. Here is a copy for those that may need it.
Option Explicit
Sub CreateMenus()
Dim cbrMain As CommandBar
Dim ctlMain As CommandBarControl
Dim ctlOLExport1 As CommandBarControl
Dim ctlOLExport2 As CommandBarControl
Dim ctlOLExport3 As CommandBarControl
Set cbrMain = Application.CommandBars.ActiveMenuBar
Set ctlMain = cbrMain.Controls.Add(Type:=msoControlPopup, Temporary:=True)
ctlMain.Caption = "Export to Outlook"
Set ctlOLExport1 = ctlMain.CommandBar.Controls.Add(Type:=msoControlButton)
With ctlOLExport1
.Caption = "Selection to Outlook tasks"
.OnAction = "Macro """ & "Export_Selection_To_OL_Tasks"""
End With
Set ctlOLExport2 = ctlMain.CommandBar.Controls.Add(Type:=msoControlButton)
With ctlOLExport2
.Caption = "Selection to Outlook appointments"
.OnAction = "Macro """ & "Export_Selection_To_OL_Appointments"""
End With
Set ctlOLExport3 = ctlMain.CommandBar.Controls.Add(Type:=msoControlButton)
With ctlOLExport3
.Caption = "Selection to Outlook notes"
.OnAction = "Macro """ & "Export_Selection_To_OL_Notes"""
End With
End Sub
Cheers!
Chuck

Export DAQ Task created in Labview to MAX

Similar Messages

Maybe you are looking for