SE401 Final Project

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

8. System Domain Diagram

9. Pre-Battle Demo Use Case

10. Operational Use Case

11. Attack Use Case

12. Judging Use Case

13. Maintenance Use Case

14. Battlebot Top Level Structure

15. Battlebot Top Level Structure

16. Battlebot Chassis

17. Battlebot Chassis

18. Battlebot Chassis Mass Properties

19. EStop

20. EStop Sequence Diagram

22. Pneumatic Subsystem

23. Pneumatic Subsystem Activity

24. Pneumatic Sequence Diagram

25. Pneumatic Parametric Diagram

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

27. R/C Transmitter

29. R/C ReceiverReceive Signal Activity

30. R/F Receiver Sequence Diagram

31. R/C Receiver

32. Controller Subsystem

33. Electronic Speed Controller

34. Electronic Speed Control

35. Drive TrainDrive Activity

36. Drive Train Electrical Power Analysis

37. Drive Train Mechanical Power Analysis

38. Drive Train Components

40. Electrical Power Subsystem

41. Electrical Power Distribution

42. Primary Weapon (Lifting Arm)

43. Primary Weapon (Lifting Arm)

44. Primary Weapon Constraints

45. Primary Weapon Activity

46. Secondary Weapon Subsystem

47. Secondary Weapon Activity

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

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

50. Questions