Quote:
Originally Posted by Al Skierkiewicz
OK here goes a list of problems and fixes...
...snip...
|
This is a great list, and pretty much the way I trouble shoot robots at competition with "loss of COMMS".
I will also add, Check the Ethernet connection on the laptop. IE, give it a wiggle. I found this was the source of intermittent comms drop for a couple teams at Centerline this past weekend.
This laundry list of items shows why it is such a frequent problem. While the folks at CTRE and NI and FIRST have done a great job at reducing the possible Idiot proofing, there are still so many ways that you can get an issue that low probability of many many things turns into a reasonably high probability that something will get you.
I.E. a 10% chance on any one item, but 10 items with that 10% chance turns into a pretty high probability that something will go wrong.
Pro-tip, when forming your alliance, ask if you can go through your partners robot with a fine tooth comb, and ask them to do the same for you. Often an extra set of eyes can help find issues and errors. Make you own checklists and review them often. Not sure what to put on the list? How about the good advice being dispersed in this thread.
These events the robots are going over are pretty violent. Even the weight of a wire or cable flopping around can be significant when the robot see a 20G pulse (1 lb acts like 20 lbs). Proper restraint and strain relief goes a long way.