Maximum average power consumption / current when transmitting close to bandwidth (nRF52)

RE: Maximum average power consumption / current when transmitting close to bandwidth (nRF52)

Stian Røed Hafskjold — Wed, 28 Nov 2018 10:31:21 GMT

Please check out the updated power profiler: https://devzone.nordicsemi.com/power/

RE: Maximum average power consumption / current when transmitting close to bandwidth (nRF52)

Larissa — Thu, 27 Sep 2018 02:28:27 GMT

Thank you! I should dig deeper into that...

Looking at the max. packet size (27 bytes in BLE 4.0) the max. in BLE 5 is 257 bytes (251 payload). Playing with the power profiler, at the minimum 7.5 ms theoretical connection interval, the total average current seems to be a pretty linear function that's around (627+[num_bytes]*9) µA. So at 257 bytes, that'll be 2.94 mA. That would be 17kB/s with ACK; but I don't know how to do the math at the higher bitrate without ACK, which is probably the more relevant and lower current.

Am I going in the right direction here, or am I way off?

RE: Maximum average power consumption / current when transmitting close to bandwidth (nRF52)

Stian Røed Hafskjold — Tue, 25 Sep 2018 07:03:39 GMT

Hi, I'm working on updating the online power profiler now, and it should be out soon with BLE 5 support. You can also use the tool as it is now to calculate for higher bandwidths if you do some calculations on your own. For example if you want to enable data length extension in your application you can extend the radio lengths with 1 us for each bit (1Mbps). Then you have additional_length*radio_average_current = additional_event_charge. And additional_event_charge / ble_interval = additional_average_current.