Facing problem in advertising packet formation.

RE: Facing problem in advertising packet formation.

Newbie — Wed, 06 Sep 2017 04:08:35 GMT

Hi, Somehow I was able to figure out my problem. Thanks for help though.

RE: Facing problem in advertising packet formation.

MartinBL — Fri, 01 Sep 2017 12:02:32 GMT

When I tried your code sd_ble_gap_device_name_set() returned error 7 because you have not initialized the variable 'sec_mode'. You can initialize it with e.g.

BLE_GAP_CONN_SEC_MODE_SET_OPEN(&sec_mode);

Is this your problem?

RE: Facing problem in advertising packet formation.

Newbie — Wed, 30 Aug 2017 08:43:20 GMT

Hello Martin, I can add extra bytes in

#define APP_BEACON_UUID                 0xA1,0x02,0x04, 0x2F, 0x64, 0x01, \
                                                            0x3A, 0x03, 0x4A, 0x00, \
                                                           0x3E, 0x01,0x02,0x03

By changing the length in

#define APP_BEACON_INFO_LENGTH          0x0B

So I don't think advertisement packet is full. Can you try at your end by adding few extra bytes and test it. I have tested it and its working. Thanks,

RE: Facing problem in advertising packet formation.

MartinBL — Wed, 30 Aug 2017 07:20:27 GMT

It looks like your advertising packet is full. It can only hold 31 bytes. Here is an explanation of how it works. You can consider to move some of the data over to the scan response packet and effectively double your advertising payload capacity.