完善资料让更多小伙伴认识你，还能领取20积分哦， 立即完善>
3天内不再提示
德赢Vwin官网
论坛|
我正在将一个产品从使用RN467到BLD模式迁移到RN48 71的过程中。然而，我们需要与使用第三方蓝牙模块的第四方设备配对。RN467 7可能只使用WorkSturnices安全性，但这不清楚，因为我的前任使用EEPROM写命令（S:L＆T.＆GT，L＆G.T）来配置它。所以，我需要RN467内存映射来完全理解正在RN467上配置。基于代码注释和BT窥探，我有RN878广告与RN467 7相同的服务，第三方设备连接，但似乎从来没有配对。我相信问题是与安全。似乎RN878实际上并没有像RN467那样使用。为了得到工作，没有结束需要验证PIN码，我相信RN48 71应该设置以下命令：SA，2SP，00，所使用的服务似乎是透明的UART，这两个RN模块支持本地。我们的产品作为第三方设备的外围设备。在透明的UART中，客户机/服务器的概念有点模糊。RN467和RN878之间使用的加密方法不同吗？我相信这在BLE 4和4.2之间发生了变化。如果是这样，我如何配置RN878为向后兼容？非常感谢您的帮助！谢谢您！J
以上来自于百度翻译 以下为原文 I'm in the process of migrating a product from using the RN4677 in BLE mode to the RN4871. However, we need to pair with a 3rd party device that uses a 4th party Bluetooth module. The RN4677 likely uses Just-Works security, but this is unclear since my predecessor uses EEPROM write commands (S:,<>,<>) to configure it. So, I need the RN4677 memory map to fully understand was is being configured on the RN4677. Based on code comments and BT snooping, I have the RN4871 advertising the same services as the RN4677, and the 3rd party device connects, but never seems to pair. I believe the issue is with the security. It seems that the RN4871 is not actually using Just-Works in a manner like the RN4677. To get Just-Works to work with neither end needing to validate a pin code, I believe the RN4871 should set the following commands: SA,2 SP,0000 The service being used appears to be the Transparent UART, which both RN modules support natively. Our product operates as a peripheral to the 3rd party device. With Transparent UART, client/server notions are a bit vague. Is a different encryption method used between the RN4677 and RN4871? I believe this changed between BLE 4.0 and 4.2. If so, how do I configure the RN4871 to be backward compatible? Any help is greatly appreciated! Thank you! J 
0
|
|
相关推荐
7个回答
|
|
|
仍然不工作…在透明UART或其他默认配置的两个模块实现之间可能存在服务和/或特性差异。我们已经经历了这两个问题，并且找不到任何看起来影响配对的东西。我们尝试用第三方设备来实现不同的服务。同样，只有RN861看起来无法通过配对或某种服务级别兼容握手。（我不是BT Guru，所以我还不知道所有的关键词。）有没有办法让RN48 71向UART发布消息或通知，如果它被远程对等设备查询的特性或特性？这也许能给我一个线索，谢谢你，J。
以上来自于百度翻译 以下为原文 Still not working.... There may be service and/or characteristics discrepancies between the two modules implementation of Transparent UART, or other default configurations. We've been through both and can't find anything that seems to affect pairing. We've attempted to implement a different service with the 3rd party device as an alternative. Again, only the RN4871 can't seem to get past pairing or some sort of service level compatibility handshake. (I'm not a BT guru, so I don't know all the key words yet.) Is there a way to have the RN4871 post a message or notification to the UART if it is queried for features or characteristics by the remote peer device? That might give me a clue what it's looking for. Thank you, J |
|
|
|
|
|
嗨，RN467将是一个更密切的迁移到RN467 7，除非你不需要BT经典。哪个固件你使用RN48 71.我建议首先把它更新到最新的固件V1.283:http://www. MicroChIP.Cu/WWWORDSTS/En/RN878，在V1.283:http://WW1. Microchip .com……AST%20NoSeS030118.PDFRADGARDS
以上来自于百度翻译 以下为原文 Hi, RN4678 would have been a closer migration to RN4677 unless you don't need BT classic. Which firmware to you use on RN4871 ? I suggest first to update it to the latest firmware v1.28.3 : http://www.microchip.com/wwwproducts/en/RN4871 under software Release notes for v1.28.3 : http://ww1.microchip.com/...ase%20Notes_030118.pdf Regards |
|
|
|
|
|
您好，RISC，虽然我同意RN467更接近，它也一样大RN467 7。RN1478相当小，但仍然应该是一个简单的迁移路径。是的，我应该提到上面，我们做固件更新到1.23.3个星期左右。这无济于事。如果我们让这个模块工作，我们将需要更新生产单位。感谢重播！J
以上来自于百度翻译 以下为原文 Hello RISC, While I agree the RN4678 is closer, its also as large as the RN4677. The RN4871 is considerably smaller, but still supposed to be a simple migration path. Yes, I should have mentioned it above, we did the firmware update to 1.28.3 a week or so ago. It didn't help. If we do get this module to work, we'll need this update on production units. Thanks for the replay! J |
|
|
|
|
|
您好，RISC，您发布的链接为1.23.3发行说明：http://WW1.Microchip .com /下载/ En/DeViceOTC/RN87x%20固件%20V1.23.3%20发行版本%20NoSeS030118.PDFIS新版发行日期为3/1／18，RNS48产品页的链接最近改为指向它。E-Notes版本的日期为1/26／18：http://WW1.Microchip .com /下载/ En/DeViceOC/RN87x%20固件%20V1.23.3%20发行版本%20NoSeS012618.PDF2都是版本1.23.3。我想知道1.23.3版本的实际固件文件是否也改变了？两者之间有一些有趣的区别，我需要研究一下。谢谢！J
以上来自于百度翻译 以下为原文 Hello RISC, The link you posted for the 1.28.3 release notes: http://ww1.microchip.com/downloads/en/DeviceDoc/RN487x%20Firmware%20v1.28.3%20Release%20Notes_030118.pdf is a new version of the release notes dated 3/1/18 and the link from the RN4871 product page recently changed to point to it. The release notes version I have is dated 1/26/18: http://ww1.microchip.com/downloads/en/DeviceDoc/RN487x%20Firmware%20v1.28.3%20Release%20Notes_012618.pdf Both are supposedly for version 1.28.3. I wonder if the actual firmware file for version of 1.28.3 changed, too? There are some interesting differences between the two that I need to look into. Thank you! J |
|
|
|
|
|
我假设你知道在配对之前两端都需要清除之前的绑定。然后你可以试试下面的命令，检查配对问题是否固定：S::22A，24WE被从MCHP支持中得到这样的命令来解决类似的问题。
以上来自于百度翻译 以下为原文 I assume that you understand that both ends need to clear the previous bondings before pairing. Then you may try following command and check if the pairing problem fixed: S:,002A,24 We were given such command from MCHP support to resolve a similar issue. |
|
|
|
|
|
MyZigBee，谢谢你的回复。我们必须尝试一下。我假设这是对EEPROM的一个写入，但是，RN1478的参考资料没有列出可用的S:命令。此外，在我在网上找到的非常老的内存映射中，这个地址没有被定义。任何指示：S.0.2a，24实际上是做什么的？我们一直在尝试各种各样的组合。快速尝试是没有希望的。这个命令是为了让透明的UART与第三方设备一起工作吗？或者它与BT 4.2与旧的和/或第三方设备一起工作有关系吗？再次感谢！J
以上来自于百度翻译 以下为原文 @myZigbee, Thanks for the reply. We'll have to give it a try. I assume this is a write to EEPROM, however, the reference material for the RN4871 does not list the S: command as available. Also, in the very old memory map I found online, this address is not defined. Any indication what S:.002A,24 actually does? We've been trying a myriad of combinations. A quick try was not promising. Is this command for getting Transparent UART working with 3rd party devices? Or does it have to do with getting BT 4.2 working with older and/or 3rd party devices? Thanks again! J |
|
|
|
|
|
我相信这样的命令关闭了蓝牙4.2中的数据长度扩展功能。如果您碰巧连接到不支持DLE特性的较旧或低端设备，则此命令应该能够使您连接和配对。然而，它与透明的UART服务无关。你将需要重新启动后，这样的设置之前，效果。BTW，我相信你认识到RN467 7是BLE经典和BLE组合设备和RN48 71BLE是唯一的。你需要确保你的第三方设备支持BLE。
以上来自于百度翻译 以下为原文 I believe such command turned off data length extension feature in Bluetooth 4.2. If you happen to connect to older or lower end devices, which does not support DLE feature, this command should be able to get you connected and paired. It has nothing to do with Transparent UART service though. You will need to reboot after such setting before it takes effect. BTW, I believe that you realize that RN4677 is BLE Classic and BLE combo device and RN4871 is BLE only. You need to make sure that your 3rd party device supports BLE. |
|
|
|
|
只有小组成员才能发言，加入小组>>
5238 浏览 9 评论
2028 浏览 8 评论
1950 浏览 10 评论
请问是否能把一个ADC值转换成两个字节用来设置PWM占空比？
3204 浏览 3 评论
请问电源和晶体值之间有什么关系吗？PIC在正常条件下运行4MHz需要多少电压？
2253 浏览 5 评论
777浏览 1评论
666浏览 1评论
有偿咨询，关于MPLAB X IPE烧录PIC32MX所遇到的问题
595浏览 1评论
PIC Kit3出现目标设备ID(00000000)与预期的设备ID(02c20000)不匹配。是什么原因
676浏览 0评论
576浏览 0评论
/6 
关注我们的微信
下载发烧友APP
德赢Vwin官网 观察
版权所有 © 湖南华秋数字科技有限公司
德赢Vwin官网 （电路图） 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证：合字B2-20210191
工商网监
湘ICP备2023018690号
1914
评论
淘帖
1858
