Report - Høgskolen i Telemark

More documents

Recommendations

Info

Preface This group project work is done as a part of the requirements for the award of the Master's degree in Systems and Control Engineering at the Telemark University College (Høgskolen i Telemark, Porsgrunn) in Norway. The report is written based on the requirements for the development of a SCADA system for control of a tank laboratory system. The entire work has been carried out on the campus of Telemark University College (HiT). Some of the necessary technical information and data needed have been obtained from the previous bachelor thesis report presented for the designed four-tank laboratory process and also the master thesis of Victor Okpanachi Ademu. The entire implementation has been done using Silverlight 4 web application development tool of the MS Visual studio Ultimate 2010 and using C# programming language as well as the WPF application development tool of the MS Visual studio Ultimate 2010. It is imperative that the reader should have some basic knowledge of object oriented analysis and design, C# programming, the use of UML, Silverlight, SQL and WPF in order to fully understand this report. We wish to convey our sincere gratitude to Hans-Petter Halvorsen (MSc) for his guidance and supervision in implementation of this task all the way through. He has also consistently been able to correct us and provide solutions whenever we faced troubles in letting us know what next to do. We also would like to express our gratitude to Associate Professor Nils-Olav Skeie (PhD) for guiding us in the analysis and design of the software. Porsgrunn, 22nd, November 2010 Arome Damian Okpanachi Emuobosa Ogheneruona Utake Manjula E.V.P.J Raghunath Balasubramanian Ronnie Anseth Sunday Success Obada 6
Nomenclature This section gives a listing of all the abbreviations used in this report. AC API CORBA COM DAQ DBMS DC DCOM DCS DDE DLL FDUCD FURPS+ GRASP GUI HMI HTML IIS IIOP IT LAN MAX MIMO MS NI ODBC OLE OOA OPC ORB Alternating Current Application Programming Interface Common Object Request Broker Architecture Component Object Model Data Acquisition Database Management System Direct Current Distributed Component Object Model Distributed Control System Dynamic Data Exchange Dynamic Link Library Fully Dressed Use Case Document Functionality-Usability-Reliability-Performance-Supportability- Design Limitation General Responsibility Assignment Software Patterns Graphical User Interface Human Machine Interface HyperText Markup Language Internet Information Services Internet Inter-ORB Protocol Information Technology Local Area Network Measurement & Automation Explorer Multiple-input and Multiple-output Microsoft National Instruments Open Database Connectivity Object Linking and Embedding Object Oriented Analysis OLE for Process Control Object Request Broker 7
Page 1 and 2: Project report 2010 Candidates: Tit
Page 3 and 4: Table of contents ABSTRACT: .......
Page 5: B1: System Sequence Diagrams (SSD).
Page 9 and 10: Overview of tables and figures Figu
Page 11 and 12: Figure B. 14: Sequence diagram of t
Page 13 and 14: 1 INTRODUCTION SCADA systems are wi
Page 15 and 16: OPC Foundation defines the standard
Page 17 and 18: 2.1.2.2 Human Machine Interface The
Page 19 and 20: 2. Communications infrastructure: T
Page 21 and 22: system architecture (not vendor dep
Page 23 and 24: As far as new technologies are conc
Page 25 and 26: Figure 2-4: The main functions of a
Page 27 and 28: In order to define the button behav
Page 29 and 30: service hosted in an application or
Page 31 and 32: Figure 2-9: SCADA Application using
Page 33 and 34: Tank 3 Tank 4 Three - way valve-2 T
Page 35 and 36: Figure 2-13: NI USB-6008 DAQ device
Page 37 and 38: Area of the drain in tank i 0.16, 0
Page 39 and 40: Figure 2-16: Example of SCADA syste
Page 41 and 42: Figure 2-17: Diagram of real time d
Page 43 and 44: 3 ANALYSIS OF SOFTWARE This section
Page 45 and 46: Control Application SCADA server Sy
Page 47 and 48: 4 SYSTEM DESIGN 4.1 Design of Softw
Page 49 and 50: 4.2.4 Configuration page The config
Page 51 and 52: Figure 4-7: Design of the control a
Page 53 and 54: 4.2.8 Configure report page When th
Page 55 and 56: access level only permits the opera
Page 57 and 58:
Figure 4-13: Database model adopted
Page 59 and 60:
Figure 5-2: The configuration backu
Page 61 and 62:
Figure 5-4: The control application
Page 63 and 64:
} To write to multiple channels, th
Page 65 and 66:
The code that t2 triggers (Tick2) c
Page 67 and 68:
Figure 5-6: Controller configuratio
Page 69 and 70:
} Configuration = e.Result.ToArray(
Page 71 and 72:
The UserLevel variable is provided
Page 73 and 74:
Figure 5-12: Setpoint configuration
Page 75 and 76:
5.4.1 Unit Test The unit tests were
Page 77 and 78:
correct tables in the database. Tes
Page 79 and 80:
6 DEPLOYMENT This section gives an
Page 81 and 82:
There are two different ways of upd
Page 83 and 84:
• Introducing students to the pro
Page 85 and 86:
[27] http://databases.about.com/cs/
Page 87:
APPENDICES Appendix A: Task Descrip
Page 91 and 92:
System : Timer : Sensors 1 : CheckW
Page 93 and 94:
System : Admin 1 : Login() 2 : Conf
Page 95 and 96:
B2: Fully Dressed Use Case Document
Page 97 and 98:
Table B. 4: FDUCD of SQL Use case S
Page 99 and 100:
B3: Sequence Diagram PowerUp initia
Page 101 and 102:
Power up : Control Algorithm Read S
Page 103 and 104:
Power Up Alarm system SQL Operator
Page 105 and 106:
PowerUp : Reporting : SQL : Printer
Page 107 and 108:
B5: Object Diagram Configuration Fi
Page 109 and 110:
CREATE TABLE [TagTask] ( [TagId] [i
Page 111 and 112:
SELECT dbo.Controller.ControllerId,
Page 113 and 114:
UPDATE Task SET Task = @WriteTask2
Page 115 and 116:
CREATE VIEW MonitorTags(Valve1,Valv
show all

Report - Høgskolen i Telemark

Create successful ePaper yourself

Delete template?

Save as template?