Laird Connectivity is now Ezurio/filters:background_color(white)/2024-11/Product-Photo---BL651-Series1.png)
/filters:background_color(white)/2024-10/BL652-SA-RightLabel_0.png)
/filters:background_color(white)/2024-10/bl653-transparent-highres_0.png){kind=spacer}
/filters:background_color(white)/2024-10/BL653µ-SA-angle.png)
/filters:background_color(white)/2024-10/BL654-Series.png)
/filters:background_color(white)/2024-10/bl654pa-both_0.png)
/filters:background_color(white)/2024-12/BT850_SA.png)
/filters:background_color(white)/2024-12/BT860ST.png)
Answer
The communications protocol for Bluetooth is a ping pong type style, so every connection event begins with the Master sending the slave a packet and the Slave then responds to that packet with any data it may have. Therefore, when the Master has no data to transmit it will send an EMPTY_PDU to the Server and the Server, if it has data to send, will send back the data in response. You can see this readily where there is no data transmissions, the Master and Slave ping pong EMPTY_PDU’s back and forth on every connection event, if Slave Latency was incorporated then during these periods of no data transmissions you would see Master send EMPTY_PDU and no response from Slave because it has no data to send and was allowed to skip the connection event because of it.