AnsweredAssumed Answered

FW: vrf Agilent VEE Pro 7.5 and LabVIEW 8.0

Question asked by VRFuser on Aug 20, 2007

I think Les just nailed it.
3) 60+ engineers back in the lab are making continuous improvements on LabVIEW.
Few years back during Vee days I asked how many people was in Vee R&D team.
The answer I got was "more than 5". Could be 6?
Hmm... 6 vs 60.
Looks to me like marketing is not the only problem.



Vlad  Losik
Electrical Engr
Tyco Electronics
M/A-COM - Commercial Product Solutions
100 Chelmsford St.
Lowell MA 01853
Phone 978-656-2629

-----Original Message-----
From: Les Hammer [mailto:les_hammer@att.net]
Sent: Friday, August 17, 2007 6:07 PM
To: VRF
Subject: RE: [vrf] Agilent VEE Pro 7.5 and LabVIEW 8.0

> I should also mention that VEE has one thing that Labview does not,
> and
that is this list.

NI does have a Discussion Forum for things like this.

In my opinion some of the the LabVIEW advantages are:
1) The "State Machine."
   LabVIEW's "While loop" looks like a box into which you put program statements.
   You can feed in several items, including a "starting state."
   Process that state in a case statement and output, among other things, the next state.
   The loops also make handling arrays easy - automatically processing each element
   and building an output array.

2) You can make a .dll out of your program.  A C++ program can call this .dll.

3) 60+ engineers back in the lab are making continuous improvements on LabVIEW.

4) Needed items are "just there" in the menu.  Recently I needed to do Bluetooth
   communications.  Turn on LabVIEW, connect up the icons and we're talking.
   Where's the VEE Bluetooth icon?
   A few years back I made a LabVIEW program that uses the microphone input on
   my PC as an input to an audio scope.  Everything I needed was in LabVIEW.
   What icon do I use in VEE to get the microphone input?  Sure, I probably can
   call some windows function, but with LabVIEW I don't have to find that function.

VEE's advantages:
1) VEE does a better job of routing the program lines/traces.  In LabVIEW a trace can
   be going under another object but not really be connected to it - making it confusing.
   The programmer has to manually route things properly.

2) Everything is kept in one programing file.  In LabVIEW when you make a sub-VI it
   creates another file.  This can lead to confusion/mistakes when archiving
files:
   oops, forgot to save that one.

3) Speaking of the program files:  VEE - text based - there is some hope of editing
   it to go back a revision.  LabVIEW - binary.

~~Les Hammer


---
You are currently subscribed to vrf as: losikv@tycoelectronics.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com"
with the word subscribe in the message body.
To unsubscribe send a blank email to
"leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list,  email "vrf@agilent.com". 
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at
"http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".

---
You are currently subscribed to vrf as: hua_jing@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list,  email "vrf@agilent.com". 
If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "http://www.vrfarchive.com/vrf_archive".
Search the Agilent vrf archive at "http://vee.engineering.agilent.com".

Outcomes