![]() ![]() Not sure, probably best to pop in a feature request/ issue on Github if this would be useful to you? I think our software folks have recently merged some super early wake up stuff for the Badger and Enviro builds, so hopefully we’ll be able to roll that out to Inky Frame and make things a bit more snappy. Is that delay really related to MicroPython start-up time? Does that imply a compiled C++ program can behave differently? ![]() I found reset to be occasionally useful when Inky Frame got itself into a confused state when I ran broken code on it and I needed to interrupt it :) Yep, you don’t have to press reset, under most circumstances a button press will wake it up on its own. I found it useful to think of the battery behaviour as ‘off by default’ - you need to hit a wake up trigger/tell the board to stay awake, otherwise it will turn itself off to save battery. This is correct, you will always need to press a button (or use the RTC/external trigger) to wake it up when running on battery, whether or not you press reset. If you are doing this in your code bear in mind that pulling this pin high this might interfere with doing things with wireless - GP25 is also the wireless interface’s SPI pin (though I haven’t noticed any problems reading the battery and posting data via wireless on Enviro). Sounds like you weren’t pulling GP25 high? I got those sort of readings before I figured out you needed to do that on a Pico W. Then when I put some similar code into my program it was showing voltage level on USB and about 0.1V (clearly wrong for my 3 alkaline) on battery power. Is there documentation on how the external trigger works? Is it 5V safe? Should a MicroPython program bring Pin(2) high as soon as possible in the code?Īre there any plans for a MicroPython library like the C++ InkyFrame class to make all this easier?įor the RTC timer, how accurate is the clock likely to be? Is that delay really related to MicroPython start-up time? Does that imply a compiled C++ program can behave differently? I assumed the RTC chip is somehow waking up the RP2040 and it wouldn’t matter what runs afterwards? Or does the length of button press determine the initial power-on time until Pin(2) is held high to maintain power? If so, that doesn’t seem like an ideal hardware design. If this doesn’t seem to be working, try holding one of the front buttons down for a second or two - it needs a fairly solid press to wake it up (this is because there’s a short delay whilst MicroPython starts up, so it can miss quick button presses). If I power it on and then press button B for about 1.5 seconds my MicroPython code runs. Is that confirming the behaviour I observe? I do not have to press reset at all. ![]() Once you hit reset on a battery powered Inky, you’ll have to press one of the buttons to trigger it to wake up and run main.py. ![]() However, if you’re powering Inky Frame by battery things will work a little differently - the hardware level power saving features will kick in, which can be a bit confusing and make it look like you have a duff battery. In Getting Started with Inky Frame it does state I think that’s a little confusing from a user interface point of view. It does wake up on button presses but these need to be fairly long presses for it to wake up. I think that can confuse the situation at times. This is for code which isn’t using the rtc timer. After powering it on the reset button also does nothing. My Inky Frame does not appear to ever run the MicroPython code when I power it on. Thanks, I had a quick play with the voltage stuff and it appeared ok on REPL but then when I put some similar code into my program it was showing voltage level on USB and about 0.1V (clearly wrong for my 3 alkaline) on battery power. ![]()
0 Comments
Leave a Reply. |