SE401 Final Project - PowerPoint PPT Presentation

Slide1 l.jpg
Download
1 / 50

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

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.

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


Slide1 l.jpg

SE401 Final Project

Presenters:

Farhad Shroff

Jerome Pineda

Lyndon Kidwell

Steve Meagher

May 11, 2010


Slide2 l.jpg

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 l.jpg

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


Slide4 l.jpg

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


Slide5 l.jpg

Requirements Packages


Slide6 l.jpg

System Requirements


Slide8 l.jpg

System Domain Diagram


Slide9 l.jpg

Pre-Battle Demo Use Case


Slide10 l.jpg

Operational Use Case


Slide11 l.jpg

Attack Use Case


Slide12 l.jpg

Judging Use Case


Slide13 l.jpg

Maintenance Use Case


Slide14 l.jpg

Battlebot Top Level Structure


Slide15 l.jpg

Battlebot Top Level Structure


Slide16 l.jpg

Battlebot Chassis


Slide17 l.jpg

Battlebot Chassis


Slide18 l.jpg

Battlebot Chassis Mass Properties


Slide19 l.jpg

EStop


Slide20 l.jpg

EStop Sequence Diagram


Pneumatic subsystem l.jpg

Pneumatic Subsystem


Pneumatic subsystem activity l.jpg

Pneumatic Subsystem Activity


Pneumatic sequence diagram l.jpg

Pneumatic Sequence Diagram


Slide25 l.jpg

Pneumatic Parametric Diagram


R c controller transmitter l.jpg

R/C Controller Transmitter

Control Assignment & Controller Inputs

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


R c transmitter l.jpg

R/C Transmitter


R c receiver receive signal activity l.jpg

R/C ReceiverReceive Signal Activity


R f receiver sequence diagram l.jpg

R/F Receiver Sequence Diagram


R c receiver l.jpg

R/C Receiver


Controller subsystem l.jpg

Controller Subsystem


Electronic speed controller l.jpg

Electronic Speed Controller


Electronic speed control l.jpg

Electronic Speed Control


Drive train drive activity l.jpg

Drive TrainDrive Activity


Drive train electrical power analysis l.jpg

Drive Train Electrical Power Analysis


Drive train mechanical power analysis l.jpg

Drive Train Mechanical Power Analysis


Drive train components l.jpg

Drive Train Components


Electrical power subsystem l.jpg

Electrical Power Subsystem


Electrical power distribution l.jpg

Electrical Power Distribution


Primary weapon lifting arm l.jpg

Primary Weapon (Lifting Arm)


Primary weapon lifting arm43 l.jpg

Primary Weapon (Lifting Arm)


Primary weapon constraints l.jpg

Primary Weapon Constraints


Primary weapon activity l.jpg

Primary Weapon Activity


Secondary weapon subsystem l.jpg

Secondary Weapon Subsystem


Secondary weapon activity l.jpg

Secondary Weapon Activity


Summary l.jpg

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 l.jpg

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/


Slide50 l.jpg

Questions


  • Login