which is better Labview or VEE pro

[RRCAT]

 Hello

 I would like to know  which graphical  programming  software is better and why? The question why in short comparision between labview and VEE pro.

kane

[GerdW]

Hi Kane,

what kind of answer do you expect in a LabView forum? Most of us only work with LabView, many of us for several years...

But it's also interesting for me to read some informations on VEE too... Atleast there is also a website (www.agilent.com) with an user forum 🙂

[tst]

Also if you search for "VEE" here you should find some threads on this (and presumably also if you search for "LabVIEW" in the VEE forums).

[falkpl]

I have been using labview for almost 10 years, so obviously I am biased towards it but two years ago I spent some time learning and converting some VEE code to labview.  Learning both environments I found LV to be the superior graphical environment but this is my personal opinion. 

Paul

[Ben]

Please see Dennis' response # 9 in this thread.

http://forums.ni.com/ni/board/message?board.id=170&message.id=146968#M146968

I think it is "classic" and concidering that Dennis is our top contributor, his choice to go with LV say a LOT!

Ben

[Dennis_Knutson]

I just went to Agilent's web site and had a look at their new release. It now supports NI  Data Acquisition boards!

I suspect they did that because it was next to impossible to find VEE drivers for any type of DAQ. I think VEE's emphasis has always been on GPIB type of instruments. Not much of anything in the way of data acquisiton, vision, sound, motion, etc. And while I could find a failrly large number of 'panel drivers' for VEE, they were almost entirely for Agilent instruments. Agilent seems to be concentrating on plug & play type drivers for newer instruments (and from other vendors). And while you can use them (just like LabVIEW can use them), you have no way to modify them. Contrast that with the number of instrument drivers NI has availaible written in LabVIEW itself.

I also noticed that the VEE 'forum' was a mail server similiar to Info-LabVIEW. I would recomend to anyone considering VEE that they subscribe to this first. It would be interesting to see how much traffic there is and how fast questions get answered.

[altenbach]

Better: LabVIEW

Why?: It is much more versatile and powerful. (Ask a VEE programmer to create an entry for one of our LabVIEW coding challenges  and see how far he/she gets. 🙂 Of course it might be hard to find a VEE programmer in the first place ...).

Back in 1995 when I started with LabVIEW, HP really tried to convince me that VEE is better via many phone calls, junkmail and free demo software. Our lab had high regards for HP hardware, so there clearly was some bias towards VEE that I had to convincingly argue against.

LabVIEW was love at first sight, but could never get the hang of VEE (yes, I installed it and gave it a fair try!). LabVIEW has never let me down. Every programming task I throw at it is done in record time and works as designed.

I know of a group in a similar situation that decided on VEE back then. Suffice to say, they switched over to LabVIEW years later. Learn from their mistake! 🙂

[tbob]

I learned VEE before I learned Labview.  Worked with VEE for one year.  Yeah I thought it was pretty good.  I liked the graphical concept vs text based programming.  Then I was introduced to Labview 5.1.  WOW.  What an improvement.  I've been using LV ever since and would never go back to VEE.  LV has a lot more functionality, more drivers, etc.  Take a look at how VEE implements a loop, then look at Labview's loop.  Labview is much more easier to understand and code.  Just see for yourself.  I'm sure if you went to a VEE website, you would hear different opinions.  But you should try both and decide for yourself which you would rather work with.  I would lay 10:1 odds that you would choose Labview.

[napview]

About a year ago I got the latest EDR Bluetooth test box from Agilent and guess what? Its dll drivers completely hosed up the ones installed from NI. So the gpib32.dll from Agilent had to be renamed so the NI GPIB card can run properly. Other annoying thing was like someone else already mentioned that Agilent now uses dll to develop drivers (CIN function) and if you want to modify them in LV then there is no way.

So where was the story about LV vs VEE? I tried to use LV to control the box but a few GPIB commands did not work properly so the technical support person who does not about LV sent me an example in VEE (of course to work with Agilent). Then I downloaded the free trial version of VEE to open the example and it was nice to have a big variable display box (like LV controls) and the similar wiring connection but after playing around with it, I believe LV is more flexible and takes LESS space on the front panel and block diagram is way better to debug than VEE, just some simple things like that.

[jwdz]

Better: LabVIEW