Quote:
Originally Posted by David Brinza
"No Comms" is not a DS problem - it's a failure of the link between the robot and the field wireless access point. Unless ALL of the robots lose their links in a match, the problem lies within the robot.
Here are some likely causes of the problem: unplugged or intermittent power/ethernet connections, burying the adapter in the robot, problem with the wireless adapter +/-12V supply from the PD module and mounting the wireless adapter such that the security button gets pushed as the robot is bumped.]
If you momentary lose the wireless adapter, it can take up to 45 sec for the robot to get synch'd with the field - very painful!
|
We eliminated all of these trough inspection and troubleshooting at the match. ALL electronics were mounted on lexan...3 different ethernet cables were tried with the same results...2 power cables were tried with the same results, PD block was changed, receiver mounted on top of robot on lexan with the same result, security button protected...I literally beat my head on the robot with this one. It is sad to see what the students built fail because of something they did not build.
On a side note, we were also told about the 45 second "re synch" however, during our final elimination, our bot lost coms at the beginning of the match and NEVER regained comms for the rest of the match...about 1:45...so I don't buy that either.