We've been in the habit of using System.out.println to view robot data items (i.e. telemetry). This is simple to do, but has various drawbacks:
Difficult to read data as it scrolls though a console at 50 Hz
Difficult to read data when there are multiple different println statements
The console (e.g. RIOlog) doesn't always respond correctly
While println is simple and useful, these drawbacks often cause problems when trying to view telemetered data. Instead, consider using SmartDashboard.put...() calls in robot code for data items (e.g. SmartDashboard.putNumber("Label", value). The data values are published to any tool which can receive NetworkTables data, such as Shuffleboard and OutlineViewer.
Shuffleboard has widgets which can display data in various formats. For example, a Dial widget which might be useful for showing the robot's inclination example.
See also Issue #31 (Data Visualization - AdvantageScope). This may replace the need for using the dashboard for telemetry during development and debug.
We've been in the habit of using System.out.println to view robot data items (i.e. telemetry). This is simple to do, but has various drawbacks:
While println is simple and useful, these drawbacks often cause problems when trying to view telemetered data. Instead, consider using
SmartDashboard.put...()calls in robot code for data items (e.g.SmartDashboard.putNumber("Label", value). The data values are published to any tool which can receive NetworkTables data, such as Shuffleboard and OutlineViewer.Shuffleboard has widgets which can display data in various formats. For example, a Dial widget which might be useful for showing the robot's inclination example.
See also Issue #31 (Data Visualization - AdvantageScope). This may replace the need for using the dashboard for telemetry during development and debug.