CHIP1是如何知道扫描发生的？

如何切换状态
定义CyByLyState（状态）（CyByLyState =（状态））采用与CyByLyGate（）返回值类似的输入参数
仍然需要帮助识别扫描响应包已被发送（外围侧）
并且在中央侧帮助从广告分组识别扫描响应分组。
当做，
维拉杰



     以下为原文
  Got how to switch states

• #define CyBle_SetState(state) (cyBle_state = (state))
  
  
  
  • takes input parameters similar to CyBle_GetState() return values
    
  
  

 
Still need help with recognizing that a scan response packet has been sent(Peripheral side)
And help at central side recognizing a scan response packet from a advertisement packet
 
Regards,
Viraj

当中央设备接收到一个扫描响应包时，将出现CyByLyEvtGAPCXSCAN PrimeSsR.结果，然后可以继续处理模式切换。
不幸的是，我看不到一种方法来访问是否有一个扫描响应发出；CyPress处理他们的二进制广告，因此不太可能有钩子来处理扫描响应发出后的切换模式。
此外，为什么有这样一个奇怪的转换过程，哪一边是扫描和广告？ChIP1可以被设置为总是扫描，然后ChIP2将永远是广告。切换连接启动/设置的方向对于我所能想到的应用程序来说没有多大意义。
你是否已经测试过CyLySyState（状态）定义了你写的作品？我认为你必须调用Cyle函数来打开广告，并且正确地扫描ON/OFF，否则BLE堆栈会崩溃或混乱。



     以下为原文
  CYBLE_EVT_GAPC_SCAN_PROGRESS_RESULT will occur when the central device receives a scan response packet; You can then proceed to handle the mode switching afterwards.
 
Unfortunately, I don't see a way to access whether there was a scan response sent out; Cypress handles the advertisements in their binary, and thus it is unlikely there are hooks to handle switching modes after a scan response was sent out.
Also, why have this odd process of switching which side is scanning and advertising? Chip1 could just be set to always scanning, and then chip2 would be always advertising. Switching the direction of the connection initiation/setup doesn't make alot of sense for applications that I can think of.
 
Have you tested that the CyBle_SetState(state) define that you wrote works? Afaik, I thought you had to call cyble functions to turn the advertising, and scanning on/off properly otherwise the BLE stack crashes or messes up

CysLyStState（状态）没有，也没有返回任何东西，所以我不知道为什么。我放弃了那个API
我想先从ChIP1开始发布一个中断的广告，然后我希望ChIP1能够从ChIP2中听到指令，而ChIP2也必须等待其他芯片的类似事件。
因此，直到我命令CHIP2，它仍然会扫描，当收到命令，它切换到广告，广告所需的数据，然后回到扫描仪监视其他芯片的其他中断。
当做，
维拉杰



     以下为原文
  The CyBle_SetState(state) didn't and it's not returning anything too, so I couldn't figure out why. I dropped that API
 
I want to issue advertisement initially form Chip1 for an Interrupt, and then I want Chip1 to listen for instructions from Chip2, while Chip2 must wait for similar events form other chips too
So until I command Chip2 it will still scan, and when command is received it switches to Advertisement, advertises the required data, and then goes back to Scanner for monitoring other interrupts from other chips
 
Regards,
Viraj

嗯，我建议发送一对夫妇的广告，而不是仅仅一个（无线传输容易出错）。然后，当您切换CHIP1进行扫描时，设置超时，以防CHIP2没有接收到广告，然后它可以重试广告或处理您想要的应用程序中的问题。
对于这样的设置，我将设计CHIP1进行被动扫描，当它得到并中断连接到CHIP2（设置为广告）时，读取当前在广告包中返回的数据/值，然后断开连接，以允许其他设备连接和读取。当他们需要数据时。唯一的缺点是处理多个设备同时试图连接的错误/定时，但是它简化了BLE模式到只有一个。
埃普拉特



     以下为原文
  Hmmmm; I would suggest sending a couple advertisements rather than just one (wireless transmissions are prone to error). Then, when you switch Chip1 to scan, set a timeout in case the Chip2 didn't receive the advertisements and then it can retry the advertisements or handle the issue in your app how you want.
 
For a setup like this, I would architect Chip1 to be passively scanning, and when it gets and interrupt to connect to Chip2 (which is setup as advertising), read the data/values you are currently returning in the advertisement packets, and then disconnect to allow other devices to connect and read the data when they need it. The only downside to this is handling the errors/timing for multiple devices trying to connect at the same time, but it simplifies the BLE mode to only one.
 
Epratt