What is the meaning of "application processing" ?

[purgoufr]

Hello, I use sdk 8.0.0 and s110. I read this blog

And I did not understand some terms;

1. Application processing(for example 2ms each adv interval)
2. Number of packets to send in each connection interval(for example 1 packet)

Where and how do we organize these terms? How do we change it?

[endnode]

Application processing is the when ARM Coretx-M MCU executes code of your application FW. In other words what you compile into binary and is processed at given interrupt or other trigger.

Number of packets is linked to mechanism how BLE Link Layer works. If you understand what Connection interval is and that normally (unless packet is lost or one of the sides uses Slave/Master Latency) two PDUs are exchanged (one Master -> Slave and one Slave -> Master) then it should be easy to understand that if both sides are able to execute more than one of such PDU-pair. If any of sides have more then one packet ready before connection event is scheduled and the opposite side reflects on MD bit in PDU header (More Data) then another PDU pair is exchanged until there are no more data o one of the sides have limit within the interval (these are stack and configuration specific).

[purgoufr]

The purpose is quite simple. I want to implement experimental work done on this blog I can change tx power, advertise interval and payload data bytes. But I'm trying to figure out how the guy who shared the experiment changed "application processing". I'll show you a piece of experiment;

Advertising 2: TX power: +4dBm adv interval: 1200ms payload: 10 bytes application processing: 2ms each adv interval. Average current consumption: 33,4 uA

Advertising 3: TX power: +4dBm adv interval: 1200ms payload: 10 bytes application processing: 0ms each adv interval. Average current consumption: 25,7 uA

I'm trying to figure out how he did it.

(1/2)