Basically titles, its out team's only drawback.

My team is using a LinearOpMode op mode and they've got a speed variable that is a public static volatile double. The variable shows up in Panels, but when they change it, it seems to have no effect. They've verified the variable isn't changed using telemetry.

They are using the variable in a loop in the runOpMode method and I'm wondering if this is known not to work.

Another question is should updates survive after stopping and starting the op mode?

Thanks

When I shoot the last pollens are missed bc of the intake/transfer backspin, but atp we cannot afford a counter roller like Astra machina has so I thought about adjusting the angle of the hood dynamically using this formula

Do you think it will work or nah?(Yes we have counter rollers on the shooter so the balls won't get out but the trajectory is still affected)

Se FTC y la mayoría de lenguajes de programación y si no lo aprendo no pasa nada tengo 15 años de edad y 6 años de estudio de programación son campeon de FTC y tengo el connect awart con mi equipo de FTC CETROB

To all FTC teams running practice matches, here is a recording of the official BIOBUZZ scorekeeper timer for the 2026–2027 season:

https://www.youtube.com/watch?v=bu-fyXAcD9M

Why is this video better than the top Google hit? As far as our team has found, even videos claiming to be BIOBUZZ timers don't have the 1:00 chime. We recorded this video recently from the official FTC scoring system, so it is the same exact timer you will see at a meet.

Want to run the scoreboard yourself? Follow FTC's install and use instructions.

Scoring setup manual: https://ftc-resources.firstinspires.org/ftc/event/scoring-setup

Installation page: https://event-portal.firstinspires.org/ftc/2027/local

Wishing you a fantastic season!

We’re planning to build the goBILDA StarterBot this season, but I’m looking for advice on how to move forward after that.

Last year, I was the only person on our team with previous FTC experience, so we built a starter robot and competed with it without making any significant modifications. This year, only about half of that team is returning, and even the returning members are still learning. We’re basically still a rookie team in terms of our design and building experience.

I want us to go beyond just following the assembly instructions this year, but I honestly don’t know how to make that jump. Once we have a working starter robot, how do we figure out what to improve and then actually design those changes?

We also have a limited budget, so I’d like to reuse as many parts as possible and plan upgrades before ordering extra components.

I’m a parent coach for a community team. The boys had planned to use a hybrid of blocks and Java this year so more members could contribute, but we just learned today that the pedropathing they want to do won’t work with any kind of hybrid code.

Does anyone have a resource experienced block coders could use to get comfortable with Java? Unfortunately, our blocks coders aren’t scheduled to take the AP Java class until next semester.

Based in Toronto area.

Is this idea feasibile or is it just asking for a disaster/inconvenience?

okay so this isn't the first time I've tuned PID/FF, also not the first time for a shooter so I have some experience. But for some reason this year I cannot seem to get anything to work. I spend 10 minutes tuning for 1 velocity, just for it to overshoot when increased or undershoot when decreased. Then I tune for that and now its out of sync with every other setpoint. I've tried pure PID, pure FF, both, nothing wants to work. Also is it normal for any "D" value to completely make the motors go haywire? Or for the "I" value to continue increasing even when past setpoint? I don't know, never had these problems in the past. Other things to note, I had something kind of working a little bit ago, but then we geared our shooter motors 2:1 for more torque and it seems we have these issues. Also while typing this I've realized the angle the motors and wheels are on might mean gravity is adjusting them... Any help would be appreciated. Oh and if anyone asks I'm using the basic PIDController library along with SimpleFeedForward.

Our team is competing at today’s Kentwood, MI qualifier. Apparently the format for judging has changed. Instead of separate scheduled times for the teams to appear before the judges in a separate room, apparently judging will take place in the pits.

After 9 seasons of competition at multiple different qualifiers and state championships, this seems like a big change and one that came with no advance warning.

Is this something that’s happening across FTC? Is it just a FIRST in Michigan thing? Any insight as to why the change?

One of the things we’ve always valued about FIRST (compared to other robotics formats) is the broader focus on non-technical skills and professionalism. Losing the separate judging seems to be a significant change in the spirit of FIRST, and not a positive one.

In trying to teach my programming team about field coordinate systems (and how they're used for field-centric navigation), I came across this document. Granted, its copyright is 2025 and the most recent field is shows is DECODE, but it suggests three field arrangements:

• Square. In my head, I equate this with "normal." Red Alliance and Red Wall are to the right from the audience's POV. The Red portion of the field in autonomous is adjacent to the Red Wall. Positive X is away from the audience. Positive Y is towards the Blue. The field they use as an illustration is from INTO THE DEEP.

• Diamond. I've coached FTC for 9 seasons now, and we haven't had one of these in those nine years. Field is at a 45º angle to the audience. Red Alliance has the right side of the field (seen from the audience), and the Red Alliance Wall/ stations is on audience right and away from the audience. Positive X is away and to the left from the audience POV. Positive Y is toward the audience and to the left.

• Square + Inverted Alliance. The document shows DECODE as an example, where the Red Alliance station/area is to the audience left, while the Red portion of the field is to the audience right (I figured they did this for better visibility near the goals). Positive X runs from the back toward the audience. Positive Y runs to the audience right.

But… In thinking about the field for BIOBUZZ, it would seem that we have a fourth option:

• Square + Inverted Alliance Station & Field Area. The Red Alliance Zone is to the audience left, and the Red Alliance share of the autonomous field is to the left as well. I can't find anything anywhere that definitively says which way the axes are oriented on this year's field, but I'm presuming it'll follow DECODE's pattern—even though the areas of the field each alliance controls follows a different pattern.

My real question, though, is whether there's any "normal" any more.

• Last year's "inversion" makes sense if they did it for visibility reasons—though they could have chosen to keep the Red Alliance station to the audience right and put their portion of the field on audience left.

• So… Why is BIOBUZZ somewhat inverted and not the same Red-to-the-Right that almost every other game in recent memory has been?

Do you guys know what are the best software to work with?? i've heard about road runner and it works AMAZING for me. But im not really into ftc so i wanted to know if theres anything else i've been missing out

(fyi this is in roadrunner) So basically I'm working on assembling the paths and subsystem actions for my team's auto. My team wants my auto to be pretty versatile and ready for a lot of situations in case the robot misses a shot or our teammate's robot like spontaneously combusts and isn't active during auto. So I decided to use a LinearOpMode so I can just use basic if statements in order to branch out which path I'll run with Actions.runBlocking(). And I kinda want the flywheel of the shooter to always be running to a regression that my teammates made, so I don't have to waste much time waiting for the velocity to adjust. So I'd want my turret constantly setting the velocity to that regression while all the branches are running. Unfortunately, I don't think I can put my entire path tree in an action, with all the if statements, to run inside a parallel action with the turret adjusting its velocity.

So that's where I got stuck.

I considered multi-threading, but like idk how to do that, and I also heard it's advised not to do that either.

If there's any way to have my turret constantly adjust power in the background while the if statement tree runs simultaneously, that'd be great.

Tuning normally only this time when we ran the RR angular ramp logger opmode and instead of getting a regression when we clicked "latest" we got this error "0 !== 2008". Did it multiple times and got a different number each time. downloaded the .json and then tried with the file still got same error.

We're Alphire, FTC team 26456. For most of our practice time we were just using a phone stopwatch and a whiteboard. The whiteboard kept getting wiped, nobody remembered which run was actually the good one, and we never had the real match sounds. Working out ranking points and flower ownership by hand in the middle of a run was also a mess, so we built a web app to handle it for us.

​We cleaned it up and put it online in case other teams want to use it this season: www.pitpad.app

​Basically, you pull up the arena scoreboard on a laptop or monitor and it runs auto, transition, teleop, and endgame with the official sounds. From there, you scan a QR code or type in a PIN on a phone or tablet to use it as the scorer (tapping hive tips, flower changes, fouls, and the post-match check). It supports 2v2, 1v1, 1v0, and 3v0 setups, plus a ghost score option if you want a target score to race against.

​A few other things we built into it:

​OPR calculation for 2v2 scrimmages, plus solo practice stats (average score, cycle consistency, auto success rate, and how close you were to each ranking point)

​A 60-second hive tip sprint, a 30-second endgame park drill, and a field reset checklist

​A manual training log for tracking things like auto pathing trials or driver drills with notes, plus CSV, JSON, and printable exports for your notebook

​Dark, light, and high-contrast sunlight modes (handy if you're testing outside or in a bright pit), and 10 language options

​You can open the arena display right away to mess around with the scoring, or create a team account if you want to save runs and track stats over time. It's still a team project, so if something breaks or scores weird, please let us know.

I am from an FTC team in Ottawa, Canada. I am just trying to see if anyone in this sub has and would be willing to sell their limelight. Price and shipping is all negotiable. Getting a little desperate since the chances of them restocking this year are slim.

oo my god

Tudo é penalidade

Hello, our team has been having issues with the intake on our GoBuilda Starterbot for the BIOBUZZ 2026-2027 season. I'm hoping you can share guidance on what we can try and whether anyone else has had issues with this starterbot's intake. Our main issue is that when approaching the pollen, we can't get the pollen to go in. We find that it will only work when we push the bot against the wall, so basically using it to guide the pollen into the intake. We have removed the white bar after testing whether it was beneficial or not, and we have created a front ramp to try to guide the pollen into the intake. Despite these modifications, the intake is still not performing as it should. I would really appreciate any help.

Hello! I am working on a project and collecting feedback from FTC Teams! If you can, please fill out the form below! Thank you!

https://forms.gle/6B8F8XPpqqkbx8HZ6

Recently, my team and I were tuning the "PedroPathing" system to create autonomous routines. However, we ran into an issue during the localization test: even when we set the target distance to 2 inches (the standard is 48 inches), the robot just keeps moving indefinitely. Does anyone have any idea what might be causing this?

I care a great deal about *Strategy*. I mentioned a lot of observations in my previous post https://www.reddit.com/r/FTC/s/kR6tMPF9fD about what I am seeing in early competitions and people added great insight.

But that was mainly focusing on scoring robots. Now, I get it: it is still early in the season and not every one has a fully working robot, that's fine! But if you find yourself in a match driving a robot that is only capable of moving around the field, there is more to life than just smashing your opponents.

Not to say that defense is bad, I just want to see teams get more creative and strategic!

• One option would be to put a stick on your robot so you can go around and empty out the flowers for your partner. More pollen = more points!

• If you have a collection but not a shooter, send pollen to your half of the field or a pre-determined place for your partner by pushing or rolling it!

• I have seen a lot of teams avoid pollen because it is next to nectar and at this stage people aren't capable of handling an accidentally ingested nectar, so that can be a push-bots job: move nectar out of the way! Put it on your garden tape for at least some points.

I bring this up because I will see teams that either have a broken shooter or no shooter trying to push their opponents out of prime shooting spots, but this frequently backfires and crowds or bumps their alliance partner who is lining up to score. Or, I will see two opposing teams that both have non-working/non-existing shooters pushing on each other for the sake of defense and counter defense: if we defend each other, that means our partners are free to score! While counter-defense is a move, I think there are more ways to help out than locking horns with another non-scoring robot and turning the match to a 1v1. I have seen matches where there is only 1 scoring robot and the partner of that robot is aimlessly bumping their equally aimless opponents!

I say all of this because according to the ranking system: the incentive is to get as many tips as possible, not slow down your opponent's scoring. According to table 13-1 ranking is first based on average ranking points, and ties of average ranking points are broken by average alliance scores. So yes, you want to win and get 3 ranking points, but you also want to get a high score to break any ties and you want more RP. So, trying to get the tipping ranking point(s) is more important to the rankings than trying to keep your opponent's score from increasing. Plus, risky defense occasionally brings in penalties that could swing the match.

Playoff matches are different, go crazy there with the defense if you want.

My team isn't sure what localization to use. We are a rookie team so no previous experience and we are having to make large changes to other portions of our bot before next comp so no clue how budget will look. We want to use pedro pathing so would prefer ideas that are compatible. My current ideas are the SparkFun OTOS or just motor encoders. Obviously i would prefer two dead wheels with a pinpoint but i don't think we can afford that. I am looking for suggestions, other ideas, or just a vote on which of my options to choose.