Final Design Review Winter Term 2005

Slides:



Advertisements
Similar presentations
System Area Network Abhiram Shandilya 12/06/01. Overview Introduction to System Area Networks SAN Design and Examples SAN Applications.
Advertisements

1. 2 FRC 2010 Driver Station Doug Norman & Stephanie Brierty National Instruments January 8, 2010 Thanks to Joe Ross – Team 330.
Team 7 / May 24, 2006 Web Based Automation & Security Client Capstone Design Advisor Prof. David Bourner Team Members Lloyd Emokpae (team Lead) Vikash.
Handheld TFTP Server with USB Andrew Pangborn Michael Nusinov RIT Computer Engineering – CE Design 03/20/2008.
Lesson 15 – INSTALL AND SET UP NETWARE 5.1. Understanding NetWare 5.1 Preparing for installation Installing NetWare 5.1 Configuring NetWare 5.1 client.
Microprogrammes control the KOMBIS TMM8003. For the reliable operation of its systems and devices there are several programs located in two controllers.
Final Presentation Spring 2003 Project ID: D0822 Project Name: WinCE integrating BT media share application Supervisor: Evgeny Rivkin Performed by: Maya.
BLUETOOTH CONTROLLER BLUETOOTH CONTROLLER HARDWARE AND LIBRARY HARDWARE AND LIBRARYPROJECT ComFUTURE TECHNOLOGY.
Remote Surveillance Vehicle Design Review By: Bill Burgdorf Tom Fisher Eleni Binopolus-Rumayor.
SP2 Mikael Nystrom. Agenda Översikt Installation.
1 Semester 2 Module 2 Introduction to Routers Yuda college of business James Chen
Computerized Train Control System by: Shawn Lord Christian Thompson.
Local Area Networks: Software © Abdou Illia, Spring 2007 School of Business Eastern Illinois University (Week 8, Thursday 3/1/2007)
BLU-ICE and the Distributed Control System Constraints for Software Development Strategies Timothy M. McPhillips Stanford Synchrotron Radiation Laboratory.
1 Windows 2000 Product family (Week 3, Monday 1/23/2006) © Abdou Illia, Spring 2006.
Computer Emergency Notification System (CENS)
Ch.2 – Introduction to Routers
Remote Access Using Citrix Presentation Server December 6, 2006 Matthew Granger IT665.
Processes Introduction to Operating Systems: Module 3.
James Crosetto BS (Computer Science and Computer Engineering) Jeremy Ellison BS (Computer Science and Computer Engineering) Seth Schwiethale BS (Computer.
Source Controller software Ianos Schmidt The University of Iowa.
SMOOTHWALL FIREWALL By Nitheish Kumarr. INTRODUCTION  Smooth wall Express is a Linux based firewall produced by the Smooth wall Open Source Project Team.
Software Architecture of Sensors. Hardware - Sensor Nodes Sensing: sensor --a transducer that converts a physical, chemical, or biological parameter into.
1 © 2004, Cisco Systems, Inc. All rights reserved. CCNA 2 v3.1 Module 2 Introduction to Routers.
XFEL The European X-Ray Laser Project X-Ray Free-Electron Laser Wojciech Jalmuzna, Technical University of Lodz, Department of Microelectronics and Computer.
Lesson 1 PLC BASICS. PLC Definition  Programmable Logic Controllers are industrial computers that control machine and other applications.  PLC have.
Chapter 2 Operating Systems
Introduction to Operating Systems Concepts
Chapter Objectives In this chapter, you will learn:
Operating System Overview
Basic Computer Hardware and Software.
COMPSCI 110 Operating Systems
Instructor Materials Chapter 1: LAN Design
Obstacle avoiding robot { pixel }
Operating System & Application Software
Create setup scripts simply and easily.
By Sonia Thakur James M.Conrad Presenter: Bin Huang
AT Commands Supports AT commands
File System Implementation
CCNA Routing and Switching Routing and Switching Essentials v6.0
Credits: 3 CIE: 50 Marks SEE:100 Marks Lab: Embedded and IOT Lab
Automatic human detector garbage can.
Basic Computer Hardware and Software.
Monitoring Robot Prepared by: Hanin Mizyed ,Abdalla Melhem
MetaOS Concept MetaOS developed by Ambient Computing to coordinate the function of smart, networked devices Smart networked devices include processing.
Basic Computer Hardware & Software
DT80 range Modbus capability
Technology Literacy Hardware.
Introduction to Operating System (OS)
Chapter 10: Device Discovery, Management, and Maintenance
CCNA Routing and Switching Routing and Switching Essentials v6.0
Session III Architecture of PLC
Embedded Team Coordinator: Ben Brantley Henry Barnor Ezra Birch
Chapter 3: Windows7 Part 4.
Basic Computer Hardware and Software.
Cart Control System Cart DIO Speed Pulses RS232 Links VCS Peripheral
Serial Data Hub (Proj Dec13-13).
Chapter 10: Device Discovery, Management, and Maintenance
DEBROS: A UNIX-like OS for 8-bit microcontrollers
Chapter 2: System Structures
Web Server Administration
Chapter 3: Operating-System Structures
Chapter 2: The Linux System Part 1
CS703 - Advanced Operating Systems
Multiple Processor Systems
Chapter 2: Operating-System Structures
Embedded XINU and WRT54GL
Instructor: Mort Anvari
Chapter 2: Operating-System Structures
Chapter 13: I/O Systems.
Presentation transcript:

Final Design Review Winter Term 2005 Embedded Team Coordinator: Ben Brantley Henry Barnor Ezra Berch Thiago Costas Tully Foote Jeff Lamb David Rosen Alan Somers Final Design Review Winter Term 2005 Darpa Grandchallenge March, 14 2005 Embedded Team

Embedded Team Scope Provide a stable and uniform software and hardware platform for the other teams software to run on. (Computing and Hardware) Provide computer interface to actuators and sensors. (Actuation + adrive+ SDS) Establish a convenient, robust, and efficient inter-module messaging system. (SkyNet) Provide a user interface appropriate for driving the vehicle. (SkynetGUI) March, 14 2005 Embedded Team

Specifications Control of vehicle actuation capable of the following (defined from time command is issued by planning): < 2 Seconds lock to lock steering < ¼ Second to full brake < ¼ Second to vehicle response to a throttle input Computing hardware and management to survive 1 CPU failure and provide 7 computers initially, expandable to 12 computers. Including OS and non-race specific peripherals. A intermodule and intercomputer messaging system capable of: 1ms Timestamping accuracy 1ms latency >200mbs bandwidth Reliable message passing available March, 14 2005 Embedded Team

Serial Device Server (SDS) The SDS allows us to connect all serial devices to all computers via TCP/IP. This will allow the computer failure spec to be met. The SDS is a single point of failure, but without it, we cannot meet the redundancy spec. March, 14 2005 Embedded Team

Serial Device Server (SDS) Specifications -Processor Type: ARM7 44MHz -Memory: 8MB SDRAM/4MB flash -32 serial ports -1 Ethernet port -SkyNet will talk to each port via TCP/IP -RJ45 serial ports require physical adapters to DB9 -1U size (will be mounted in rack) Specs: -Physical connections robust enough to survive desert driving -Abstraction layer allows clients to connect a serial device without the SDS, without having to re-write client code -Round-trip time (total latency) through the SDS is 8 ms -Can support simultaneous communication to all serial ports

Driving Software(adrive) Current version fully operational w/ Steering, throttle, brake Listening to commands over skynet Returns position upon request over skynet. Allows interface to simulator as well as hardware.

Race Computers Race Computers: 7 Dell Power Edge P4, 2.8Ghz Running Gentoo Linux, Kernel >= 2.6.9 NFS mounted home directories for testing NIS authentication for easy user management Gigabit NICs connected to Gigabit switch 4 user, 8 computer KVM switch - easy development March, 14 2005 Embedded Team

Laptops 7 Laptops running Debian, Kernel 2.6 NFS mounted home directories when in shop NIS authenticated when in shop Single team account at field test 8th laptop acts as field server providing webserver, dns, subversion and dhcp March, 14 2005 Embedded Team

Field Wireless 2 wireless access points configured as a bridge. Allows access to race computers from base camp in the field. Allows access to race computers whiles vehicle is in motion. Enables drive-by-wire of vehicle. March, 14 2005 Embedded Team

Operator Interface (skynetGUI)-Spiral 1 Graphical display of state and rddf Graphical Display of fused sensor maps Displays planned path and path history Start and stops modules on race computers Load balances the modules Logs and displays last 500 Adrive commands March, 14 2005 Embedded Team

Module Starter Starts modules on race computers based on skynet message Config file provides ID, to uniquely identify each module starter Kill modules based on skynet message March, 14 2005 Embedded Team

Current Resources Managed In Shop and Field Test 1 Print server installed in shop. 1 Distributed compilation machine – P4 3GHZ – reduce compile time and load on laptops. Compatible with race computer setup. 2-3 Development workstations in shop in addition to 8 laptops. Laptops running Debian distribution. NFS/NIS on all development machines with local team accounts for non-networked use. Exploring NFS/NIS solutions for field tests. 3 wireless access points (Field base, shop, alice). Field Server provides DNS, DHCP, subversion, Bugzilla and Wiki. Exploring backup operations for multi-day field tests. March, 14 2005 Embedded Team

Actuation Part 1 Throttle Steering Brake Atmel controller with three DACs interfacing with the Ford digital throttle. Position Feedback provided by the throttle position sensor via OBDII (not yet implemented) Steering RoboteQ controller connected to a DC motor Motor and gearbox on order. Interim solution of legacy Parker Servo Motor Brake Atmel controller providing a 4 bit digital signal to pneumatic solenoid valves controlling 4 pneumatic cylinders. Functional and calibrated. Independent brake pressure transducer for feedback. March, 14 2005 Embedded Team

Actuation Part 2 Transmission E-Stop OBD-II This will be the same as last year. A linear actuator cable pull, controlled over serial interface. Not yet implemented. E-Stop Analog circuitry under development. Radio system from airplane remote control. Will have RS-232 interface. OBD-II Autotap OBD-II converter to serial interface. CAN buss interface issues. Investigating alternative CANalyzer by Vector Informatiks associated with Bosch March, 14 2005 Embedded Team

Skynet Distributed message passing and control system. Used for intermodule communication. REQUIREMENTS Machine/IP independent module location (so that we don't have to lock a module onto a given machine) Support for identifying machines capable of running a module and startup of that module on that machine (in case a machine goes down in the race) Very low latency operation (<1 msec timestamping, ~1 msec latency). We are going to need this for timing synchronization > 97% reliability for all messages, 100% reliability for select messages Need the ability to uniquely identify modules that may have multiple instances running (such as multiple image processing modules) Need ability to disconnect modules (so multiple people can run simulations at the same time on the same set of computers) March, 14 2005 Embedded Team

Architecture March, 14 2005 Embedded Team

API C, C++ Three messages paradigms: Short, unreliable messages Long, reliable messages Distributed global variables Very little structure forced upon the module Rate limiting of modules handled automatically March, 14 2005 Embedded Team

Control and Operator Interface Spun off into separate project, SkynetGui Integrates sensing, planning, and state output visually March, 14 2005 Embedded Team

Status Messaging Control - Implemented over global variables layer. Short, unreliable messages Large messages Reliable messages Shared global variables – no demand yet Module Registration Control - Implemented over global variables layer. Skynet Operator Interface Synchronized module timing. March, 14 2005 Embedded Team

RFA responses COTS board Simulation environment Not feasible due to resources and manpower. Simulation environment New modelling sub team CDS 190 is working on this. Maintenance of development environment New sub team build team In charge of build dependancies and code structure. Latency of Skynet Messages Quantified 1024 byte packets exchanging at a total bandwidth of 2MB/s on an otherwise unladen network, round-trip latencies averaged 459 us with standard deviation of 105 us and a maximum 743 us. More comprehensive tests under development. March, 14 2005 Embedded Team

Timeline March 2005 Spring Break Field Test Spring Term 2005 Implement preliminary E-Stop Functionality Continue testing and verification of SDS functionality. Implement operational skynetGUI Provide ability to remotely start and stop modules. Provide the networking and computers necessary to support the field test. Spring Term 2005 Replace Parker System with Roboteq Steering. Implement transmission and ignition actuators. Provide a functional message passing system between modules. Maintain computing hardware necessary to run tests setup in Alice. Maintain and improve skynet and skynetGUI. March, 14 2005 Embedded Team

Summary Adrive implemented over skynet listening for commands and providing feedback. Brake throttle and steering actuation implemented with SDS and calibrated. SkyNet providing base functionality. skynetGUI basic visualization functionality, other functions under development. Module Starter under testing, expect operational by spring field test. 3 fully functional workstations providing access to all computing in Alice. March, 14 2005 Embedded Team