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
blockedcan't work on it for nowhardwareRelates to configuration of or interaction with Pi GPIO hardwareideaAn idea for discussion before deciding to do it!
More thoughts. On a Pi, it's possible that other applications are using some of the pins I think....
so, it would be great at start-up to scan all the pins and see if we have the ability to configure them.
If we cannot, we should report them as unusuable, and disable them on the UI, maybe with some tooltip to explain why.
blockedcan't work on it for nowhardwareRelates to configuration of or interaction with Pi GPIO hardwareideaAn idea for discussion before deciding to do it!
ppal docs state that "Pins are constructed by retrieving them using Gpio::get.
An unconfigured Pin can be used to read the pin’s mode and logic level."
so a new option would be at start-up to read the actual HW setup, and load that and show in the UI, to not interrupt how things are working on the HW.
The text was updated successfully, but these errors were encountered: