Should SCADA be Web based and Client/Server ?

R

Thread Starter

Rainer Lehrig

- As I know, most SCADA packages use the "fat client" model
- As I know, most SCADA packages are running under Windows only
- As I know, most SCADA packages are closed source and expensive
- As I know, most SCADA packages don't support ANSI-C
- As I know, you can't integrate foreign libraries written in C/C++ into your SCADA system

What do you think about this in contrast ?
You can test it on Linix and/or Windows.
http://pvbrowser.org

Example Server:
pv://pvbrowser.de

It seems to work well.

Is this approach viable for SCADA application ?
Is it secure enough ?
Is it mature enough ?

### This is from pvbrowser introduction ###############################
1 Introduction

The "ideal" process visualization would run in a standard web browser. In this case nothing had to be installed on the client computers, because web browsers are standard. Unfortunately web browsers have not been invented with process visualization in mind. In principle a web browser reads a HTML file from the webserver and displays it's content. Each time a HTML file is read the network connection is opened and closed. Dynamic changes in the content are difficult and inefficient.

A Java Applet might be a solution. Unfortunately complex Java Applets need a long time to load. Furthermore Java Applets are not famous for being fast. We have build a new browser in C++, which is optimized for process visualization. Instead of HTML it dynamically handles Qt Widgets. pvbrowser can be run as standalone application or as kpart for konqueror.

Because pvbrowser is a browser it can display any visualization. There is no need to update client computers running pvbrowser, when you change your visualization. This is in contrast to many process visualization systems which use the "fat client" model. Furthermore pvbrowser supports many platforms at the same time.

When you choose the URL of your pvserver from within pvbrowser a TCP network connection is opened. The network connection will stay open until you terminate the session with your pvserver. After opening the network connection pvserver will start sending commands to pvbrowser. Each command is a line of text which is terminated by a newline. pvbrowser will interpret the text and call the according functions from the Qt widget library. Thus pvserver handles the whole widget tree within the main window of pvbrowser. When the user triggers an event (e.g. hit a button), a line of text will be send from pvbrowser to pvserver. In pvserver there is an event loop, in which these events can be handled.

For programming pvserver we provide a library that encapsulates the lines of text send to pvbrowser. The reference for this library can be found in "ProcessViewServer Programming" in the Manual, which is also available from the online help of pvbrowser and pvdevelop.

A substantial part of pvserver is not written manually. Instead pvdevelop will gently generate the code for you. The functions provided by the library can be inserted by choosing from a menu in pvdevelop.

The whole layout and design of the masks you are using in your visualization is made graphically using pvdevelop.
 
E
1 - Yes
2 - More or less
3 - No - you want open then use OPC and your favorite programming software VB, C++, Delphi, Java, etc. Build you own (thin) Server client.
4 - Both SCADA I use work with ansi-C
5 - Both SCADA I use allow libs from C/C++, DLLs, ActiveX.

PLCs and their software are less 'open' than SCADA but I 'know' that the PLC works well ...If only I could get all the bugs out of the software.

Greetings
 
Top