Originally Posted by SlimBoJones (Post 833030)

This was a brilliant move. We simply got baited into an extremely vulnerable position, and paid for it dearly. It was a perfectly executed reversal, and cost us the match.

I made the call to try and score on 3015 as they were stationary at their own airlock delivering an empty cell to their payload specialist. Normally you'd think this is a good opportunity to strike a stationary target...

We thought so too, and it ended up costing us the match.

Great work 3015, 2053 and 3003! We learned a lot that match, and that sometimes the best shots in Lunacy are the ones you DON'T take :P .

Originally Posted by esquared (Post 833420)

1503's Robot Signal light would go fully out, then blink fast, then come solid again. Once they began to try driving again, the RSL would go out, blink fast, then solid again over a period of roughly 30-45 seconds. While they were located at what was eventually found to be a faulty console location, the robot symptoms they experienced are not possible if the robot was being E-Stopped intermittently. If that was occurring, their RSL would be solid, then go to a slow blink, then solid. If it was an intermittent radio communication issue, the RSL would have gone into a fast-blink mode if the bridge lost contact, then come back solid once regained. I spoke with 1503 immediately following that match, and their drivers agreed that the RSL was doing precisely as I explained above. We then powered up their robot, and showed them the process the RSL light goes through after a reboot. While the robot was on, I showed them what would happen if the radio modem power/ethernet was pulled loose/plugged back in, and the process was also as described above. They seemed satisfied that the symptoms of their robot out on the field matched a poweroff/poweron rather than an E-Stop.

To the robot, the E-Stop button is a disable/enable condition no different than using the dongle normally attached to the competition port. This was evident from the match in finals where the faulty E-Stop was diagnosed. Team 188's robot would sit with their RSL light slowly blinking. This indicates a successful link with the Driver Station, either through the field or when tethered. If the E-Stop was rapidly toggled/intermittent, 1503's robot would have been going in/out of enable mode, thus the RSL would be solid/slow blinking.

I regret not having the chance to follow up with 1503 to determine exactly what their situation was once they were in the pits. If anyone from 1503 could contact me/post if you found anything specifically wrong with your robot following that finals match it would be appreciated. I can add your situation to a list of common robot 'gotchas' being compiled.

Originally Posted by Pat Fairbank (Post 833550)

I'm afraid we found nothing. We checked every terminal and every wire from the battery all the way to the cRIO. We then tethered up and drove the robot around (with the same battery); it worked fine. We rammed it repeatedly into a wall to see if there were any loose connections to dislodge; nothing. We always run electrical checks between matches, and we always zip-tie our battery connectors, and we didn't experience a single electrical problem at FLR up to that point. I guess I don't believe in coincidences...

Originally Posted by Coffeeism (Post 833578)

Everything seemed ok... The only think I'm scratching my head about is the one time our autonomous did not go off.

Originally Posted by esquared (Post 833562)

If you were able to watch the robot's operation from your position in the audience/driver station, do you agree the Robot Signal Light was behaving as specified in my post? I'd like to have everyone on the same page regarding robot symptoms to ensure that NI/FIRST have accurate information regarding what happened.

Originally Posted by Bongle (Post 833596)

Which match did this problem occur in? I wasn't able to watch the finals, but someone else on 2702 managed to go down at take some HD footage of some of the quarterfinals. I might be able to pass along some footage if I can find this problem occurring in what I have.

Originally Posted by Kricu (Post 833549)

I'm not going to lie you guys were a great alliance. You definitely deserved to win it all. I did cry a little bit when 174 changed their autonomous so it turned in the beginning so we couldn't pin them from the start. I'm glad we taught you not to get stuck in the corners and to make sure you didn't get pinned during the autonomous so I could score 15+ shots on 174. Anyways nice job winning it.

Originally Posted by esquared (Post 833585)

Depending on whether all DS's are detected during the initial match setup (before robots are out on the field for the next match), the FMS seems to briefly toggle through Auto-Disable, Auto-Enable, then Auto-Disable as it sets up.

Originally Posted by esquared (Post 833599)

QF3 Match 2

Originally Posted by petek (Post 833611)

According to FIRST this is not the case.

Originally Posted by Bongle (Post 833617)

I have it, but I only have a stable shot of 1503 and their RSL for 5-10 seconds total throughout the match. The camera man was concentrating on the moving robots, and would only glance at 1503 periodically when they were not moving. If you think it'd be useful, I could edit the 1503 portions tonight.