-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recommended code change #44
Comments
I guess it would depend on if the low battery output on the PowerBoost goes low or if it goes open circuit when the battery is low. Have you tested it to see if it still shuts down on low battery? |
I'll try and let you know. |
I've tested it, seems to work fine, at least for me. I haven't had a chance to check the datasheet of the chip used on the Adafruit inverter, but I would assume it would give a good solid logic high and low. |
Excellent, would you like to submit a pull request? |
I've never done a pull request, nor am I sure what it is. Any advice? |
Its how you contribute to open source code on Github :) I can understand if you'd rather not but its quite rewarding if you did want to get involved, once you have helped one project it can get addictive and you end up contributing quite a bit even if its just correcting spelling mistakes in various projects :) |
I'm very happy to contribute if I can, but didn't know how, and not everyone is interested. I'll see what I can figure out :) |
I think people would be interested in it but it would be best if they can enable the functionality optionally? Perhaps by setting a variable to turn it on? |
While everything works fine on the Pi Zero W that has the shutdown circuit on it, while testing on an unmodified Zero W it immediately shuts down. Looking at the code, it appears it sets a pulldown on GPIO18, but it appears a pullup is needed at GPIO15. Is there a reason this isn't a good idea?
changed to:
# setup the low battery check pin
GPIO.setup(lipopi['low_battery_pin'], GPIO.IN, pull_up_down=GPIO.PUD_UP)
The text was updated successfully, but these errors were encountered: