SE401 Final Project
Sponsored Links
This presentation is the property of its rightful owner.
1 / 50

SE401 Final Project PowerPoint PPT Presentation


  • 50 Views
  • Uploaded on
  • Presentation posted in: General

SE401 Final Project. Presenters: Farhad Shroff Jerome Pineda Lyndon Kidwell Steve Meagher. May 11, 2010. Introduction. Team Establishment Virtual team, diversity of experience and domain backgrounds Farhad Shroff – Everett, WA ; Aerospace Lyndon Kidwell – Bellevue, WA Software

Download Presentation

SE401 Final Project

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


SE401 Final Project

Presenters:

Farhad Shroff

Jerome Pineda

Lyndon Kidwell

Steve Meagher

May 11, 2010


Introduction

  • Team Establishment

    • Virtual team, diversity of experience and domain backgrounds

      • Farhad Shroff – Everett, WA ; Aerospace

      • Lyndon Kidwell – Bellevue, WA Software

      • Steve Meagher – Houston, TX ; Mechanical

      • Jerome Pineda – El Segundo, CA ; Aerospace

  • Project Selection

    • Existing requirements and design structure

  • Operating Mantra

    • Weekly WebEx / Teleconference meetings

    • Email for more frequent communication

    • Ownership of subsystem and model definition

  • Presentation Goals:

    • Show our model and approach to MBSE of the system

    • SysML diagrams

    • Use of Artisan Software


Outline

  • Introduction - Jerome

  • Requirements – Jerome

  • High level Use Cases - Farhad

  • System Level Structure – Farhad

  • Chassis – Farhad

  • Estop - Farhad

  • Pnuematic - Jerome

  • R/C Transmitter - Jerome

  • R/C Receiver - Lyndon

  • Controller - Lyndon

  • Drive Train - Lyndon

  • Power - Steve

  • Primary/Secondary Weapons - Steve

  • Summary / Conclusions


Requirements

  • Basis for project: Professional Class / College Building Rules for Battlebots

  • Parsed out requirements for Subsystems into packages

    • System

    • Activation / Deactivation

    • Controller

    • Electrical Power

    • Pneumatics

    • Weapon

  • Allocate requirements to each subsystem to drive block and internal definition diagrams


Requirements Packages


System Requirements


System Domain Diagram


Pre-Battle Demo Use Case


Operational Use Case


Attack Use Case


Judging Use Case


Maintenance Use Case


Battlebot Top Level Structure


Battlebot Top Level Structure


Battlebot Chassis


Battlebot Chassis


Battlebot Chassis Mass Properties


EStop


EStop Sequence Diagram


Pneumatic Subsystem


Pneumatic Subsystem Activity


Pneumatic Sequence Diagram


Pneumatic Parametric Diagram


R/C Controller Transmitter

Control Assignment & Controller Inputs

Two choices for steering:Conventional (car like)Tank Steering


R/C Transmitter


R/C ReceiverReceive Signal Activity


R/F Receiver Sequence Diagram


R/C Receiver


Controller Subsystem


Electronic Speed Controller


Electronic Speed Control


Drive TrainDrive Activity


Drive Train Electrical Power Analysis


Drive Train Mechanical Power Analysis


Drive Train Components


Electrical Power Subsystem


Electrical Power Distribution


Primary Weapon (Lifting Arm)


Primary Weapon (Lifting Arm)


Primary Weapon Constraints


Primary Weapon Activity


Secondary Weapon Subsystem


Secondary Weapon Activity


Summary

  • Exporting issues

  • Stand alone models – lack of a repository to work simultaneous

  • Integration of components and data flows manually intensive

  • Organization of the model

    • Packages

    • Naming conventions

      • Naming, namespaces, data types

    • Benefits

      • Export of individual package to reuse

      • Consistent interface definition

      • Data types defined by industry or domain

      • Clear compartmentalization

  • Tutorial was too task oriented

    • Hard to learn SysML and tool at the same time


References

[1] Battlebots

http://www.battlebots.com/BattleBots.com/Home/Home.html

[2] Vantec Electronic Speed Controllers

http://www.vantec.com

[3] Futaba R/C Controllers

http://www.futaba-rc.com/

[4] Kickin' Bot : An illustrated guide to Building Combat Robots

Grant Imahara (Myth Busters)

ISBN0-7645-4113-7

[5] Team TBD – Florida State University

http://www.eng.fsu.edu/ME_senior_design/2003/team9/


Questions


  • Login