

WRO 2023
Repository of Team FE0901 participating in WRO 2023 Future Engineers
- Size
- 81.3 × 114.3 mm
- Copper layers
- 2
- Thickness
- 1.6 mm
- Parts
- 32
- Nets
- 55
- Pads
- 240
- Tracks, vias
- 331, 35
- Pours
- 139
- Routed
- Yes
- KiCad
- KiCad 7 (file 20221018)
- Created
- 24 Aug 2023
- Updated
- 6 Nov 2023
Overview
WRO 2023 is an open-source printed circuit board by PorridgePi, from the PorridgePi/WRO-FE-2023 repository on GitHub. It is a 2-layer board of 81.3 × 114.3 mm with 32 parts on 55 nets, routed with 331 tracks and 35 vias.
It is built around the AT8236 and XT60-M. Its parts include 24 connectors and 3 ICs. It belongs with the RP2040 boards of this library.
Main components
2README
README.mdWRO 2023 Future Engineers
Team Information
Team ID: FE0901
Team Name: raffles institution team 3
Team Members
Overview
Welcome to the GitHub repository for Team FE0901 participating in WRO 2023. In this competition, we are building an autonomous robotic vehicle capable of completing 2 different challenges. This README provides a simple overview. If you wish to delve deeper into our engineering process, please check out our Engineering Journal or download it as PDF.
Demo
A demonstration video of our robot in action can be found on YouTube (or in the video.md file): https://youtu.be/pbWbQL5pThI
Key Timestamps
Open Challenge
Obstacle Challenge:
- Run 1: 03:40
Usage
For Code, Using Visual Studio Code:
- Clone this repository:
git clone https://github.com/PorridgePi/WRO-FE-2023 - Change directory:
cd ./WRO-FE-2023/ - Initialise Git submodule(s):
git submodule update --init --recursive - Open the repository in VSCode:
code ./ - Install the PlatformIO plugin
- Select the appropriate PlatformIO Environment
- Use the PlatformIO plugin to compile and upload code onto the microcontroller (Raspberry PI Pico)
For Camera (OpenMV): Using the OpenMV IDE
- Open the camera code (
src/omv_main.py) in OpenMV IDE - Upload code onto OpenMV by:
- Select
ToolsMenu - Click
Save open script onto OpenMV Cam (as main.py)
- Select
For Documentation, Using Obsidian:
- Clone this repository:
git clone https://github.com/PorridgePi/WRO-FE-2023 - Open the cloned directory as a Vault
For PCB, Using KiCAD:
- Clone this repository:
git clone https://github.com/PorridgePi/WRO-FE-2023 - Open the file
schemes/WRO_2023/WRO_2023.kicad_pro
Repository Content
.github/workflows/platformio-ci.yml: GitHub Actions CI workflow for PlatformIO (Documentation).vscode/: Folder containing VSCode workspace settingsextensions.json: List of recommended and unwanted extensions (Documentation)
models/: 3D modelsothers/: Other filesschemes/: Schematic diagram and PCBWRO_2023: PCB files that can be opened in KiCAD
scripts/: Scripts for PlatformIOci.sh: Script for CI test
src/: Main codelib/: Libraries for components- Notably:
lib/private/Common.h: Shared code betweenopen.cppandobstacle.cpplib/Mecha_QMC5883L: Forked version of library for the QMC5883L magnetometer
- Notably:
test/: Test codemain.cpp: Placeholder fileobstacle.cpp: Code for the Obstacle Challengeopen.cpp: Code for the Open Challenge
t-photos: Team photov-photos: Photos of the vehicle (from many different angles!)video: Contains video.md with the link to the video of the driving demonstration.clang-format: ClangFormat code style file - to format code in VSCode.gitignore: gitignore file (Documentation)platformio.ini: PlatformIO configuration file (Documentation)README.md: This file
Reminders before Running
- Calibrate compass(es)
- Ensure steering mechanism is tightened
- Clean wheels to ensure grip
Hardware used
- Motor: 1x GM25-12CPR
- Servo: 1x MG996R
- Motor Driver: 1x AT8236
- Microcontroller: 1x Raspberry Pi Pico
- Voltage Regulator (5V): 1x CKCS-BK-2
- LiDAR: 5x TF-Luna
- Camera: 1x OpenMV M7
- Compass: 1x GY-273 and 1x GY-271
- Battery: 1x Turnigy nano-tech 1300mAh 3S 45~90C Lipo Pack
Continual Integration (CI) Testing
We have a simple CI testing setup with GitHub Actions, using the scripts/ci.sh script to automate the process of building our code for all different environments in platformio.ini. It checks for build success and ensures that the code can be successfully compiled.
CI is a critical aspect of our development process. It allows us to detect issues and errors in our codebase as soon as they occur. This early detection is invaluable in preventing the accumulation of errors and simplifying debugging.
Besides, our project involves multiple team members working collaboratively. CI ensures that all code changes made by different team members do not introduce regressions or break existing functionality.
To check the status of our CI, go to the Actions tab and view the workflow runs. If everything is going well, you should be only seeing green ticks. However, if you are seeing red crosses, something is up, but don't fret, we are definitely working hard to iron out the bugs!
(or alternatively, just look at the badge below for the CI status)
Parts
32| Qty | Value | Footprint | References |
|---|---|---|---|
| 9 | Conn_01x02_Pin | Connector_JST:JST_XH_B2B-XH-A_1x02_P2.50mm_Vertical | J12, J13, J17, J18, J19, J20, J21, J23, J24 |
| 2 | Conn_01x04_Pin | Connector_JST:JST_XH_B4B-XH-A_1x04_P2.50mm_Vertical | J14, J16 |
| 2 | IN1 | Jumper:SolderJumper-3_P2.0mm_Open_TrianglePad1.0x1.5mm | JP1, JP2 |
| 1 | AT8236 | Personal Symbols:AT8236 | U3 |
| 1 | CKCS_BUCK02+ | Personal Symbols:CKCS_BUCK02+ | U2 |
| 1 | Conn_01x03_Pin | Connector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_Vertical | J15 |
| 1 | MG996R Servo | Connector_PinHeader_2.54mm:PinHeader_1x03_P2.54mm_Vertical | J1 |
| 1 | Motor 1 | Connector_PinHeader_2.54mm:PinHeader_1x06_P2.54mm_Vertical | J2 |
| 1 | Motor 2 | Connector_PinHeader_2.54mm:PinHeader_1x06_P2.54mm_Vertical | J3 |
| 1 | OUT1 | Jumper:SolderJumper-3_P2.0mm_Open_TrianglePad1.0x1.5mm | JP3 |
| 1 | OUT2 | Jumper:SolderJumper-3_P2.0mm_Open_TrianglePad1.0x1.5mm | JP4 |
| 1 | Pico | MCU_RaspberryPi_and_Boards:RPi_Pico_SMD_TH | U1 |
| 1 | SolderJumper_3_Bridged12 | Jumper:SolderJumper-3_P1.3mm_Bridged12_RoundedPad1.0x1.5mm | JP5 |
| 1 | TF-Luna 1 | Connector_JST:JST_XH_B6B-XH-A_1x06_P2.50mm_Vertical | J4 |
| 1 | TF-Luna 2 | Connector_JST:JST_XH_B6B-XH-A_1x06_P2.50mm_Vertical | J5 |
| 1 | TF-Luna 3 | Connector_JST:JST_XH_B6B-XH-A_1x06_P2.50mm_Vertical | J6 |
| 1 | TF-Luna 4 | Connector_JST:JST_XH_B6B-XH-A_1x06_P2.50mm_Vertical | J7 |
| 1 | TF-Luna 5 | Connector_JST:JST_XH_B6B-XH-A_1x06_P2.50mm_Vertical | J8 |
| 1 | TF-Luna 6 | Connector_JST:JST_XH_B6B-XH-A_1x06_P2.50mm_Vertical | J9 |
| 1 | TF-Luna 7 | Connector_JST:JST_XH_B6B-XH-A_1x06_P2.50mm_Vertical | J10 |
| 1 | TF-Luna 8 | Connector_JST:JST_XH_B6B-XH-A_1x06_P2.50mm_Vertical | J11 |
| 1 | XT60-M | XT60:AMASS_XT60-M | J22 |
Similar boards
- 2 layers40 × 61 mm

