Nonomiya,
its just some level higher a protocol.
You can yeald good results with less effort when using IVI. For
example, state caching means the driver 'knows' the actual state of the
device and performs just the required steps to change to another
requested state. And as the devellopers of the IVI driver probably know
the device and its capabilities much better than a 'simple' user, such
a state change in IVI is probably much quicker than one based on VISA
commands. Simulation allows you to devellop an app while the real
device is absense, which might be a hige advantage. And when changing a
device (say, replacing a DMM by another different type, maybe
even of a different brand), ideally you just have to change your
IVI configuration in MAX. Your app should continue working flawlessly,
as all IVI drivers should support common IVI commands of their class.
And don't think this will not happen. McMurphy's law will assure that a
device will break whenever you really have no time to wait for a
repair. If the device is not discontinued or repair serevice is
no longer availabel. Or a calibration period expires while you
have to operate continuosly.
I would not like to miss IVI in my projects.
Just my Euro 0.02!
Greetings from Germany!<br>-- <br>Uwe
