LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Choosing Driver for third party instruments

Hello,

 

I am working on designing a new test system and we are planning on using some Keysight Precision Power supplies N6700, N6900 and N5700 series. I was wondering if I should chose the labwindows cvi drivers or the labview drivers for the project.

 

my main concerns are:

long term support

availability of functions

reliability of using LabVIEW vs lab windows cvi

instrument drivers vs direct scpi commands on LabVIEW vs lab windows cvi

compatibility with test stand

overhead difference between lab view and labwindows

hardware requirements for labview driver and test stand based system vs labwindows cvi and test stand based system

 

anyone have any experience or technical insight into the pros and cons of chosing labwindow cvi/ivi drivers vs labview drivers for third party instruments?

 

0 Kudos
Message 1 of 8
(385 Views)

I bet they both call the same DLL, so the difference will be null to miniscule. 🙂

G# - Award winning reference based OOP for LV, for free! ADDQ VIPM Now on GitHub
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
Certified-LabVIEW-Developer
0 Kudos
Message 2 of 8
(377 Views)

Personally, I am partial to using my own drivers using the SCPI commands and written in LabVIEW.  The N5700 follows the standard SCPI commands for nearly all power supplies I have used in the last 10 years.  So that driver I can reuse.  The N6700 series is a little different due to it having up to 4 modules.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 3 of 8
(356 Views)

I would stick with the LabVIEW drivers that use SCPI commands for long term support and reliability.

 

I try to avoid any driver that just calls a DLL as future DLL compatibility is always a dice roll. Plus you have always distribute that DLL and some need to be "installed" or properly "registered" meaning they need their own installer ran after installing the LabVIEW application, adding another layer of complexity and another possible failure point.

 

 

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 4 of 8
(347 Views)

@Yamaeda wrote:

I bet they both call the same DLL, so the difference will be null to miniscule. 🙂


I have some experience with the LabVIEW drivers.  They are fancy wrappers for SCPI commands - although I must say, the fancy wrappers makes life very easy for the developer.

 

I know nothing of the CVI drivers, though.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 5 of 8
(343 Views)

@VP95 wrote:

Hello,

 

I am working on designing a new test system and we are planning on using some Keysight Precision Power supplies N6700, N6900 and N5700 series. I was wondering if I should chose the labwindows cvi drivers or the labview drivers for the project.

 

my main concerns are:

long term support

availability of functions

reliability of using LabVIEW vs lab windows cvi

instrument drivers vs direct scpi commands on LabVIEW vs lab windows cvi

compatibility with test stand

overhead difference between lab view and labwindows

hardware requirements for labview driver and test stand based system vs labwindows cvi and test stand based system

 

anyone have any experience or technical insight into the pros and cons of chosing labwindow cvi/ivi drivers vs labview drivers for third party instruments?

 


This is a little confusing for me, though.  Are you asking about drivers or platforms?  It's a little odd that you would be more concerned about drivers than platforms.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 6 of 8
(339 Views)

Hello,

 

the platforms are a concern as well.

0 Kudos
Message 7 of 8
(329 Views)

If you are thinking of integrating with TestStand, I would say, "why not both?"  I think it matters more about the developers' familiarity with the different languages than anything else.  TestStand will be happy with LabVIEW, LabWindows/CVI, and a whole bunch of other stuff as well.  Mix and match as needed.

 

I don't use TestStand regularly at all, so maybe there is a big difference between theory of operation and reality.  😉

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 8 of 8
(314 Views)