Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

project style instrument driver

Solved!
Go to solution

Hi All,

 

1. What is the advantage or significance of the Project-style Instrument Driver over LLB type instrument driver?

2. Should the project file be located in "C:\Program Files\National Instruments\LabVIEW 8.0\instr.lib" directory?

 

(My problem is If i use the driver from location other than the mentioned directory, all the VIs linked to the path showing C:\Program Files\National Instruments\LabVIEW 8.0\instr.lib\Chroma ATE 6310)

 

Please find the attached image.

 

Can anyone explain why this happens?

 

Thanks,

Davidson

0 Kudos
Message 1 of 12
(6,732 Views)

Hello Davidson,

        LabVIEW project-style Plug and Play Instrument Drivers have a number of advantages, many of which pertain to developing or modifying the Instrument Driver.  From the end-user perspective, the main advantage that I see is that you can open up the project and have another way of viewing the VIs other than the VI Tree or function pallets.

 

       Yes, all LabVIEW Plug and Play Instrument Drivers (project-style or not) and LabVIEW wrappers around other instrument drivers should be located in ...instr.lib.

 

Here is a tutorial that recommend you take a look at: How to Use an Instrument Driver in LabVIEW.  There is a cool LabVIEW feature that allows you to download and install an Instrument Driver through LabVIEW instead of having to manually download and install it.

 

Cheers,

 

NathanT

Message 2 of 12
(6,719 Views)
Solution
Accepted by topic author Davidson_D

Hi Nathan,

 

Thanks for the very useful link. Cool Smiley Happy

So if i need to get rid of the cross linking, i need to (manually download) copy the driver to the C:\Program Files\National Instruments\LabVIEW 8.0\instr.lib" directory.

 

Thanks,

Davidson

0 Kudos
Message 3 of 12
(6,702 Views)

Hi Davidson

 

In fact you should have made Nathan's post the accepted solution. But You gave him the right credits so it's ok

greetings from the Netherlands
Message 4 of 12
(6,694 Views)

Albert,

 

I'll keep this in mind for my next post.

 

What happened actually is "Accpted Solution" option appeared for both replies, but i clicked on my reply first thinking that i can select Nathan's reply next.

I mistook it.

 

Thanks for the regards Albert.

 

Thanks,

Davidson 

0 Kudos
Message 5 of 12
(6,686 Views)

Hello Davidson,

       I am glad that you are up and running now.  There is a lot of good documentation available from ni.com/idnet that talks about using and developing instrument drivers.

 

Cheers,

 

NathanT

Message 6 of 12
(6,671 Views)

Dear all,

I meet the same question, please attation the driver's local.

Boone

0 Kudos
Message 7 of 12
(5,412 Views)
What exactly is your question? What is the problem in the image? You are pointing to something that most of us cannot read.
0 Kudos
Message 8 of 12
(5,382 Views)

Dear Boone,

 

Is your question related to why the list of VIs shown below?

If so it is the dependencies which your main VI (Arrow pointing) has in the instrument library folder.

 

Please go through the following link to get a better understanding of how to use Project Explorer.

 

http://zone.ni.com/devzone/cda/tut/p/id/7197#toc2

 

Thanks,

Davidson

0 Kudos
Message 9 of 12
(5,367 Views)

Dear all,

At first thanks for you so kind to answer my question.

I want to include drivers in project, the driver have like project than before, not use the drivers at ...\National Instruments\LabVIEW 8.6\instr.lib.

some people will modify the drivers, so the drivers in this project not like in other project, so I want include the drivers in project by project.

I want you can understand my means, I sorry for my poor English.

Boone

0 Kudos
Message 10 of 12
(5,308 Views)