This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

notification vs. writes: full-duplex?

We are using the S110 as a peripheral that emits data via notifications.

Is it safe for the central to also send characteristic writes while notifications are being emitted by the S110 ("full-duplex" communication)? Or do we need to design our protocol to be "half-duplex" (ensure central and peripheral cooperate to not try to communicate at the same time)?

Would sending these writes at the same time increase any chance that the notifications wouldn't make it all the way back to the central?

Parents
  • The communication will not happen at the same time as the protocol states how information is shared. So for a connection event the bluetooth core spec states that the central will start every connection interval and then the central and peripheral will share information based on that. So yes, you can do a characteristic write from the central and still have the notifications from the peripheral. The softdevice/stack will handle this for you so that it is sent without interfering for each other.

Reply
  • The communication will not happen at the same time as the protocol states how information is shared. So for a connection event the bluetooth core spec states that the central will start every connection interval and then the central and peripheral will share information based on that. So yes, you can do a characteristic write from the central and still have the notifications from the peripheral. The softdevice/stack will handle this for you so that it is sent without interfering for each other.

Children
No Data
Related