View Single Post
  Spotlight this post!  
Unread 10-03-2014, 01:16
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,113
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Possible FMS problems.

Quote:
Originally Posted by Canon reeves View Post
The big question that has me stumped is how most of these problems that yall talked about wouldn't occur off the field, even when we ran into the wall vigorously a lot?
One of your mentors asked me that several times, and my answer is still the same: running into the wall is a jolt in one direction. Being bumped by another robot from the side, or from behind, is another direction. If there's a loose connection that causes problems related to being hit, it won't necessarily show up with a hard impact to only the front of the robot.

The one time I was close enough to see the speed controllers' LEDs during one of the on-field episodes, the robot was definitely completely without power immediately after being bumped from behind. Some ten seconds later, a second gentle bump on the corner coincided with the power coming back on. Nothing in software or the field communication can cause that kind of failure.

Quote:
We only verified a D-link reboot twice, and that was on matches that we had definite battery problems. By no means am I an expert on any of this so please explain why it makes sense. Thanks for the input!
The D-Link rebooting was only verified visually twice (it was mounted on the robot such that the lights are only visible from a narrow angle of view). The real-time field data monitor showed a loss of radio communication every time I was able to watch, and the FTA says it happened every time your robot had a problem on the field, though the logs I was able to review were only clear about the cRIO reboot and were inconclusive about the D-Link (the Driver Station apparently doesn't ping the bridge during enabled mode, and the FMS stops recording when the cRIO is not responding).

The one "smoking gun" we identified was the intermittent SB50 connection. Right after that penultimate match, it was definitely easy to cause the robot to lose power by pushing on the red wire in the right direction. I understood that the connector was going to be replaced. Afterwards, when the robot had yet another verified radio reboot with associated logs suggesting a complete power dropout, I noted the same loose feel to the red wire's terminal. I didn't think to ask whether it was the entire connector and its wiring that had been replaced, or if it was just the housing, or if it was just the terminals and wires. It is possible that the red SB50 shell was reused, and that the underlying fault is that its "spring" isn't holding the terminal hard enough to the matching battery connector. Or it is possible that the terminal itself wasn't changed and has a bad surface that doesn't provide a secure contact.

Being unable to help 4490 correct the repeatedly-appearing problem is definitely something I feel bad about.
Reply With Quote