Lesson 43: Logging and Telemetry

Telemetry is information the robot reports while it runs. Logging is saving that information so you can inspect it later. Together, they turn "it felt weird" into data you can debug.

Log Events and Values

Useful logs include both continuous values and important events.

• Battery voltage
• Motor commands
• Encoder positions and velocities
• Gyro heading
• Current autonomous step
• State changes
• Fault messages

Name Logs Clearly

A log called leftVelocity is better than value1. Include subsystem names when useful, such as Drive/LeftVelocity or Shooter/Ready.

Do Not Log Everything Forever

Too much data can hide the useful data. Start with values that answer real questions: Why did autonomous stop? Did the shooter reach speed? Did the sensor change when the mechanism moved?

Use Logs After Matches

After a match, write down the driver report and compare it to the logs. If the driver says the robot turned slowly, check battery voltage, motor commands, gyro angle, and drive faults.

Practice

Choose one autonomous routine and list the ten values you would want logged while testing it.