CC2541: Disabling Scan in CC2541

Hi Clement,

Yes, sure. I am using CC2541 in the  ECU for the pneumatic module. So the ECU gets advertisements from BLE enabled pressure sensors and ECU then advertises to the connected phone and the details will be displayed in app. Currently I am facing connection problem with the phone (some times it takes time(5-10s) to get connected (sometimes it doesn't bond in some devices)  and I wanted to test step by step and so first i want to disable the scanning from my ECU and check the connection (if the unit was overloaded by the scanning).

So yes, I have already disabled GAPObserverRole_StartDiscovery() , but then it not only disables scanning, the unit itslef becomes non discoverable in the phone too, which is not what I wanted. I see in some BLE stack, the GAPROLE_Scan_Disable, which I cannot find my in my BLE stack.

Best,

Varun

Hi Varun,

May I ask you where you have found the code example you have used as base for your project?

When it comes to advertisement, they are enabled by the following code:

uint8 new_adv_enabled_status = TRUE;
GAPRole_SetParameter( GAPROLE_ADVERT_ENABLED, sizeof( uint8 ), &new_adv_enabled_status );

Best regards,

Hi Clement,

Thanks for your reply. Since this is a legacy project, we received the code from our counter part. But however, advertisements are already enabled like the way you suggested during initialization. 

However, while testing with various android phones using sniffer apps, I observed with some devices it is working as intended but in some, it is not getting bonded and when I try to bond it with phone, the unit (ECU) goes undiscoverable. I killed the app and checked in other phones, but it is still undiscoverable and hence I need to restart the CC2541 again to be discoverable to devices. I am curious if anyone here faced such problems ?

Best,

Varun

Hi Varun,

I haven't found any case with a similar issue. It may mean something wrong is going on with the application layer.

With the details currently shared, I am not sure I can go further in the analyze of this issue. Maybe, some BLE sniffer logs could help.

Best regards,