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

SE401 Final Project PowerPoint PPT Presentation


  • 45 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

SE401 Final Project

Presenters:

Farhad Shroff

Jerome Pineda

Lyndon Kidwell

Steve Meagher

May 11, 2010


Se401 final project

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

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


Se401 final project

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


Se401 final project

Requirements Packages


Se401 final project

System Requirements


Se401 final project

System Domain Diagram


Se401 final project

Pre-Battle Demo Use Case


Se401 final project

Operational Use Case


Se401 final project

Attack Use Case


Se401 final project

Judging Use Case


Se401 final project

Maintenance Use Case


Se401 final project

Battlebot Top Level Structure


Se401 final project

Battlebot Top Level Structure


Se401 final project

Battlebot Chassis


Se401 final project

Battlebot Chassis


Se401 final project

Battlebot Chassis Mass Properties


Se401 final project

EStop


Se401 final project

EStop Sequence Diagram


Pneumatic subsystem

Pneumatic Subsystem


Pneumatic subsystem activity

Pneumatic Subsystem Activity


Pneumatic sequence diagram

Pneumatic Sequence Diagram


Se401 final project

Pneumatic Parametric Diagram


R c controller transmitter

R/C Controller Transmitter

Control Assignment & Controller Inputs

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


R c transmitter

R/C Transmitter


R c receiver receive signal activity

R/C ReceiverReceive Signal Activity


R f receiver sequence diagram

R/F Receiver Sequence Diagram


R c receiver

R/C Receiver


Controller subsystem

Controller Subsystem


Electronic speed controller

Electronic Speed Controller


Electronic speed control

Electronic Speed Control


Drive train drive activity

Drive TrainDrive Activity


Drive train electrical power analysis

Drive Train Electrical Power Analysis


Drive train mechanical power analysis

Drive Train Mechanical Power Analysis


Drive train components

Drive Train Components


Electrical power subsystem

Electrical Power Subsystem


Electrical power distribution

Electrical Power Distribution


Primary weapon lifting arm

Primary Weapon (Lifting Arm)


Primary weapon lifting arm1

Primary Weapon (Lifting Arm)


Primary weapon constraints

Primary Weapon Constraints


Primary weapon activity

Primary Weapon Activity


Secondary weapon subsystem

Secondary Weapon Subsystem


Secondary weapon activity

Secondary Weapon Activity


Summary

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

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/


Se401 final project

Questions


  • Login