[mototom]

First, thanks everyone for helping out with this issue, it has been pretty frustrating for us and we just want to make sure everything is working ok.

Second, forgive me if I don't quote or post properly formatted responses as I am not a CD maven.

So, just to update what happened next.

Quote:
Originally Posted by Landonh12 View Post
I'm volunteering on Carver. Usually when we have a connection problem the FTAs go out and fix the issue almost immediately. I don't think we've seen one disconnect during a match so far.

There have been a couple of times that the connections have started to freak out, but not during a match. We're sorting it out.
The Pink team's last match they died and then came back.

I saw that match and went and checked their driver station log and they did indeed disconnect during that match. They did not experience a brownout, and I did not troubleshoot anything on their robot, nor do I know if they experienced any further issues.

Possibilities I can come up with for just on the robot itself:

I cut off the list to save space. We did indeed check all these things. We have a pretty solid electrical engineering mentor who is fanatical about his team's wiring and they had gone over everything. We detect brownouts in our code because our encoders might reset, and we checked the DS logs and saw no evidence of that. The ethernet port has a pigtail on it, but again, we have not seen this issue in the pits, any of our prior regionals, or in any of our prior matches. Our RSL stayed solid the entire time.

The bottom line is that our last three matches of the day were all on the red side and we experienced NO ISSUES during that time after having made no changes to our robot or driver station.

Just watched match 103 which 329 was in and didn't see anything out of the ordinary other than the dance in auto, which I'm assuming is intentional.

Yes, we were on the red side, and our robot was the last to connect, and our sendable chooser that picks our autonomous mode did not come up until the instant before the match started and our drivers were unable to pick the correct autonomous mode. We have since changed the default autonomous mode to be the one we intended on using from now on. So, the dance, while not intentional and perhaps amusing, was not related to this issue.

Robots losing connection during match is not a field fault. It is a driver station or robot issue.

While I agree that this is usually the case with one robot having connection issues at multiple drivers station. When many robots seem to have it at one driver station or one alliance side, then it makes me question whether this is isolated to a single robot, especially this late in the season when all of these robots have been connected to the field dozens of times before.

A big shout out to the FTA who was there for us during our last match. (Sadly, I do not know his name, or I would mention it here) He made sure we had the time to get our sendable chooser and select our autonomous (although it was already fixed). He also stayed right by us the entire time with his tablet making sure everything was running smoothly for us. That was terrific and we really appreciate that! He reported no issues to us regarding any of this.