Closed christinecho closed 8 years ago
I created this issue when we hadn't decided if we were going to use the beam break sensors. This was the thing where when I let go of the intake button, the rollers would go in the opposite direction for a set amount of time so the balls were not touching the shooter wheel...probably not that useful now that we're using beam break
Okay, I'll close this then.
did this maybe mean that the shooter should be backdriving in the beambreak command to avoid the smokey situation that happened at ship?
When I saw this I assumed it was referring to using the beam break sensors to score in the low goal and tell the drivers when the ball is scored. In reference to backdriving the shooter as part of the intake, I think you should strip that out entirely. Either that or bring some marshmallows to toast over those 775s.
Just had a quick question about the code that was added. Sorry I wasn't able to come today. I looked at it and it seems as if you've written code to override the beam break for intake and back drive, but we already had buttons for that (our intake and back drive buttons on the operator joystick override the beam break). In terms of what Dan said, I think a good solution would be to print on the driver station (if possible) whether the ball is in the robot or outside the robot. Thanks!
On Tue, Mar 8, 2016 at 8:33 PM, eburnette1 notifications@github.com wrote:
Closed #25 https://github.com/gatorbotics1700/Robot-2016/issues/25.
— Reply to this email directly or view it on GitHub https://github.com/gatorbotics1700/Robot-2016/issues/25#event-582760770.
Christine Cho Class of 2017
@christinecho wait what does this mean? is this for the intake?