Skip to content

Rangetest cleanup configuration option #757

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 3, 2025
+6 −0
Merged

Rangetest cleanup configuration option #757

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c5aeb19
Rangetest cleanup configuration option
ford-jones Aug 20, 2025
6e0e795
Improved naming
ford-jones Sep 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions meshtastic/module_config.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -530,6 +530,12 @@ message ModuleConfig {
* ESP32 Only
*/
bool save = 3;

/*
* Bool indicating that the node should cleanup / destroy it's RangeTest.csv file.
* ESP32 Only
*/
bool clear = 4;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we call it clear_on_reboot? Based on your firmware PR I think that's the intended functionality, correct?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Certainly, I will change that now 👍

}

/*
Expand Down