1 / 50

Integrating MBSE in Battlebot Design: Approaches and Challenges

This presentation, led by a diverse team of experts, focuses on the integration of Model-Based Systems Engineering (MBSE) in designing a battlebot. The team members, hailing from various domains like aerospace and software engineering, share their experiences with project requirements, subsystems, and overall structure. Key topics include SysML diagrams, system requirements, and the challenges of maintaining effective communication and model organization. The discussion emphasizes real-world applications through practical use cases, ultimately aiming to enhance the design process of robotic combat systems.

lilian
Télécharger la présentation

Integrating MBSE in Battlebot Design: Approaches and Challenges

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SE401 Final Project Presenters: Farhad Shroff Jerome Pineda Lyndon Kidwell Steve Meagher May 11, 2010

  2. 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

  3. 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

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

  5. Requirements Packages

  6. System Requirements

  7. System Domain Diagram

  8. Pre-Battle Demo Use Case

  9. Operational Use Case

  10. Attack Use Case

  11. Judging Use Case

  12. Maintenance Use Case

  13. Battlebot Top Level Structure

  14. Battlebot Top Level Structure

  15. Battlebot Chassis

  16. Battlebot Chassis

  17. Battlebot Chassis Mass Properties

  18. EStop

  19. EStop Sequence Diagram

  20. Pneumatic Subsystem

  21. Pneumatic Subsystem Activity

  22. Pneumatic Sequence Diagram

  23. Pneumatic Parametric Diagram

  24. R/C Controller Transmitter Control Assignment & Controller Inputs Two choices for steering:Conventional (car like)Tank Steering

  25. R/C Transmitter

  26. R/C ReceiverReceive Signal Activity

  27. R/F Receiver Sequence Diagram

  28. R/C Receiver

  29. Controller Subsystem

  30. Electronic Speed Controller

  31. Electronic Speed Control

  32. Drive TrainDrive Activity

  33. Drive Train Electrical Power Analysis

  34. Drive Train Mechanical Power Analysis

  35. Drive Train Components

  36. Electrical Power Subsystem

  37. Electrical Power Distribution

  38. Primary Weapon (Lifting Arm)

  39. Primary Weapon (Lifting Arm)

  40. Primary Weapon Constraints

  41. Primary Weapon Activity

  42. Secondary Weapon Subsystem

  43. Secondary Weapon Activity

  44. 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

  45. 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/

  46. Questions

More Related