如何选择GUI上的类型？

你好，
我们有一个KBA，它解释了如何配置BLE外围设备来执行定向广告：
配置BLE外围设备执行定向广告-KBA218959
请回顾一下，如果需要进一步的帮助，请告诉我们。
谢谢，
纳达



     以下为原文
  Hi,
 
We have a KBA which explained how to configure BLE peripheral to perform directed advertisement here:
Configuring BLE Peripheral to Perform Directed Advertisement - KBA218959
 
Please kindly review and let us know if you need further help.
 
Thanks,
Nada

HI NDMA，我怎么做直接广告的中央设备，有随机的公共地址，在每一个回合的蓝牙？将分配这些设备的“身份”地址在CyByLyStudioMoDeFieln.AdvPARAM-GT；DoDATADDR做这个把戏吗？



     以下为原文
  Hi ndma, how do I do direct advertisement for Central devices that have random public addresses at every turn on of its Bluetooth? Will assigning the "Identity" address of these devices in the cyBle_discoveryModeInfo.advParam->directAddr do the trick?

这应该是有帮助的：
HTTP://OrgIn www. CyPress .COM/FUMU/PSOC-4-BLUE /解析随机存储器



     以下为原文
  This should be helpful:
http://origin-www.cypress.com/forum/psoc-4-ble/resolving-random-storing-public

嗨，E.普拉特1616216。我已经阅读了链接，连同KBA20328在另一个THealpSoC 4 BLE广告过滤中提到的。所以，我正在分享我学到的东西。
1。应用KBA218959，我做了直接广告，分配BDADDR从CybLygGAPGETPEBDADDR获得到CybLyDebug yDeMeNo..AdvPARAM-GT；DUNCTADDR。它适用于使用可解析私有地址（RPA）的Android设备，但对于iOS设备（iPad）也不适用。这意味着，在处理使用RPA（iPad）的设备时，直接广告是不可行的，它会改变每一个功率周期和时间间隔。
2。我还尝试使用CybLyGAPGETPERDEFACTIGIGIKIN（）作为直接广告的DATTADDR获得的对等设备的标识地址。不幸的是，这两种设备（Android和iPad）都无法连接到BLE。这意味着设备将当前使用的RPA，而不是它的身份ADDR与直接广告中的地址进行比较，然后决定它是否是目标设备进行连接。



     以下为原文
  Hi, e.pratt_1639216. I have read that link along with the KBA203286 that you mentioned in another threadPSoC 4 BLE advertisement filtering. So, I'm sharing what I learned/found out.
 
1. Applying KBA218959, I did direct advertising by assigning bdAddr obtained from CyBle_GapGetPeerBdAddr to cyBle_discoveryModeInfo.advParam->directAddr. It worked for an Android device that uses Resolvable Private Addresses (RPA) but did NOT for an iOS device (iPad) that also uses RPA w/ changing of Addr every ~15mins. What this means is that direct advertising is not the way to go when dealing with devices employing RPA (ie. iPad) that changes every power cycle and time interval.
 
2. I also did try using the Identity Address of the peer device obtained using CyBle_GapGetPeerDevSecurityKeyInfo()  as the directAddr for the direct advertisement. Unfortunately, both devices (Android & iPad) were not able to connect to the BLE. What this means is that devices compare the current RPA it uses, not its Identity Addr, with the address in the direct advertisment; then decides if it is the target device for connection.

您好！
嗯，那太糟糕了。不确定，但是我想你能在失败的时候更新你正在使用的地址吗？
我认为RPA实现的思想是对SSL中使用的私有/公钥对有类似的方法，但是我没有仔细观察实现的使用。



     以下为原文
  Hi capardogracielle_2279656
 
Hmmm, that is a bummer. Not sure, but I would think you would be able to just update the address you are using upon failure?
I think the thought with the RPA implementation was to have a similar approach to Private/Public key pairs used in SSL, but I haven't looked too carefully at what the implementation employs.