Subrate Base Event number in subrating

I'm running the subrating sample (ncs\v3.1.1\nrf\samples\bluetooth\subrating) on two nRF54L15-DK boards.

I'm puzzled by something I can see through my protocol analyzer.

Subrate Base Event value is very high:

Subrate Factor has been set to 10, which is as expected. This means that every tenth connection event, the can be active transmission/receipt of data. The other 9 connection events, there will be no radio activity. Which of the connection events in each sequence of 10 is to be used is specified in the Subrate Base Event parameter, which the Central chooses. But here it's 142, much higher than the Subrate Factor of 10, which doesn't make sense to me unless there's something I've misunderstood.

I'm also seeing only one exchange of ATT PDU every 10 connection events. i.e. a REQ then 10 conn events later, the expected RSP and then another 10 later, another REQ and so on.  Normally there'd be time in a connection event for both the REQ and RSP pDUs to be exchanged. Maybe there's a good reason for this or maybe it's related to the very high subrate base event value?

Note that the connection interval in my example is 10 ms.

Could someone explain what I'm seeing please?

Thanks in anticipation.

Parents Reply Children
No Data
Related