June 2026 - RoboCup-small - lists.robocup.org

Ri-one Radio Communications Technical Challenge Submission
by NAITO Yuzuru 27 Jun '26

27 Jun '26

Dear All, On behalf of Team Ri-one, please find our submission for the Radio Communications Technical Challenge (Wi-Fi track): https://github.com/Rione/ssl-2026-TechChallence-Wireless Our approach uses commercial off-the-shelf components (Radxa ROCK 5A + Intel AX210, Wi-Fi 6E) to provide a low-cost, high-bandwidth, interference-resistant link, aimed at lowering the barrier of entry for new teams. The README.md (English) covers hardware, firmware/environment setup, methodology, and measured results. We have also published our robots' circuit designs this year; please find them here: https://github.com/Rione/ssl-Circuit/tree/baa913cb75b0630cb045215d907af2356… We look forward to your questions, and to seeing you in Korea. Best regards, Yuzuru Naito Team Ri-one

1 0

GreenTea Radio Communications Technical Challenge Submission
by GreenTea 26 Jun '26

26 Jun '26

Dear All, On behalf of Team GreenTea, please find our submission for the Radio Communications Technical Challenge (Wi-Fi track): https://github.com/greentea-ssl/wifi-technical-challenge The report (README.md, English) is self-contained, covering all required items, methodology, hardware, firmware, and a reproduction guide with raw data. We look forward to your questions, and to seeing you in Korea. Best regards, Kohei Fujita Team GreenTea

1 0

ER-Force Radio Communications Technical Challenge Submission
by Christoph Schmidtmeier 26 Jun '26

26 Jun '26

Hi all, here is the link to our radio communications submission: https://github.com/robotics-erlangen/radio-challenge-2026 Sadly, there is no measurement data and documentation yet due to unfortunate delays, but we hope to provide them as soon as possible from our hotel in South Korea. Thank you for your understanding. See you in the venue. Best Regards, Christoph ER-Force

1 0

TIGERs Mannheim Radio Communications Technical Challenge Submission
by andre＠ryll.cc 26 Jun '26

26 Jun '26

Dear Community, we extensively documented our wireless communication solution in hardware and software for the radio communications technical challenge. We hope this makes it easier for other teams to adopt our solution. If you have any questions you can find me on the SSL Discord server. You can find the documentation here: https://github.com/TIGERs-Mannheim/Firmware/blob/master/WirelessCommunicati… Together with our open-source electronics here: https://github.com/TIGERs-Mannheim/electronics Best, Andre Ryll TIGERs Mannheim

1 0

A-Team Radio Communications Technical Challenge Submission
by William Stuckey 25 Jun '26

25 Jun '26

Hi All, A link to our radio communications submission is can be found on our GitHub Wiki here: https://github.com/SSL-A-Team/firmware/wiki/Radio-Communication-Tech-Challe… We look forward to seeing everyone in Korea. Best, Will

1 0

RoboCup 2026 – Open Source Award Submission The Bots
by Henry Bryant 17 Jun '26

17 Jun '26

Hello SSL Community, The Bots would like to submit a new ball receiving method using the existing kicker solenoids found on most SSL robots for the Open Source Award. Officially, its title is Solenoid Active Damping, which refers to the method by which a ball is damped - using the electromechanical energy found on robots with active control of the kicker solenoid to stop the ball. This method completely decouples the ball receiving damping needed from the ball dribbling damping needed, where the one tends to affect the other. In general, SSL robots that use a capacitor based kicker board have a significant amount of energy sitting unused during the receiving of a pass. That energy can then be used to keep the kicker extended after a short kick at the exact threshold where the kicker would otherwise collapse with any extra applied force. You can imagine the solenoid active damping similar to when one stops a soccer ball by pulling their foot back to absorb the energy as the ball gets to their feet. In a similar way, the solenoid is held with minimal possible force so that when the golf ball contacts it, the energy is almost completely damped as the wall collapses from under it. In the repository below, you can find the detailed documentation (as a README file) for the Solenoid Active Damping system with relevant code used for our RP2040 on the Chicker board in micropython. The important takeaway from this code is not the exact syntax shown in micropython for the RP2040, but rather the concept of how the implementation is formed - this is because each team's kicker boards will differ based on the chip used. You can find all the documentation, relevant code for the RP2040, and videos from later testing (not on the TDP) here: https://github.com/sfunderbots/Electrical/tree/main/Chicker/solenoid-active… Associated full code for the RP2040 on The Bots Chicker board here for reference: https://github.com/sfunderbots/Electrical/tree/main/Chicker/firmware Note that the code shown here is not the most recent version - the latest includes a fix to compensate for the voltage on the high voltage net lost over time, which is described in the README. We hope this open source system will help new teams wanting to keep cost and complexity of their robot low, by utilizing already existing hardware from the robot's kicker board used to kick a ball to be used in reverse. Subsequently, this system also aims to improve pass receiving performance without the need of a dribbler. Thank you for your consideration, ~Henry Bryant The Bots

