LabVIEW
LabVIEW better than VB?
Martin.D wrote:
> HI,<br><br>Our customer requested that a motion system should be
> constructed with VB and Omron hardware. Fortunately they accepted
> LabVIEW and NI-hardware due to the fact we said this would result in
> a shorter delivery time (because I have not used VB for large apps before).
> They are considering re-writing the application in VB after delivery,
> so that the in-house programmer can further develop the system.
> The system is quite complex - it involves 10-axis of motion to control
> and parallel software loops. The question I am asked again and again -
> "Why is LabVIEW better than VB for this?". Unfortunately after much
> investigation this seems hard to summarise. I have read all the previous
> posts but there does not seem to be any argument to convince that LabVIEW
> is the better solution here. I'm looking for a sentence or two that goes
> some way to convincing people LabVIEW is the better solution - any ideas?
Mostly it depends with what you are familiar with. I couldn't write
almost any real app in Visual Basic and deliver it in a reasonable time.
There are people who claim they can do anything in Visual Basic in a
short time, but for me I simply miss the overview over what methods do
what and when in VB.
Why do they want to consider to rewrite the whole app? That is a major
undertaking and really only justified if they are not happy with what
they have now and consider redoing it anyhow, and/or don't feel you
would be available in the future for timely maintenance work. as such it
seems more a management and communication problem to me than what
software really is better.
Rolf Kalbermatter
> HI,<br><br>Our customer requested that a motion system should be
> constructed with VB and Omron hardware. Fortunately they accepted
> LabVIEW and NI-hardware due to the fact we said this would result in
> a shorter delivery time (because I have not used VB for large apps before).
> They are considering re-writing the application in VB after delivery,
> so that the in-house programmer can further develop the system.
> The system is quite complex - it involves 10-axis of motion to control
> and parallel software loops. The question I am asked again and again -
> "Why is LabVIEW better than VB for this?". Unfortunately after much
> investigation this seems hard to summarise. I have read all the previous
> posts but there does not seem to be any argument to convince that LabVIEW
> is the better solution here. I'm looking for a sentence or two that goes
> some way to convincing people LabVIEW is the better solution - any ideas?
Mostly it depends with what you are familiar with. I couldn't write
almost any real app in Visual Basic and deliver it in a reasonable time.
There are people who claim they can do anything in Visual Basic in a
short time, but for me I simply miss the overview over what methods do
what and when in VB.
Why do they want to consider to rewrite the whole app? That is a major
undertaking and really only justified if they are not happy with what
they have now and consider redoing it anyhow, and/or don't feel you
would be available in the future for timely maintenance work. as such it
seems more a management and communication problem to me than what
software really is better.
Rolf Kalbermatter
@Joe Guo wrote:
Although labview is faster in development and easier to maintain, it is much harder to distribute. Every version of labview has its own runtime engine and there are no compatibility.
I find it funny that people claim that VB has no runtime. The file vbrun6.dll is exactly that, a runtime library to allow to execute Visual Basic applications. The fact that it is often already on a system does not mean that you don't have to distribute it for those who don't have it. Also Each major VB version has it's own runtime version as well (vbrun300.dll, ..., vbrun6.dll, etc)
If you wanted me to execute a VB app you would have to provide me with the according VB runtime lib as well as it isn't present on my system.
Rolf Kalbermatter
