Networks

Example: elevator controller.

2008 Wayne Wolf

Overheads for Computers as Components 2nd ed.

Terminology
Elevator car: holds passengers. Hoistway: elevator shaft. Car control panel: buttons in each car. Floor control panel: elevator request, etc. per floor.

2008 Wayne Wolf

Overheads for Computers as Components 2nd ed.

Elevator system
floor floor floor floor

floor

Hoistway 1
2008 Wayne Wolf

Hoistway 2

Overheads for Computers as Components 2nd ed.

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.

2008 Wayne Wolf

Overheads for Computers as Components 2nd ed.

Elevator position sensing

sensor

fine coarse
2008 Wayne Wolf Overheads for Computers as Components 2nd ed.

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 2nd ed.

2008 Wayne Wolf

Elevator system requirements

name inputs outputs functions performance manufacturing cost power physical size/weight elevator system F floor control, N position, N car control, 1master F displays, N motor controllers responds to requests, operates safely elevator control is time-critical electronics is small part of total electronics consumes small fraction of total cabling is important

2008 Wayne Wolf

Overheads for Computers as Components 2nd ed.

Elevator system class diagram

Coarse-sensor* Fine-sensor*
1

Master-control-panel*
1 1 1 1

Car
1

N 1 1

1 1

Controller
F 1 N

Car-control-panel* Floor-control-panel* 1

Floor

Motor*
Overheads for Computers as Components 2nd ed.

2008 Wayne Wolf

Physical interfaces
Sensor* hit: boolean Car-control-panel* Floors[1..F]: boolean emergency-stop: boolean open-door, close-door: boolean Master-control-panel... Motor* speed: {o,s,f}
2008 Wayne Wolf

Coarse-sensor*

Fine-sensor*

Floor-control-panel* up, down: boolean

Overheads for Computers as Components 2nd ed.

Car and Floor classes

Car request-lights[1..F]: boolean current-floor: integer Floor up-light, down-light: boolean

2008 Wayne Wolf

Overheads for Computers as Components 2nd ed.

Controller class
Controller car-floor[1..H]: integer emergency-stop[1..H]: integer scan-cars() scan-floors() scan-master-panel() operate()

2008 Wayne Wolf

Overheads for Computers as Components 2nd ed.

Architecture
Computation and I/O occur at:
floor control panels/displays; elevator cars; system controller.

2008 Wayne Wolf

Overheads for Computers as Components 2nd ed.

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 2nd ed.

2008 Wayne Wolf

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.
2008 Wayne Wolf Overheads for Computers as Components 2nd ed.

Testing
Build an elevator simulator using an FPGA:
simulate multiple elevators; simulate real-time control demands.

2008 Wayne Wolf

Overheads for Computers as Components 2nd ed.