What's the advantages when developing a family of R232 automotive communcation driver based on IVI technology, compared to traditional write/read low-level functions?

[jacky Wang]

  IVI is based on the well established VISA standard with new features,such as simulation, caching, COM, and so on....Sometimes i don't need these new function. For example, I want to develop an family of automotive communcation drivers(KW2000, ALDL, KW71) based on R232 port. I can use basic I/O write/read functions to fulfill this or use IVI technology. So what is the major advantages if based on IVI, can I speed up development greatly? (What I care most is development speed)

[Robert M]

You've mentioned two of the three main options when it comes to device drivers.  The one you didn't mention is using LabVIEW plug and play drivers.  There is usually a plug and play driver for an instrument if there's already an IVI driver for it.  What instrument are you connecting to?  You can search our Instrument Driver Network to see if there is one available for your instrument.  If you do not need the additional features of an IVI driver, then we recommend using the plug and play driver, as it is generally easier to use and results in a shorter develop time.

Hope this helps,

[jacky Wang]

  Actually I am more familiar with CVI, rather than LabVIEW. I connect PC to ECM (engine control unit) via an AVT automotive communication box, which supports a lot of automotive protocols.

  I somewhat have difficulty to learn IVI driver development based on CVI, could you give me some suggestions about it? Which is a recommended path for entry into IVI driver development in a short time?

Thanks!

Jacky

[Robert M]

Jacky,

Are you looking to develop an IVI driver or do you want to simply develop an applicaton to communicate with an ECM?  What kind of AVT do you have?

[jacky Wang]

That's just my concern.: which is good sultion to develop a family of communication drivers? What I most care about is development speed and conventiency. Actually I don't care about whether to use IVI or not.

Introduction to AVT718 box:

Multiple protocol interface.
R232 connection to host computer.
Protocols supported:KW71, CAN, KW2000.ALDL, LIN, etc.

[Robert M]

Jacky,

What's your end goal?  Are you developing this AVT and want to provide an API to your customers?  Or are you using this AVT for a quick project you are working on?  Or are you developing a suite of functions for your company to use for a while in the future?  What is the scope of what you are doing?  How many of these protocols do you want to implement?

[jacky Wang]

I am developing a suite of functions for my company to use for a while in the future, there are 7 protocols totally.

If I use IVI, I expect to have a class driver, and 7 specific driver for 7 protocols, then in future, if we want to add some protocols, I can add specific drivers based on that class driver.

if not IVI, then I have to develop 7 individual drivers for  7 protocols.

Now what i try to make clear is:

1, NI IVI driver development wizard could speed up my development??? assuming I have a command of IVI development.

2, Are there more advantages if i use IVI?

3, if IVI, What is a recommended study path for developing IVI driver. I have little knowledge about IVI driver development, even though I have been using CVI .

[Robert M]

Hi Jacky,

The IVI Driver Development Wizard will definitely speed up your development.  The wizard, among other things, provides a template, allowing you to reuse common instrument functionality.  We have some tutorials on our site that will be a great starting point for you:

Developing an IVI Driver - Architecture and Development Tools Overview
How IVI-C Instrument Driver Technology Enables System Longevity and Platform Portability
Improving Test Performance through Instrument Driver State Management
IVI Specific Driver Test Suite Description

Regards,

Message Edited by Robert M on 12-06-2005 01:58 PM