LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Which Language is right for the job?

Currently we have a LabVIEW application that a 3rd party vendor created specifically for our needs. This application handles all data logging and instrument control of a large printing press. There is a secondary program that was developed in-house that acts as the user interface to this LabVIEW program and communicated through DDE. My question centers around the fact the we are currently in the process of upgrading the functions of these two programs and would very much like to maintain only one development language. Should we do everything in LabVIEW or VB/C++ with Measeurement Studio? Can someone please point out some quick easy to understand benefits of using either language and which they feel would be a strong
er environment for a growing department. Thanks.
0 Kudos
Message 1 of 3
(2,264 Views)
timsorenson wrote in message
news:50650000000800000057160000-983677784000@quiq.com...
> Currently we have a LabVIEW application that a 3rd party vendor
> created specifically for our needs. This application handles all data
> logging and instrument control of a large printing press. There is a
> secondary program that was developed in-house that acts as the user
> interface to this LabVIEW program and communicated through DDE. My
> question centers around the fact the we are currently in the process
> of upgrading the functions of these two programs and would very much
> like to maintain only one development language. Should we do
> everything in LabVIEW or VB/C++ with Measeurement Studio? Can someone
> please point out some quick easy to understand benef
its of using
> either language and which they feel would be a stronger environment
> for a growing department. Thanks.


Well, you asked in a Labview group, so my answer is Labview.
Of course, it depends on what software you need written.
Here are my reasons.

1) If you require instrument control (DAQ etc), etc. labview is very very
good!
2) Development time in labview is very short, you can't beat it in the
speed in which you can go from initial architecture to final application.
3) It sounds like the majority of the code you mention is already in
labview.
It is easier to write "user interface" in labview than to write "instrument
control"
in CB/C++.
4) You can always hire labview programmers on contract. The NI Alliance is
good for this. (but of course, you can hire anyone you want for c++ too).


Cheers,
bob stockwell
stockwell@co-ra.com
Sunrise Software, LLC
7421 Mt. Sherman Rd.
Longmont, CO 80503
Message 2 of 3
(2,264 Views)
I would also take a strong look at the support requirements for your company. If you are jobbing it out, make sure you are dealing with a company that will be there in the future. If you are going to support it on house, where is your current expertise? Is it in VB/C or LabVIEW? Like most sophisticated tools, I do not believe that you can occasionally use LabVIEW and effectively support a complex application. If you have the in-house commitment to LabVIEW, I would certainly agree that LabVIEW is an excellent choice for this type of application. If you plan on jobbing it out to a LabVIEW shop, it is also a good choice.
Stu
0 Kudos
Message 3 of 3
(2,264 Views)