You are on page 1of 30

CONTROLLER

AGENDA Hyperloop

• Hyperloop Competition

• Competition Team

• Team
Printed Circuit
• Printed Circuit Board Board

• Sensor Data Sensor Data

• Actuation
Actuation
• Communication
Communication
• Conclusion
• Questions Conclusion

2
INTRODUCTION Hyperloop

• Celeste Bean Competition

• Connor Buckland Team

• Ben Hartl
Printed Circuit
• Cameron McCarthy Board

• Connor Mulcahey Sensor Data

Actuation

Communication

Conclusion

3
HYPERLOOP Hyperloop

• Cities < 700 miles apart Competition

• Max speed of 760 mph Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

4
HYPERLOOP Hyperloop

• Depressurized steel tube Competition

• Magnetic levitation Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

5
COMPETITION Hyperloop

• Organized by Elon Musk and SpaceX Competition

• Design and build a proof of concept pod Team

• Compete in Summer 2016 on 1-mile long track


Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

6
COMPETITION Hyperloop

Competition

Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

7
DESIGN WEEKEND Hyperloop

• 1200 original applicants Competition

• 1 of 120 teams invited to Design Weekend at Texas A&M Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

8
DESIGN WEEKEND Hyperloop

• 1 of 30 teams admitted to the final stage of the competition Competition

• Few teams with a Computer Engineering Team Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

9
UCSB TEAM Hyperloop

Competition

Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

10
UCSB TEAM Hyperloop

• 23 undergraduate students Competition

• Computer Engineering Team

• Computer Science
Printed Circuit
• Mechanical Engineering Board

• Electrical Engineering Sensor Data

• Physics
Actuation
• Economics
Communication

Conclusion

11
UCSB TEAM Hyperloop

• $50,000 budget raised from donors, crowd funding, and UCSB Competition

Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

12
UCSB TEAM Hyperloop

• Length: 14’ (4.3m); Width: 3’5” (1.0m); Height: 3’4” (1.0m) Competition

Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

13
PRINTED CIRCUIT BOARD Hyperloop

• 8.1” x 8.1” printed circuit board Competition

• (2) ARM Cortex-M4 Team

microcontrollers Printed Circuit

• 430 components Board

• Designed for flexibility Sensor Data

• Sensor Data Actuation

• Telemetry & communication Communication

• Actuation Conclusion

14
SENSOR DATA Hyperloop

• Must report: Competition

• 3D position, velocity, and acceleration Team

• Roll, pitch, and yaw Printed Circuit

• Temperature Board

• Pressure Sensor Data

• Power consumption Actuation

Communication

Conclusion

15
NAVIGATION SYSTEM Hyperloop

• Find position, velocity, and acceleration Competition

• The tube has reflective strips every 100’


Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

16
NAVIGATION SYSTEM Hyperloop

• Photoelectric sensor detects strips Competition

• 2 inertial accelerometer determine position between strips


Team
• Velocity compared to hard-coded profile for safety
Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

17
ATTITUDE SYSTEM Hyperloop

• Find roll, pitch, and yaw Competition

• 4 short ranging sensors on the bottom for roll and pitch Team
• 4 long ranging sensors on the sides for yaw
Printed Circuit
Board
Roll
Sensor Data
Pitch
Yaw
Actuation

Z
Communication

Conclusion

X Y 18
SENSOR LOCATIONS Hyperloop

Competition
• Photoelectric sensors (2) – navigation
• Long ranging sensors (4) – data acquisition
• Short ranging sensors (4) – stability Team
• System Circuit Board
Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

19
BATTERY MANAGEMENT Hyperloop

• Detects battery packs’ voltage levels Competition

• Issues alerts is voltage is too low or high Team


• Determines current draw to calculate power consumption
Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

20
MAGNETIC LEVITATION Hyperloop

• Controls 6 Arx Pax H3.0 magnetic levitation engines Competition

• Interface with motors via ASi BAC motor controller Team


• Programmable via ASi BACDoor software
Printed Circuit
• Motor speed controlled using analog 0 – 5 V signal Board

Sensor Data

Actuation

Communication

Conclusion

21
TRANSIT ACTUATION Hyperloop

• Raises and lowers the pod to various heights to levitate or rest upon wheels Competition

Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

22
TRANSIT ACTUATION Hyperloop

• Motor activates service propulsion wheel to move pod through tube Competition

Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

23
BRAKE ACTUATION Hyperloop

• Air valve actuates eddy current braking system Competition

• Rotates the magnetic arrays Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

Eddy current braking for high speed Friction brakes to come to full stop
24
BRAKE ACTUATION Hyperloop

• Air valve actuates secondary friction brakes Competition

Team

Printed Circuit
Board

Sensor Data

Actuation

Communication

Conclusion

25
EMERGENCY PROTOCOL Hyperloop

• Emergency state activated by: Competition

• Emergency pod stop command Team


• Large deviations in velocity profile
Printed Circuit
• Protocol Board

• Engage eddy current brakes


Sensor Data
• Engage frictional brakes at lower speeds
Actuation
• Disengage brakes once pod stop completed
Communication
• Disengage magnetic levitation engines
• Use linear actuator to activate service propulsion wheels Conclusion

• Engage service propulsion motor until tube exit completed


26
COMMUNICATION Hyperloop

• Must communicate sensor data once per second Competition

• SpaceX provides a Network Access Panel (NAP) that provides wireless Team
network access
Printed Circuit
• Ethernet module on printed circuit Board
board sends data
Sensor Data

Actuation

Communication

Conclusion

27
NETWORKING APPLICATION Hyperloop

• Developed secure Competition

application level
Team
protocol
Printed Circuit
• Displays and logs Board
sensor data
Sensor Data
• Sends control
Actuation
messages
Communication

Conclusion

28
CODE ARCHITECTURE Hyperloop

• Managed a git repository for version control Competition

• Ensures that code remains clean Team

• Avoids merge conflicts Printed Circuit


Board

Sensor Data

Actuation

Communication

Conclusion

29
CONCLUSION Hyperloop

• Thank you to Dr. John Johnson and Will Miller Competition

• Thank you to Elon Musk and SpaceX Team

• Thank you to our generous sponsors Printed Circuit


Board

Sensor Data

Actuation

Communication

Conclusion

Jonathan Siegel Tilt Contributors


30

You might also like