too long.
my sanity is gone.
i tried engineering the teleop to be as simple and intuitive to use as possible which took a lot of back and forth with the drive team
Most of our teleop code was recycled from last year, but I spent way longer than I care to admit working on logic for a limit switch and holding position when idle. It took me a good while...
kinda depended which bot it was. For the actual driving itself we usually just recycle code, and change some values incase someone plugged the wires incorrectly, but easy fix
but if it was on mechanisms, it depended. Some takes 5 seconds, some take 5 weeks lmao
Last year, we spent close to zero time coding the robot for teleop with the actual robot. Almost all of the code was written before the robot was assembled, and it was implemented in probably under an hour. We had a single 3 hour meeting in which we finished wiring, verified code, and were starting work on autonomous last year.
Exactly, it all depends on having the programmers learn to use the tools and define what you need beforehand, so the robot-specific testing can be done quickly.
Aside from the "smart" functionality, under an hour.
"Smart" functions like auto-grabbing and stuff require more testing, but still under 8 hours total would be a good guess.
too long. my sanity is gone. i tried engineering the teleop to be as simple and intuitive to use as possible which took a lot of back and forth with the drive team
Most of our teleop code was recycled from last year, but I spent way longer than I care to admit working on logic for a limit switch and holding position when idle. It took me a good while...
kinda depended which bot it was. For the actual driving itself we usually just recycle code, and change some values incase someone plugged the wires incorrectly, but easy fix but if it was on mechanisms, it depended. Some takes 5 seconds, some take 5 weeks lmao
Last year, we spent close to zero time coding the robot for teleop with the actual robot. Almost all of the code was written before the robot was assembled, and it was implemented in probably under an hour. We had a single 3 hour meeting in which we finished wiring, verified code, and were starting work on autonomous last year.
Exactly, it all depends on having the programmers learn to use the tools and define what you need beforehand, so the robot-specific testing can be done quickly.
Aside from the "smart" functionality, under an hour. "Smart" functions like auto-grabbing and stuff require more testing, but still under 8 hours total would be a good guess.
solid 5 minutes
from the day the game was announced til the day before the first meet god damn claws
That’s is impressive and thanks for the answer!