用什么优化的方式来实现1主机和3从机的通信？

在BLE中，没有适合于串行协议的配置文件。您需要使用自定义配置文件。您可以以客户端从客户端周期性地执行读取的方式来设计配置文件。还要注意，同时连接到多个奴隶是不可能的，你将需要时间复用。
谢谢，
希马



     以下为原文
  In BLE there is no profile exactly suitable for serial protocol. You will need to use custom profile. You can design the profile in such a way that Client perform reads periodically from the slave. Also note that simultaneous connection to multiple slaves is not possible, you will need to time multiplex.
 
Thanks,
Hima

嗨，Hima，
谢谢你的回答，
我用心率收集器和心率传感器和时间多路复用实现了上述方案。
但我面临以下问题
1.加密不足
2.有时外围设备停止广告/通知。



     以下为原文
  Hi Hima,
 
Thanks For the answer,
 
I have implemented above scenario with heart rate collector and heart rate sensor and time multiplexing.
 
but i am facing some issue as below
 
1.INSUFFICIENT_ENCRYPTION_KEY_SIZE
2.sometimes peripheral device stops advertising/notification.

1。您需要更大的加密密钥大小。这似乎很不言自明？
2。根据您如何编写外围保佑事件处理程序，您可能会遇到一个事件，在这个事件中，芯片做了一个事件，使它停止广告（基于代码，因为我没有看到它失去广告没有一些事件/通知/代码告诉它）。
我建议您查看代码流，看看是否有可能导致广告停止的情况。
另外，只是FIY，通知只在设备连接到另一个蓝牙设备时工作；未连接的通知不起作用，这可能是您所看到的。



     以下为原文
  1. You need a larger encryption key size. This seems pretty self-explanatory?
2. Depending on how you write the peripheral BLESS event handler, you might run into an event where the chip does an event that causes it to stop advertising (based on code, since I haven't seen it lose advertisement without some event/notification/code telling it to).
I would suggest looking at your code flow and seeing if there are cases that could cause the advertisement to stop.
Also, just fyi, the notifications only work when the device is connected to another Bluetooth device; Notifications while unconnected shouldn't work, and this could be what you are seeing.

谢谢普拉特，
谢谢你提供的信息，我会通过的。
请你检查一下这里的原木，想个办法好吗？
P.S.
2个不同的主日志（在单独的日子里）和1个从日志
谢谢。
Tray-SM Save3.3.TXT.ZIP
5.3 K
Turbo Mig.Tx.Zip
83.2 K
MID02-10-2017.TXT.ZIP
38.6 K



     以下为原文
  Thanks e.pratt,
 
Thanks for the information i will go through it.
 
can you please go through the logs attached here and and figure out something?
 
P.S-
2 different master logs(taken on separate days) and 1 slave log
 
Thanks.

•   teraterm-slave3.txt.zip 5.3 K  
  
  
•   teraterm-master.txt.zip 83.2 K  
  
  
•   master02-10-2017.txt.zip 38.6 K  
  
  

因为大多数事件都是成功的，我认为代码中会有一些暂时性的事情发生。
加密不足的错误有以下文件：
＊＊＊＊＊＊＊
可能，您有时使用加密密钥或加密密钥大小的错误值。
下面的事件使我认为您的代码行为异常（在Teraterm Mist.txt中）：
第21行：连接设备API错误：0x103无效状态：状态：扫描
第75行：连接设备API错误：0x103无效状态：状态：连接
第91行：连接设备API错误：0x103无效状态：状态：扫描
第168行：CyByBasCSETrimeDistabor描述符API错误：0x02无效操作
等。



     以下为原文
  Since most of the events are successes; I would assume there is something transient occurring in your code.
The insufficient encryption error has the following documentation:
/** Insufficient key size for the security requirements of this device */
Possibly, you are sometimes using the wrong value for the encryption key or encryption key size.
 
The following events make me think your code is behaving erratically (in Teraterm-master.txt):
Line 21: ConnectDevice API Error: 0x103 invalid state: state: scanning
Line 75: ConnectDevice API Error: 0x103 invalid state: state: connected
Line 91: ConnectDevice API Error: 0x103 invalid state: state: scanning
Line 168: CyBle_BascSetCharacteristicDescriptor API Error: 0x02 invalid operation
etc. etc.

谢谢你的耐心！！
请看（Teraterm大师TXT）：第57967行之后。
作为主要问题的原因之后，我无法弄清楚，如你所见，扫描进度显示了外围设备（00 A05000 AAA/BBB/CC/DDD），但无法连接。
DeVICE-3是无论如何，所以我得到CyLype EvtTimeOut: 4
然后，我开始获得CyByLyEvtGAPHAuthAuthAt失败，原因是：不够加密，密钥大小和连接设备API错误：0x103无效状态：状态：扫描
作为一个解决方案，我正在使用“CyStualReSeTe（）”；“如果在加密错误出现的情况下，在60秒的两侧和规划上做同样的事情。”
有没有办法告诉心率传感器关于心率收集器的复位？或任何解决办法，使所有设备将同步。
但不要觉得这是一个更好的方法。



     以下为原文
  Thanks For the patience..!!
 
Can you please look(in Teraterm-master.txt): after Line 57967.
 
as main problem causes after this and am unable to figure out as you can see scan progress shows the peripheral devices(00a050000aaa/bbb/ccc/ddd) but unable to connect.
 
device-3 is anyhow down so i am getting CYBLE_EVT_TIMEOUT: 4
 
Then i get start getting CYBLE_EVT_GAP_AUTH_FAILED, reason: INSUFFICIENT_ENCRYPTION_KEY_SIZE and ConnectDevice API Error: 0x103 invalid state: state: scanning
 
for time being as a workaround am using "CySoftwareReset();" for the 60 sec on both side and planning to do same if encryption error comes.
 
is there any way to inform heart rate sensor about heart rate collector has resetted?or any workaround so that all devices will be in sync.
 
but don't feel this is a better way.

看起来你的一个连接尝试失败了，之后你的代码/状态机退出了WAKE，并在继续扫描时开始尝试连接。
尝试为失败案例添加处理程序：连接、扫描、读取数据、加密等。
这样，如果重试加密失败，可以多次重试；如果加密失败，则重置加密数据，等等。
我认为代码看起来是按时间复用方式运行的，而您只需要处理故障案例。



     以下为原文
  It looks like one of your connection attempts fails, after which your code/state machine gets out of wack and starts trying to connect while still scanning, etc.
Try adding handlers for failure cases for: connecting, scanning, reading data, encrypting, etc.
That way, you can say retry encryption a couple times if it fails; Reset the encryption data if it fails too much, etc.
I would say the code looks to be behaving in a time-multiplexing fashion, and you just need to handle the failure cases.