Norbert B
2006-05-19 08:40:18 UTC
gumby,
you can store the physical channel information in teststand as strings and pass them to a "init DAQmx"vi you create to build your task. you can there combine the channelstrings to a single channelstring (please check out the DAQmx-examples for multiple channel configuration) and pass this to the creat virtual channel vi. now add timing and trigger infos, and you then can measure the correct channels. if you want to use these channelsettings in several vis of your application, you would like to pass the reference to the DAQmx to teststand. please remark that the reference is no pointer but a struct (container). in teststand 3.5 you will be prompted to create an appropriate datatype for this parameter if you hit the correct button.
Norbert B.
you can store the physical channel information in teststand as strings and pass them to a "init DAQmx"vi you create to build your task. you can there combine the channelstrings to a single channelstring (please check out the DAQmx-examples for multiple channel configuration) and pass this to the creat virtual channel vi. now add timing and trigger infos, and you then can measure the correct channels. if you want to use these channelsettings in several vis of your application, you would like to pass the reference to the DAQmx to teststand. please remark that the reference is no pointer but a struct (container). in teststand 3.5 you will be prompted to create an appropriate datatype for this parameter if you hit the correct button.
Norbert B.