On today’s FIRST Updates Now stream, there was discussion about desiring an uptime counter on the roboRIO, with the example given of a roboRIO losing communication being identified by field staff as the roboRIO rebooting, without it actually rebooting.
While wpilib doesn’t expose an uptime counter in the roboRIO, the driver station log will show you the time since reboot when the FRC_Netcomm task loads. This can be seen on the following page on frc-docs:
Using that, and the code starting notification, you can determine if the roboRIO rebooted, the code restarted without a roboRIO reboot, or if communication was lost for another reason (like a bad Ethernet cable).
There was also discussions about the FMS log. The DS log actually logs much more then the FMS log, so as a CSA my first choice is to look at the DS log. The only things (that I remember) that are in the FMS log that aren’t in the DS log are the bandwidth and trip times.