Report - Høgskolen i Telemark

More documents

Recommendations

Info

They take advantage of component-based development using models like DCOM, RMI and CORBA’s Internet Inter-ORB Protocol (IIOP) which all depend on object model-specific protocols [14]. Web services develop these models by connecting with SOAP (Simple Object Access Protocol) and XML to eliminate the barrier introduced by the object model-specific protocol [14]. The basic structure of a Web Service is shown in Figure 2-7. LOCATION A LOCATION B SOAP over HTTP SOAP over HTTP INTERNET USER XML XML WEBS ERVICE Figure 2-7: The basic structure of a Web Service [14] According to [14], SOAP calls are remote function calls that call up method executions on Web Service components at location B, the output is then represented as XML and sent back to the user at location A. 2.5 ASP.NET ASP.NET is a web application that allows users to program dynamic web pages, web applications and web services [16]. 2.6 WCF service The three main communication procedures as presented in [10] with other systems that Silverlight provides are services via • WCF • Direct HTTP communication via the ‘HttpWebRequest’ and ‘WebClient’ classes and • Raw communication using sockets However, the focus will be on WCF due to the fact that it was the communication procedure that was adopted in this project. As presented in [17] and [18], WCF is an API in the .NET framework for developing connected, service-oriented applications. By using WCF, data can be sent asynchronously from one service endpoint to another [17]. Based on [17], a service endpoint can either be a 28
service hosted in an application or it can be part of a constantly accessible service hosted by IIS while an endpoint can be a client of a service that calls data from a service endpoint. 2.6.1 WCF RIA services Based on [19], WCF RIA Services is an enhancement to WCF as it builds upon the WCF stack; it offers a means of sharing validation and logic between the client and the server as well as a basis for validation, data access, and security which can be shared between Silverlight and other clients. 2.7 OPC OPC is ’open connectivity’ via ’open standards’ [20]. OPC is an open connectivity in industrial automation and the enterprise systems that are supported in the industry. Interoperability is guaranteed through the creation and maintenance of open standards specifications. OPC is a series of standard specifications and it was originally based on Microsoft's OLE COM and DCOM technologies, the specification defined a standard set of objects, interfaces and methods for use in process control and manufacturing automation applications to facilitate interoperability [20]. The COM/DCOM technologies provided the framework for software products to be developed. As presented in [20], the OPC specifications are: • OPC Data Access (DA) • OPC Alarm and Events (AE) • OPC Batch • OPC Data eXchange • OPC Historical Data Access • OPC Security OPC • XML-DA OPC • OPC Commands • OPC Complex Data • Unified Architecture (UA) Based on [1], the most used standards in the process industry are: • OPC Data Access (OPC DA) - Provides access to real-time, continually changing data, used to move real-time data from PLCs, DCSs, and other control devices to HMIs and other display clients, also used for computing and estimating values and writing values. • OPC Alarm and Events (OPC AE) - Provides alarm and event notifications on demand (in contrast to the continuous data flow of Data Access) [20]. These include process 29
Page 1 and 2: Project report 2010 Candidates: Tit
Page 3 and 4: Table of contents ABSTRACT: .......
Page 5 and 6: B1: System Sequence Diagrams (SSD).
Page 7 and 8: Nomenclature This section gives a l
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: In order to define the button behav
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?