I somewhat agree with the idea of posting communications issues to the scoreboard. It would be a great asset to scouting to be able to tell the difference between "That big hit happened to knock out the robot's comms, freezing it on the field" and "That big hit broke their drive train. Probably not the most robust robot out there". However, it still works out without it since I usually end up being able to tell the scouting team where the problem is just by the DS status lights and the RSL (I've become very skilled at identifying low batteries after our attempts at adding a ball magnet drained our battery 30 seconds into a match
).
I think what would be more useful is if something was put out by FIRST that explained what all of the publicly visible status lights meant. At the moment, things like the team light is completely undocumented for the average FIRSTer. Of course, even the documentation that is there isn't usually read (I'm one of 3 people on our team who know how to read the RSL, even though I've explained it to them many times
)
__________________
"To have no errors would be life without meaning. No strugle, no joy"
"A network is only as strong as it's weakest linksys"