training:software:data_logging
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| training:software:data_logging [2024/11/19 12:34] – Jay Tarbotton | training:software:data_logging [2024/11/19 12:44] (current) – Jay Tarbotton | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| If we want to look at robot data after we are done with a test or competition match, we need to save the data into a file that can be retrieved later. The WPILib DataLogManager class allows us to capture the data to file with very little effort. In most cases all we need to do is start the data logging during initialization - any data already being published to network tables will then also be captured in the log file. We can also tell the DriverStation to log Joystick data for the operator controllers. | If we want to look at robot data after we are done with a test or competition match, we need to save the data into a file that can be retrieved later. The WPILib DataLogManager class allows us to capture the data to file with very little effort. In most cases all we need to do is start the data logging during initialization - any data already being published to network tables will then also be captured in the log file. We can also tell the DriverStation to log Joystick data for the operator controllers. | ||
| - | |||
| - | When running on the RoboRio, log files are created in internal flash memory unless a USB flash drive is inserted. With a flash drive log files can be moved to a laptop for analysis by removing the flash drive after shutting down the robot and inserting the flash drive into the laptop. Log files on internal RoboRio memory must be transferred over the network using the Data Log Tool or AdvantageScope. | ||
| - | |||
| - | In simulation mode log files are stored in the logs folder in the project folder. | ||
| __References: | __References: | ||
training/software/data_logging.txt · Last modified: by Jay Tarbotton