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
1 of 1 people found this helpful
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. 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.
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.
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?
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.