1 / 15

Networks

Networks. Example: elevator controller. Terminology. Elevator car : holds passengers. Hoistway : elevator shaft. Car control panel : buttons in each car. Floor control panel : elevator request, etc. per floor. Elevator system. floor. floor. floor. floor. floor. Hoistway 1. Hoistway 2.

cqueen
Download Presentation

Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Networks • Example: elevator controller. Overheads for Computers as Components

  2. Terminology • Elevator car: holds passengers. • Hoistway: elevator shaft. • Car control panel: buttons in each car. • Floor control panel: elevator request, etc. per floor. Overheads for Computers as Components

  3. Elevator system floor floor floor floor floor Hoistway 1 Hoistway 2 Overheads for Computers as Components

  4. Theory of operation • Each floor has control panel, display. • Each car has control panel: • one button per floor; • emergency stop. • Controlled by a single controller. Overheads for Computers as Components

  5. Elevator position sensing sensor fine coarse Overheads for Computers as Components

  6. Elevator control • Elevator control has up and down. • To stop, disable both. • Master controller: • reads elevator positions; • reads requests; • schedules elevators; • controls movement; • controls doors. Overheads for Computers as Components

  7. Elevator system requirements Overheads for Computers as Components

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

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

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

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

  12. Architecture • Computation and I/O occur at: • floor control panels/displays; • elevator cars; • system controller. Overheads for Computers as Components

  13. Panels and cab controller • Panels are straightforward---no real-time requirements. • Cab controller: • read buttons and send events to system controller; • read sensor inputs and send to system controller. Overheads for Computers as Components

  14. System controller • Must take inputs from many sources: • car controllers; • floors. • Must control cars to hard real-time deadlines. • User interface, scheduling are soft deadlines. Overheads for Computers as Components

  15. Testing • Build an elevator simulator using an FPGA: • simulate multiple elevators; • simulate real-time control demands. Overheads for Computers as Components

More Related