Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Anyone have any ideas on how to create hardware independent VISA drivers in Labview?
mbuttman
Member
06-06-2002 06:36 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Looking for any ideas on developing hardware independent VISA drivers similar to IVI but using Labview 6.0.2.
mikeporter
Proven Zealot
06-06-2002 09:30 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Could you explain a little more about what you have in mind? In one form or another I have been writing instrument drivers that have had some level of hardware independence since 1985--and in LabVIEW!
What are you wanting to do?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
For help with grief and grieving.
What are you wanting to do?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
For help with grief and grieving.
06-07-2002 09:32 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I am trying to create VISA drivers using the NI model and use them in a structure similar to how the IVI drivers are used. I was thinking of maybe using an ini file to define the instrument model (ie Agilent 8153 or Agilent 8163) and dynamically load the driver for that model but before I explore that idea I thought I would ask around for some advice. Thanks.
btejani
Member
06-07-2002 09:26 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
A good starting point would be the Instrument Driver Development Tools & Resources web page.
As for how to develop a driver with some level of interchangeability, this will depend on your requirements. If you need only to swap between a handful of instruments, you can use case structures in your driver that send different commands to the instruments. If you want full coverage of all features of all instruments with full interchangeability, you will be hard pressed to find any architecture, including IVI, that can provide that. If your needs fall somewhere in between the previous two, I suggest using IVI. Otherwise you will end up reproducing much of the code that has already been written to support IV
I drivers.
--Bankim
As for how to develop a driver with some level of interchangeability, this will depend on your requirements. If you need only to swap between a handful of instruments, you can use case structures in your driver that send different commands to the instruments. If you want full coverage of all features of all instruments with full interchangeability, you will be hard pressed to find any architecture, including IVI, that can provide that. If your needs fall somewhere in between the previous two, I suggest using IVI. Otherwise you will end up reproducing much of the code that has already been written to support IV
I drivers.
--Bankim
06-07-2002 09:35 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Actually one of my requirements is full interchangability. IVI sounds promising but many of the instruments I am using (Optical powermeters, Digital Communications Analyzers, Tunable Lasers) are not defined by IVI classes yet.
btejani
Member
06-07-2002 10:22 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Is your requirement full interchangeability for the features you use, or for all features of all instruments?
You can define your own classes, even if the IVI Foundation hasn't defined them yet. We (as in National Instruments) have in the past assisted developers in building their own class drivers, and there's no reason we wouldn't be able to help you out in that task.
The best step would be to contact us directly at instrument.driver@ni.com.
--Bankim
Bankim Tejani
Instrument Drivers/IVI
You can define your own classes, even if the IVI Foundation hasn't defined them yet. We (as in National Instruments) have in the past assisted developers in building their own class drivers, and there's no reason we wouldn't be able to help you out in that task.
The best step would be to contact us directly at instrument.driver@ni.com.
--Bankim
Bankim Tejani
Instrument Drivers/IVI
06-07-2002 10:40 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
I think IVI is the way to go. I will contact you. Thanks.
