© 2000 Morgan Kaufman Overheads for Computers as Components Networks zExample: elevator controller.

Slides:

Advertisements

Similar presentations

Elevator System Control Devices and Applications

Advertisements

Hard&Soft Contest, Suceava Team of Timisoara LEEFT 3 : Lift (Elevator) Environment Forged Tenderly by the Team of Timisoara Slide 1 LEEFT.

Case Studies Elevator control system Elevator control system Comet case studies From task structuring to target system configuration.

Unit 7 Discrete Controllers

Techniques for Object Discovery from Real Time UML, B.P. Douglass.

Department of Electrical and Computer Engineering Texas A&M University College Station, TX Abstract 4-Level Elevator Controller Lessons Learned.

© 2008 Wayne Wolf Overheads for Computers as Components 2 nd ed. Networks zExample: elevator controller.

Embedded and Real Time Systems Lecture #4 David Andrews

Simple Logic Elevator Group 10: Zhen Yu Wu Wai Seng Ho Tat Chi Chio.

Project Doors Group Doors 3 Presenters: Becky Smith, Tim Hollosy Demo Given by: Tim Hollosy.

1 CPN Models as Enhancements to a Traditional Software Specification for an Elevator Controller Jens Bæk Jørgensen Department of Computer Science University.

REAL-TIME SOFTWARE SYSTEMS DEVELOPMENT Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.

Generic Simulator for Users' Movements and Behavior in Collaborative Systems A Application D Design D Document Alex Surguch, Niv Saar, Mattan Margalith,

Courseware Basics of Real-Time Scheduling Jan Madsen Informatics and Mathematical Modelling Technical University of Denmark Richard Petersens Plads, Building.

© 2000 Morgan Kaufman Overheads for Computers as Components 2 nd ed. Introduction zExample: model train controller.

© 2000 Morgan Kaufman Overheads for Computers as Components 2nd ed. Introduction Example: model train controller. 1.

Using the Windows Event Viewer and Task Scheduler Chapter 5.

1.  Project Goals.  Project System Overview.  System Architecture.  Data Flow.  System Inputs.  System Outputs.  Rates.  Real Time Performance.

1 Embedded Systems Development. 2 Topics covered  Embedded systems design  Architectural patterns  Timing analysis  Real-time operating systems.

Real-Time Software Design Yonsei University 2 nd Semester, 2014 Sanghyun Park.

REAL-TIME SOFTWARE SYSTEMS DEVELOPMENT Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.

© 2005 ECNU SEIPrinciples of Embedded Computing System Design1 Introduction zExample: model train controller.

© 2000 Morgan Kaufman Overheads for Computers as Components Introduction  Example: model train controller.

Foundations of Real Estate Management BOMA International Module 4: Building Operations II Elevators and Escalators ®

Manufacturing Engineering Elevator Lift System Operation Copyright © Texas Education Agency, All rights reserved. 1.

Embedded Computer Systems Chapter1: Embedded Computing Eng. Husam Y. Alzaq Islamic University of Gaza 1 © 2010 Husam Alzaq Computers as Components.

Elevator Control System

1 소프트웨어공학 강좌 Chap 11. Real-time software Design - Designing embedded software systems whose behaviour is subject to time constraints -

Software Dynamics: A New Method of Evaluating Real-Time Performance of Distributed Systems Janusz Zalewski Computer Science Florida Gulf Coast University.

