Has anyone designed a "functional" hardware interface layer (as opposed to an instrument-based HIL like IVI)?

[dowNow]

This type of interface layer would basically be a lookup table of device neutral operations vs. instrument type, instrument address, function prototype, other instrument specific info. The goal is of course to allow instrument interchangeability without affecting application code.

So I'm trying to figure out different ways to arrange this, one approach would be to have a custom step type for each operation, and some properties document that contained the current hardware setup. Properties would be loaded at runtime into either step or local variables etc.

Anyway, on the slim chance there is someone out there who could discuss this with me, let me know.

[JLS]

Hello,

It sounds like you are looking for more of an abstraction that provided by IVI class drivers. This is an interesting proposition, however, I think that interchangeability among instruments of different classes will be very minimal. For example, you may be able to "initialize" and "close" most hardware, but as soon as a program configures a measurement of some kind (such as configuring parameters for a resistance measurement on a dmm), it becomes relevant only for a certain "class" of instruments. Feel free to post more here, or to email instrument.drivers@ni.com for more opinions 🙂

Best Regards,

JLS