We have an IVI driver for instrument A, and want to use the class driver to access it. So I modified the IVI driver to be class-compliant, used MA-Ex to create for it:
an Instrument Driver Software Module entry
a Driver Session, whose hardware is listed as instrument A
a Logical Name
and I modified our test software to successfully use the class driver to initialize the IVI driver.
I have another IVI driver for instrument B, and want to use the class driver to access it. Thing is, instrument B is not one specific piece of hardware ... it's a synthetic instrument that uses several of our hardware instruments. So I tried to duplicate the steps I used for instrument A above. The difference is that I can't associate its driver sesson with any one piece of hardware and MA-Ex won't allow me to connect it with more than one. So I left it unconnected to any hardware. If I initialize my IVI driver using the specific driver call, I can give it either its resource name (which we invented) or its logical name. If I try to initialize using the class driver call with the logical name, I get "Function or method not supported". If I try to initialize using the class driver call with the resource name, I get "The session name or logical name could not be resolved to a session or driver session".
I tried turning my instrument B driver into a Simulation Driver Software Module and creating for it a simulation driver session. The results were the same as above.
We don't have source for the class drivers, so we can't go in with our debugger to see what, exactly, is failing. And from reading the description of the Configuration Store, we can't figure out what we're missing or doing wrong.
Our MA-Ex version is 4.2
Our IVI Compliance version is 3.0
Can anyone offer any help or suggestions? Thanks in advance ...
B
