feat/resonance_tester: accepts ACCEL_PER_HZ in TEST_RESONANCES #312
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dalegaard
requested changes
Jun 21, 2024
rogerlz
force-pushed
the
feat/accel_per_hz_gcode
branch
from
2dd67ae to
b44121d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
as suggested by @lhndo in https://github.com/DangerKlippers/danger-klipper/issues/295, it complements https://github.com/DangerKlippers/danger-klipper/pull/224 and allows the user to try different accel_per_hz without having to edit the config and restart the firmware.
Checklist