CY8C4248LQI-BL483上的广告活动持续时间取决于扫描响应吗

你知道你看到的频道间延迟范围的测量结果吗？（你能在这儿张贴吗？）
否则，这听起来像一个用柏树无线电代码处理柏树的错误。



     以下为原文
  Do you know the measurements of the inter-channel-delay range you were seeing? (can you post them here?)
Otherwise, that sounds like a bug with the BLE radio code for cypress to handle

谢谢你的回答！
第一个图显示了具有30字节有效载荷数据和0字节的广告响应事件的广告事件的功耗。在所有三个频道的广告的整个持续时间大约为5.5毫秒。
第二个图显示了具有相同设置的广告事件的功耗，除了扫描响应分组：选择了31个字节的有效载荷。
肉眼可见，两个通道间延迟较长，导致总持续时间约为6.6毫秒。
对于这个测量，来自CyPress 100的代码在100天内进行项目，第27天使用BuryPosil测量[1 ]。如前一篇文章中所提到的，我正在改变的是在“空白设置”、“外围角色”和“扫描响应包”下的扫描响应的有效载荷量。
最好的问候！
〔1〕HTTPS://GITHUBCOM/CyPress半导体ToC/COPS-4-BLU/TRAE/MIST/100A项目，在100100天/Day027



     以下为原文
  Thanks for your answer!
The first plot shows the power consumption of an advertising event with 30 Bytes of payload data and 0 Bytes for the scan response packet. The whole duration of the advertising on all three channels is about 5.5 ms.

 
The second plot shows the power consumption of an advertising event with the same settings, except for the scan response packet: There 31 Bytes of payload were chosen.

Visible to the naked eye, the two Inter-Channel-Delays are longer, resulting in a total duration of about 6.6 ms.
 
For this measurement the code from Cypress 100 Projects in 100 Days, Day 27 BLE_Power_Measurement was used[1]. As mentioned in the previous post, all I am changing is the amount of payload for the scan response under tab "Gap Settings", Peripheral role -> Scan response packet.
 
Best regards!
 
[1] https://github.com/cypresssemiconductorco/PSoC-4-BLE/tree/master/100_Projects_in_100_Days/Day027_BLE_Power_Measurement

假设项目中的所有组件都已更新到最新版本（BLE看起来像V5.5是最新版本）？；
潜在的这种延迟可能是由于省电模式的怪异，扫描响应数据的缓冲区溢出，或者正在处理的/正在运行的中断。
不过，我认为我同意您最初的评估，CyPress库很可能有一个错误导致这个延迟随扫描响应数据波动。



     以下为原文
  Assuming you have all of your components in the project updated to the latest versions (BLE looked like v5.5 was latest?);
Potentially this delay could be caused by something weird with power saving mode, buffer overflow of the scan response data, or interrupts being handled/functions being run.
However, I think I agree with your initial assessment that the cypress library most likely has a bug causing this delay to fluctuate with scan response data.

非常感谢你的帮助！最新版本应该是V3.30A（根据CyPress的网站），是的，我正在使用这个版本。
有没有可能从一个柏柏尔人那里得到答案？



     以下为原文
  Thanks a lot for your help! The latest version should be v3.30a (according to Cypress' website) and yes I am using this version.
Is there any possibility to get an answer from one of the Cypress guys?

对不起，你是对的，版本是BLE组件的3.30（我读错了）
潜在的，你可以打开他们的案件，以获得与塞浦路斯FAES的直接沟通，确定问题的原因。



     以下为原文
  Sorry, you're right; the version is 3.30 for the BLE component (I misread that pretty bad )
Potentially, you could open a case with them to get some direct communication with the Cypress FAEs on determining the cause of the issue.