You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked that there is no other Feature Request describing my wish.
I checked that this feature is, in fact, not supported.
I accept that this issue may be closed if any of the above are found to be untrue.
What should be possible that currently is not?
For boards like PiShock Lite/2023 or my own PCBs, a user changing the RF TX pin should be discouraged/warned against.
Currently the only relevant information is on the Wiki, and having the pins pre-set in the UI during setup.
I think the only thing that's missing at this point is a warning stating that the pin has already been set by their choice of firmware, and that changing it is not recommended.
For generic WEMOS, Seeed, etc dev boards, leaving the RF pin undefined in the platformio.ini could be used as a way to suppress that warning, letting the user enter their chosen pin.
Other remarks
No response
The text was updated successfully, but these errors were encountered:
hhvrc
changed the title
[Enhancement] Have a warning on changing RF TX pins on pre-defined boards
[Feature] Have a warning on changing RF TX pins on pre-defined boards
Dec 1, 2023
Pre-submission checklist
What should be possible that currently is not?
For boards like PiShock Lite/2023 or my own PCBs, a user changing the RF TX pin should be discouraged/warned against.
Currently the only relevant information is on the Wiki, and having the pins pre-set in the UI during setup.
I think the only thing that's missing at this point is a warning stating that the pin has already been set by their choice of firmware, and that changing it is not recommended.
For generic WEMOS, Seeed, etc dev boards, leaving the RF pin undefined in the
platformio.ini
could be used as a way to suppress that warning, letting the user enter their chosen pin.Other remarks
No response
The text was updated successfully, but these errors were encountered: