[kylelanman]

@rspurlin

Perhaps you could provide me with a little more insight. What you just provided was great.

The light on the alliance station, what does this indicate? Our RSL light was indicating normal operation while our alliance light was flashing. A few seconds later the RSL started flashing too. Our assumption is that the classmate lost comms first and then when the robot noticed the classmate was gone it disabled itself and the RSL updated to indicate it was disabled.

After this happened logging out of the Driver profile, into Developer, running arp -d, logging out of developer, and back into driver gave us comms for a few seconds. I'm hoping you can answer this question. Does the system allow a team to logout in the middle of a match if everything is connected correctly? I was not on the field but was told that they tried this in an earlier match and it did not let them logout.

I have 1 final question as to how the FMS is setup. I kinda assumed from day one that the FMS controls the robot. When allowed the classmates send signals to the FMS that get forwarded to the robot. Or is the FMS setup so that the classmates control the robots directly and the FMS send signals to the classmate to change the mode (teleop, auto, disabled)? I understand physically how the network is setup I asking from a logical stand point.

Here is scenario 1.
Classmate ---- FMS ---- AP ---- Robot
FMS ---- Classmate ---- AP ---- Robot



A bad cable between the driver station and the switch or the alliance switch and the main switch is my theory. We only had comm problems on the red alliance. I have come across plenty of network cables that provide partial connectivity.