Comparison of Log Replay Tools
Several logging tools are available to FRC teams with different capabilities and use cases. This page compares non-replay logging tools to several replay-capable logging tools, including AdvantageKit.
Skip to the summary section to compare the features of each logging tool.
Non-Replay Logging
(DataLogManager, Epilogue, Monologue, etc.)
These tools allow for logging and/or live streaming of data published from robot code, which can be viewed using AdvantageScope. This is sufficient for the majority of debugging tasks, such as verifying pose estimation accuracy, checking joystick values, and debugging simple issues in code that was configured for logging ahead of time. However, these tools do not support replaying data to simulated robot code (as explained here).
CTRE Signal Logging & Hoot Replay
CTRE's signal logging system for Phoenix 6 automatically records CAN data from supported devices. For 2025, CTRE introduced the Hoot Replay feature that allows data from a single Hoot log to be replayed to robot code during simulation. This enables simple debugging of code under the following circumstances:
- Code logic is dependent only on data from logged devices and/or custom signals (if manually integrated by the user).
- Code logic is not affected by joystick inputs, non-CAN devices, NetworkTables values (such as vision measurements or dashboard choosers), or other non-replayed values.
- Code logic does not depend on the timing of signals (such as in which loop cycle a signal arrives).
Hoot Replay is non-deterministic, which means that no guarantee is made that replayed robot code will match the behavior of the real robot. It is best used when debugging issues of limited scope that are highly dependent on Phoenix APIs.
Hoot logging is enabled by default and does not require architecture changes to code. This enables replay of simple logic (such as non-vision odometry) without requiring any code changes. However, replaying high-level logic dependent on non-Phoenix data (such as joysticks or vision inputs) may require code architecture changes to log and replay custom user signals.
AdvantageKit
AdvantageKit guarantees deterministic replay of robot code in simulation, allowing for additional fields to be logged or code logic to be adjusted in replay with complete certainty of the original and adjusted behavior of the real robot. AdvantageKit guarantees that the replayed robot code will match the behavior of the real robot.
AdvantageKit is not enabled by default. Code bases not already using hardware abstraction for subsystems must be restructured when switching to AdvantageKit.
AdvantageKit is free and open-source. It can be used with hardware from any vendor, including CTRE, REV, and more.
Summary
| Non-Replay | CTRE/Hoot (Nondeterministic) | AdvantageKit (Deterministic) | |
|---|---|---|---|
| Record data viewable in AdvantageScope | |||
| Replay of enabled and autonomous state | |||
| Low-level replay of code using Phoenix APIs | |||
| Replay of Phoenix timestamps | |||
| Guarantee of replay accuracy See previous pages for full examples | |||
| Replay of all Driver Station data Full robot mode, joystick inputs, etc. | |||
| Replay of FPGA timestamps Used by WPILib, commands, etc. | |||
| Replay complex code logic Commands, autos, pose estimation, etc. | |||
| Replay code using any vendor library Phoenix, REVLib, Limelight, etc. | |||
| Replay code using non-CAN inputs Vision, analog inputs, DIOs, etc. | |||
| FRC language support | |||
| Pricing |
*Code logic replayed using Hoot Replay may not match the behavior of the real robot. Phoenix timestamps available during Hoot Replay use a different time base than the real robot.
**Use of non-Phoenix values requires manual implementation of logging and replay logic, including conversion of time bases and custom code architecture supporting hardware abstraction (or similar). Nondeterministic replay makes no guarantee that replayed code will match the behavior of the real robot.