Welcome to the Wiki page of Team 1 of VANT151 – 2025S. Our team consists of 12 members divided into five sub-teams: Coding, Mechanical, Electrical, Structural, and Documentation. In this course, we undertook a multidisciplinary project to design and build an electric tricycle prototype aimed at addressing key challenges in cycling. This page documents our design process, sub-system development, and finalized prototype. The primary objective of our project is to improve the safety, efficiency, and user experience of cycling through innovative engineering solutions. Our prototype combines mechanical design, electronic systems, structural components, and programmed functionality into a cohesive vehicle capable of racing and demonstrating additional features at the Vantage One Capstone Conference.
Introduction
At UBC Okanagan, personal vehicles remain the dominant mode of transportation, but their environmental impact is a growing concern. With transportation being a major source of greenhouse gas emissions, shifting toward more sustainable commuting options is essential in addressing climate change. Although alternatives like cycling and walking exist, they currently represent only a small share of campus travel.
To address this, UBCO’s Climate Action Plan (CAP 2030) sets ambitious goals to reduce emissions and promote active transportation. One promising solution is the electric tricycle — a practical, inclusive, and environmentally friendly option that makes cycling more accessible for a wider range of users.
Our project aims to design a tricycle that is safe, weather-resistant, comfortable, and efficient. By aligning with Target 4 of the UBCO Transportation Plan, our design encourages students, faculty, and staff to choose tricycles over cars for their daily commutes, leading to a more sustainable campus and reduced carbon emissions.
Team Requirements
Functions
The primary functions of this electric tricycle are to:
Provide reliable motor-assisted propulsion for improved cycling efficiency.
Steer and drive smoothly under user control using a remote-control system.
Maintain structural stability and support the weight of an average adult rider.
Include at least one functional extra feature, such as lighting, a horn, or temperature sensing.
Objectives
The objective of this tricycle project is to enhance the overall functionality and user experience of cycling by:
Reducing the physical strain required to operate the vehicle.
Ensuring safe, stable, and responsive vehicle handling.
Integrating programmable systems for automated or user-controlled behavior.
Constraints
The constraints for the design and build of the electric tricycle are:
The prototype must fit within the physical and material limitations of the lab space and university-provided resources.
All components must operate safely within the electrical power limits allowed in the course (24 V system).
The vehicle must be able to complete the designated Capstone race course.
The project must be completed within the 8-week course duration, concluding at the Capstone Conference on July 7, 2025.
The design must adhere to fabrication limits, using tools such as 3D printers, laser cutters, and basic hand tools available in UBC’s engineering labs.
Gantt Chart
The chart below shows the work distribution for Team 1
Coding
Overview of the Arduino code
This project implements a wireless communication control system using two Arduino boards and nRF24L01+ modules. The transmitter captures user inputs (joystick and buttons), encodes them into a structured data packet, and sends it via RF to the receiver. The receiver parses the data and executes control tasks, such as steering, motor throttle, fan toggling (cool/heat), LED, roof, and chair servo movement. The system supports two modes: '''manual mode''', where the user directly controls the vehicle, and '''autonomous mode''', where the vehicle follows a preprogrammed figure-eight path. An LCD screen on the receiver displays real-time information, including current temperature, fan status, and chair angle.
The core control logic relies on structured data exchange using a Signal struct, combined with state variables. An ACK payload system enables real-time status feedback from receiver to transmitter.
Requirements
Function
Develop transmitter & receiver code to implement remote control.
Control motor to make the car run.
Control servo motor to open and close the roof, and move the seat forward and backward in six gears.
Control LED on and off.
Control fan to switch in three gears (cold air, hot air, off).
The screen displays the current temperature, fan status and chair rotation angle in real time.
Control the car to run automatically along the predetermined track.
Objective
Build a two-way communication system between the transmitter and the receiver, and use the nRF24L01+ module to achieve data transmission.
Integrate a joystick and multiple buttons on the transmitter to control the movement of the car and various auxiliary systems.
Provide a user-friendly mode selection interface and real-time information feedback through the LCD screen.
Achieve precise control of LED lights, roof motors, seat motors, and fans (cold/hot mode).
Use non-blocking timing logic (millis()) to achieve smooth motion control of servo motors.
Write a preset automatic navigation logic so that the car can complete autonomous movement of the "8"-shaped path.
Implement the function of returning status information so that the transmitter can obtain temperature, fan status, and chair angle in real time.
Constraints
During development, the team faced several hardware and software limitations, which were addressed through optimized coding strategies:
1.Limited I/O Pins
The Arduino Uno has a limited number of digital and analog pins. Efficient pin mapping and sharing strategies were necessary to accommodate servos, fans, buttons, joystick, and the LCD display.
2. Servo Speed Control Precision
The default Servo library does not support variable speed. Custom logic was written to interpolate servo angles over time using millis() to ensure smooth transitions.
3. RF Data Packet Size
The nRF24L01+ has a max payload of 32 bytes. The Signal struct was optimized to include only essential fields, and transmission intervals were set to 30ms to balance latency and stability.
4. Real-Time Feedback Synchronization
ACK payload communication requires synchronous timing. A statusPacket structure and internal status flags were introduced to manage display data and avoid desynchronization or delays.
5. Power Consumption Management
Simultaneous use of Peltier modules, motors, and servos causes high current draw. Timed operation gaps and throttled activation logic were implemented to prevent brownouts or resets.
All base and extra functions must be tested and debugged within the 8-week timeline.
The Design
Initial Design Sketch 1 and 2
During our initial brainstorming phase, we came up with two main design directions. These are captured in the sketch, which outlines both the layout of components and the overall structure of the design.
1. Functionality First
Our top priority was making sure the design met all functional needs. This included things like where the breadboard would go, how far sensors could reach, and how cables would be routed. The sketch highlights the areas we wanted to keep accessible or protected, which guided decisions around port placement and the shape of the enclosure.
2. Form & Ergonomic
Initial Design Sketch 3
We also thought about how the design would feel and function in the user’s hands. One of the options had a wider, flatter layout that would be easier to handle, while the other took on a more vertical form to save space. Both concepts took into account airflow, wiring space, and how easy it would be to swap out parts.
3.Working Within Constraints
Looking at things like component dimensions and breadboard fit, we weighed the pros and cons of each design. Sketching both ideas gave us a fast way to compare them before getting into detailed CAD modeling.
Decision Matrix for Controller Selection
D1
D2
D3
Ease of Use
3
2
5
Economic
2
4
5
Aesthetics
2
4
5
After comparing all three controller designs using criteria such as ease of use, cost-effectiveness, and visual appeal, our team decided to go with Option 3. It scored the highest across all categories, with perfect scores in usability, affordability, and aesthetics. This design is the most user-friendly, which is essential for smooth operation, and it’s also the most economical, helping us stay within budget. Visually, it also fits best with the rest of the bike’s aesthetic, making it both practical and appealing.
Transmitter Hardware
The transmitter consists of an Arduino Uno and an nRF24L01+ wireless module. The interface includes the following inputs:
1 joystick module:
Provides analog X/Y directional input (A0/A1), and a digital press input to toggle fan modes (OFF → COOL → HEAT → OFF).
3 push buttons:
Button 1 (LED): Toggles the vehicle headlight.
Button 2 (Roof): Used to select manual mode during startup; controls the roof servo in manual mode.
Button 3 (Chair): Used to select autonomous mode during startup; controls the chair servo in manual mode.
LCD display (20x4 I2C):
Displays a welcome message, prompts for mode selection, then clears and shows live status information.
Joystick inputs are read via analog pins, and button states are packed into a Signal struct and transmitted to the receiver via nRF24L01+.
Operating Sequence
Program Flowchart
Initial Transmitter Flowchart
The flowchart provides an overview of the system’s intended behavior, breaking down how it processes input, manages states, and handles user interaction.
1.Initialization Phase
At startup, the system initializes all hardware components, including sensors, output devices (like LEDs or displays), and any necessary communication protocols. This ensures that the system begins in a known and stable state.
2.Idle & Monitoring Loop
Once initialized, the system enters an idle loop where it continuously monitors for specific readings, button presses. This forms the backbone of the real-time decision-making process.
3.Condition-Based Branching
Depending on the input received, the system evaluates conditions and branches accordingly. For example, if a button is pressed , the system transitions into the appropriate action or response sequence.
4.Response Execution
When a condition is met, the system executes the corresponding action, such as turning on the motor, or changing LED states.
5.Return to Monitoring
After responding to the input, the system returns to the monitoring loop, allowing it to continuously react to new inputs. This flow enables smooth, responsive operation without needing to restart or reset.
Extra Features (if any):
Beyond the basic controls, the codebase includes several advanced features related to logic implementation, servo management, and bidirectional data flow:
Servo Control (roof sliding)'':
The roof servo rotates 180° over 3 seconds using time-controlled interpolation. This is implemented using millis() instead of delay(), allowing non-blocking execution.
Incremental Chair Rotation with Auto-Reset
The chair servo rotates in 30° increments with each button press. After 5 presses (150° total), the system automatically resets the chair by rotating -150°. A chairState counter and a switch-case logic manage this state machine.
Bidirectional Communication via ACK Payloads
The receiver uses ACK payloads to send live status data (temperature, fan state, chair angle) back to the transmitter for LCD display. This enhances real-time monitoring and avoids redundant signal traffic.
Autonomous Mode Path Logic
In autonomous mode, the vehicle executes a figure-eight path using time-based motor control. The code employs a millis()-based state machine to control timed left and right turns without sensor input.
Recommendations
1. Modular Structure
Refactor repeated logic (e.g., fan mode switching, LED control) into separate functions. This improves code readability and makes future updates easier and less error-prone.
2. Communication Reliability
Add timeout and retry mechanisms to handle cases where wireless signals are lost or delayed. This ensures the system remains safe and responsive even under poor communication conditions.
3. Flexibility in Auto Mode
Allow the user to exit automatic mode at any time (e.g., by holding a button). This provides better control and ensures safety if conditions change during operation.
4. Code Comments and Testing
Include clear comments for key functions and logic, so that all team members (and future users) can understand the code easily. During testing, isolate each function (e.g., steering, fan control) to verify performance before full integration.
These improvements will enhance the code’s maintainability, robustness, and usability. They are highly recommended before final submission.
Electrical/Electronic Design
Overview of the electrical and electronic sub-system
Requirements
Functions
The receiver circuit receives wireless signals and controls output devices accordingly.
The system adjusts motor power and steering direction based on the user's commands.
Additional features such as LED indicator.
The system can drive both a brushed DC motor and a servo for vehicle propulsion and direction.
Objectives
To design an Arduino-based receiver circuit that integrates wireless control, motor actuation, and steering via servo for efficient and safe operation.
Controls a brushed motor via MOSFET switching
Operates a servo motor for steering
Ensures safe current handling
Maintains efficient system performance
Follows a clean and organized component layout
Implements well-structured, readable code
Includes a status indicator LED for system feedback
Constraints
All components must be powered safely and reliably using a battery pack. Voltage regulation and common grounding must be ensured.
The system must be compatible with the transmitter-side control scheme, and all functions should respond accurately to user input.
Arduino code should be modular, readable, and commented to allow for future debugging and enhancement.
The design must account for limited space, resources, and heat dissipation within the prototype.
Electrical connections (e.g., solder joints, breadboards) should be robust and vibration-resistant for real-world racing conditions.
The system must integrate the NRF24L01 module for wireless communication between the controller and receiver.
The electrical system must operate using a 9V power supply to stay within safety and component limits.
Evaluation
Design
Safe
Ease of Connection
Put the breadboard on the front
No
Difficult
Put the breadboard on the back
Yes
Easy
In our electrical system design, the placement of the breadboard was evaluated based on two constraints: safety and ease of connection. Mounting the breadboard on the front was found to be unsafe and made wiring more difficult due to exposure and limited space. In contrast, placing it on the back of the chassis offered better protection during movement and collisions, and also allowed easier wiring and component access. Therefore, the back-mounted design was chosen as it better meets both the safety and usability constraints.
The Design
1.Drive and Steering Circuit:
Purpose
• To provide smooth and adjustable motor speed control suitable for the eCycle prototype.
Components
• Drive motor
• MOSFET (for switching)
• PWM signal from the microcontroller
• Battery pack (power source)
• Flyback diode (across motor terminals)
Functions
• The drive motor is powered and controlled using a combination of a MOSFET and a PWM signal from the microcontroller.
• The motor receives power from a battery pack, and its speed is regulated by modulating the duty cycle of the PWM output.
• A flyback diode protects the circuit from voltage spikes during sudden shutdowns.
2.Fan Circuit:
Purpose
Receiver Circuit
• Provides passive or active airflow to assist in general cooling or heat dissipation.
Components
• Fan Motor
• MOSFET (for switching and speed control)
• Resistors or PWM control system
• Toggle Switches (if using manual resistor-based control)
Function
• Fan speed is controlled via PWM for dynamic speed adjustment.
• Alternatively, fan speed can be set using three toggle switches, each tied to different resistors for low/medium/high speeds (older method).
Design Notes
PWM + MOSFET control is preferred for efficiency and precision.
Ensure only one switch is active at a time in the resistor-switch method to prevent overload.
Can run continuously, or in coordination with the Peltier system for improved HVAC performance.
3.Peltier Circuit:
Purpose
• Provides active cooling for the system using a Peltier module, which transfers heat away from components.
ComponentsPeltier Circuit
• Peltier Module (thermoelectric cooler)
• MOSFET (for switching power)
• Flyback Diode (to protect from reverse voltage spikes)
• LED Indicators (to show cooling status)
• Microcontroller (Arduino) for PWM control
• Sensors or wireless input for control triggers
Function
• The Peltier module is activated via PWM from the microcontroller to adjust the cooling intensity.
• Can be triggered automatically based on sensor data or manually via wireless command.
Design Notes
• Mounted on a heat sink or plate for effective heat transfer.
• Flyback diode prevents back EMF damage during rapid switching.
• Status LED gives visual feedback for troubleshooting or user confirmation.
4.Boards Mounting:
All circuits were first built and tested on a breadboard to make sure they worked.
After testing, we moved them onto a permanent board (protoboard) and attached it securely inside the vehicle using screws, standoffs, or tape.
We kept all wires neat and labeled to make it easier to fix problems and help team members understand the setup.
5.Autonomous Program:
The autonomous system is designed to operate based on sensor feedback and following programmed rules.
The electronic team focused on making the wiring robust to prevent communication loss.
The NRF24L01 module allows remote override but is not required for autonomous decisions.
The HVAC system is controlled automatically based on temperature input, activating the fan and Peltier module as needed.
All signals are processed through the Arduino, which handles motor, steering, and cooling actions without user input.
Extra Features (if any):
Our design includes additional features to enhance functionality and user interaction.
A push-button is used to control onboard lighting, allowing the user to turn the LEDs on or off manually.
In addition, the roof of the vehicle is designed to open using a servo motor, providing an interactive mechanical element.
In addition, both the roof and seat are motorized and can adjust automatically.
These features are fully integrated with the electrical system and can be operated either manually or as part of the programmed routine.
Conclusion:
In our electrical system design, the placement of the breadboard was evaluated based on two constraints: safety and ease of connection. Mounting the breadboard on the front was found to be unsafe and made wiring more difficult due to exposure and limited space. In contrast, placing it on the back of the chassis offered better protection during movement and collisions, and also allowed easier wiring and component access. Therefore, the back-mounted design was chosen as it better meets both the safety and usability constraints.
Mechanical Design
The Mechanical sub-team should design, model, fabricate and test the mechanical components of the prototype using SolidWorks and other tools, considering the following constraints and rubrics outlined in the course syllabus and project brief.
The three members in this sub-team are responsible for the full development and integration of key mechanical subsystems of the electric cycle.
Requirements
Functions
The mechanical subsystem must perform the following core functions to support the safety, efficiency, and comfortability of the operation of the electric cycle prototype.
Absorb shocks and road vibrations through a front suspension system to enhance rider comfort and reduce fatigue during operation on uneven terrain.
Transfer power from the motor to the drive wheels efficiently using a reliable drivetrain system that supports both manual and electric modes of propulsion.
Provide precise and responsive directional control via a mechanical steering mechanism that enables the rider to maneuver the vehicle safely at low to moderate speeds.
Ensure structural stability and rider safety under various operational loads, including braking, acceleration, turning, and uneven surfaces.
Facilitate rider customization and usability, including features like an adjustable seat mechanism that accommodates different body sizes and riding preferences.
Enable efficient assembly, maintenance, and testing, by incorporating modular, lightweight, and accessible mechanical designs compatible with available fabrication tools.
Objectives
Ensure Structural Integrity
The mechanical components must withstand all expected static and dynamic loads during normal and high-stress operation, ensuring rider safety and system reliability.
Maximize Reliability and Durability
• All mechanisms (e.g., suspension, drivetrain, steering) should operate consistently over time without failure under real-world use conditions.
Minimize System Weight
• Use structurally efficient and lightweight designs to reduce overall system mass, thereby improving energy efficiency and motor performance.
Enable Ease of Assembly and Maintenance
• Design all components to be modular, accessible, and easily removable for testing, replacement, and adjustments during the development cycle.
Ensure Safe Integration with Other Subsystems
• Provide robust and compatible mounting interfaces for the electrical, thermal, and control subsystems, ensuring system-wide safety and alignment.
Enhance User Comfort and Ergonomics
• Mechanical systems such as the adjustable seat and suspension must contribute to a comfortable and customizable riding experience.
Constraints
Must fit within the provided team prototype design space.
All components must be manufacturable using 3D printer, laser cutter, hand tools.
Must withstand expected loads during operation (including racing conditions).
Must support integration with electrical and structural sub-systems.
Assembly must be completed by Week 6 to allow for full prototype integration and testing.
The Design
The Mechanical Team will be responsible for brainstorming, sketching, CAD modeling, and fabricating the following components:
1. Front Suspension
Front Suspension
Materials
• Constructed using sheet metal and plastic components, chosen for strength, lightness, and cost-effectiveness.
Function
• Absorbs road vibrations and minimizes shock transfer to the rider, improving comfort on uneven terrain
Design Features
• Flexible joints or linkages for vertical movement.
• Integrated mounting brackets with the wheel holder for easy assembly.
Use Cases
• Enhances ride comfort.
• Improves shock absorption for better rider endurance and stability.
Front Suspension PartFront Suspension Weighted Matrix
Selected Final Design:
After comparing multiple design alternatives using weighted matrices, the team has selected the following final configuration for implementation:
Front Suspension: Option B, featuring a flexible plastic arm with integrated rubber damping, due to its superior manufacturability, cost-efficiency, and lightweight properties (22/25 score).
Wheel inner part
2.Drive Train
Chain and gear system supporting both manual and electric propulsion.
Materials
• Composed of metal gears and chain components modeled in SolidWorks for precise fitting.
Function
• Transfers pedal or motor power to the rear wheel using a gear and chain system.
Design Features
• Gear system for smooth torque transfer.
• Chain drive suitable for high torque but slightly noisier.
Wheel
• Optionally integrates a differential for dual-wheel drive.
Use Cases
• Ideal for motor-assisted cycling.
• Supports efficient energy transfer in both manual and electric modes.
Steering
3.Steering System
Materials
• Primarily metal rods and joints.
• Ergonomically designed handlebar (possibly rubberized or cushioned).
Function
• Provides manual directional control using a direct mechanical linkage.
Design Features
• Simple rod system connects the handlebar to the front steering arm.
• No electronic or assisted components, reducing complexity.
Use Cases
• Suitable for precise and responsive steering.
• Works well in low-speed environments like campuses or urban trails.
Steering ConnectorSteering System Weighted Matrix
Direct Mechanical Linkage(Option A) receives a perfect score (25/25), offering excellent responsiveness, ease of manufacturing, minimal complexity, and full reliability. It is ideal for a student-built, low-speed electric vehicle like an e-tricycle.
Cable-Pulley Steering(Option B) may reduce space constraints but introduces tension-related failures and steering inaccuracy.
Servo Motor Steering(Option C) adds weight, complexity, and power consumption while requiring software and electronics integration beyond the scope of basic mechanical design.
4.Wheel Holder (E-Tricycle Specific)
Reinforced metal bracket with vibration dampers for stability.
Materials
Wheel Holder
• Likely metal bracket with reinforcement and possibly rubber dampers for vibration control.
Function
• Acts as a mounting bracket for the auxiliary wheel and connects it to the main bike structure.
Design Features
• Provides positional stability and load transfer to the frame.
• Designed to withstand vibrations and stress.
Use Cases
• Useful for low-speed stability, parking, and balance support, especially for beginners or differently abled riders.
Adjustable Chair
Extra Feature:
Adjustable Chair
Sliding track system with locking mechanisms to accommodate different rider sizes.
Materials
• Made from plastic or cushioned metal, ensuring comfort and durability.
Function
• Allows forward-backward adjustment to accommodate different rider sizes.
Design Features
• Mounted on slots or tracks integrated into the frame for easy positioning.
• Secured with locking mechanisms.
Use Cases
• Enhances ergonomics for pedalling and steering.
• Accommodates users of varying heights and comfort preferences.
This configuration balances simplicity, safety, and user comfort, and it has been selected as the most practical solution for the project’s scope and constraints.
Chair back supportAdjustable Chair drawing
Adjustable Chair Moving part
Front Wheel:
Front Wheel Weighted Matrix
The Single Front Wheel has a significantly higher score (23/25) because it is simple, lightweight, and easier to manufacture. While it is slightly less stable at low speeds than the dual front wheels, it is more maneuverable and easier to meet the project steering requirements.
1. Main Rear Wheel (Center)
Back WheelThis is the primary drive wheel. It’s connected to the drivetrain (possibly motorized or gear-driven).
It looks like it has a belt or chain sprocket in the center, suggesting power is being transferred to it.
2. Support Arms + Small Side Wheels (Left & Right)
These are stabilizer wheels — like training wheels.
They’re mounted on angled or straight arms extending outward from the rear axle.
Their purpose is to prevent the vehicle from tipping left or right.
The arms are rigid and likely bolted or fixed in place for strength.
These serve as mounting bases for the support arms and possibly house the rear axle shaft.
They provide a strong connection point for both the main wheel and stabilizers.
Structure Support
Structure Support
Acts as a mechanical and structural connector
Features a cylindrical body for mounting or insertion
Includes a cross-shaped locking end for secure engagement
Designed to interface with frames or housings
Commonly used in wheel assemblies
Provides rotational alignment
Ensures structural integrity at connection points
Evaluation:
The mechanical subsystem successfully meets the majority of the project’s functional and design objectives.
The front suspension system utilizes a flexible plastic arm with integrated rubber damping, which provides basic shock absorption. This solution is lightweight, easy to fabricate using available tools, and appropriate for low-speed, urban terrain.
The drive train employs a chain and gear system that ensures reliable torque transfer for both manual and electric modes. The system is durable and compatible with standard manufacturing processes.
The steering system uses a direct mechanical linkage that offers precise and responsive control. This simple design reduces complexity and integrates effectively with the single front-wheel layout.
The wheel holder and adjustable seat contribute to stability and comfort. They provide customization for different rider sizes and improve usability.
Overall, the subsystem design demonstrates a strong balance of safety, manufacturability, and functionality, while remaining within the project’s constraints (fabrication tools, design space, and timeline). The components align well with the needs of a student-built electric cycle intended for low-speed, urban use.
Recommendations:
It is recommended that the mechanical subsystem, as currently designed, be adopted for prototype construction and testing.
The selected front suspension (Option B) offers the best trade-off between manufacturability, weight, cost, and performance, and should be fabricated as designed.
The chain and gear drivetrain should be implemented for its proven reliability and compatibility with both manual and electric propulsion systems.
The direct mechanical steering linkage should be retained to ensure safe and responsive control without unnecessary complexity.
The single front wheel configuration is recommended for its simplicity, lightness, and ease of integration with the steering system.
The wheel holder and adjustable seat designs should be fabricated as specified, to support rider stability and ergonomic adaptability.
Further work is encouraged in the areas of prototyping and physical testing, particularly to validate suspension performance under different load conditions and to ensure the structural integrity of fabricated components during real-world use.
Structural Design
Overview of the structural sub-system
As the structural sub-team, our primary role is to design a rigid, safe, and lightweight frame that can support the electric bike’s components, protect the rider from weather, and ensure integration with other sub-systems. The requirements are categorized as Functions, Objectives, and Constraints as follows:
Requirements
Functions
Support the weight of the rider, motor, battery, and full frame structure under static and dynamic loads, including road crater impacts or sudden stops.
Provide secure mounting points for sub-systems such as the mechanical, and electrical enclosures.
Enable easy and tool-free assembly and disassembly of the weather enclosure (e.g., panels and supports), ensuring maintainability and adaptability during testing and final showcase.
Objectives
Minimize structural weight to maintain the bike’s overall efficiency, targeting an added mass of no more than 4.0 kg.
Maximize frontal visibility for the rider while ensuring enough coverage from rain, aiming for at least 80% unobstructed forward view.
Ensure smooth wheel operation by minimizing friction or misalignment between the wheel and adjacent structural elements, so the motor can drive the bike without mechanical resistance.
Maintain bearing seat precision to keep the axle and wheel properly aligned.
Prevent any interference between the wheel guard (fender or housing) and the tire during operation by ensuring a minimum clearance of 5 mm and limiting guard deflection to less than 3 mm under normal loads.
Design all components to be manufacturable using UBC Mechanical lab tools, including 3D printing, laser cut, vacuum forming, and bending equipment.
Constraints
The structure must fit within the overall bike envelope: maximum width 15.0cm, length 30.0cm, and height 20.0cm.
The entire prototype must follow a 1:5 scale relative to a real electric commuter bicycle.
The weather protection system must block at least 85% of frontal rain impact under simulated wind speeds of up to 35 km/h and 30° angle of incidence.
All materials and structural components must comply with UBC safety guidelines — no sharp edges, flammable plastics, or untested adhesives are allowed.
The canopy and weather panels must be removable within 5 minutes without the use of tools, to meet serviceability and competition constraints.
The Design
Option 1: Lightweight and Aesthetic Design
Tricycle Structure Drawing Isometric View
The first design option prioritized a lightweight structure, a sleek and visually appealing appearance, and enhanced seating comfort. These features made it an attractive concept, especially from a design and user-experience perspective. However, the complexity of the design significantly increased the difficulty of manual fabrication. Given the limitations of available materials and tools, it was ultimately not feasible to complete this design using the current resources. This revealed a key limitation in the approach: while innovation and creativity were strong, the practicality of execution was lacking within the scope of the project.
Option 2: Practical and Weather-Protected Design
Tricycle Structure Drawing Side View
The second design focused more on practicality and feasibility. It included a sliding canopy that provided protection from wind and rain, making it more suitable for outdoor conditions. The structure was easier to build using existing materials and techniques, which made this option more realistic and achievable. However, this came at the expense of aesthetics and structural elegance—the design was bulkier and less refined compared to Option 1. Nonetheless, Option 2 successfully demonstrated a balanced approach between function and ease of construction
Comparing both options emphasized an important engineering lesson: there is often a trade-off between ideal design and practical execution. While Option 1 pushed the boundaries of design innovation, Option 2 delivered a functional and complete model within the project's constraints. Future development could explore combining the aesthetic strengths of Option 1 with the practical advantages of Option 2, aiming for a more refined yet manufacturable design.
1.Enclosure
Purpose:
EnclosureProvides weather protection from rain, wind, and debris.
Enhances rider comfort and usability in all seasons.
Supports the project goal of promoting year-round cycling at UBCO.
Key Functions:
Integrates with the structural frame without affecting wheel movement or steering.
Design Features:
Frontal panel is transparent and slightly curved to improve aerodynamics and visibility.
Side panels include doors or windows for easy access and ventilation.
Materials:
Panels made from acrylic plastic for transparency and rain resistance.
Supporting frame made from 3D-printed PLA parts.
Enclosure Drawing
Designed to be compatible with laser cutting, and bending tools in the UBC Engineering Design lab.
Door
2.Doors
Type: The tricycle features a door integrated into the side panel of the canopy.
Mechanism: embedded hinges allow the doors to open and close smoothly without requiring extra space to swing out. This is especially useful in tight urban or bike lane environments.
Accessibility: Doors are sized to allow comfortable entry/exit for most users. Their position is aligned with the seat height for ergonomic access.
Tool-Free Removal: The door modules are detachable for maintenance or showcase setup
Design Considerations:
Transparent or semi-transparent panels were used to preserve lateral visibility.
Edges are filleted or rubber-lined to avoid sharp corners and ensure compliance with UBC safety standards.
3.Natural Ventilation
Vent Openings: Small cutouts or vents are positioned at the front and rear of the enclosure. These are angled to allow airflow without letting in rain.
Passive Cooling: The ventilation design relies on cross-ventilation, where air enters from front inlets and exits through rear vents, creating a cooling flow.
Material Gaps: Tolerances between panels and the frame were intentionally kept small but breathable, preventing heat buildup during long rides.
Purpose:
Prevents fogging of panels during cool/rainy weather.
4.Structure Support
Structure Support
Function: This part is used to connect the mechanical component (e.g., a wheel shaft or motor) to the structural frame. Explanation:
The cross-shaped end with recesses fits into a corresponding socket or bracket.
The square slots may support locking features like pins, bolts, or even sensors.
The cylindrical shape makes it suitable for rotational or axial loads, likely related to the wheel system. Use Case: Used to support the wheel and connect it to the frame. This allows for rotation while remaining structurally supported.
Structure Joint
5.Structure Joint
Function: This is a structure joint used to connect two structural parts together securely. Explanation:
The interlocking stepped notches ensure a tight, aligned fit, helping to extend the length of a structural member.
This design increases rigidity and strength at the joint.
Ideal for applications where strong, extended support is needed (e.g., a frame or chassis). Use Case: Used to connect strong structure parts together, such as the main body of an electric tricycle or cart frame
Extra Features (if any):
Sliding Window
Sliding Window: A small sliding panel within the front or side canopy allows the rider to control airflow without opening the entire door. This provides ventilation adjustability in real time
Convertible Roof:
The roof section is foldable, allowing the user to switch between open-air mode on sunny days and fully enclosed mode during rain.
Lightweight and attached using snap-fit joints or magnetic latches for tool-free conversion.
This increases usability and comfort while also demonstrating design adaptability in different environmental conditions.
IMPORTANT! Put your code in a Microsoft Word document and protect the document with a password! I shall ask for the password when I grade your code.
File:Transmitter Code Protected.docx
The environmental data presented — including carbon footprint, energy use, and material emissions — were generated using SolidWorks Sustainability analysis tools. These tools assess lifecycle impact based on modeled materials, assumed part geometries, and a standard 10-year usage period.
Although our project is a scaled prototype, we extrapolated the environmental impact data to simulate a full-scale bicycle. This approach was used to visualize what the total impact would be if the current model were manufactured in real size using the selected materials and battery specifications.
Due to limitations in exact scaling and the estimation nature of SolidWorks data, the numbers may not reflect real-world mass-manufactured data precisely. However, they provide a reliable relative comparison between our student-built model and commercial EV bikes, which helps highlight the sustainability benefits of our lighter structure and simplified assembly.
References
Add your reference list here.
About Us
Sub-teams:
Coding
Abdulelah AlsanieFirst name family name: Abdulelah Alsanie
Position: Group Leader, Coding Sub-Team
I am Abdulelah Alsanie and I was primarily responsible for the core programming of the Arduino-based wireless control system, with a focus on handling wireless input, motor control, and steering logic. I designed and implemented the modular code structure, which greatly improved debugging efficiency and code maintainability.
I also contributed to the overall architecture of the transmitter controller, ensuring optimal user interaction design and reliable input handling.
Additionally, I collaborated closely on the autonomous mode implementation, particularly the figure-eight path execution logic, using non-blocking millis()-based state machines for timed turns and transitions. My role as team lead included coordinating development efforts and ensuring that the communication and integration across sub-systems (e.g., motor, servo, and RF) remained robust and synchronized throughout the project.
Gengle WangFirst name family name: Gengle Wang
Position: Coding Sub-Team
I am Gengle Wang and my focus in this project was on implementing and refining the autonomous control features, including the figure-eight navigation logic, as well as structuring and decoding the Signal data packets used in communication between transmitter and receiver.
I played a key role in developing and testing the control routines for auxiliary systems:
Fan control (OFF → COOL → HEAT) via Peltier modules
LED toggle logic
Chair servo rotation with auto-reset feature
I also contributed to writing the status feedback system using ACK payloads, which enabled the transmitter LCD to display real-time temperature, fan state, and chair angle. Additionally, I supported documentation efforts by contributing to the coding sub-team’s wiki, outlining code structure, signal definitions, and testing protocols.
Electrical/Electronic
First name family name: Bhujong MalaithamBhujong MalaithamPosition: Electrical Sub-Team
I am Bhujong Malaitham and i participated in building the essential electrical functions, including steering, motor throttle, Peltier module integration, and LED lighting systems.
I took the lead in assembling the controller circuit, ensuring proper wiring, grounding, and physical layout on both breadboard and permanent board.
Additionally, I was responsible for integrating the extra mechanical features, such as the roof and seat motor systems, into the electrical circuit, making sure they worked reliably with the Arduino and power components.
I contributed to maintaining a safe and organized hardware layout, especially during the transfer from breadboard to protoboard, and ensured the circuit was secured inside the chassis following the final design decision.
Bolin PanFirst name family name: Bolin Pan
Position: Electrical Sub-Team
I am Bolin pan and i worked on implementing and wiring the basic electrical functions, including steering via servo motor, motor throttle using PWM and MOSFET switching, and the Peltier cooling system.
I contributed to ensuring proper power delivery, flyback diode protection, and PWM-based fan speed control, supporting overall system performance and safety.
I also helped develop content for the electrical sub-team’s wiki, documenting the design of the drive, fan, and cooling circuits as well as component selection and layout considerations.
Yan ChenFirst name family name: Yan Chen Position: Electrical Sub-Team
I am Yan Chen and i focused on the implementation of core electrical functions, including steering, motor control, and Peltier module integration, ensuring proper operation via Arduino and MOSFETs.
My primary contribution included designing and documenting digital circuit diagrams used in the project, including representations of the drive and fan circuits, Peltier system, and PWM/MOSFET control logic.
I supported the electrical testing process and assisted in translating physical hardware into clear schematics for debugging and communication with the rest of the team.
Mechanical
Ivan LiFirst name family name: Ivan Li
Position: Mechanical Sub-Team
I am Ivan Li i was primarily responsible for the design and layout of core mechanical systems, including the front suspension and drivetrain system.
I created the initial configuration and design plan, ensuring that all mechanical components adhered to project constraints, such as weight, space, tool limitations, and safety requirements.
My focus was to balance structural stability, performance, and manufacturability, leading to the selection of the flexible arm suspension (Option B) and the chain and gear drivetrain compatible with both manual and electric propulsion modes.
I ensured that all subsystem designs supported safe integration with electrical and thermal components, and contributed to the overall structural planning of the prototype.
Haoquan WangFirst name family name: Haoquan Wang
Position: Mechanical Sub-Team
I am Haoquan Wang and i led the SolidWorks modeling for most key mechanical components, particularly the drivetrain, mounting brackets, and wheel holder structures.
My responsibilities included creating precise and manufacturable CAD models, ensuring dimensional compatibilityacross interconnected parts, and validating that all assemblies supported the vehicle’s structural and operational needs.
I also performed design reviews for fit and functionality, making sure that the wheel assembly, steering linkages, and support arms worked seamlessly together.
My models contributed directly to fabrication and testing, enabling the mechanical system to move from design to physical integration efficiently.
First name family name: Chi ZhangChi ZhangPosition: Mechanical Sub-Team
I am Zhang Chi and I contributed to the mechanical sub-team’s wiki documentation, helping to clearly outline the project objectives, constraints, and key design choices.
I worked on the design of extra features, including the adjustable seat mechanism, ensuring ergonomic adaptability for different users. I also contributed input on wheel holder and stabilizer designs to support user comfort and safety.
Additionally, I played a key role in preparing the oral presentation content for our sub-team, effectively communicating our design process, evaluation matrices (e.g., for suspension and steering), and final decisions to the class and instructors.
Structural
Zihan LiuFirst name family name: Zihan Liu
Position: Structural Sub-Team
I am Zihan Liu and i was responsible for designing the base structural frame of the electric tricycle prototype. This included ensuring the frame could withstand both static and dynamic loads, and that it adhered to the dimensional and material constraints outlined in the project brief.
I focused on the secure and vibration-resistant mounting of electrical components, ensuring that motor, battery, and control modules were safely and rigidly integrated into the structural base without compromising performance.
My work also ensured clearance, structural stability, and compatibility with mechanical and electrical sub-systems, especially in relation to wheel alignment and smooth drivetrain operation.
Additionally, I helped refine the removable canopy design by aligning the structural base with tool-free disassemblyrequirements for fast maintenance and competition compliance.
First name family name: Nalan WangNalan WangPosition: Structural Sub-Team
I am Nalan Wang and i focused on integrating structural supports for critical mechanical interfaces, including the adjustable seat, wheel holder, and roof system. My design work emphasized rigidity, modularity, and precision in alignment.
I also contributed to the design and fit of key structural elements such as structure joints and structure supports, enabling a secure connection between load-bearing parts using interlocking, stepped, or socket features.
During the final assembly phase, I participated in aligning all structural subsystems with the weather enclosure, ensuring the proper placement of the doors, ventilation features, and convertible roof elements.
My work supported the overall goal of ensuring weather protection, user comfort, and seamless integration between mechanical and structural systems, while meeting the fabrication constraints using UBC lab tools.
Documentation
Manan AroraFirst name family name: Manan Arora
Position: Documentation Sub-Team
I am Manan Arora and i contributed extensively to both the draft and final wiki, with a focus on content structuring, technical writing, and visual organization. I developed the following sections:
Draft Wiki:
Introduction: Wrote an overview of the project scope, goals, and sub-team responsibilities.
Team Requirements and Sub-Team Requirements: Compiled and edited functional, objective-based, and constraint-related requirements from each sub-team.
Generating Design Alternatives & Evaluation (4%): Summarized the design ideation process, decision matrices, and trade-offs that led to final selections across all subsystems.
Final Wiki:
Formatting: Ensured clean structure, heading hierarchy, figure placement, and cross-referencing across the document.
Conclusion: Drafted a final summary evaluating project success, system integration, and lessons learned.
Appendices:
Design descriptions
Sub-system performance results
Recommendations for future improvements
Integrated part drawings, schematics, and flow charts
Run WechapinanFirst name family name: Run Wechapinan
Position: Documentation Sub-Team
I am Run Wechapinan and i was responsible for content creation and media integration across all required project deliverables. I supported both the draft and final wiki, and took the lead in preparing:
Oral Presentation Slides:
Designed the structure and flow of the presentation.
Provided visuals, tables, animations, and concise text summaries for each sub-team.
Integrated sustainability content, including energy efficiency, material use, and social/environmental considerations.
Basic Features:
Uploaded and maintained conference web pages.
Helped compile renders and figures showcasing the prototype development.
Final Wiki Appendices:
Created schematics and subsystem flowcharts for the TX/RX programming, electrical wiring, mechanical assemblies, and ventilation design.
Documented extra features (e.g., lighting, convertible roof) and ensured alignment with relevant figures and tables.
