Online Power Profiler data interpretation

Hi 
I'm trying estimate the nRF52840s current with the Online Power profiler, the data seemed a bit unclear to me.

I have used the following setting:
Chip nFR53840
Voltage: 3
DCDC = ON
LF clock: External
Radio TX power -16dBm
Role: "Central"
Connection interval: 1000ms
TX Payload 6bytes
RX payload 1024
Data Packet Length Extension = ON
Connection Event Length Extension = ON
PHY: 1Mbps
Slave latency: 3ms
Rest is default

When I then want to read out avg current for a time period of 1second? how do I do that? 

Under "BLE event details" it says 4000ms? It looks like the "Interval" is 4x"Connection interval" ? so that implies 4evnets?? 

I assume that "Total average current 23µA" is for a time periode of 4000ms?

But I want the current use of 1event + idle time until 1sec has passed. =)

Hope somebody can help

Parents
  • Hi,

    The average current is just that, the average current over an infinite time period. It's not tied to any time frame.

    If you want the energy consumed by 1 BLE event you need to calculate in terms of energy or charge, not ampere. You can read out the "BLE event total charge" from the tool.

    If one event consumes 100uC, you will get an average current of 100uA if this event occurs every second. 50uA if it occurs every 2 seconds, and so on. Then you can just add the idle current to that number.

    When you set the slave latency to 3, it skips 3 connection events so that the BLE event interval becomes "connection interval x 4".

Reply
  • Hi,

    The average current is just that, the average current over an infinite time period. It's not tied to any time frame.

    If you want the energy consumed by 1 BLE event you need to calculate in terms of energy or charge, not ampere. You can read out the "BLE event total charge" from the tool.

    If one event consumes 100uC, you will get an average current of 100uA if this event occurs every second. 50uA if it occurs every 2 seconds, and so on. Then you can just add the idle current to that number.

    When you set the slave latency to 3, it skips 3 connection events so that the BLE event interval becomes "connection interval x 4".

Children
Related