1 0

Inquiry about Follow-up Procedures & Detailed Daily Schedule for RoboCup 2026 Incheon (SSL)
by 梁子超 16 Jun '26

16 Jun '26

Dear RoboCup Registration Support Team, I am writing on behalf of Team Mountain. We have successfully completed the full payment for our SSL team and have already received the official competition invitation letter. As first-time participants in RoboCup with limited experience, we would greatly appreciate your detailed guidance on the following two matters: Post-invitation procedures: After receiving the invitation letter, do we only need to arrive in Incheon, South Korea, during the competition period (June 30 – July 6) to participate in the matches? Or are there any additional mandatory pre-event formalities, document submissions, online uploads, or on-site check-in preparations that we must complete in advance? Could you please list all required procedures clearly? Competition schedule: When will the complete daily detailed competition timetable (covering June 30 to July 6) be officially released? We need the specific schedule to arrange our team’s travel, robot shipping, and accommodation plans accordingly. Thank you very much for your patience and continuous support. We look forward to your reply. Best regards, Liang Zichao Team Leader Team Mountain

1 0

RC2026 two weeks out
by David Brand 16 Jun '26

16 Jun '26

Hello, As we are now two weeks away from the competition, we have a last few additional pieces for you. In the days after the last announcement we got a final confirmation that the venue indeed will be open from 7:00 to 23:00. While we have updated the times in the schedule we currently do not plan to extend the matches, so that the additional time will purely be for you to work on the robots and your software. Also anyone must have left the venue by 23:00, so we will start to clear the SSL area from 22:45 on and in case everything runs smoothly, we might be able to push back that time for later nights. Also another small update regarding the power: Each team table in the team area will have a power budget of 3 kW instead of the 2 kw we got as info beforehand. Plus a small reminder, the deadline for [Open Source Submission](https://ssl.robocup.org/robocups/robocup-2026/robocup-2026-awar… is today (June 16th) AoE, so if you haven't sent your submission yet, you have about another 15 hours till the deadline. Radio Information Request Please fill out the radio information survey so we know what radio technologies your team is using. This will let us allocate you a frequency and deconflict teams and the venue. The link is: https://forms.gle/MUN482c2oF8e1uJY8 Technical Challenges (Reminder) As already announced we will be hosting two technical challenges this year. The [radio communications challenge](https://robocup-ssl.github.io/technical-challenge-rules/2026-radio-communications-challenge.html) aims at providing a list of known good radio solutions in the future, to reduce the entry barrier for new teams. The [SSL RCJ Soccer Junior Cooperation Challenge](https://robocup-ssl.github.io/technical-challenge-rules/2026-ssl-rcj-soccer-junior-cooperation-challenge.html) is a challenge hosted together with RoboCup Junior Soccer and will see Junior and Major teams solving a task together. While the challenge itself will only be published on the Wednesday of the competition, it might make sense to already take a look at the [communication module](https://github.com/robocup-junior/soccer-communication-module) used in RCJ Soccer. Will it definitely won’t be required, I have heard that it might be helpful. To submit a radio solution to the Tech Challenge you need to make that submission to the SSL mailing list by June 26th (AoE). To join the Cooperation Challenge with Junior you need to fill out the [form](https://forms.gle/az63vys8jpErBj9e6) before June 30th 18:00 o’clock (KST). As this is the same form as in the announcement of the Tech Challenge all teams that have already done so, do not need to do it again. After the deadline has passed, we will get in contact with all teams directly to tell you the next steps and see if you are still up for the challenge. Award Voting, Excellence Award and Scientific Publications Like last year we will be doing the voting this year via online forms. As we especially wanted to give you more time to evaluate the Open Source Submissions (can be found [here](https://ssl.robocup.org/robocups/robocup-2026/robocup-2026-open-sourc… after the deadline) as well as the (E)TDPs ([list of eligible teams](https://ssl.robocup.org/robocups/robocup-2026/robocup-2026-awards/)/…), we also already set up the voting forms for both of them: - [Open Source Ballots](https://forms.gle/oAUmnhBLL5SgbGKz7) (already available, but final form will only be available after all submissions have been made) - [Best (E)TDP](https://forms.gle/7rLdcD1yF28XEXhS8) But as in the previous years the voting will only be due during the RoboCup as the Open Source Presentation is an essential part of the award. Also as last year you will be getting a unique team code, so that malicious votes can be eliminated. In case you already want to look at the questions beforehand, feel free to use “test” as team name as well as the unique code, which allows us to easily delete these votes. As part of the excellence award, teams who have contributed to the SSL shared projects can receive two additional points. Therefore if non-committee members of your team have made changes to any of the shared projects, please send a mail to the OC mailing list with links to the contribution(s) (PRs, Issues, etc.). The OC will have a look at them and get back to you, whether the contribution qualifies for the additional points in the Excellence Award. In addition to that, we are also looking for scientific publications made in the last or previous years by members of SSL teams as part of their work, so that we can add them to the list of the scientific publications on the [homepage](https://ssl.robocup.org/scientific-publications/). If yours is still missing there or you now of any, please also send that as mail to the EC committee. Streaming Like every year, we’re going to stream our SSL matches to YouTube. This year, the aim is to professionalize our streams and create a foundation for future tournaments. This includes a [dedicated SSL Youtube channel](https://www.youtube.com/@smallsizesoccer), a unified look and feel, and tools needed to quickly set up your own streams. Make sure to join the Discord channel [#streaming-and-youtube](https://discord.com/channels/465455923415220234/1483367409904783492) The South Korean RoboCup organisation has provided us with three streaming PCs, one for each match field. Therefore, ideally, every match will be streamed. This however requires your help, therefore, a Call To Action: If you are excited to livestream one of the fields during RoboCup, then reach out to the OC/TC. You won't be expected to stream every match, but together we can ensure that all matches get streamed. If you have any hardware that you are willing to lend to the SSL ( cameras / webcams / microphones / stream decks / encoder boxes / gimbals / .. ), please reach out to the OC/TC. If you have design experience, and want to help with creating OBS stingers / SSL logos / streaming layouts / RC2026 banners / .., please reach out to the OC/TC. Referee Quiz As a quick reminder from the last mail, every team participating in the RoboCup2026 needs to be able to fill out their assigned impartial roles for matches, when they do not play. These members have to take the [referee quiz](https://forms.gle/oRRTrdaw3VqyCdHs7) beforehand. In case you have any open questions or any trouble during your travel, please let the OC/TC know as soon as possible. This allows us to see whether we can help you in any way. See you in Incheon! David. (on behalf of the SSL committees)

1 0

RoboCup 2026 – Open Source Award Submission TIGERs Mannheim
by Andre Ryll 16 Jun '26

16 Jun '26

Dear SSL Community, I hereby submit a completely new generation of TIGERs robots for the Open-Source Award. Don't be afraid, they have no wheels, they are not playing on the field, and still they are pretty awesome! In the repositories listed below you can find all the files for a 2-axis (pan, tilt) camera gimbal system. It is powered by a single PoE connection and understands the SSL Tracking Protocol. Just put it next to the field, punch in its location and it will happily track the ball all-day long. So that your camera always gets the perfect shot at the action. It is made of a cheap Raspberry Pi Zero, a custom driver board with STM32G4 microcontroller (featuring field-oriented control), some off-the-shelf components (PoE hat, display, motors) and a few 3D printed parts. The firmware even has jerk-limited trajectories to ensure maximum smoothness when following the ball. There are two variants available. One small one for an action cam and a bigger one to mount our various league streaming cameras. The small variant has already been extensively tested and an earlier version of that was successfully used at the Schubert Invitational Tournament in spring in Germany. You can find all the hardware (mechanics, electronics) here: https://github.com/TIGERs-Mannheim/gimbal-hardware Software running on the Pi is here: https://github.com/TIGERs-Mannheim/gimbal-rpi And the firmware for the microcontroller here: https://github.com/TIGERs-Mannheim/gimbal-mcu-firmware As an additional bonus, we also open-sourced our buildroot configurations to build custom Linux images here: https://github.com/TIGERs-Mannheim/tigers-buildroot The OS running on the gimbal is also made by buildroot and the gimbal-rpi repository also contains instructions on cross-compiling to ease remote development and debugging. The buildroot setup may be of particular interest to other teams using a Raspberry Pi in their infrastructure. It features an A/B style update system (also remotely) and a read-only root file system with overlay for user changes. So you can still make changes, but it doesn't break if you just power it off as well. Best regards, Andre Ryll TIGERs Mannheim

1 0

RoboCup 2026 – Open Source Award Submission luhbots soccer
by Tim Füchsel 15 Jun '26

15 Jun '26

Dear SSL Community, we, the luhbots soccer team, are happy to announce our submission for the Open Source Award 2026. This year we would like to present a new simulation framework for the SSL. The aim of this simulator is being able to speed up simulation time, with the long-term goal of eventually using it to train AI models aimed at specific tasks to aid our strategy. Some of it's main features are: * A rigid body physics simulation of the robots and the ball. * Decoupling of the simulator and the network components, allowing embedding the simulator into other programs and specifying the time step size. * An implementation, compliant with the official SSL-protocols. * Being able to be used as a drop-in replacement for other SSL-simulators. The source code and documentation can be found on our GitHub page: https://github.com/luhbots/luhsoccer_simulation Furthermore our new software is now also available at this address: https://github.com/luhbots/luhsoccer_trioxide Best regards Tim Füchsel luhbots soccer

1 0