Embedded Systems an integrated computational, electrical, and - - PowerPoint PPT Presentation

Laboratory for Perceptual Robotics – Department of Computer Science

www-robotics.cs.umass.edu/~grupen/503 Overview of Our Course

Embedded Systems

2 Laboratory for Perceptual Robotics – Department of Computer Science

Embedded Systems

…an integrated computational, electrical, and mechanical system… hardware (sensors, actuators), software with RT constraints, interfaces low power, small size, rugged, cheap

3 Laboratory for Perceptual Robotics – Department of Computer Science

Embedded Systems

Lecture Units:

• analog circuitry
• semiconductors
• control
• actuators
• sensors, interface,

signal processing

• RT computing

electromechanical mechanism computation I/O circuitry

team projects rely on peer instruction

4 Laboratory for Perceptual Robotics – Department of Computer Science

Laboratory Projects - 2019

Individual

• Photovore

Team: Self-Driving Fleet

• sensor/motor interface – IMU?, encoder?, ping?,

motor, camera

• Communication – blue tooth, WiFi?
• ption - balancing control (inverted pendulum)
• GPS, odometry? – long-term precision challenge
• lane following – respecting signage
• long-range, multi-agent – traffic challenge

5 Laboratory for Perceptual Robotics – Department of Computer Science

1953 experiment in “Cybernetics”

• ne motor, 4 state control logic

light and bump sensors Behavior:

• seek light
• obstacle avoidance
• recharge

Principles:

• parsimony – simple is better
• normally active behavior
• tropism – positive (attraction) and

negative (repulsion)

Grey Walter’s Tortoise

6 Laboratory for Perceptual Robotics – Department of Computer Science

Braitenbergs Vehicles – 1984 simulation study

Valentino Braitenberg, “Vehicles: Experiments in Synthetic Psychology,” MIT Press; Reprint edition (1986) ISBN:0262521121

• sensors map to motors via simple analog logic
• apparently complex behavior results from simple control rules

interacting with a complex environment

• inhibitory and excitatory signals
• uphill analysis and downhill invention –

some systems are easier to invent than to analyze

7 Laboratory for Perceptual Robotics – Department of Computer Science

Simple Braitenbergs Vehicles

Coward, Explorer, Lover, and Aggressor

8 Laboratory for Perceptual Robotics – Department of Computer Science

Project #1 - photovore

see web site for details

Chris Vigorito Dirk Ruiken

9 Laboratory for Perceptual Robotics – Department of Computer Science 10 Laboratory for Perceptual Robotics – Department of Computer Science

Project #1 - project management

A draft pr project ct pl plan an is the first step of every project---before the first circuit is prototyped. The plan enumerates all the ta tasks required and sets co compl pletion times. This level of description makes it clear that all aspects of the project have been considered (nothing has been left out), how tasks depend on one another, and provides reasonable time estimates. It also should include a description of the pr produ duct cts (designs, numerical values) that verify the completion of each task or establish parameters necessary for subsequent tasks. Inevitably, the plan will need to be modified as it unfolds so it make sense to do it in a way that is easily edit-able. I like the excel spreadsheet for a Ga Gantt chart---you can find templates on-line you can use. Find one that you like.

. 11 Laboratory for Perceptual Robotics – Department of Computer Science

Project #1 – Photovore Project Management

1. Design 2. Prototype 3. Implementation (8 hours) 4. Demonstration (0.5 hours) 5. Report

a) CdS/R2/Rmotor resistances (0.5 hours) b) voltage divider, Vout (light/dark) (1 hour) c) switch logic (1 hour) d) circuit layout (pin-2-pin) (1 hour) e) chassis structure, motor mount, wheels/skid concept (1.5 hours) a) circuit breadboard (4 hours) b) logic/performance checkout (0.5 hours) a) #1 - summary of progress, re-plan, critical evaluation (2 hours) b) #2 – summary of project, demo results, critical evaluation (2 hours)

Task Task Task Task Task

This is an outline for your report fill in the result for each subtask

10 hours 12 hours

12 Laboratory for Perceptual Robotics – Department of Computer Science

project management GANTT chart

Task 1 - Design Task 2 - Prototype Task 3 - Implement Task 4 - Demo Task 5 - Report

9/9 9/13 9/16 9/20

• evaluate and adapt your schedule, include subtasks (1a, 1b, …) as required
• assess risks and plan time and contingencies
• creativity is encouraged, but only if it’s on your GANTT chart!

a b c d e a b a b e report estimate

13 Laboratory for Perceptual Robotics – Department of Computer Science

project reporting – individual weekly lab report

NO NO MORE than 2 pages in ON ONE PDF FILE (LastName-mm-dd-yy.pdf) Include co compl pleted d pr produ duct cts for the previous week's tasks (drawings, designs, numerical values), note any va vari riations in yo your r plan, and include a revised project plan. Reports don’t need to be beautifully written, but must be organized to be read. They should be written for your “project manager.” It's tempting to jump right to a picture of your final concept in week 1, but stick to your plan and work out the results of preliminary subtasks first. The project plan minimizes the chances that you'll waste time and make costly mistakes. I will review and grade notebooks every week. Grades will reflect the completeness of the design process, critical analyses, experimental evaluation, and weekly project management.

14 Laboratory for Perceptual Robotics – Department of Computer Science

project reporting – final reports

NO NO MORE THAN N 5 5 pa page ges in ON ONE PDF FILE (LastName-mm-dd-yy.pdf) includes the last (final) revision of the pr project ct pl plan an, summarizes all the pr produ duct cts at a level of detail adequate to reproduce your results draw conclusions about the fi final p perfo formance and revisions you would make it you had to do it over again It should be written using complete sentences and a logically organized sequence of thoughts. In weeks when you submit final project reports, individual weekly lab reports are not required.