ST意法半导体
直播中

潘础功

7年用户 142经验值
私信 关注
[问答]

BlueNRG-MS无法在单个连接事件中传输多个写请求?

嗨,
我注意到每个连接事件不可能有多个ACI_GATT_WRITE_CHAR_VALUE。
我设置了以下连接:连接间隔为40ms,连接事件长度为21.875ms(我可以继续并行通告的最大值)。
使用嗅探工具,我看到发生的事情如下:
- 大师 - >奴隶:写请求
- 等待40ms(下一个连接间隔)
- 奴隶 - >主人:写回应
- 等待40ms(下一个连接间隔)
- 大师 - >奴隶:写请求
- 等
这是正常的行为吗?为什么不能在同一连接事件中包含Write响应,以及更多写请求?
请注意,如果我使用ACI_GATT_WRITE_WITHOUT_RESP(写入命令),我不会遇到问题,并且可以在同一个连接事件中发送多个(大约每700us)
谢谢你的帮助。
基督教

#bluenrg-MS

以上来自于谷歌翻译


以下为原文




Hi,
I have noticed that it is not possible to have multiple ACI_GATT_WRITE_CHAR_VALUE per connection event.
I have set up the following connection: connection interval of 40ms and connection event length of 21.875ms (the maximum I can while continuing to advertise in parallel).
Using a sniffing tool, I see that what is happening is the following:
- Master -> Slave : Write Request
- Wait for 40ms (next connection interval)
- Slave -> Master : Write Response
- Wait for 40ms (next connection interval)
- Master -> Slave : Write Request
- etc.
Is that a normal behavior? Why isn't it possible to have the Write response inside the same connection event, and more write reqests?
Note that if I use ACI_GATT_WRITE_WITHOUT_RESP (Write command), I don't face the issue, and it's possible to send multiple ones inside the same connection event (around every 700us)
Thanks for your help.
Christian

#bluenrg-ms

回帖(2)

曹皓轩

2018-9-29 14:18:50
嗨基督徒,
是的,这是一种预期的行为,因为从设备将等待其自己的连接间隔来发送ACI_GATT_WRITE_CHAR_VALUE所需的响应。
亲切的问候
安德里亚

以上来自于谷歌翻译


以下为原文




Hi Christian,
yes, it is an expected behavior since the slave will wait for its own connection interval to send the response required by the ACI_GATT_WRITE_CHAR_VALUE.
Kind regards
Andrea
举报

潘础功

2018-9-29 14:28:31
对于我的教育,你介意我指点蓝牙核心规范中的参考吗?

以上来自于谷歌翻译


以下为原文




For my education, would you mind pointing me to the reference in the Bluetooth CORE Specifications?
举报

更多回帖

发帖
×
20
完善资料,
赚取积分