[问答]

RN4871连接尝试中止对LS命令的响应

问答对人有帮助，内容完整，我也想知道答案 0 我只见过这一次，但我碰巧正在监控从终端的RN861的串行数据。作为我的PIC启动序列的一部分，它发布一个LS命令来学习自定义特性的句柄。我碰巧在同一时间启动蓝牙连接。我已经把波特率降低到了RN1478上的2400，我有四个定制特性和定制服务，所以响应“LS”需要相当长的时间。反应停了一段时间，从来没有到“结束”，我的PIC正在等待。谁能用RN878确认这一点？以上来自于百度翻译以下为原文 I have only seen this once, but I happened to be monitoring the serial data from the RN4871 with a terminal. As part of my PIC's boot-up sequence, it issues an LS command to learn the handles of the custom characteristics. I happened to initiate a Bluetooth connection at the same time. I had lowered the baudrate to 2400 on the RN4871 and I have four custom characteristics and a custom service so it takes a fairly long time to respond to "LS". The response stopped part way through and never came to the "END", which my PIC was waiting for. Can anyone confirm this with their RN4871? 0
2019-1-28 11:38:19　　评论淘帖0 邀请回答您可以邀请以下用户，快速回答问题 × qun333 该类别下有 57 个回答。邀请回答 caoguiqun 该类别下有 56 个回答。邀请回答技术发广告该类别下有 56 个回答。邀请回答 psw30 该类别下有 44 个回答。邀请回答伊丹姿子该类别下有 41 个回答。邀请回答 uwufwjrw 该类别下有 39 个回答。邀请回答 hetao1111 该类别下有 38 个回答。邀请回答 lc123617 该类别下有 35 个回答。邀请回答欧阳大大该类别下有 32 个回答。邀请回答作死不止该类别下有 31 个回答。邀请回答 asd010 该类别下有 31 个回答。邀请回答 60user92 该类别下有 29 个回答。邀请回答 wy8719 该类别下有 29 个回答。邀请回答嘻嘻爱哈哈该类别下有 28 个回答。邀请回答 haikitty 该类别下有 28 个回答。邀请回答 ju978779 该类别下有 28 个回答。邀请回答 xiuzhen122 该类别下有 27 个回答。邀请回答 pol666 该类别下有 27 个回答。邀请回答 ueywyrsdfs 该类别下有 26 个回答。邀请回答 lhly23 该类别下有 25 个回答。邀请回答举报薛槐敏相关推荐 • 从RN4677迁移到RN4871问题 1915 • RN4871触发引脚 2183 • RN4871怎么从激活切换到关闭再返回 1976 • 使用更新工具更新RN4871固件要注意什么？ 1760 • RN4871无响应我可以在不使用命令的情况下恢复出厂设置吗？ 1846 • RN4871 SW 1.28可用吗？ 864 • RN4871 pictail板上的固件怎么更新 1569 • RN4870系列与RN4871系列相比有什么优点 1328 • RN4871休眠模式怎么实现 1665 • RN4677或RN4871禁用发现？ 815 2个回答

答案对人有帮助，有参考价值 0 我以前只手动发布这个命令，从来没有见过它不完整，所以不能确认。我不确定检查句柄是必要的，尽管——从一个干净的板岩开始，句柄总是被分配相同的顺序，所以我只需把句柄硬编码成字符。ErristAccess命令；第一个特性总是0072，并且我认为它们从那里增加了2。在启动过程中，通过执行句柄的读取来检查最后一个特性是否存在。如果这产生错误，我擦除设备（PZ）并重写所有服务/特性。这是初始设备需要的真正必要的，因为此后服务/特性持续存在。以上来自于百度翻译以下为原文 I have only ever issued this command manually and have never seen it not complete so can't confirm. I am not sure that checking the handles is necessary, though - AFAIK the handles are always assigned the same sequence when starting from a clean slate, so I just hard-code the handle into the characteristic access commands; the first characteristic is always 0072 and I think they increment by 2 from there. On boot up I check if the last characteristic exist by performing a read from its handle. If this produces an error, I wipe the device (PZ) and rewrite all services/characteristics. This is only really necessary for initial device bring-up as the services/characteristics persist thereafter.

2019-1-28 11:43:28 评论举报王军

答案对人有帮助，有参考价值 0 谢谢你的建议。我没有重复过我所报告的问题，所以可能是由别的原因引起的。关于硬连接的句柄，我已经考虑过了，但是如果RN861固件中的一些设计改变改变了最初的句柄分配，我不希望我的代码变得过时，然后必须WOR。关于如何编写一个处理新旧RN871S的PIC代码。此外，我已经把LS解析工作得很好，所以我不妨使用它。以上来自于百度翻译以下为原文 Thanks for the advice. I have not had a repeat of the problem I reported, so maybe it was caused by something else. Regarding hardwiring the handles, I had considered that, but if some design change in the RN4871 firmware changes the initial handle assignments I didn't want my code to become obsolete, and then have to worry about how to write one PIC code that handles new and old RN4871s. Besides, I've got the LS parsing working well, so I might as well use it.

2019-1-28 11:58:47 评论举报吕声城