Add thermal fan control for T-Beam 1W - #3371
Open
agessaman wants to merge 2 commits into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Before this PR, the fan on the Lilygo T-Beam 1W spun continuously, which was using extra power for little benefit because the temperature only spiked on transmits. This PR uses the thermistor near the PA to measure the temperature and spin the fan based on its temperature. It implements a few board-specific commands and custom settings persistence.
get fanreturns fan settings and current temperatureset fan.lo <temp in C>-- temperature to stop the fanset fan.hi <temp in C>-- temperature to start spinning the fanset fan on|off|autocontrols fan activationBy default, the fan spins for 15 seconds after a transmit. In testing, this was shown to be sufficient to control PA temps in all but the most extreme situations. Tested with both repeater and companion firmware (using companion CLI).