RN4020的最佳实践？

嗨，我不知道你把什么叫做最佳实践。你用哪一个PIC来控制RN4020模块？（当我几年前开发了这个模块时，我使用了2×RN4020 PopT尾，因为它更快地尝试命令，然后实现只模拟使用终端窗口手动键入的命令的软件）。最好的方法是看AN1861固件是如何实现的HA。NDLE命令应用注释AN1861：HTTP://www. McCHIP.COM//WavaPabeSe/AppNo.ASPX？AppNeNo.En52528可以看到“C.C.C”如何处理中央项目中的命令，以及外围项目中的“外围设备”。



      以下为原文

    Hi,
I'm not sure what you call best practice.
Which PIC do you use to control the RN4020 module ?
(when I developed with that module a couple of years ago, I used 2 x RN4020 Pictail because it is much faster to try commands and then implement the software which just mimics the command you type manually using a terminal window).
 
The best way is to look how the AN1861 firmware is implemented to handle commands
 
Application note AN1861 :
http://www.microchip.com//wwwAppNotes/AppNotes.aspx?appnote=en572728
you can see how the "central.c" handles commands in the central project and same for "peripheral.c" in the peripheral project.
Regards
 

我正在寻找最好的方法来连接两个RN4020模块，其中两个模块以前从未见过对方，并且它们在哪里共享一个共同的数据块（制造商专用数据），告诉中央节点与外围节点配对是可以的，而忽略其他有效的。连接。本文以HTTP：//MyCHIPPrdult.COM/FAQ：96启动了后端流，这是一个基于终端的慢速过程，我正在寻找一个高速的例子。我错过什么了吗？我确实使用了所有的命令/响应交互，大约一半的时间使用没有特定问题的特定的数据字段。我的环境是一个具有PIC24F插件模块的浏览器16/32和一个RN4020 PICTHOST。一个聚合是我的中心节点，另一个聚合是我的外围节点。



      以下为原文

    I am looking for the BEST way to get two RN4020 modules connected where the two modules have never seen each other before and where they both share a common piece of data (MANUFACTURER SPECIFIC DATA) that tells the central node that it is OK to pair with the peripheral node, and ignore other potential connections. The article I started this post stream with (http://microchipdeveloper.com/faq:96) is the terminal based SLOW SPEED procedure for which I am seeking a working HIGH SPEED example. 
 
I do not see that covered in AN1861. Am I missing something?
 
I do have all the command / response interactions covered and about half the time using the MANUFACTURER SPECIFIC DATA field without issue. My environment is an Explorer 16/32 with a PIC24F plug-in module, and an RN4020 PICtail. One aggregate is my central node, another aggregate is my peripheral node.

你收到的广播有两种格式。根据RN4020用户指南，它们有不同的含义：01EC01CF7B6，0，35，BRCST：0201040CFF46E616C526565664 C4C43这是一个不可连接的广告。这只是纯粹的广播信息。我们已经讨论了如何插入有效负载。01EC01CF7B6，0，，0035B0358E607DD021A08123A000 0300，-35。这是一个可连接的广告。意思是你可以用“C”命令直接连接它。下面的128位值是私有服务的UUID。如果您还没有定义任何私有服务，那就是MDP服务的UUID。很容易识别您想要连接的设备。您不必交替发送可连接或不可连接的广告。相反，您定义具有唯一UUID的私有服务，例如，11223、3545、566、8889900AABBCCDDEFEF（您可以使用任何您认为在这个世界上独一无二的UUID）。然后直接用命令“A”做广告。中央设备将发现这个独特的UUID当接收命令“F”广播，而不进入观察员模式。然后中央设备可以解析接收到的数据并找到它想要连接的MAC地址。您不必有复杂的时间来做这件事，只是在定义私有服务时使用具有唯一UUID的简单可连接的广告。



      以下为原文

    SJFreeland
 
The broadcast that you received has two format. According to the RN4020 user guide, they have different meaning:
 
001EC01CF7B6,0,-35,Brcst:0201040CFF446E616C526565664C4C43
This is a non-connectable advertisement. It is just pure broadcast information. We have discussed how to interpolate the payload.
 
001EC01CF7B6,0,,00035B0358E607DD021A08123A000300,-35
This is a connectable advertisement. Meaning that you could connect to it immediately with "C" command. The following 128-bit value is the UUID of a private service. If you haven't define any private service, that is the UUID of the MDLP service.
 
It is easy to identify the device that you want to connect. You don't have to alternatively sending connectable or non-connectable advertisement. Instead, you define a private service with unique UUID, for instance, 11223344556677889900AABBCCDDEEFF (you could use any UUID that you think unique in this world. ) and then advertise directly with command "A". The central device will find this unique UUID when receiving broadcastings with command "F", without going into observer mode. Then the central device could parse the received data and find the MAC address that it wants to connect. You don't have to have complex timing to do that, just simple connectable advertisement with unique UUID when defining a private service.