Quote:
Originally Posted by Dmentor
This thread seems to have veered onto a tangent. I can't comment on what occurred at Chesapeake but I wanted to confirm Kyle's statement regarding NASA/VCU.
At NASA/VCU, we continued to follow this procedure and it worked great until Q38 where we were once again immobile during the whole match. Of course everything checked out just find in the pit, but in the debrief with the drive team, the only deviation from the startup procedure that we used in the pits and what was used on the field was that when the DS was powered on for Q38 it was not in a disabled state (??).
Thanks so much to the NASA/VCU crew for ensuring that all the teams had the best possible opportunity to shine!
|
Good job on making it to semi-finals! I remember going against your bot in Q38. It started during autonomous at the outpost and did move; however, it stopped moving after our alliance partner collided with your bot. There was a huge collision with 3-4 robots around that outpost that match (if I remember correctly). The immobile part may have been caused by the collisions :S
Also, the DS does not need to be enabled or disabled. However, before you turn the robot on make sure it is disabled or enabled and on tele-op. The field judges are supposed to automatically turn each driver station on disable and autonomous at the beginning of each match (from what I have seen)