Wsecs-机台自动化培训.ppt

The RAD Environment For Equipment Interfaces Technical Overview Overview Introduction to component architecture Brief history of SECS communication WinSECS design How to use WinSECS Summary Component Architectures Application is a collection of components assembled to meet a need Components are difficult to create but easy to use Components are assembled with “glue” language like Visual Basic Granularity of components determines both flexibility and productivity Windows NT Components OLE Custom Controls (OCXs) Provides a standard interface for components “Containers” glue components together Visual Basic, Powerbuilder, Delphi Extremely large third-party market See for a list Quick Visual Basic Primer Powerful RAD tool for building both UI and non-UI applications Event-driven programming language Based on three fundamental constructs Properties Methods Events Quick Visual Basic Primer Properties Characteristics of the object E.g. Name, Colour, Size Methods Services object can perform E.g. Send, Duplicate, Update Events Asynchronous notification E.g. MessageSent, ButtonPressed First Generation Low-level interface Poor debugging Low productivity Hand coded message parsing Example products GW Associates SDR Old SDT with SECS Second Generation High-level interface Improved debugging at SECS level 4GL language “Flexible” message definitions Example products FASTech’s Grapheq Third Generation Powerful, context sensitive IDE Full flexible message formatting No runtime constraints Strong support for industry standards Address EI, not EC Structured for re-use Begin use at characterisationrather than at first silicon Introducing WinSECS RAD environment for integrated equipment interfaces Leverages FASTech’s extensive experience Builds on the power of Windows NT and Visual Basic Everything configurable at runtime What is WinSECS? 32-bit OLE control (OCX) Based on Windows NT 4.0 SP3 RS-232, HSMS and Terminal Server (Telnet TCP/IP) Tested with Visual Basic 4 5 as a con