BLE_HID_Keyboard example reconnect to android takes 20 secs

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

cross mob
user_1881301
Level 2
Level 2
First like received

17-05-2017 11:38:16.770 [RX] - HID notification: 00,00,00,0c,00,00,00,00,<CR><LF>

   

reset pioneer board at 11:38:17

   

17-05-2017 11:38:17.837 [RX] - BLE HID Keyboard Example Project <CR><LF>

   

Bluetooth On, StartAdvertisement with addr: 00a050000008<CR><LF>

   

CYBLE_EVT_ADVERTISING, state: 3 <CR><LF>

   

reconnect at 11:38:37 - 20 seconds later

   

17-05-2017 11:38:37.224 [RX] - CYBLE_EVT_GATT_CONNECT_IND: 0, 4 <CR><LF>

   

CYBLE_EVT_GAP_DEVICE_CONNECTED <CR><LF>

   

AUTH_COMPLETE: security:1, bonding:1, ekeySize:10, authErr 0 <CR><LF>

   

CYBLE_EVT_GAP_ENCRYPT_CHANGE: 1 <CR><LF>

   

HID notification: 00,00,00,01,00,00,00,00,<CR><LF>

   

how is the re-connection time reduced ?

0 Likes
5 Replies
Anonymous
Not applicable

Scan interval, passive versus active scanning, connection parameters, etc.

0 Likes

The HID example sends advertising packages every 25ms the first 30 secs.

   

I'm using a "standard" android based mobile phone and a "standard" notepad app as the receiver of the HID keyboard keys - so none of the mentioned parameters can be changes at that end.

   

The very first connect is done within a second - but the auto re-connect is always taking 20 secs.

0 Likes
Anonymous
Not applicable

Are you hard resetting? Soft resetting might have different results.

   

Have you tried running a debugger on the PSoC? Determing what the timing is on the chip might shed light on what is causing it to take so long.

   

Have you checked the supervision timeout setting on the PSoC? (That is the time until it times out with no received packets from the other side of the connection).

0 Likes

Yes hard resetting the CYBLE-222-005 (via the reset key on the Pioneer test board) - then it starts advertising, and the Android is responding after 20 secs. Checked with the TI CC2540 BT packet sniffer.

   

I'm running the program from the PSoC 4 Creator/debugger.

0 Likes
Anonymous
Not applicable

Since the BLE device is only advertising, it is NOT the one initiating the connection, that would be the Android phone. So, if it takes that long it is either the connection parameters (which you can't change) or the android phone is really slow in finding it...

   

Since you checked with the packet sniffer, then that means the BLE is actually advertising on the CYBLE. I'm not sure what more you could do from the CYBLE standpoint 😕

0 Likes