Hi,
I have a (stupid?) question. As I understood the idea of the IVI spec that it provides some sort of abstraction from the hardware. That means an instrument e.g. a power supply is not controlled with a driver xxxx for instrument yyyy from supplier zzzz - instead an application instantiates class dcpwr and calls a methods IviDCPwr_ConfigureVoltageLevel. All the binding to a specific interface and and supplier is done in background using the IVI driver frame work and specific IVI-driver for that instrument. The abstraction allows to exchange an instrument by another one of different supplier. In best case there is not need to change the application in case of instrument change due to the abstraction.
I hoped to find this idea in python-ivi as well. Espically for an environment where VISA drivers (e.g. by NI) are present it is no effort to installs suppliers specific IVI drivers and than using the generic IVI classes.
Why does python-ivi does not dock at this point of generic IVI class DLLs?
Or the other way around: Is it possible to use python-ivi in a way the generic instances can be created without a need of creating specific instrument.py modul?