Is Sniff Mode supported only as a Slave or as a master or Slave in the BTM41x and BTM51x modules?

Answer

Based on a scenario between two BTM41x modules (referenced in the BTM41x Low Power Modes Application Note), the role of a device (master/slave) does not have an impact on sniff mode. In the scenario, sniff mode requests were accepted with requested parameters and were applied on the link, regardless of which end they were initiated from. Thus, at least one end must actively request sniff mode at some point after a connection has been created and the other end must at least not reject sniff mode. If the other end requests sniff mode as well, then the parameters of the most recent request will apply to the link.

Again, this has been done between two BTM41x modules. The relevant source code from this scenario was later ported across to the BTM51x. Confirming tests and measurements have not been carried out on the BTM51x. However, there is no obvious reason why it should behave differently on the BTM51x.

Please note that sniff configuration refers to Rfcomm based links :SPP, HSP, HFP. For AVRCP/A2DP there are some a default setting.

It should be possible to evaluate if a remote device requests sniff mode: Disable local sniff mode by setting Sniff parameters to zero (S561- S564, by default these are zero) and while in a connection check ATi13 repeatedly. If the response is ‘1: b,c,d,e’ then sniff mode has been entered, caused by the remote end. The resulting sniff parameters (b,c,d,e) are likely to be the ones requested by the remote end.