CYBLE 012011 BLE not discoverable on CySmart App

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
AmMa_2724956
Level 2
Level 2
First like received

Hello,

I had written a code  which used BLE, emEEPROM and ADC blocks.

The code works fine on CYBL-11573-56LQXI and CYBL022001 PSoC 4 BLE modules. The device is discoverable on CySmart app and functionality also works.

The exact same code on CYBLE 012011 BLE module does not work. The device is not discoverable on CySmart app.

What could be the issue.

Thanks,

Ameya

0 Likes
1 Solution

Hello Ameya,

1) Sometimes the device gets disconnected (more so on specific devices, even though the android version of the device is same).

Ans: There will be some problem with particular mobiles. Can you please let us know the disconnection error that you are getting. For this in firmware, you can get the event parameter value from the CYBLE_EVT_GAP_DEVICE_DISCONNECTED event as follows:

Printf ("Error code is: 0x%x \r\n",*(uint8 *) eventParam);

2) On some devices the services are not discoverable (although the ble module is visible)

Ans: Can you change the default Bluetooth base UUID with a different base UUID. To do so, change the UUID from the Bluetooth base UUID, i.e., it should not be of the format 00000000-0000-1000-8000-00805F9B34FB (which is generated in BLE Component custom service/characteristic UUID). You must edit the number format of the custom characteristic / service UUID to make it different from the Bluetooth base format.

Thanks,

P Yugandhar.

View solution in original post

0 Likes
3 Replies
Yugandhar
Moderator
Moderator
Moderator
500 solutions authored 1000 replies posted 5 likes given

Hello Ameya,

Can you please check with different mobiles. Can you please share your project?

Thanks,

P Yugandhar.

0 Likes

Hello PY_21,

Thanks for replying.

Earlier it was not working on any device with the module. Then I changed the project, that is created new project with the same code.

It worked like other two modules. It is discoverable.

But there are some issues (irrespective of the module)

1) Sometimes the device gets disconnected (more so on specific devices, even though the android version of the device is same).

2) On some devices the services are not discoverable (although the ble module is visible)

Thanks,

Ameya

0 Likes

Hello Ameya,

1) Sometimes the device gets disconnected (more so on specific devices, even though the android version of the device is same).

Ans: There will be some problem with particular mobiles. Can you please let us know the disconnection error that you are getting. For this in firmware, you can get the event parameter value from the CYBLE_EVT_GAP_DEVICE_DISCONNECTED event as follows:

Printf ("Error code is: 0x%x \r\n",*(uint8 *) eventParam);

2) On some devices the services are not discoverable (although the ble module is visible)

Ans: Can you change the default Bluetooth base UUID with a different base UUID. To do so, change the UUID from the Bluetooth base UUID, i.e., it should not be of the format 00000000-0000-1000-8000-00805F9B34FB (which is generated in BLE Component custom service/characteristic UUID). You must edit the number format of the custom characteristic / service UUID to make it different from the Bluetooth base format.

Thanks,

P Yugandhar.

0 Likes