Hi folks, one of the mentors from 488 here
During our second quarterfinals match at the PNW DCMP, we got disabled for about 10s due to a connectivity loss between the Robo RIO and the DS. We’re trying to get to a full root cause of what happened so we can make sure it doesn’t happen again, but I’m a little stumped by the logs here.
The logs from our RIO pretty clearly indicate that for 10s during the match, the RIO lost connection with the DS, but still had a connection to the FMS.
[no DS, FMS, disabled, Elimination 7 1] ... | Disabled init (Red3, 63.0s, DS disconnected, FMS connected, Is disabled: true, Is enabled: false, Is auto: false, Is teleop: true, Is test: false, Is browned out: false, Is output enabled: false, Battery voltage: 11.800892333984375)
On the DS, we see agreement that the DS cannot connect to the RIO:
Warning 44004 FRC: The Driver Station has lost communication with the robot. Driver Station Ping Results: link bad, DS ratio(.4) GOOD, robot radio(.1) GOOD, roboRIO(.2) bad, FMS-GOOD... Warning 44003 FRC: No robot code is currently running. Driver Station
After that match, we had a CSA go through the driver station logs with us, and he was very helpful in explaining to us the DS logs, though he didn’t have the RIO logs available to him at the time.
The CSA’s suspicion was that there was a network wiring fault between the RIO and the radio on the robot, which makes sense given the DS logs, but warning 44003 didn’t make sense - we’ve got one of the slowest robot code boot times in the league (if not the slowest). 10 seconds of disable was way too low for the code to have restarted.
I will also note that the drive team observed after the match that the ethernet cable fell out of our drive laptop when they picked it up, suggesting that connection could have been loose.
Now that we’ve also looked at the logs from the RIO itself, we’ve confirmed that the robot code was in fact running the whole time and didn’t restart.
Is it a known issue for the DS to erroneously report error 44003 if a component loses network connectivity?
How could both the RIO and DS continuously report the ability to connect to the FMS but not each other? (I have some theories for this one, but I’m curious if other teams have seen similar situations.)