CYBLE_EVT_GAPC_SCAN_PROGRESS_RESULT will get trigger when the Central will receive adv data from any BLE peripheral. So what you were seeing may not be the same device, it will be different devices.
Please refer our Central projects for reference: https://github.com/cypresssemiconductorco/PSoC-4-BLE/tree/master/100_Projects_in_100_Days
Refer Day 10, 11
Thanks & Regards,
1 of 1 people found this helpful
It is also possible that you are performing an active scan, which will cause the peripheral to send an additional packet (called a scan response) immediately after the primary advertisement packet. The scan response usually contains less important information like a partial or complete device name, which your application rarely needs to process. You can perform a passive scan instead by setting the correct value before calling the CyBle_GapcStartScan() function:
cyBle_discoveryInfo.scanType = CYBLE_GAPC_PASSIVE_SCANNING;
If you don't need or want to switch between active and passive mode in code, you can also set this as the default scan mode in the BLE component configurator: