1. Team Suspect Presents: Aspen Mieszko Kruger Garrett Earnshaw Yoni Mekuria Joe Chmura

2. Welcome to Aspen

3. Aspen’s Purpose  To dynamically control a network of peripheral devices, a network that controls as well as senses.  Why “Aspen”?

4. Baseline 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.

5. General Description  Aspen Core will connect to a computer via RS232.  Aspen Core will control network of “Leaves” via CAN

6. General Description (cont.)  Each Leaf will handle interface between the CAN and its specialized function.

7. PC – 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.

8. Core 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.

9. General 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.

10. Division of Labor

11. Schedule

12. 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).

13. Contingency 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.

14. Questions