@changeddaily said in Wipy3 Low power modes: rwble.c Sorry, I cannto find the file either. It is only referenced in the libraries.

@colateral I believe that the Pycom firmware uses one core for networking and the other to run the actual MicroPython code, or something similar. Not sure how easy it would be to disable one of the cores altogether. There has been discussion about changing the frequency though, there must be a thread somewhere in the forum with instructions IIRC.

@jcaron With version 1.14.0.b1 I get 1.6 seconds.

@beyonlo said in 30uA and LoRaWAN: @marcozennaro said in 30uA and LoRaWAN: @malachib it is just sending. As I use ABP I don't have to wait for an acknowledge from the gateway. Using ABP do not means that node will not waiting for a possible ACK from the Gateway. Both, ABP and OTAA always waiting a time (are two DOWNLINK slot times) after sending data, for a possible ACK from the gateway, that is standard. The difference is that OTAA needs an authentication (that will use a DOWNLINK too) before to sent any data, ABP doens't. You are missing different things. First, Gateway never send ACK, it is done by the LoRaWAN Network Server when requested by the device. ABP and OTAA are activation modes and handling encryption keys. ABP itself doesn't generate any air traffic, keys exchanged out of LoRaWAN. OTAA is a way to generate keys but it has nothing to do with authentication. Whether node will wait for downlink and when is independent of activation mode, it depends on Devics Class 'A' or 'C', 'B' is not supported by PyCom and most of other devices.

@StijnK setup_sleep() is a function contained in the pycoproc.py library, and according to its code the maximum value is 2^24 - 1. So the maximum sleep time you could set is 16777215 seconds, which is about 4660 hours (more than six months). Here is the code of pycoproc.py in Github: https://github.com/pycom/pycom-libraries/blob/f848adcfb937e7b7bbc5f78db95840fa26dabe11/pybytes/pysense/lib/pycoproc.py#L24

@jardar It's not really possible to give one efficiency figure for the built-in charger because of the many modes and dynamic operation. For full details I refer you to the datasheet of the charger chip used, the BQ24040 http://www.ti.com/lit/ds/symlink/bq24040.pdf

@jcaron Ok thanks, appreciate the response and will keep all this in mind. Might reduce the frequency of the call-in's to once a day which of course would decrease power consumption appreciably.

@jmarcelino I am trying to put Lopy4 in low power mode, switching off wifi but without success. when i call wlan.deinit(), i receive a sort of reboot such as: Guru Meditation Error: Core 0 panic'ed (StoreProhibited). Exception was unhandled. Core 0 register dump: .... ================= CORE DUMP END ================= Rebooting... what could be the reason?

@jcaron Dear Jcaron: Tnx for your reply. Sorry, if I couldn't make it clear. But, I now I have made it to sending a few hundreds of bytes now (upto 1KB). As soon as I am done with the final project, I will share my updates.

Ah ok!! That's not how I viewed it at first. That's much more interesting. 184ua would be quite a lot, then I'd compare it with a teensy lc and rfm95 combo for example. But at 25ua everything is viable for battery powered sensors again. Thanks very much for your valuable insight. Kim

@tobz as @rcolistete said, it's available in the current stable firmware as well, 1.18.1.r1 (docs)