- 4 layers100 × 100 mm

- 4 layers100.1 × 60.2 mm

Hades
pms67/HadesFCS
Complete flight control system designed from scratch. Hardware designed with KiCad.
215 parts1kBSD-3-Clause - 2 layers120 × 100 mm

Root
GonzaCerv/noah-hardware
This repo contains all the hardware description for the Noah project. Here lies 3D models, electronics PCB and Firmware software of the robot.
127 parts28MIT - 2 layers110 × 110 mm

- 2 layers

Placa alimentacao
edromufu/edromufu
Repositório da EDROM-UFU destinado ao desenvolvimento do projeto humanoide para participação nas competições LARC e ROBOCUP.
26 parts9MIT - 2 layers107.9 × 63.2 mm

- 2 layers99.5 × 67 mm

Controller Board
kairobyte/bipedal_self_balance
A bipedal self balancing robot with 2DOF in each leg. Built from scratch.
23 parts7MIT
Questions
How big is the WRO 2023 PCB?
It measures 81.3 × 114.3 mm and has 2 copper layers, 1.6 mm thick.
What parts does the WRO 2023 use?
32 parts, built around the AT8236 and XT60-M. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.
Where can I download the WRO 2023 KiCad files?
From the PorridgePi/WRO-FE-2023 repository on GitHub, at the commit this page was made from: the board is schemes/WRO_2023/WRO_2023.kicad_pcb and its schematic schemes/WRO_2023/WRO_2023.kicad_sch. PCBKit opens the board in the browser, with nothing to install.
Can I use the WRO 2023 design in my own project?
Its repository states no licence, so its author keeps all rights: ask PorridgePi before reusing the design.
