- RoboCup-small - lists.robocup.org

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

26 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 梁子超 17 Jun '26

17 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

RC2026 Schedule and further information
by David Brand 09 Jun '26

09 Jun '26

Hello, After a break in the updates last week, we are back with another round of news for this year's tournament. We hope that the preparations for the tournament are going well and that all of you are already hyped for this year's RoboCup. In addition to the news please keep in mind that the deadline for open source submissions is in about a week. (Additional info can be found under [Open Source Award](https://ssl.robocup.org/robocups/robocup-2026/robocup-2026-awards/)) Tournament Structure & Schedule With the regular registration deadline having passed by, we now know that we will be playing with 14 teams in Division B, as well as 8 teams in Division A. In addition to that, we also got the general schedule for this year, so that the following schedule can hopefully be seen as the official schedule for this year. [RC 2026 Schedule](https://docs.google.com/spreadsheets/d/1bsxqOYN0DLLImdCsPusrCoxQJ… Still, when looking at it, please have two things in mind: All entries with question marks behind them haven’t been finalized yet, as we still need to book meeting rooms for example. Also we currently know for sure that the venue will be open at least from 8:00 to 22:00 o’clock for major teams, which is why we used this timeframe for the schedule. But it is not yet known whether the venue might actually be open longer. As soon as we have a final answer on that, we will update the schedule accordingly and send out an update. Based on the random numbers for June 7th (sorry for the date mixup in the last mail, using numbers from the day after the symposium would be a bit inconvenient), we received the following groups: Div A - Group 1 (Seeding Tool Group A) TIGERs_Mannheim (GermanyA) RoboDragons (JapanA) ER-Force (GermanyB) Ri-one (JapanC) Div A - Group 2 (Seeding Tool Group B) ZJUNlict (ChinaA) KIKS (JapanB) RoboCIn (Brazil) luhbots (GermanyC) Div B - Group 1 (Seeding Tool Group A) The_Bots (Canada) Delft_Mercurians (Netherlands) TritonBots (USA) GreenTea (Japan) Div B - Group 2 (Seeding Tool Group D) RoboJackets (USA) NAMeC (France) TurtleRabbit (Australia) RoboCup_Junior_SSL_Team (Germany) Div B - Group 3 (Seeding Tool Group B) Warthog_Robotics (Brazil) The_A-Team (USA) Traps (Japan) dummy (dummy) Div B - Group 4 (Seeding Tool Group C) ITAndroids (Brazil) UBC_Thunderbots (Canada) dummy2 (dummy) SeeGoals (Sweden) The schedule has been updated with the groups, so that you can already take a look, when you will be playing. Referee Quiz To be allowed to fill in one of the impartial roles (assistant / main Referee, Game Controller Operator, Vision expert) during the official matches, you need to complete this year's referee quiz before the first competition day: https://forms.gle/oRRTrdaw3VqyCdHs7 It has been redesigned this year to be closer to an actual match and therefore concentrates much more on the basics compared to last year. (Thanks a lot to TIGERs and especially Laura, who took over this task) Since all teams will need to take turns in filling in the impartial roles, if not at least two members of your team completed the quiz, your team can be excluded from the competition. In case your team has only a small number of members, please still fill in the quiz, as getting to know the rules and roles during the match is also quite crucial for the robot handler(s) of each team. But also reach out to the OC(rc-ssl-oc(a)lists.robocup.org), so that we can see whether we can adapt the amount of referee duties for your team. Communication For the textbased communication during the RoboCup we will be using the[ssl mailing list](https://lists.robocup.org/mm/lists/robocup-small.lists.robocup.org/), as well as the [SSL discord server](https://discord.gg/t724m8c). Especially for fast paced announcements from us, but also for communicating with the other teams the discord server is quite crucial. Therefore in case from your team not multiple, or ideally all, members joined both communication lines yet, please consider to do so. This helps us, as well as you, to be sure that you get critical information as soon as possible and in case that one team member might not read it, the others can forward the relevant information. In addition to this there is also the official Discord Server for the whole RoboCup: https://discord.gg/q4AfnY7fx6 In case you haven’t joined it yet, feel free to do so as well, as it is not just for the single tournament, but also for other events and a general exchange between the leagues during the year. What to bring Network/Wireless: This year you will be provided with ONE ethernet plug for your team at the field, as well as ONE at your team table. Since that won’t be enough connection points for your whole team, please bring your own routers/switches, network cables, as well as any needed adapters. Whilst personal wifis should be banned at the venue again, the venue plans to offer a public wifi. Nonetheless we still suggest using cabled solutions (also for mice, headphones, etc.) where ever possible, to declutter the radio spectrum and as a good idea in general, as radio solutions used for robots might be more powerful and therefore could lead to you not being able to use wireless solutions for personal reasons anyway. Power: South Korea uses the type C and F power plugs and outlets, which supply in general 220 V at 60 Hz. Your team table might offer only one powersocket and will be limited to a maximum allocated power of 2 kW per team. We hope that this won't be an issue for most teams, but are already in talks with the organizers, to find out about other options for charging the batteries of the robots. In case the available power would be an issue for your team, please reach out to the OC with estimates on the required power for your team table. General information: In addition to your robots you also need a machine for your central software. Since you may need to move your equipment from the competition to the practice field, a powerful laptop instead of a full size TowerPC is usually more convenient. As we need all teams to use the same color paper on top of their robots for a good calibrated vision setup, you will need to change the color paper at the venue. While we will provide you with the color paper you should bring the equipment you need to fabricate the round blobs as well as to change them inside your hull. In case of any questions, please feel free to reach out to any committee member. Thank you, David. On behalf of the SSL OC

1 0

RC2026 Tournament Structure and Awards
by David Brand 26 May '26

26 May '26

Hello, With the tournament now only being little more than a month away, we want to give you an info about this year's tournament structure. Sadly till this day, we do not know the general schedule of the tournament, such that we are currently planning around a rough idea of where each event could be. General Tournament Timeline Team Setup Days: Tuesday 30. June - Wednesday 1. July Competition: Thursday 2. - Sunday 5. July Symposium: Monday 6. July Tournament Style With the additional Division B field this year, we increased the maximum number of teams to 24 with 10 planned in Div A and 14 in Div B. Alongside that, we also adapted the tournament structure in both divisions. Due to the single field in Div A and the team registration still ongoing until June 2nd, we have currently still two different tournament options. Therefore, once the regular registration deadline has passed by, we will make an update to the [SSL grouping tool](https://github.com/RoboCup-SSL/ssl-grouping) on the day after and remove the teams which could not finish the team registration in time. For the Div A tournament the group phase will consist of two groups with either 4 or 5 teams. In case that all 9 teams, which we currently expect, finish their team registration, the elimination phase will involve the best 6 teams as part of a double elimination system, whereas in case of only 8 teams, we will be able to include all teams in the double elimination style elimination stage. For the Div B we are currently expecting 14 teams, leading to 4 groups, consisting of 3 or 4 teams. After the group phase we will have an intermediate stage, where we will determine the fifth to eighth best teams using a lucky looser round, where all of the second and third placed teams in each group will play against one team of another group. After that we will continue with 8 teams in a double elimination system. To get a better understanding of the tournament structures feel free to already take a look at both prepared schedules: [Schedule with 9 teams in Div A](https://docs.google.com/spreadsheets/d/1OLfcAZqEqS484hQ-zAwiyAP-CBwQgKJ-… [Schedule with 8 teams in Div A](https://docs.google.com/spreadsheets/d/10Bn-sD_hUCrTsEl8_GaS2gz2lRjEQ3i4… Both schedules have the same structure for the Div B. Disclaimer: As the general RC schedule has not been confirmed yet, please see the times in the schedule only as a rough idea. Once the general events have been confirmed, we will send out an update. As in the previous years the teams will be drawn into groups using the [SSL grouping tool](https://github.com/RoboCup-SSL/ssl-grouping). We have already updated the seeding pools for this year's competition (including all teams where the registration hasn’t been finalized yet) . The seeds are primarily determined by [last year's results](https://ssl.robocup.org/robocups/robocup-2025/robocup-2025-results…, as well as the participation in previous RC tournaments. As there are three German and Japanese teams in the Div A, we have decided to ignore the country of origin for Div A again this year If you notice any issues with this seeding, please notify us before the 7th of July. This is important since we will draw groups on that day and we have a much harder time adjusting the seeding when the resulting groups are already available. As we always do, we will use random.org for the random seeds required for the tool. We will draw the groups using the pre-generated random numbers for the 7th of July (which will become available at https://www.random.org/integers/?num=4&min=1&max=10000&col=5&base=10&format… on that date) to seed our tool. (The first two numbers are used to seed Div A, and the last two to seed Div B) Awards The awards for this year can be found on the [homepage](https://ssl.robocup.org/robocups/robocup-2026/robocup-2026-awards… from now on and are the same as last year. To be considered for the Open Source Award, you must submit your submission until June 16th, AoE, which is two weeks before the start of the tournament, to give all teams the option to review the submissions. In line with last year all teams, who received at least one nomination for the Best (E)TDP Award during the review process and participated in the RC2026, will be eligible. For now this includes the following teams (in a random order): - The Bots - UBC Thunderbots - RobôCIn - KIKS - GreenTea - Ri-one - Warthog Robotics - RoboJackets - TIGERs Mannheim - Traps - ER-Force - luhbots Please take your time and read the (E)TDPs again, so that you can vote for your top three choices during the RoboCup. In case of any questions, please feel free to reach out to any committee member. Thank you, David. ------------ RoboCup Small Size League | OC Member

1 0

Quori Community Gathering @ ICRA 2026
by Ross Mead 24 May '26

24 May '26

Hello colleagues! We are planning an informal, in-person gathering sometime June 1-5 (TBD) at ICRA 2026 in Vienna, Austria for current and prospective members of the Quori robotics community. All are welcome! Quori is an NSF-funded, not-for-profit, open-everything, modular, social robot platform for the robotics research community (https://quori.org). The gathering at ICRA will serve as an opportunity to meet with colleagues interested in the Quori robot platform and to network with other researchers interested in human-robot interaction and general robotics. Please RSVP to the Google Form HERE <https://forms.gle/B4VKQE3tQuf2gkUD8> to express your interest and availability, and we’ll get back to you ASAP with a proposed time and location. You are encouraged to forward this to anyone you think might be interested in Quori. Additionally, we will also host a virtual meeting shortly after ICRA 2026 for the broader Quori community. At the virtual meeting, we will (1) provide Quori development updates; (2) invite research groups to optionally share a summary of their ICRA presentations; and (3) outline plans for cost, timeline, and distribution of Quori units. We will follow up with more information. Please let us know if you have any questions or comments. Thanks and we hope to see you at ICRA 2026 and/or at the Quori community virtual meeting! -- The Quori Project Team * Ross Mead (Semio) * Bill Smart (Oregon State University) * Mark Yim (University of Pennsylvania) * Simon Kim (University of Pennsylvania) * Naomi Fitter (Oregon State University)

1 0

Technical Challenges, additional minor rule updates, used vision system
by David Brand 21 May '26

21 May '26

Hi, We are very sorry for the current delay with the RoboCup related announcements. But hopefully everything is finally figured out and we can therefore start to send you a mail every week. Therefore, if you have not already done it, it might now be a good time to join the [SSL mailing list](https://lists.robocup.org/mm/lists/robocup-small.lists.robocup.org/). Radio Communications Challenge To reduce the entry barrier for new teams, we want to provide a list of known good radio solutions. Therefore we want to encourage teams to open-source their solution and offer quantitative metrics on which the different solutions can be compared. The goal of this is not to seek one mandated solution, but rather help teams develop and implement reliable radio solutions to reduce the complexity and enhance the gameplay. To get to know more about the challenge and how to participate, please take a look at the rules for the challenge: [HMTL](https://robocup-ssl.github.io/technical-challenge-rules/2026-radio-communications-challenge.html)/[PDF](https://robocup-ssl.github.io/technical-challenge-rules/2026-radio-communications-challenge.pdf) SSL RCJ Soccer Junior Cooperation Challenge As an experiment this year, we will also be hosting a joint Technical Challenge in collaboration with RoboCup Junior Soccer. For this challenge, participating teams will be randomly paired, combining one Major and one Junior team. Both teams will then need to work together to complete the challenge. Due to the nature of Technical Challenges in RCJ, the task and its ruleset will only be published at the start of the tournament. Therefore the evaluation will take place on Saturday. Although this is a normal competition day with matches taking place, we will do our best to ensure that the time of your evaluation slot does not conflict with any matches or the preparation time beforehand. If you would like to participate in the challenge, please fill out the participation intent here: https://forms.gle/az63vys8jpErBj9e6 Filling out the form is not binding, but helps us optimize this year's schedule and the details of the challenge. Rule Changes In addition to the [new submission area in Div A](https://robocup-ssl.github.io/ssl-rules/sslrules-diff.html#_robot_substitution) we sadly missed three minor rule changes in the last mail, where the wording or names got improved: - [Robot Height:](https://robocup-ssl.github.io/ssl-rules/sslrules-diff.html#_shape) As the vision system cannot handle robots of the same team having too different heights, the requirement of them not differing by more than 0.02 m from each other was added. - [Renaming Emergency Stop:](https://robocup-ssl.github.io/ssl-rules/sslrules-diff.html#_forced_timeout)Due to misunderstandings caused by its name, the Emergency Stop has been renamed to Forced Timeout, with the functionality remaining the same. - [Vision Systems:](https://robocup-ssl.github.io/ssl-rules/sslrules-diff.html#_vision) To allow competitions to decide for themself which vision system they want to use at a tournament, the explicit wording regarding the ssl-vision project has been updated. Available vision system(s) As we are currently still in a transition phase between the [SSL-Vision](https://github.com/RoboCup-SSL/ssl-vision) and the new [vision-processor](https://github.com/TIGERs-Mannheim/vision-processor), the decision has been made that we will continue to offer SSL-Vision as default vision system on all fields for this year. In addition to that, we will also offer the vision-processor on the Div A field, as well as one of three Div-B fields. Nonetheless we currently plan to switch to the vision-processor as default for RC27 and probably will not offer the SSL-Vision system as a backup option there. Therefore please make yourself familiar with the vision-processor until the end of this year's RC, as we would like to take the chance and speak about current hurdles regarding a vision-processor implementation at this year's Open TC/OC meeting and the roadmap for coming improvements. In case of any questions regarding the included announcements, please feel free to contact any of us. Thank you, David and Will. On behalf of the SSL OC and TC.

1 0