New Firmware Development release v1.19.0.b4
-
OK - Thanks @iwahdan.
-
Hi @tuftec, well as @jcaron mentioned if you are using a Pycom device with Deepsleep shield you cannot keep track of time using RTC as the device is completely powered Off, however if you are using the newer boards that don't require the Deepsleep shield you can keep track of time using the RTC module in Micropython, you would set the time once using
RTC.init()and the RTC would keep counting from that time even in deepsleep , you can check time after wakeup usingRTC.now() -
Triple thanks @cmisztur!
-
Sorry about the scant information.
I am building custom hardware around the LoPy4 and FiPy devices.
So, based on the post by @iwahdan , does this imply that the RTC should keep going in DeepSleep for both the LoPy4 and FiPy modules? This is contrary to information I was given some time ago.
If the RTC keeps going that would be a big advantage for my application.Peter.
-
@tuftec , Also you have to take into consideration the fact that if board resets or power is lost the Time is rested to unix epoch , you can use
RTC.ntp_sync()to Sync time using an NTP server in case of hard resets. -
Any measure of time (in ms) to wake up from light sleep mode ?
I'd like to know if a wake on pin (external signal) from light sleep mode would be fast enough for some signal frequencies : 10 Hz ? 50 Hz ? 100 Hz ? 1000 Hz ?
My "MicroPython Samples". My "MicroPython Firmwares" with many options (double precision, ulab, etc).
-
Measured using only software : about 16 ms to wake up from light sleep. Both using wake on pin (interrupt) or timed light sleep.
Need to confirm with external measurement : i(t) powering LoPy4 by using oscilloscope + shunt resistor.
-
-
@martijnthe said in New Firmware Development release v1.19.0.b4:
what's the timeline for a non-beta release of v1.19.0?
We are hoping to publish the first release candidate next week.
-
On both mac and linux I'm getting unexpected sha1 checksum when I try to install the latest development release on FiPy.
-
@reidfo said in New Firmware Development release v1.19.0.b4:
On both mac and linux I'm getting unexpected sha1 checksum when I try to install the latest development release on FiPy.
Are you using the beta firmware updater?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login