RoboCup 2025 Schedule

Day 1 – Thursday, July 17:

Time (CEST)              Game                                        Phase                         Result


9am (2pm)                 TIGERs vs ER-Force                  G1                             10-0

 

Day 2 – Friday, July 18:

Time (CEST)              Game                                        Phase                        Result


9am (2pm)                 RoboDragons vs ER-Force         G1                            0-0

12am (5pm)               ZJUNIict vs ER-Force                  G1                           1-0

6:30pm (11:30pm)     RoboCin vs ER-Force                  G1                            0-0

 

Day 3 – Saturday, July 19:

Time (CEST)              Game                                        Phase                        Result


9am (2pm)                  TIGERs vs ER-Force                Upper 1.1                      –

12am (5pm)                 LUpper1.1 vs Q5                      Lower 2.1                      –

1pm (6pm)                   WUpper1.1 vs WUpper2.1       Upper Final                   –

6:30pm (11:30pm)      WLower2.1 vs LUpper1.2          Lower 3                         –

 

 

Day 3 – Progress with Obstacles

The day began, as so often, with a hearty breakfast – by now almost a fixed ritual that gives the day a bit of structure. Along with it came a bit of SIM card chaos: the search for the cards turned into a bit of an adventure, after a shop assistant from a small store sent us wandering through the alleyways of Salvador. With a strong sense of direction (and a bit of luck), we eventually found ourselves in the right place.

Then it was off to the venue for the first time – straight across Salvador. And here, a stark contrast revealed itself: while outside the usual Brazilian street life was in full swing, the venue felt almost like a different world.
Super modern, spacious, with stable internet – and most importantly: lots of room! A real upgrade for all teams.

On the technical side, things also moved forward nicely. The firmware managed to fully implement the return channel – a key feature for radio communication with the robots. Work on the FPGA continued as well – a chip in our new radio module that’s programmed on the hardware level and offers a lot of flexibility. The electronics were also put to use: cable issues were fixed, and – as always – some things were freshly soldered.

Then the highlight (or rather, the low point) of the day: the first official test slot on the field. Finally a chance to test our systems under competition conditions. Unfortunately, the first run ended in a collective crash test – several robots drove straight into the wall and had to be repaired afterward. The mood was accordingly tense.

In the mechanics department, things were buzzing: shot covers had to be re-cut, casings re-glued, and damaged parts replaced. A small-scale material battle – but that’s just how it goes. There seems to be an unwritten rule: no matter how well everything works back in Erlangen – once you’re on site, something always goes wrong.

Still: progress was made. The setup is in place, many construction sites are resolved, and the motivation is there. And sometimes, that’s enough to start the next day with a good feeling.

Team ER-Force!

Day 2 – All About the Tech

Today was all about the technical side. Each subteam was fully focused and working across all fronts.

The mechanics team had their hands full: to avoid any conflicts with the new batteries, the shot covers were quickly reshaped – creative, functional, and efficient.

The electronics team was also deep in hands-on work. A major redesign was tackled: the modular setup was reworked so that connectors can now only be plugged in correctly – unless someone really tries to force it wrong. In addition, broken light barriers were repaired, bringing back some much-needed reliability.

Firmware made the most of the day by focusing on two big topics: work on the FPGA (a chip in our new Funkmaster module that needs to be programmed on the hardware level) and intense tinkering with Active Disturbance Rejection Control (ADRC) – a system that actively counters disturbances or prevents them from happening in the first place. The central question of the day: how can we identify potential sources of error early and eliminate them reliably? Not flashy – but exactly the kind of detail that makes a difference.

The strategy team worked on fixing bugs from past test games and continued refining

the tactical routines. At the same time, one topic kept coming back: wireless communication. Already a problem child during RoboCup in Bordeaux, the connection between robots and control remains a hot topic – and a critical one.

In the late morning, the whole team gathered at the hotel pool for a meeting. A relaxed setting for a focused debrief: reflecting on our recent workshop and what insights we

want to carry forward into the competition days ahead.

The day wrapped up with what should’ve been a simple dinner order – but turned into a bit of an adventure. CPF numbers (which are required for many things in Brazil), missing phone numbers, and the ever-present language barrier created quite a bit of chaos – but also plenty of laughs. After a long wait, the food finally arrived. Verdict: delicious, a bit chaotic, but definitely a moment we’ll all remember.

 

Day 1 – Hitting the Ground Running (and Swimming)

The first full day on site kicked off with a mix of sun, sea, and serious setup work. After breakfast, we headed straight to the beach – no hesitation, straight into the water. It was the perfect way to shake off the long journey and enjoy a moment of freedom before the intensity of RoboCup truly begins.

Back at the hotel, the whole team gathered in the lobby to plan the day, unpack equipment, and organize tasks. Everyone split into their respective areas – mechanics, electronics, software, firmware and publicity – ready to dive in.

Meanwhile, part of the team ventured out to a local supermarket to stock up on supplies. It turned out to be more of a mission than expected: the language barrier made even simple things challenging. But with creativity and teamwork, we pulled it off.

After a quick bite to eat, the real work began.
The software team got everything tournament-ready – testing, tweaking, and fixing the final bugs. On the firmware side, there were still some battles with the wireless communication.
Electronics involved some re-soldering on the robots, and mechanically we added damping to the battery holders to prevent damage during rapid acceleration or sudden stops.

We also took the time to go through the scientific papers of the other teams qualified for RoboCup – gaining insight, inspiration, and valuable context for the competition.

The work carried on late into the night. It wasn’t always smooth, but the team powered through with determination and focus. We’re now fully arrived – with robots, team spirit, and a good dose of ambition in our luggage. Let’s get this RoboCup started!