10-24-2005 11:02 PM
10-25-2005 10:10 AM
When you try to compare SCPI with IVI, you're really comparing apples to oranges. SCPI defines the command set that an instrument uses for it's programming. IVI defines the functions that an instrument implements. I believe that the only software component that IVI specifies is that an IVI driver will use VISA. So, in the case of a DMM, SCPI will say that a command such as CONF:VOLT:DC will set it to measure volts while IVI will say that a compliant DMM will have a voltage measurement function. An IVI DMM does not have to implement SCPI. Use of an IVI driver hides all of the details of the actual programming implementation. You can, for example, replace a DMM from vendor A that uses SCPI, with a DMM from vendor B that uses register based programming. That is the advantage of IVI. SCPI predates IVI and was an attempt to standardize instrument commands. In theory, a DMM from vendor A that used SCPI would have the exact same command set as a DMM from vendor B that also used SCPI. That fact that vendor A and vendor B actually used slightly different command sets is one reason for the creation of IVI. An IVI class driver is a further layer of abstraction that defines common functions and lets the lower level instrument driver perform the actual implementation.
If you just want ot find a DMM that has an IVI driver and is programmed with SCPI, then I would suggest you look at the Agilent 34401.
10-25-2005 08:49 PM
10-26-2005 09:26 AM