This issue is a container to document things we may want to log. This issue should be left In Queue until we're satisfied that we won't add any more logging. (E.g. after competitions.)
Please help keep this list up to date.
Currently implemented:
(Text) Software version, match info, robot mode, command start/stop, RoboRIO disk usage
GyroSubsystem: GyroX, GyroY, GyroZ (inadvertently removed in 40bfc32)
Robot acceleration: X, Y, Z, Total (not merged)
Consider implementing:
Robot velocity - so we know how fast our robot moves (maybe temporary?)
Possibly also log peak velocity - only needs to be updated when the speed exceeds the peak. This would primarily be a convenience to help in graphing the max velocity. It may be desirable to average the velocity to filter out spikes due to play in the drive train, before logging the peak velocity.
Left and right drive train encoder values. This might allow us to replay the robot's motion, at least in autonomous. This would require that the encoders are not being reset by any commands, or any other code. That is, encoders should be reset at AutoInit, and not thereafter.
To help with auto balancing, it may be useful to log pitch (done), motor demand (set power, speed, or whatever), robot velocity, and any other parameters that might aid in visualizing what's happening from the software's perspective. For example, if a state machine is used, it may be useful to log the current state (only needs to be logged when it changes).
This issue is a container to document things we may want to log. This issue should be left In Queue until we're satisfied that we won't add any more logging. (E.g. after competitions.)
Please help keep this list up to date.
Currently implemented:
Consider implementing: