Originally Posted by Jimmy the Kidd (Post 1147944)

This is my exact line of thinking. I maybe looking into this too superficially, but when we don't work, it's when there are people in the crowd. Most of them are tech savvy, gadget toting people. Is it wrong to hypothesize that the root of our problem is as Dale says?

Originally Posted by dez250 (Post 1147956)

Is there an update on how 364 faired at connecting and working during practice day at Lone Star?

Originally Posted by Natchez (Post 1147727)

Ryan,

Thank you very much for the kind acknowledgement BUT, for the record, I was only one of very, very many that helped get the ball rolling for Fusion to have an opportunity to compete at Lone Star. With that said, it is a pleasure helping a team with such a rich history of helping others.

----------------------------------------

Everyone,

For the most part, this has been a good discussion along with good input BUT we still don't have a good answer for what has happened much less a root cause for 364's problems. The Lone Star Regional is very interested in helping 364 and FIRST determine the root cause of these problems. In this spirit, please keep posting ideas of what we should do at the Lone Star Regional to help troubleshoot this problem; we will develop a troubleshooting flow based on everyone's input.

Unless we get a better idea, our first test will be to unbag 364's robot on Thursday and attempt to hook it to the field (e.g. take robot out of bag, put battery in robot, get WPA key, etc.). We also intend to get other robots that have successfully connected at other regionals (57, 118, 231, 418, 624, 653, 1429, 1477, 2415, 3335, etc.) to test their field connections and so we can also have 6 robots connected at the same time. Depending on these test results, we probably have hundreds of options for what the next test should be; if you have any ideas, we'd like to hear about them and we don't care how silly they are (e.g. if 364's robot has no problems connecting, ask everyone in the arena to start turning on the wireless on their laptops and call their mothers from their cell phones to see if we can get 364's robot to shut down ..... if 364's robot will not connect, reconfigure 118's robot to look like 364's robot, use 364's bridge and see if 118's robot connects - the regional may even supply a "Basic Bot" that we can reconfigure). I will guarantee you one thing, our FTA will take everyone's input and will have a rock-solid troubleshooting flow when he walks in the door on Holy Thursday.

Thanks & give us your troubleshooting ideas,
Lucien

Originally Posted by bduddy (Post 1148058)

As a mere field reset volunteer I don't have many details, but St. Louis was having a ton of connectivity problems on Thursday... far more than I remember from the last couple years.

Originally Posted by BrandonHiggs (Post 1148158)

Changing the PD board is at the top of our list. It is the only piece of hardware that we did not replace at Bayou.

Originally Posted by Natchez (Post 1154478)

Everyone,

Thank you very much for your ideas & input. We will be documenting all of our testing that we conduct at the Lone Star Regional and will share it with you here.

Let the Problem Solving begin,
Lucien