The variety Of Processors And Computational Engines CS – 355 Chapter- 4 `

Reference: Ian Sommerville, Chap 15  Systems which monitor and control their environment.  Sometimes associated with hardware devices ◦ Sensors: Collect.

© 2000 Morgan Kaufman Overheads for Computers as Components I/O devices  I/O devices:  serial links  timers and counters  keyboards  displays  analog.

Slide 1 Chapter 11 Real –time Software Designs. Slide 2 Real-time systems l Systems which monitor and control their environment l Inevitably associated.

© 2000 Morgan Kaufman Overheads for Computers as Components Networks zNetwork-based design. yCommunication analysis. ySystem performance analysis. zInternet-enabled.

REAL-TIME SOFTWARE SYSTEMS DEVELOPMENT Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.

© 2000 Morgan Kaufman Overheads for Computers as Components Processes and operating systems  Operating systems.

© 2000 Morgan Kaufman Overheads for Computers as Components Processes and operating systems Operating systems. 1.

2Object-Oriented Program Development Using C++ 3 Basic Loop Structures Loops repeat execution of an instruction set Three repetition structures: while,

© 2000 Morgan Kaufman Overheads for Computers as Components Introduction zExample: model train controller.

Communicating Real-Time State Machines (CRSM) State machines that communicate synchronously Unique unidirectional channels are used for the communication.

Castor Bot. Now, we will begin creating a robot Log onto your computer On your screen, click on the website labeled “castor bot” Your building instructions.

©Ian Sommerville, Robin Abraham 2004CS 361, Summer 2004 Slide 1 Real-time Software Design.

Real-time Software Design King Saud University College of Computer and Information Sciences Department of Computer Science Dr. S. HAMMAMI.

Yu Du, Yu Long Electrical & Computer Engineering

© 2000 Morgan Kaufman Overheads for Computers as Components I/O devices zI/O devices: yserial links ytimers and counters ykeyboards ydisplays yanalog I/O.

Unit 9 – “A BIG State Machine”. Introduction New Topics Nested Case Structures Reusable Code.

SE-3910 Real-time Systems Week 1, Class 2 – Fine Print – Web page available – Review Quiz 0 – What is a Real-Time Embedded System? Embedded & Real-Time.

© 2000 Morgan Kaufman Overheads for Computers as Components Accelerators zAccelerated systems. zSystem design: yperformance analysis; yscheduling and.

Real-Time Systems, Events, Triggers. Real-Time Systems A system that has operational deadlines from event to system response A system whose correctness.

© 2000 Morgan Kaufman Overheads for Computers as Components Host/target design  Use a host system to prepare software for target system: target system.

Prestenters : Ehab Shakour Gaby Shakour Instructor : Moni Orbach.

© 2000 Morgan Kaufman Overheads for Computers as Components 1. Embedded Computing 1.1 Introduction 1.2 Complex system and microprocessors 1.3 Embedded.

Elevator Example.

© 2000 Morgan Kaufman Overheads for Computers as Components1 Design methodologies zA procedure for designing a system. zUnderstanding your methodology.

The embedded systems platform

Sequence diagrams Practice 7. Task 1  The “Author” sends his paper to the “Editor” by the message “manuscript” and waits the confirmation.

Team 2 Electricivic Ben Dannan Mark Snyder Matt Klutzke Mike Mitchell 1.

Slides created by: Professor Ian G. Harris Operating Systems  Allow the processor to perform several tasks at virtually the same time Ex. Web Controlled.

4) Design the logic to control the motor on a simple remote control car. There are two buttons on the remote control for the motor. If neither button is.

 2000 Deitel & Associates, Inc. All rights reserved. Optional Case Study - Chapter 6 Outline 6.1 Introduction 6.2 Implementation: Visibility 6.3 Implementation:

Elevator Example. Problem GSU schedules to upgrade all the campus elevators in 6 months. Due to incompatibility with the new hardware, the current software.

The embedded systems platform

Overheads for Computers as Components

Overheads for Computers as Components

Introduction Example: model train controller..

Elevator Collaboration Diagram

Processes and operating systems

Latches and Flip-Flops 1

Multiprocessor and Real-Time Scheduling

UML Diagrams: StateCharts The Dynamic Analysis Model

Presentation transcript:

© 2000 Morgan Kaufman Overheads for Computers as Components Networks zExample: elevator controller.

© 2000 Morgan Kaufman Overheads for Computers as Components Terminology zElevator car: holds passengers. zHoistway: elevator shaft. zCar control panel: buttons in each car. zFloor control panel: elevator request, etc. per floor.

© 2000 Morgan Kaufman Overheads for Computers as Components Elevator system floor Hoistway 1Hoistway 2

© 2000 Morgan Kaufman Overheads for Computers as Components Theory of operation zEach floor has control panel, display. zEach car has control panel: yone button per floor; yemergency stop. zControlled by a single controller.

© 2000 Morgan Kaufman Overheads for Computers as Components Elevator position sensing coarse sensor fine

© 2000 Morgan Kaufman Overheads for Computers as Components Elevator control zElevator control has up and down. yTo stop, disable both. zMaster controller: yreads elevator positions; yreads requests; yschedules elevators; ycontrols movement; ycontrols doors.

© 2000 Morgan Kaufman Overheads for Computers as Components Elevator system requirements

© 2000 Morgan Kaufman Overheads for Computers as Components Elevator system class diagram Car Floor Master-control-panel* Controller Motor* Coarse-sensor* Fine-sensor* Car-control-panel* Floor-control-panel* N 1 F 1 1 N

© 2000 Morgan Kaufman Overheads for Computers as Components Physical interfaces Sensor* hit: boolean Coarse-sensor*Fine-sensor* Motor* speed: {o,s,f} Floor-control-panel* up, down: boolean Car-control-panel* Floors[1..F]: boolean emergency-stop: boolean open-door, close-door: boolean Master-control-panel...

© 2000 Morgan Kaufman Overheads for Computers as Components Car and Floor classes Car request-lights[1..F]: boolean current-floor: integer Floor up-light, down-light: boolean

© 2000 Morgan Kaufman Overheads for Computers as Components Controller class Controller car-floor[1..H]: integer emergency-stop[1..H]: integer scan-cars() scan-floors() scan-master-panel() operate()

© 2000 Morgan Kaufman Overheads for Computers as Components Architecture zComputation and I/O occur at: yfloor control panels/displays; yelevator cars; ysystem controller.

© 2000 Morgan Kaufman Overheads for Computers as Components Panels and cab controller zPanels are straightforward---no real-time requirements. zCab controller: yread buttons and send events to system controller; yread sensor inputs and send to system controller.

© 2000 Morgan Kaufman Overheads for Computers as Components System controller zMust take inputs from many sources: ycar controllers; yfloors. zMust control cars to hard real-time deadlines. zUser interface, scheduling are soft deadlines.

© 2000 Morgan Kaufman Overheads for Computers as Components Testing zBuild an elevator simulator using an FPGA: ysimulate multiple elevators; ysimulate real-time control demands.