2018 Hyperlynx Preliminary Design Briefing
2018 Hyperlynx Preliminary Design Briefing
After the competition, new goals were set: grow the team to be
truly multi-disciplined, establish fundraising for the next year, and
design the new pod to be robust, simple, and safe. The pod design
was set on a 2-year timeline. For 2018: build a non-propelled vehicle to
prove our new controls and build techniques. For 2019: add an electric
propulsion system. The new rule changes in September 2017 bumped
up our propulsion plan to this year, and we hope to impress with our
resulting design.
Simple. Cheap. Fast
These are our guiding design principles. Our resources are finite, and it is critical that we design solutions that are
simple and robust, inexpensive both in money and resources, and fast to design and manufacture. We have striven to
design a pod that is “buildable”, making sure every part can be built using available techniques and materials. Aero will be
included, but is not depicted here.
For the 2018 Hyperloop Competition, the Hyperlynx design is an electrically-propelled wheeled pod with a design top
speed of 360 ft/sec and an estimated cost of $35,000.
The front axle has the same CV joints, brake disc, and
axles, with no sprocket gear. The setup is identical to allow
for future all-wheel-drive development.
Propulsion- Motor
EMRAX 208 Mid-Voltage Variant
Controllers
- 10 Arduino Pro Micros for sensor reporting, fault checking, and passing data to Flight Controller
- 4 motor controllers for linear actuators, brake stepper motor, and transmission linear actuator
STOP
● Default power-on state, or when pod comes to a stop post-flight. Passive braking remains on. Pod Health can
be determined quickly in this state.
● Transition: Crew selects “INIT” on GUI, transition to INIT
INIT
● Pod runs internal BIT test. Allows crew to enter flight parameters (distance, top speeds, acceleration/braking
profiles, any desired coast phase). Manual control panel is powered-on for rail fitment, motor testing, and brake
release for transportation (tube entry/exit).
● Transition: Crew selects “READY” via GUI, transition to READY
READY
● Protected Transition: adds 2nd level GUI confirmation and timer delay to prevent accidental transition into a “live”
state. Pod hands off control to Flight Control module, standing by for LAUNCH command. Internal Pod Abort
system activates. Pod retracts rail suspension to preflight load setting. Manual controls disabled. Data logging
begins.
● Transition: Crew selects “LAUNCH” via GUI, transition to ACCEL-N
-or- Internal Pod Abort, transition to INIT with alert
Pod States
ACCEL-N
● Pod enters Power Neutral gear. Brakes off. Motor sets 2000 RPM. Pod should not roll.
● Transition: Motor reaches 2000 RPM, transition to ACCEL-1
-or- Internal Pod Abort, transition to BRAKE
ACCEL-1
● Transmission controller slows the ring gear, transmitting power to the output shaft, until 6:1 final drive ratio (Motor
RPM / Wheel RPM) is reached. Motor maintains 2000 RPM. Pod begins to roll in this state. Smooth ramp up of
acceleration.
● Transition: 6:1 final drive ratio achieved, transition to ACCEL-2
-or- Internal Pod Abort, transition to BRAKE
-or- If COAST selected: when top speed parameter achieved, transition to COAST
ACCEL-2
● Motor sets 6000 RPM. Transmission controller maintains 6:1 final drive ratio. Maximum acceleration.
● Transition: Motor 5000 RPM achieved, transition to ACCEL-3
-or- Internal Pod Abort, transition to BRAKE
-or- If COAST selected: when top speed parameter achieved, transition to COAST
ACCEL-3
● Transmission controller set to 2:1 final drive ratio (locked). Motor maintains 5000 RPM. Acceleration tapers.
● Transition: Transmission controller achieves 2:1 final drive ratio, transition to ACCEL-4
-or- Internal Pod Abort, transition to BRAKE
-or- If COAST selected: when top speed parameter achieved, transition to COAST
Pod States
ACCEL-4
● Motor set to 5760 RPM (max). Trans controller fully engaged and locked. Min acceleration, max top speed.
● Transition: Motor reaches 5760 RPM, transition to BRAKE
-or- Internal Pod Abort, transition to BRAKE
(no COAST option from ACCEL-4)
BRAKE
● Motor controller set to idle. Trans controller engages fully and locks to ensure no downshift motor overspeeds.
Brakes set to 1.3G deceleration. Front rail suspension retracts fully to maximize braking force.
● Transition: Pod speed reaches 0, transition to STOP.
EMERGENCY BRAKE
● LV power loss, purely mechanical state. Passive braking of 1G begins. If power is restored, pod will reboot and
RPi will initiate GUI program; default state of STOP would be entered.
● Transition: None.
COAST
● Optional state; likely used for testing during external subtrack, low speed hyperloop, or while on jackstands.
Maintain top speed via motor RPM. Trans controller fully engages and locks.
● Transition: Desired braking point reached, transition to BRAKE
-or- Internal Pod Abort, transition to BRAKE
Test & Evaluation
It is our intention to show up with a race-ready pod, and this is our plan
to achieve that goal:
● All fabricated parts will have completed load analysis and follow
GD&T standards for reliable assembly
● Pod will complete simulated Internal Abort condition tests
● Fully documented operating checklists for crew and SpaceX
officials for each test phase
● Majority of SpaceX testing completed and documented prior to
competition (Functional, Mechanical Fit, Navigation, State
Transition, and Low Speed Tests)
● Scale model wind tunnel and simulated aerodynamic testing
● High speed dynamometer runs for propulsion testing
● Thermal load testing on coolant system
● Final Design Report will include all calculations, technical
documents, and FEA results
Safety Features
Automated Pod Health Monitoring
- Critical systems continuously monitored for faults External Pod GUI
- Automatic sensor fault-checking and isolation - Monitors all sensors, actuators, and BMS data
- Pod can trigger an automated self-abort - Sets flight parameters during INIT
- Allows crew to send commands to the pod including
Manual Control Panel (at rear of pod) abort and state transitions
- LED display for pod status and low voltage/high
voltage system conditions High & Low Voltage
- Controls for brakes, rail suspension, and - Battery isolation via integrated BMS or physical
transmission controller motion isolation switch on pod
- Master Switches, HV battery isolation switch, LV - If battery is isolated, motor controller is protected from
fuses, and protected HV circuit breakers overvoltage via IGBT & resistor bank
- - Protected battery pack circuit breakers
Emergency Braking - High Voltage is grounded to the chassis
- Calibrated, passive mechanical braking in the - Low Voltage operates with a floating ground
event of LV power loss - Active liquid cooling for High Voltage system.
We know the Hyperloop team at SpaceX is small, so thank you for the
work you’ve put into hosting the competition.
This design project has been a labor of love for the last two years; but the
knowledge we’ve gained about design, manufacturing, systems
integration, engineering, and teamwork has been enormous.
We feel like better engineers because of it.
Thank you!
Team Information
www.DenverHyperlynx.com
[email protected]
Primary Contact
Wencil Stanek
[email protected]
[email protected]
301-442-4650