12-02-2009 07:19 AM - edited 12-02-2009 07:23 AM
12-03-2009 08:52 AM
Hello Jon,
It is very probable that simulating the board is causing the difference. When do you plan on having a board to test with? Hopefully someone with a real device will run your code and let us know what they see.
Cheers,
NathanT
12-03-2009 05:24 PM
Hi Jon,
Your VI gives the same behavior on a real 5105 module as well. The reason for this is that only channels 0 and 1 are listed in the niScope Software Module's Physical Names list and this is what you are querying. To add more channels to this list, you will need to go into Measurement & Automation Explorer (MAX), navigate under Configuration on the left side to My System »IVI Drivers »Advanced »Instrument Driver Software Modules »niScope, and select the Physical Names tab of the main section in the middle, as shown below.
You can then add up to channel 7 for compatibility with the 5105. Out of curiosity, I am wondering what the overall goal of this program is, since you are simply getting information from the software module as to what physical names it contains. This is not something that will be dynamic based on the specific device selected for the driver session.
Hope this helps,
12-03-2009 05:32 PM
Sorry for the double post, I meant to mention at the end of my last post that you can change your software module to have 8 physical names for the channels, and then create different driver sessions with the appropriate virtual names. Then, instead of querying the physical names, you can get the virtual names for the driver session. I have shown an example of this below.
Hope this helps,
12-04-2009 03:59 AM
Hi Daniel,
Thanks for that. So the physicals names are based on the Software Module itself and have no relation to the actual hardware. I did consider using virtual names but I thought by using physical names I could get round the user having to create the virtual names before the instrument can be used. I will just go back to using the virtual names then and have to ensure that the user always creates them.
In answer to what it is actually for I am creating an IVI-Scope LabVIEW module that allows run-time access to a pop up an interactive soft front panel for debug purposes.
Thanks for your help.