team suspect presents: aspen mieszko kruger garrett earnshaw yoni mekuria joe chmura

Team SuspectTeam SuspectPresents:Presents: AspenAspen

Mieszko Kruger

Garrett Earnshaw

Yoni Mekuria

Joe Chmura

Welcome to AspenWelcome to Aspen

Aspen’s PurposeAspen’s Purpose

To dynamically control a network of peripheral devices, a network that controls as well as senses.

Why “Aspen”?

Baseline ObjectivesBaseline Objectives

Design and implement a core module that can control a network of devices (Aspen). Control the network through the use of a PC interface. Control peripheral devices with a Controller Area

Network (CAN). Accepting a wide range of nodes (e.g. inferred, power,

other network protocols, etc.) Dynamic network accepting hot-pluggable nodes.

General DescriptionGeneral Description

Aspen Core will connect to a computer via RS232.

Aspen Core will control network of “Leaves” via CAN

General Description (cont.)General Description (cont.)

Each Leaf will handle interface between the CAN and its specialized function.

PC – Core Module InterfacePC – Core Module Interface

Friendly GUI with status and control of all Leaves.

Customized ASCII protocol through RS232.

Call and Response Handshake.

Character parsing on both ends.

Core Module – Node InterfaceCore Module – Node Interface

Tolerant CAN line with error checking for very noisy environments.

Dynamic hot-pluggable nodes.

Node check-in every 3 minutes for live node availability.

General Node DesignGeneral Node Design

Half node design will be universal to interface with the standard network

The interface will consist of retrieving data from the CAN chip and using this data to perform a controlling or sensing activity

Custom developed protocol for wide range of nodes.

Division of LaborDivision of Labor

Tasks Team Member in ChargePower (core and leaves) Yoni, JoeColdfire MieszkoUser Interface MieszkoCommunication w/ Leaves (Core & PC) Garrett, Mieszko, JoeCAN Programming Joe, GarrettDocumentation GarrettNode Design Yoni, JoeCabeling Yoni

ScheduleSchedule

Risks and Contingencies Risks and Contingencies

Getting the Coldfire to function properly.Getting necessary licenses for software

needed.Learning CAN technology.Powering the individual leaves.Demon Magic (i.e. bad luck).

Contingency PlansContingency Plans

Redesign processor from the ground up using FPGA.

Use other technologies like I²C instead of CAN for Leaves.

Use individual power sources for each leave.

Tap Dance and accumulate good karma.

CI 2

QuestionsQuestions