Labkey - smart driver Vi - the interface of the same category instruments

[sees]

NI engineer should sort and gather some general instruments driver into a driver VI. It would be a smart Labkey. NI can define a standard command used text script just same as SCPI for general instrments such as DC/AC source, meter, oscilloscope, E-load........ For oscilloscope sum VI, we can just use NI standard functional command, the Labkey can as a interface to find which model or vendor oscilloscope connected and translate the command into the connected instrument command. so NI can reduce drivers quantity and the user can not care for the difference of the command of the different equipment model and vendor. If the developer replace the model or vendor of equipments with others they should not modify their software. The Labkey driver VI should be smart and adapt the change automatically. Just like as .NET frame.

[RavensFan]

I don't see how you ever could get this idea to work.  It is not up to NI to define a standard and try to get all the instrument equipment manufacturers to comply.  It is up to the equipment manufactureres to agree to a standard and comply to.  Only then could NI work to a standard that would work for multiple instruments.

Until you get the manufacturers to work together, the best you can have is for a company like NI to maintain a database of drivers that have been created to work with the hundreds of different instruments out there.

[Dennis_Knutson]

What you are descibing is called IVI and has been around for a dozen years or so.

[Brian_Powell]

To expand on what Dennis said, you'd use the IVI Class Drivers (included with LabVIEW), which provide an abstraction that insulates test programs from the specific driver implementations (some included with LabVIEW and many more downloadable from http://ni.com/idnet) that know how to talk to particular models of instruments.

[G-Money]

Functionality already implemented through the IVI Class Driver.