Notebook 2026 T-Vex team Summary part One : “Introduction” 1.The Team 2.Diagram Caption 3.WEEKS 1 to 3 part two : ContenT Weeks 4 to 12 part three : conclusion Week 13 Code Strategy Checklist extra Pictures Part ONE : INTRODUCTION The team Louis VERTICELLI: Mechanic Samuel LABIGNETTE: Mechanic Ugo SOFIA: Mechanic Arthur STRIMBU-LEE: Coder Ode NITOUMBI: Coder Martin Krembel : Mentor : Metal bar : Chain : multidirectional wheel : screws :Piston : Direction of the movement : Gear Diagram Caption : Vex push back balls : High goal : Mid goal : little goal : Flex wheels : Red, Blue or Green motor : Loaders : Elastic bands : Direction of the Cube Robot Part: Field Part: Week 1: In this first week, we will discuss possible team members, wary of the people we pick and set of skills we expect from them. The aim is to create an efficient and bonded team, as to optimize our efforts. Consequently, we have kept most of our team members from last year and concentrated on replacing those who left. We also agreed it would be important to regularly update our notebook to keep up with progress. The use of this notebook is also useful to help members catch up on what has been or is being done during their absence. It was settled we would try to put it up to date as regularly as possible, preferably on a weekly basis. Finally, we have decided to use a digital notebook, as it makes it more accessible for other members. WEEK 2: This week, all of the team’s members have been chosen. We agreed to keep last year’s name: T-Vex: a clever wordplay with the infamous “T-Rex”, as our team is ready to devour the competition. One of the members has also designed an intelligent team logo (see below). Soon after, we eagerly started our project: The first step to our robot’s construction is the full understanding of the rules and requirements of the competition. In order for everyone to fully grasp the objective, every single member is tasked with reading a section, and eventually, the entirety of the Vex Robotics Game Manual. Furthermore, we advised each other to look up the available vex V5 parts and think of possibilities for their uses. In parallel and to make the most out of our time, we have ordered a starter kit and gathered parts from last year’s robot after dismantling it and started doing some research online. We will then organize a meeting to sum up the important points of the manual and start brainstorming ideas for our robot and strategies. Here is the Flag/Logo of our team Week 3 Meeting Report This week, we had the meeting that we planned last week. During the meeting, we read the Push Back game manual and shared important information. We wrote down the main rules and requirements below to understand the game better and keep everything clear in one place. Robot Rules • Maximum robot size: 18 in × 18 in × 18 in Field Information • Field size: 12 ft × 12 ft square • 88 Blocks total (44 red, 44 blue) • 4 Goals: 2 Long Goals and 2 Center Goals (upper and lower) • 4 Loaders • 2 Park Zones Scoring Summary • Block scored in a Goal: 3 points • Controlled zone in a Long Goal: 10 points • Controlled Upper Center Goal: 8 points • Controlled Lower Center Goal: 6 points • Autonomous Bonus: 10 points • Parking: 1 robot = 8 points, 2 robots = 30 points VexV5 Push Back field On top of that, we have divided the robot’s tasks as well as what it is expected to do or be able to: 1.) Move around smoothly 2.) Pick up cubes 3.) Score cubes at different levels (high/medium/low) 4.) Sort blue and red cubes depending on our team’s colour 5.) Collect cubes from loaders 6.) Do points 1 through 5 while being autonomous 7.) Clear goals of enemy cubes 8.) Leave enough space for 2 robots in parking It is important to note that the last two points are not a priority for our team. We have determined it would be better to fully concentrate on main objectives first . T-Vex sincerely believes in simplicity. We think the best robot is not the most complex, in the contrary, we believe it is the simplest. Indeed, it is our core belief that complexity only leads to more complexity and is susceptible to make the robot harder to control, have more issues, and harder to disassemble or fix. As true engineers at heart, we aim to find the easiest and most efficient solutions to a problem. Consequently, our aim is to successfully complete the competition’s basic functions BEFORE launching ourselves into complexity. Regarding our own work repartition. We stand by the idea roles should not be imposed. Everyone should be able to do as they please, as long as all the tasks are being taken care of. We will try to limit the amount of people per active task to 3 (2 being preferable). Roles might even come automatically as people get more knowledge and more accustomed to what they are doing. The roles we have seen for now include: researcher, builder/mechanic, sketcher, logistics manager, coder and archivist/notebooker. We also started to put our ideas in common and talked about ways to make our robot’s tasks attainable. Nothing has been put on paper yet. Part two: Content WEEK 4 By the fourth week, we began constructing the core structure of our robot. With our overall layout already planned, the next step was translating our design into a functional build. We started by assembling a square, reinforced base made of metal structural components. This base served as the foundation of the robot and allowed us to mount the wheels in a way that ensured optimized mobility and stability. We also allocated space within the chassis for the robot’s brain and control system. After completing the base, we repeatedly disassembled and reassembled sections of the robot to improve alignment, weight distribution, and overall efficiency. We decided on using 4 green motors for optimal stability. By the end of the week, the foundation of our robot was solid and ready for further development. Chassis: Top view Chassis: side view Chassis WEEK 5 During the fifth week, we shifted our attention to designing the intake system. Our objective was to collect blocks as quickly and reliably as possible. Our first prototype used flex wheels mounted at the front of the robot. When activated, these wheels would rotate inward to pull blocks into the chassis. However, after multiple tests, we realized this approach was inefficient. The blocks did not consistently follow the motion of the wheels and often failed to move far enough into the robot’s internal structure. Our internal system consisted of four vertical metal rods with large disks attached at both ends. Elastic bands were stretched between the disks to help guide and control the blocks. This mechanism was designed to direct blocks either toward a flattened central rod for the lower goal or upward toward the elevated goals. While promising in theory, the intake mechanism itself lacked reliability and needed to be changed. We also changed the motors we used for mobility by replacing them with 2 red motors. We believe they will better withstand the robot’s weight, reducing the number will help us stay within the limited amout of motors our robot can have. Side view: intake system Top view: new chassis with intake system New chassis with intake system WEEK 6 In the sixth week, we decided to redesign our collector entirely. We placed it at the front of the robot with the flex wheels on top of the cubes this time for better intake. Consequently, we developed a new mechanism shaped similarly to the Greek letter Pi to empty loades, as the new collector could not do it by itself: A long, thin metal bar formed the main horizontal component, with two shorter vertical bars attached at its center. This structure was then mounted onto two extended support rods. Once completed, we planned to integrate it into the main chassis by adding reinforced mounting points at the front of the robot. It is placed at the front of the robot and kept vertically to respect the maximum extension length. It can then be lowered using a motor when needed. It works by lifting the balls in the loader and then acting like a slide to direct them towards the collector for the cubes to be “swallowed” by our robot. “Pi mechanism” New collector New collector with “Pi mechanism” collector WEEK 7 During the seventh week, we began prototyping the vertical chassis system responsible for lifting the blocks and scoring at different heights. We aim to install two tall metal supports at the back of the robot and connect them with a horizontal crossbar at the top. Another crossbar at the bottom will define the lower boundary of the lifting structure. This framework should allow us to test how blocks would travel upward inside the robot toward the designated scoring height. In short, cubes will be brought to the top with a chain that acts as a chairlift. Balls can therefore be scored on bottom and top goals for now using this system (we have yet to figure out a way to score at medium height). We will also use elastics as support/ ramp for the balls as they allow for optimal grip, preventing the cubes from falling back down the ramp, while still allowing them to be brought upwards. Chain with elastic bands and chassis Furthermore, we added a triangle shape and the back of the robot. Its aim is to ease the alignment of the robot with the long goals, without us having to aim. Indeed, the long goals have a triangular base. Hence, the shape we added should fit in perfectly with the goals, allowing us to simply move the robot towards it, and aligning it straight with the goal by default. WEEK 8 Here, we focused on bringing our prototype from week 7 to life. Our main feature is the vertical chain-driven conveyor system, made of three parallel chain tracks with evenly spaced paddles. As the chains rotate, the paddles. move and bring up the balls like a chairlift as described above. We equiped the chain with a blue/ speed motor for maximum speed of the chain, and therefore maximum speed of the cube’s upbringing. Different points of view of the chain WEEK 9 During the ninth week, we focused on finalizing our robot by integrating a color sensor (AI camera) capable of distinguishing red and blue cubes. This addition allowed us to program the robot so that, when a specific button on the controller is pressed (see “Code” section), only the selected color is directed toward the scoring goal, while cubes of the opposite color are automatically rejected by the system: flex wheels are turned the opposite direction of the chain. We left a gap between them and the elastic right before which acts as a ramp. The deformable nature of the elastic allows the cube to go downwards (and does not chanhe anything if the wheels don’t turn), into an empty storage space. This sensor significantly increased the efficiency and strategic value of our robot. During a match, we no longer need to carefully choose which blocks to collect. The robot can intake any block that enters the collector, and the sorting mechanism will automatically separate them based on color. As a result, our robot operates faster, reduces decision-making time during gameplay, and allows us to focus more on positioning and overall match strategy. Moreover, we realised this mechanism can also be used to score at medium height, solving our previous problem of not being able to score there. Sorting and medium height scoring mechanism WEEK 10 We participated in a friendly competition at Diekirch. We seized this opportunity to observe other teams and upgrade our robot through match experience. For instance, we fixed our code which had many defects, and tested our autonomous and skills codes, which also require consequent improvement. During this week, we therefore did our maximum to prepare for the competition, choosing some pilots through selection processes described in “Part Three”, solidifying the robot, and doing practice matches WEEK 11 This week, we focused on designing pneumatics to create an extendable arm and solidifying our robot again by adding metal bars. The arm will be mounted on the superior part of the robot and be used to empty long goals. Indeed, they are made in such a way that cubes are exposed in some parts. The arm will therefore push the balls out as shown below. WEEK 12 The entirety of the team was on holidays and did not have access to the robot, which didn’t allow us to do any consequent modifications. Pneumatic arm to empty goals Part three: Conclusion All that is left to do is perfect the autonomous code, skills code, the selection of pilots within the team, the making of the arm to clear goals and cable management. At the time we are giving in this notebook, these steps are not yet complete. We will select our pilots by a small, in-team competition. The members will have to complete a series of drills as fast as possible. Drills may include picking up or spitting out cubes, scoring, and an obstacle course. Pilots have also been tested on the 7th of February, during a friendly competition at Diekirch. Besides that, Our robot is theoretically done. All extra modifications are not fundamental to the robot’s functions, but should enhance its competitiveness. We have decided not to include our code in our notebook as it is still not complete and is subject to change in the following week. However, we have tried to elaborate a code that aims to fully exploit all of the robot’s function. Our code also aims to reduce energy consumption by targeting which motors to activate. For instance, we have programmed our robot so that its chain only turns when necessary, instead of in continuation. Here is our controller. While some members have their own personal settings, here are the default controls we have agreed on (which are also subject to change): Display screen Power/home button Buttons: X: Activate automatic sorting for blue cubes B: Activate automatic sorting for red cubes Y: Stop automatic sorting A: not defined Left Joystick: control the robot Right Joystick : not defined L1: Move chain downwards L2: Move chain upwards (for high goals and cube intake) R1: Manual Sorting/score at medium height R2: Increase cube speed to score Up arrow: Activate arm to clear goals Down Arrow: Retract arm to clear goals Left Arrow: Not defined Right Arrow: Not defined WEEK 13 Code Strategy For this competition, we chose a strategy focused on speed and quantity of scoring, rather than storage or complex systems. Our robot will not store many blocks or use the loaders often. Storing blocks can slow the robot down, add weight, and make the design more complicated. Instead, we prefer a simple, light, and reliable robot that can move quickly around the field. The robot will make many fast trips back and forth to push or carry a few blocks and score them immediately. By repeating these quick actions many times, we hope to score more points during the match. We will mainly prioritize the upper goals, as they are the easiest for our robot to reach. This allows us to maximize our score with each trip as they give the most points. To help with this, we will use a simple and efficient sorting system so blocks can be scored quickly without losing time. Once our blocks are scored, we wil focus on ejecting the opponent’s blocks to maintain our control of zone. Overall, our strategy is to keep the robot fast, simple, and efficient, and to score as often as possible throughout the match. We will adapt this depending on our teammated and their ideas. T-Vex : Checklist A verifier: L a c h a r g e d u p n e u m a L a f i x a t i o n d e s m o t e u r s L a b a t t e r i e T o u s l e s m a i l l o n s d e l a c h a i n e L e s v i s d e r e n f o r t s L e s v i s d e s e r r a g e s T o u s l e s e l a s t i q u e s EXTRA PICTURES