06-15-2011 06:50 AM
I have updated an oscilloscope driver to handle a newer USBTMC model (Agilent DSO1012A) that is replacing an obsolete GPIB model (Agilent DSO3102A) in a test system. The driver needs to work with either model. I created a simple VI (attached) to see how the VISA Find Resource VI works, but it fails to identify the USBTMC model properly. Instead, it appears in the resource list as "ARSL1::INSTR" (see screenshot). MAX correctly identifies it with a USBTMC resource name, and if I use a VISA Resource Name control in my LabVIEW code the USBTMC resource name also appears correctly in the list. The updated driver is working fine with the USBTMC scope, it's just the VISA Find Resource VI that I have a problem with.
I would like to automate the process as one test system has the old model, and another has the new model. Here are some details of the set up:
LabVIEW 8.0 (specified by the customer), NI-MAX 4.3.0, NI-VISA 4.2, NI 488.2 2.52, IVI Compliance Package 2.3 (includes USBTMC kernel driver)
I have tried running the VI on a different workstation with LabVIEW 2010, and the result is the same. I also tried a similar Tektronix USBTMC scope, again with the same result.
Note on the attached VI: The regex used should find all available resources. Normally, I would use a regex designed to search for the two scope models explicitly.
TIA for any help.
07-01-2011 02:23 AM
Even though there were no replies, I feel obliged to update this post with an admission of guilt, or rather stupidity. The USBTMC device was being found, but for some reason the index spinner on the indicator was defaulting to 1. The device was at index 0, so I didn't see it. D'oh! After over 30 years programming, this may be my finest (senior) moment.
Sorry if I confused anyone. Mea culpa.