Greetings and welcome to the 5887 Imperator build thread 2024. Founded in 2016, Crescendo will be our 8th season on FRC and our first year on The Open Alliance. We are excited to start sharing all our robot, impact and managing process throughout First in Show.
FRC Team Imperator 5887 is a high school robotics team based in Tecnológico de Monterrey Campus Puebla. Founded in 2016, our team not only competes in the First Robotics Competition, but we also focus on inspiring younger generations to pursue success in STEAM areas regardless of their age, gender and origin. As a team, we believe that science is for everyone! Membership is open to all high school students in Tecnológico de Monterrey Campus Puebla.
Imperator's resources:
2023:
Events attended:
- Regional Monterrey, Rank:#9/42
- Regional Puebla (Hosts), Rank:#8/35
- Mexico All Star, Rank:#18/42
- Tidal Tumble Rank: #20/42
Quesillosauro:
Quesillo is the robot we developed during the offseason and is the best robot we've developed so far. Is the robot which got the best out of every area and everyone in our team
Podcast:
One challenge, six robots, one field. Two and a half minutes filled with pure fun and adrenaline. The goal: spread science and technology, make friends, help your community, and learn that together, we can change the world. Welcome to BEYOND THE ROBOT, a podcast co-produced by Imperator 5887 and Micelio Media about the stories behind the FIRST community; because this isn’t just a competition, this goes beyond the robot.
2024:
We will be attending to Regional Monterrey in week 1 as has been the case for the last few years, and we are hoping to attend to a second regional, Arizona East Regional in which we are currently in waitlist.
2 Likes
Week 1 update:
Pre Kick-Off
Scrum/Agile
- In order to have a good planning and workflow for this season, we opted to use the Scrum Agile Methodology. Scrum is an agile team collaboration framework commonly used in software development and other industries. Scrum prescribes for teams to break work into goals to be completed within time-boxed iterations, called sprints. Each sprint is often no longer than one month but we decided to divide our whole building season in weekly sprints. Scrum is often used in software development and for big but quick proyects, so it was easy to implement it on FRC.
- As well we also do a Daily Scrum Session, where we put a timer with 15 min (so we don’t extend the session) where each of the development team leaders reports:
-
What did your team do today?
-
What will your team do tomorrow?
-
Is there anything blocking you?
Prototypes
- We divided the team into 6 teams, 3 teams that did a shooter protoype and the other 3 which did an intake prototype and on saturday we decided which things we can take out of each prototype. Here are 2 of our prototypes:
Scouting:
- Hi everyone! As a little project of our scouting area to make the manual easy to understand for the new members who are not in touch with FIRST’s previous games, we created a Handbook, covering what we consider to be the most important aspects of this season’s game:
1. Game overview and objectives.
2. Game timing breakdown.
3. Arena (and close up to every scoring item)
4. Scoring (and scoring glossary)
5. Game Rules (new rules and previous season’s rules).
Here’s the link which will be updated with along with further manual versions.
https://www.canva.com/design/DAF51JA_ZIs/AjSRRQkDBxEhq8m9tSU_hg/edit?utm_content=DAF51JA_ZIs&utm_campaign=designshare&utm_medium=link2&utm_source=sharebutton
Additionally, we will endeavor to carry out a weekly manual review using Nearpod. There are 44 points in total, 3 draw it, 2 fill in the blanks and 2 quizzes.
Here’s this week’s Quiz!:
Programming:
Since this week was mainly prototyping, it was difficult to get members working on software, either way a couple of things were done:
- For any mexican or spanish based team who can make a use of it, we made a presentation indicating everything you need on your computer to start programming for FRC:
-
Since this year we got our second Limelight, we wanted to try implementing pose estimation. We succesfully configured our limelights with the Photonvision image and started doing our first tests and researches
-
We started planning our first autonomous paths by drawing them and drawing them in pathplanner in our Crescendo repo for when we got our chassis ready, we can implement first the swerve routines.
Field:
- Thankfully we finished the building of the field with the exception of the stage, and pasted all of the april tags so our programming team can work with them properly
Media:
- The Media team kicked off their season with new members! The new members got up to speed on the skills needed for video production and documenting the team’s progress throughout the season, culminating in the release of their first complete Instagram reel on Tuesday of week 2. The team also prepared for the release of the next season of Beyond the Robot, with the first episode scheduled for a 17 January release on Spotify and Apple Podcasts.
That is a wrap for our first building season week of Crescendo, we are so ready and excited for what it's about to come, so bring it on.
1 Like
Week 3 update:
CAD:
- During this week, we had the opportunity to complete our robot’s CAD, which consists of a 2-wheel shooter, an intake, a structure that loads both mechanisms, and our swerve chassis. This design was determined by prioritizing this year’s game tasks. As a team, we prioritized shooting towards the speaker and passing under the chain to achieve faster cycles. Therefore, next week, we will cut the robot pieces with laser in order to start the assembly.
- In the meantime, we are also finishing our climbing prototypes and since the climbing is almost last on our priority list, we’ll take advantage of our pneumatics sponsor and we’ll do a simple but effective hook for our climb.
Programming:
-
So this week we started on the wrong foot but we managed to end our most perfect week yet. Starting the week we realized the new update on Pathplanner, so we had to translate our code to the new Pathplannerlib features. When we started to test it, it didn’t work quite well, the robot’s field was wrongly oriented, the distances were not even close to accurate among other things that went wrong with the chassis.
-
We re-read our whole code and noticed a couple of things that could’ve been wrong, so we opted to try YAGSL but it also didn’t work for our robot, we kept testing with pathplanner trying to fin any kind of precipitated solutions but nothing worked. So while reading YAGSL wiki, we noticed that in order for swerve third party solutions to work, all angle motors on the modules, should increment while spinning counter clockwise. Surprisingly, we corrected that on our code and pathplanner worked amazing, so we started working immediately on basic auto routines.
Here you can see some of our tests:
https://drive.google.com/drive/folders/1iaw4lMcUBg4OYky4xf08olLT3EzB-hf5?usp=drive_link
-
Parallely, we worked with the rev color sensor and started by just getting a few color values in Hexadecimal and then into RGB. We used a basic timed skeleton code to simulate a note, entering our intake and activating just a motor and it worked perfectly, so done with that.
-
Additionally, since this year we want to use Pose Estimation on our code, since week one we migrated our vision system to Photon Vision so we remade our previous practices made with the default Limelight UI. For an instance, we started with chasing an april tag with PID controllers:
Next week we will be working with 3 main things:
- Pathplanner event markers
- Pose estimation
- Pathplanner Target rotation override
If anyone has any helpful tips for this topics, we will be deeply gratefull
Scouting:
- This week, our scouting team focused on making the first draft of our in-event scouting system.
We settled the base of our info compilation drafts by getting to re-visualize our goals for the game and determining the aspects of robots in competition we find more versatile to create strategies and possible alliance partner profiles for playoffs.
This season we are striving to launch a web-app for our scouters to gather data more efficiently, as well as implementing a more refined data analysis to generate accurate strategies and facilitate the process of alliance selection!
The web development team gathered with our scouting and data analysis team and started to have a think about how we will capture, display and further analyze our data.
Our task for the week was to generate possible app layouts which may be accesible for the user, efficient in gathering data and simple to materialize for our back-end developers.
- Right now this is just a framework template, and since our developers are new to the whole devops practice, they are still working on back end testing.
Media:
-
This week, the media team continued to ramp up its production of social media content, alongside welcoming three new members! These tasks went hand-in-hand with the opening of our new TikTok account (@imperator.5887), and the ramping up of social content production will be critical to cover our regionals in detail and at the necessary speed.
-
The graphic design team continued work on finalizing the designs of team uniforms, pitlane materials and other merchandise in preparation for the season.
And that’s a wrap for our third week
Any recommendations for all areas are well welcomed!
6 Likes
