Blog

This year at Robotech, we’re launching a weekly blog to share everything we do throughout the season. It will be a space where we explain how we organize ourselves and how we grow as a team over time. We’re very excited and eager to start this new challenge with energy and commitment.

We’re open to being a source of inspiration through everything we’re doing, hoping other teams can make it their own and take it even further.

We’re happy to share our experiences, our learnings, and anything that might help you.

And if you want to go even further, you’ll soon be able to access our full FLLPlanner: a step-by-step guide to achieving great results.

Reserve your spot: www.fllplanner.com

Week 1

02/06/2025 - 08/06/2025

We had our first meeting of the season, where we discussed new ways to organize ourselves and set clear goals for both the team and each member. We also planned our training by combining courses with reading personal development books, which each member will read on their own. This approach will help us improve our skills and get ready for the challenges ahead.

Week 2

09/06/2025 - 15/06/2025

We started by dividing up individual tasks according to each team member's strengths, in order to work more organized and efficiently. Then we started sorting through all the parts we had, a task that will take a long time but was essential to know exactly what we were missing.

Week 3

16/06/2025 - 22/06/2025

This week we finished looking at what pieces we needed to have of all kinds, and then we went piece by piece to make a list that we would then buy. Finally, we started building different missions from next year board that we had previously designed in 3D.

Week 4

23/06/2025 - 29/06/2025

During this week we finished rebuilding all the missions that were pending. To make it more efficient, we divided ourselves into pairs and worked in an organized way. Thanks to this dynamic, we were able to assemble all the missions we needed to start the tests on the board.

Once the new missions were assembled, we removed those from last year, as well as the old tapestry from the counter. We then did a thorough cleaning to have the surface completely clean. Then, we placed a tapestry from another season, but inside out, to avoid visual distractions and clearly mark the new season. Finally, we distributed the reconstructed missions in their corresponding place on the counter.

We have done tests to compare the behavior of the Spike 3 with the Pybricks. In the image we took during the test, it can be clearly seen that the robot programmed with Spike (dots on the left) makes many more precision errors, while with Pybricks (dots on the right), the movements are much more constant and precise.

After analyzing the results, we found that Pybricks makes about three times fewer errors than Spike, and also moves faster around the board. Therefore, we decided to adopt Pybricks as the main programming system for this season.

After the tests, we started building specific attachments for each mission. We progressed very quickly and in a single day we managed to have 7 functional attachments, designed from the simplest to the most complex. This will allow us to optimize the outputs and combine them later to generate the definitive attachments for each route.

Regarding the project part, we have begun to prepare the bases based on data collected in interviews with experts and visits related to the topic. These initial sources have provided us with relevant information that will help us build a solid and well-founded proposal.