02-09-2006 09:49 AM
02-09-2006 10:23 AM
02-09-2006 02:00 PM
02-09-2006 02:41 PM
02-09-2006 06:33 PM
Ok, I'll admit your good...
But I think that NI should create an 'Add Global Channel to Task' vi. Your solution may be the only way to do this but it has the unfortunate side effect of invoking MAX which can be painfully slow.
02-10-2006 09:56 AM
01-15-2008 06:54 AM
Old thread, but let me pipe in as the 2nd person you've heard of who'd like this feature.
Use case: I'd like to interleave app-defined global virtual channels with the internal physical channel named something like "_aignd_vs_aignd" because various global channels require very different gains from the daq board and I'm seeing ill effects like bleed-through or cross-over or whatever the right term is. By interleaving a scan that ties both differential inputs to AI Gnd, my "real" channels appear to show better isolation. (Note: project is at a stage where software fix is far preferable to electronics hardware fix, such as adjusting bias resistors.)
I downloaded the example above and will try it out. The earlier comment about slow speed of dealing with MAX may drive me to adapt the suggestion shown in this similar thread. Question: when you feed an existing task in as an input to "Create Task.vi", the help says that the task is copied. Since I will ultimately want the app to use a single task containing all the channels of interest, doesn't that imply that I should Clear the input task immediately after copying it with "Create Task"?
Other note: I know that I could drop a channel property node to determine the physical channel associated with a global virtual channel. Then I could do the config based on physical channels alone. But I would lose the association to each global channel's unique parameters such as scaling, etc. In short, yeah there are workarounds, but they're more of a pain than they ought to be.
-Kevin P.
01-17-2008 05:20 AM - edited 01-17-2008 05:22 AM