[问答]

处理丢弃的写请求的最佳方法是什么

问答对人有帮助，内容完整，我也想知道答案 0 我正在做一个应用程序，我有一个中心和多个外围设备。人们的愿望是中央向外围设备发送数据。它经历扫描、连接、写入数据、断开连接等过程。最初我用的是：无应答但有时消息被删除了。我改为使用： CygLay-GATCt文字特征值如果接收到响应，则此函数会导致CyByLyEvtGATCKWRIGETEYRSP。我有一个时间监视器，以便如果响应没有及时返回（80ms），我尝试用另一个调用发送第二次：如果我第二次调用那个函数，我得到一个CyByrError的无效操作。如果我没有得到回复，有没有办法重新发送消息？有没有更好的方法来确定写不成功并重新发送？或者我需要断开，重新连接，重新发送？以上来自于百度翻译以下为原文 I am working an application whereby I have a Central and multiple Peripherals. The desire is for the Central to send data to the Peripherals. It goes through a process of scan, connect, write data, disconnect, etc… Initially I was using : CyBle_GattcWriteWithoutResponse but sometimes the messages were getting dropped. I changed to using: CyBle_GattcWriteCharacteristicValue This function results in CYBLE_EVT_GATTC_WRITE_RSP if the response is received. I have a time monitor so that if the response does not come back in time (80ms), I try to send the write a second time with another call to: CyBle_GattcWriteCharacteristicValue If I call that function a second time, I get a CYBLE_ERROR_INVALID_OPERATION Is there a way to resend a message if I don’t get a response? Is there a better way to determine that a write was not successful and resend it promptly? Or do I need to disconnect, reconnect, and resend? 0
2018-10-1 17:22:30　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × 36切53 该类别下有 65 个回答。邀请回答 hnui2002 该类别下有 50 个回答。邀请回答细水爱长流该类别下有 33 个回答。邀请回答不cdvdhgdh 该类别下有 31 个回答。邀请回答 iwuwjgj 该类别下有 26 个回答。邀请回答 cslb2000 该类别下有 25 个回答。邀请回答珠海易胜该类别下有 23 个回答。邀请回答 ggfx 该类别下有 23 个回答。邀请回答 h1654155958.0210 该类别下有 22 个回答。邀请回答 hrtuoyu 该类别下有 22 个回答。邀请回答 ncmza 该类别下有 21 个回答。邀请回答 shaoye88 该类别下有 21 个回答。邀请回答瑾年Invader 该类别下有 20 个回答。邀请回答望望Ll 该类别下有 20 个回答。邀请回答 april_yu 该类别下有 20 个回答。邀请回答 zkzk196599 该类别下有 19 个回答。邀请回答 lucas_songlea 该类别下有 18 个回答。邀请回答 nvwuwy 该类别下有 18 个回答。邀请回答 zhan81411 该类别下有 17 个回答。邀请回答 cmh22 该类别下有 17 个回答。邀请回答举报陈小艳相关推荐 • 请求将更改反向移植到发布分支的最佳方法是什么？ 380 • IPMB接口的请求和应答协议解析 2277 • 使用ESP模块作为不同天线的测试设备的最佳方法是什么？ 357 • CyU3PUsbRegisterSetupCallback的fastEnum参数可确保只有\"未知\" 设置请求才会发送到我的回调， \"未知的\" 请求是什么？ 423 • 请问从USB-PD端口请求更高电压最简单最快的方法是什么 474 • 请问时钟抖动或结束时钟抖动的最佳方法是什么？ 1815 • UCOS中请求信号量函数OSSemPend如果请求失败能跳出循环吗 1506 • 请教关于给簇中元素赋值的最佳方法？ 10432 • 请求信号量能请求成功吗？ 775 • 请问从中央设备读取请求时会产生什么事件？ 1314 1个回答

答案对人有帮助，有参考价值 0 功能cyble_gattcwritecharacteristicvalue()将事件cyble_evt_gattc_error_rsp或cyble_evt_gattc_write_rsp取决于成功的编写特点。你应该等待，直到你得到一个回应。有可能，你可以尝试的功能cyble_gattcreliablewrites()可靠地写入数据。（见表表/ API参考，通过右键点击的组件在PSoC Creator IDE并选择“打开表”/“开放API文档”）调用另一个写请求应该是美好的，但它可能是你发送的请求太快，取决于你的发射/接收窗口/定时/延时芯片前有时间超时/尝试请求。你不应该重新尝试的请求命令。尝试撞击你的时间从80ms起来说1或2秒，如果您收到一个在尝试一种新的读写响应。如果你想做的东西是不可能发生的错误（一般invali_operation连接扫描时，广告在中央模式，等等）或者祝福不能执行该操作ATM（打一次以后可能或可能不工作）。以上来自于百度翻译以下为原文 The function CyBle_GattcWriteCharacteristicValue() will return the event CYBLE_EVT_GATTC_ERROR_RSP or CYBLE_EVT_GATTC_WRITE_RSP depending on successful write of the characteristic. You should be waiting until you get one of those responses. Potentially, you can try the function CyBle_GattcReliableWrites() to reliably write the data. (See the BLE datasheet/API reference by right-clicking on the BLE component in the PSoC Creator IDE and selecting the "Open Datasheet"/"Open API Documentation") Calling another write request should be fine, but it could be you are sending the request too quickly depending on your BLE Tx/Rx windows/timing/latency before the chip has time to timeout/try the request. You shouldn't have to reconnect to try a BLE request command. Try bumping your time from 80ms up to say 1 or 2 seconds to see if you are getting one of the two write responses before attempting a new write. The INVALI_OPERATION error generally occurs if you are trying to do something that is impossible (connect while scanning, advertise while in central mode, etc.) or if the BLESS can't perform that operation ATM (calling again later may or may not work).

2018-10-1 17:36:39 评论举报黎歆俭