Our B bot recently completed at the first ARL qualifier, with additional code changes to hopefully improve accuracy. Sadly during practice matches we had some plates break which caused issues throughout the entire day.
Video: youtu.be/mmptuJ0MmTI
Code: github.com/TeamParadise/Celestial
Over the off-season, I've been working on improving the code for our main FRC robot (1165A), as the only programmer on my team (at the current time). The code before was extremely messy, with a lot of unnecessary code, especially after we decided to keep the arm in a static position instead of letting it move.
Over the off-season, I've worked to clean up the code, I've added new code to point the arm to the speaker and automatically shoot (unused due to the static arm), added brand new autos, and added new commands to shoot as quickly as possible. We recently competed at the first ARL (Arizona Robotics League) August qualifier, and were able to rank 2nd, and were the only undefeated robot during qualification matches. Although, there is still lots to improve on, as our autos were less than ideal and we had a lot of issues with shooting, but the code was run at the competition with a pretty high degree of success.
Example Match Video: www.youtube.com/watch?v=551T4-lM2ko
Link to our code on GitHub: github.com/TeamParadise/2024-Robot
I've created a fairly basic NixOS configuration for my laptop, using GNOME. It doesn't have many features right now, but it's fully functional with everything that is implemented, and I've been using it as a daily driver for quite a while.
Configuration is here, it's pretty simple, so hopefully, somebody might be able to use it as a starting point or for reference: github.com/UHDbits/nix-config
Screenshots of the basic setup are shown below
I've created code for our second FRC robot for the off-season, 1165B, also known as Celestial. This code was created 100% with AdvantageKit support in mind, which allows us to log a very high amount of values when on the field, allows us to review them, and allows us to replay the logs, making troubleshooting potentially a lot easier. This robot project was also created to use as little "time"-based code in general, which means, instead of speeding up the flywheels for a certain amount of time, and then shooting, we speed up the flywheels, wait for them to reach our desired speed, and once they do, then we shoot. Sadly, the robot wasn't very successful at the 2024 July Arizona Robotics League, where the code officially shipped, but we have rebuilt and are going again in around 3 days, so hopefully we should perform better.
Code Link: github.com/TeamParadise/Celestial
Match Example (worked mostly, had issues with accuracy at some points though. Hardware started having issues after this match): youtu.be/MBtHAzQgkLg
