Closed VegaDeftwing closed 1 week ago
This may be related to #37 as well, as you should be able to use these pins for a seperate LORA board.
This also may need to spawn a new issue to add a method of sending arbitrary commands to the pins that are brought out. I don't know what support in the app would look like for this. Most likely anybody wanting anything beyond a simple glowing light on these pins would have to maintain their own fork, but that sounds reasonable to me.
This may relate to #1 to be sure that the pins are still accessible on other boards.
In https://github.com/VanceVagell/kv4p-ht/issues/59 there are two outlines on the board, one for each module. Their spacing is 0.1" different, and the pin outs are CLOSE, but not exactly the same. So you end up with a footprint that looks like this:
I've labeled all the pins, and underlined the ones that are already in use. Everything else is available for hacking.
Does that accomplish what you want from this? @VegaDeftwing
Yeah, this looks like a good solution to make it much more hackable. I still would've liked to see a SAO header, as I think it would be fun but it looks like the board is pretty packed already now.
Being handled in #63
This is becoming more relevant as I'm planning to do away with the dev boards and put an ESP32 directly on the board. I'll bring out unused pins to headers, and also make an SAO header.
Done in #86. Resolve please (it won't let me.)
Bringing out some of the unused GPIO - especially a pair of I2C lines - would be great for hackability so people can experiment with adding things like small OLED screens, extra buttons, etc. This probably just means bringing a trace out from the header and leaving some unpopulated holes. Maybe just steal the SAO standard?