Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

SmartDashboard data doesn't save to log file

Open
  • Is something wrong?
#212 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
observability-sre

Research direction

Start with the referenced frc1678/C2025-SystemCore code and compare the SmartDashboard fields seen live in AdvantageScope with the corresponding pulled log from Quals 11. Reproduce the live-versus-recorded discrepancy if possible and trace where swerve module positions, setpoints, and pose data enter logging. Done means those fields are present and updating in the saved log as they do live.

Written by the indexing model from the issue text.

Description

WPILib

We (1678) are currently competing at Madtown Throwdown. We have encountered a very weird issue during this event.

From what we can see, there seems to be an issue with logging data. Specifically, data relating to the positions and setpoints of swerve modules.

Here is a timeline of what happened:

Quals 3: No issue with data, stuff logged as expected

System Check before Quals 11: During our checks no issues, robot functioned as expected. When looking at the logs post-match we discovered the issue was present here as well.

Quals 11: For the most part, robot functioned as expected during the match. We pulled the log to look at a separate issue.

When we tried to look at the log from Quals 11, this is we discovered the issue.

Image

The robot(fused) pose and the vision pose (from the limelight) stay in the default position the entire log. Other things that are related like the module positions and states also are nonexistent.

Image

I ran additional tests on the robot before turning power off. These values update when connected to the robot and viewing data live via AdvantageScope. When I went and pulled this log (new section of Q11 log) the same data that was logged live was nonexistent in the log file.

Seems like all these fields are not getting initialized.

We swapped battery and power cycled and ran these two tests again. Same issue, the data is visible live but nonexistent in the log.

Our code for reference: https://github.com/frc1678/C2025-SystemCore

Storage also is nowhere near full, Internal is ~35% full and we are putting all logs on a thumb drive which is ~20% full

@corsetto pinging for notifications

Dominant language
Java
Stars
190
Forks
25
Avg merge
6h 20m
Merged PRs (30d)
12

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from wpilibsuite/SystemcoreTesting

All issues in wpilibsuite/SystemcoreTesting

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.