> 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: 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".
> 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: 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".
Since one of my customer has License for both Agilent VEE Pro 7.5 and LabVIEW 8.0,I have been asked to make a document which List out advantages and disadvantages of this graphical languages. I know it is a worst thing to do on earth but I don't have any choice (Do or Die).I have captured some points but I just want to post this question with a hope that there is someone at other end who can help me. Please forgive me if you think I have asked irrelevant question. If this question is discussed earlier anywhere please point me to the link
Regards,
Karthik SP
With warm regards,
Karthik.SP
Software Engineer,
Embedded Systems
--- 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".