Can a DAQmx Task generated in LabVIEW be used in VB.NET?

[Bazza]

Hi,

My question is simple (I think), but I thought it may be worth giving some background to why I am asking the question.

I have a LabVIEW code module I call in the setup group of teststand that generates a whole range of measurement tasks for a given sequence. Scattered throughout that sequence I have further LabVIEW modules that use those tasks to make measurements (according to the application requirements of the test package). The tasks are cleared at the end of the sequence with another labVIEW code module.

My question is based around what software can use these labVIEW generated tasks to start/stop/read/write measurements. Specifically I am interested in knowing whether .NET apps can use these tasks. This is necessary because an increasing number of developers that are starting to use my test development stations only have experience with .NET tools. My thought is that if they can still use the standard LabVIEW code modules to generate and clear the tasks (these are implemented as well proven custom step types in TS), they can implement the business logic of the test package with the tool they are familiar with.

I know using MAX to manage the DAQmx tasks would allow any app to use them, but there are some very specific reasons for not using MAX in this way (mostly logistical). Ultimately I need to know whether the tasks generated with 'DAQmx Create Task.vi' and 'DAQmx Create Channel.vi' have the same global scope as they do when generated in MAX.

I would willingly try this out myself but my knowledge of .NET at this time is very limited and I feel I would not get to fully appreciate any issues related to the implementation.

Any help with this would be greatly appreciated - just hope I havnt clouded the question with all my guff!

Also, I have cross posted this message to the LabVIEW board....

Thanks

Bazza

[nd]

Bazza,
I believe the answer is no.They do not.
You will have to store your tasks in MAX for them to be accessible across multiple IDEs like LabVIEW and .NET.

Could you be a little more specific on what you mean by the logistical aspects of having tasks in MAX?
What are your concerns? Is it just having too many tasks in there? Or someone blapping over them ?
Thanks!

[Bazza]

Thankyou for your reply Nandan.

Not exactly the answer I wanted to hear, but none the less helpful!

There are several issues I have with MAX managing the tasks.

To fully appreciate the problem, it may be useful to know a little about our systems. We currently have two runtime stations with fixed PXI hardware installed - this is to grow to atleast 6 in the next 18 months (and deployed as far as Japan, Germany, and the US aswell as in the UK). In the UK we have 4 test development engineers (this number is also very likely to grow) producing functional test packages that will all eventually go onto every runtime station. Each package will need to be installed with ease onto a runtime station by users very unlikely to be NI literate (IT person). We do not want to have to send a TDE out to every station every time a package is released.

1. The potential for TDE's specifying task names already in use is high. Especially as Packages are developed in parallel. I realise this could be managed with a good set of guidelines.

2. How easy is it to combine the tasks from a new test package onto a system with lots of existing tasks? If this has to be a manual task, I think it is too much to expect of someone with little knowledge of MAX - unless it could be automated into an installation process? Currently each package instsallation is self contained in that it is an executable and does not require manual intervention (all current packages are in LabVIEW only).

3. I hadnt thought about the issue of someone deleting / altering the tasks but it could be a real issue. Although isnt there a way of making a user login to MAX before they can edit things? (Not looked into this, just typing as I think!)

4. I am also slightly concerned about the sheer number of tasks that MAX would eventually have to handle. It is likely that an average of 12 test packages will be written annually, each with 40 measurement tasks (this is an rough average based on test packages completed to date). This means in one year alone we could easily have 480 tasks, and the plan is to have test packages written for the systems for many years to come.

Ideally it would be possible for each test package to have its own set of measurement tasks that are loaded in to MAX when the sequence is loaded and out of MAX when the sequence is unloaded. Is it possible to programatically enter measurement tasks into MAX? (and to remove them?)

Thankyou for your time in reading this message. I hope you understand the logistics involved with our systems!

Cheers,

Bazza

[brents]

Hi Bazza,

MAX is designed to be the repository for global NI-DAQmx tasks, channels, and scales. The NI-DAQmx Assistant makes configuration of these items quite easy. However, if interactive configuration is not your bag, NI-DAQmx 7.4 (which just shipped!) supports saving tasks, channels, and scales to MAX programmatically through the ADE of your choice. In fact, programmatic saves may make it easier for your individual programs to "install" shared configurations. And, the programmatic saves interface has options for "allow interactive deletion?" and "allow interactive editing?" which can be leveraged to make it difficult for your coworkers to inadvertantly delete or modify your configurations in MAX.

Thanks,
Brent

[Bazza]

Thankyou Brent!

That is exactly what I wanted to hear. Sounds like it will do everything required of our systems.

I am downloading it as I write this.

Regards,

Bazza