AGENDA. Hyperloop Competition Team Printed Circuit Board Sensor Data Actuation Communication Conclusion Questions. Hyperloop. Competition.

Transcription

1 CONTROLLER

2 AGENDA Questions 2

3 INTRODUCTION Celeste Bean Connor Buckland Ben Hartl Cameron McCarthy Connor Mulcahey 3

4 HYPERLOOP Cities < 700 miles apart Max speed of 760 mph 4

5 HYPERLOOP Depressurized steel tube Magnetic levitation 5

6 COMPETITION Organized by Elon Musk and SpaceX Design and build a proof of concept pod Compete in Summer 2016 on 1-mile long track 6

7 COMPETITION 7

8 DESIGN WEEKEND 1200 original applicants 1 of 120 teams invited to Design Weekend at Texas A&M 8

9 DESIGN WEEKEND 1 of 30 teams admitted to the final stage of the competition Few teams with a Computer Engineering 9

10 UCSB TEAM 10

11 UCSB TEAM 23 undergraduate students Computer Engineering Computer Science Mechanical Engineering Electrical Engineering Physics Economics 11

12 UCSB TEAM $50,000 budget raised from donors, crowd funding, and UCSB 12

13 UCSB TEAM Length: 14 (4.3m); Width: 3 5 (1.0m); Height: 3 4 (1.0m) 13

14 PRINTED CIRCUIT BOARD 8.1 x 8.1 printed circuit board (2) ARM Cortex-M4 microcontrollers 430 components Designed for flexibility Telemetry & communication 14

15 SENSOR DATA Must report: 3D position, velocity, and acceleration Roll, pitch, and yaw Temperature Pressure Power consumption 15

16 NAVIGATION SYSTEM Find position, velocity, and acceleration The tube has reflective strips every

17 NAVIGATION SYSTEM Photoelectric sensor detects strips 2 inertial accelerometer determine position between strips Velocity compared to hard-coded profile for safety 17

18 ATTITUDE SYSTEM Find roll, pitch, and yaw 4 short ranging sensors on the bottom for roll and pitch 4 long ranging sensors on the sides for yaw Roll Pitch Z Yaw X Y 18

19 SENSOR LOCATIONS Photoelectric sensors (2) navigation Long ranging sensors (4) data acquisition Short ranging sensors (4) stability System Circuit 19

20 BATTERY MANAGEMENT Detects battery packs voltage levels Issues alerts is voltage is too low or high Determines current draw to calculate power consumption 20

21 MAGNETIC LEVITATION Controls 6 Arx Pax H3.0 magnetic levitation engines Interface with motors via ASi BAC motor controller Programmable via ASi BACDoor software Motor speed controlled using analog 0 5 V signal 21

22 TRANSIT ACTUATION Raises and lowers the pod to various heights to levitate or rest upon wheels 22

23 TRANSIT ACTUATION Motor activates service propulsion wheel to move pod through tube 23

24 BRAKE ACTUATION Air valve actuates eddy current braking system Rotates the magnetic arrays Eddy current braking for high speed Friction brakes to come to full stop 24

25 BRAKE ACTUATION Air valve actuates secondary friction brakes 25

26 EMERGENCY PROTOCOL Emergency state activated by: Emergency pod stop command Large deviations in velocity profile Protocol Engage eddy current brakes Engage frictional brakes at lower speeds Disengage brakes once pod stop completed Disengage magnetic levitation engines Use linear actuator to activate service propulsion wheels Engage service propulsion motor until tube exit completed 26

27 COMMUNICATION Must communicate sensor data once per second SpaceX provides a Network Access Panel (NAP) that provides wireless network access Ethernet module on printed circuit board sends data 27

28 NETWORKING APPLICATION Developed secure application level protocol Displays and logs sensor data Sends control messages 28

29 CODE ARCHITECTURE Managed a git repository for version control Ensures that code remains clean Avoids merge conflicts 29

30 CONCLUSION Thank you to Dr. John Johnson and Will Miller Thank you to Elon Musk and SpaceX Thank you to our generous sponsors Jonathan Siegel Tilt Contributors 30