Task interface for large device count

[VegHead]

I've got 3 18-slot PXI Chassis populated with strain and S-series cards. I can synchronize and use 2 at a time when necessary.

The systems will be used as a dynamic data acquisition system, meaning that no two uses for the system will be the same.

My users are MAX and LV illiterate and one or two are computer illiterate. So I’m trying to create an interface that will ask them questions about sensor type, sensor location…. That will ultimately generate a task for each device used. The strain cards are 2 channel and can’t be combined in tasks. The S series cards can be combined in tasks.

This probably doesn’t sound like any big deal, but what I run into next is saving the set up. I would like to just save the tasks but have found that this is no small obstacle to over come. All I’ve been able to come up with would be saving the task.vi inputs into some file and parsing the info back and forth to recall/save a setup or use the limited MAX vi’s to save and recall the tasks.

The MAX option doesn’t seem very good as it doesn’t allow a way to clear out all of the unused tasks in MAX. Since the users are MAX illiterate the task list will never be cleared out and will end up being thousands of tasks long by years end. Not acceptable in my opinion.

So has anybody out there already created some wizard or cool user interface that covers all of my needs and more?

If that is a pipe dream I’m definitely open to any suggestions.

I’ve been programming for about 10 years and have my CLD so don’t dumb up your suggestions, throw it at me as hard as you can.

Thanks

[Grampa_of_Oliva_n_Eden]

Not knowing how this will be used combined with non-computer literate users ......

I have used graphic interfaces the operators can relate to and then did all of the channel configuration explicity behinf the scenes.

Here is an application I developed for the Army that determines if their equipment can withstand the forces of being transported strapped under a helicopter.

http://forums.lavag.org/index.php?act=attach&type=post&id=6507

The operators know how to rig an plug in load cells. I do the rest.

Ben

[crelf]

You *can* make your own interface - pretty much all the right hooks are there, but it sounds like the only real issue is that you can delete groups of tasks. You're going to need to train your users, whether it's to use your homebrewed version or MAX. You might want to add the functionality in your software to do the dynamic task deletion, but I'd still steer the users to MAX for the gross channel definition and configuration. If your users know their sensors and equipment well, then teaching them MAX should be relatively striaght-forward.

[VegHead]

QUOTE(crelf @ Jul 31 2007, 01:01 PM)

You *can* make your own interface - pretty much all the right hooks are there, but it sounds like the only real issue is that you can delete groups of tasks. You're going to need to train your users, whether it's to use your homebrewed version or MAX. You might want to add the functionality in your software to do the dynamic task deletion, but I'd still steer the users to MAX for the gross channel definition and configuration. If your users know their sensors and equipment well, then teaching them MAX should be relatively striaght-forward.

That is basicall the conclusion I've been coming up with.

I suppose that I should teach them how to export their configuration also. I supposed another option is to programatically save the *.nce file with the data and when they want to recall their Tasks they will have to import through MAX and select the *.nce file that is with the data.

Any suggestions on saving and recalling MAX configurations?

Since recalling configurations merges with the existing tasks I can see this getting way out of hand. The users won't take the time to clean up after themselves. Any suggestions about importing?

I've also noticed that import wizard show's every thing it's going to import along with yellow warnings all over the place. I don't want users to have to deal with this.

Is there a way you know of to programatically clear out all tasks and virtual channels before importing?

My thought is that I'll have a standard configuration including 1 task for every piece of hardware. The user then has a starting point, can name his channels, configure them and scale them. When he's done I can delete all the tasks that are unchanged and save the configuration.

If the user wants to recall a configuration I would programatically clear all tasks then import the user setup.

Thanks,

Dave