12-29-2005 03:29 AM - edited 12-29-2005 03:29 AM
Thanks TommyHelter for replying,
I agree that LabView has its great strengths that any other SCADA package can't do, LabView is a programming language .. But:
In most of the SCADA applications (which is our discussion topic here) I don't need the "capabilitty of doing more sophisticated data measurements" as you said. I just need some quick and easy tools to visualize and monitor field instruments, status of the process/machine and to control some parameters (and of course other SCADA features: Trends, Alarms, Recipes, Historical .. etc). And in case of I wanted to do some sophisticated things, Many SCADA packages offer the ability to write your own "Scripts". Again, It's not as powerful as LabView can do, But this is what most of the SCADA applications engineers require.
DSC is doing a great job, But I think if the folks here that developing LabView and the DSC consider overcoming these limitations I mentioned in this thread, LabView (plus DSC) would be the only software that can do DSC plus SCADA applications effectively.
Note that I spend a long time comparing the features of SCADA applications (InTouch - iFix - RSview - Citect - Omron cx-supervisor - Lookout - InfLink ..)
On the other side, SCADA can't cann't be used to build DAQ applications, LabView is number one in DAS applications.
Just my openion.
And thank you all for your valuble comments.
Message Edited by Ayman_Metwally on 12-29-2005 03:34 AM
12-29-2005 10:48 AM
12-29-2005 12:40 PM
12-29-2005 12:46 PM
12-29-2005 01:09 PM
12-29-2005 06:16 PM
12-30-2005 02:19 AM - edited 12-30-2005 02:19 AM
It's not that SCADA applications can't be developed using LabView .. No .. This isn't our point here ..
Anything can be developed using any programming language, Our point here is: How much does it cost (i.e. TIME and EFFORT) to build SCADA application using LabView compared to using SCADA packages that were made for this purpose.
We once - Me and another colleague wrote a medium SCADA application (800 PLC I/O) using Visual basic and some ActiveX controls.. It looks great and does every thing the client wants. Take a look here
BUT: 20,000 lines of vb code (to develop and then to debug) is very bad thing if we compare developing the developing using InTouch for example, We used too many MS Word macros to generate the code (even this can't be used to develop the graphical code of LabView!)
You can compare it your self .. start the stop watch and build the same application using LabView and any other SCADA package.
Another thing is the "Effort" .. You need a good labview programmer to build the code required for Alarming for example .. It's OK with me and for people that are good in LabView programming .. But: If I have to many large projects .. I think that "right clicking" and "checking boxes" (this is the environment of SCADA packages) is easy for many people so I can get the project done quickly and move to another one.
I really like labView as a data acquistion system builder. I built 4 sophisticated systems using labView and it's very powerful .. But when it comes to SCADA .. I stick to my point that it's not made for that in the first place (especially if you didn't use DSC)
Thanks Kasara for your input, I appreciate it ..
Message Edited by Ayman_Metwally on 12-30-2005 02:22 AM
12-31-2005 05:48 PM
12-31-2005 06:36 PM
01-03-2006 12:22 PM