error in ble_app_beacon sample when modyfing advertising parameters

RE: error in ble_app_beacon sample when modyfing advertising parameters

Artucas — Tue, 19 Apr 2016 19:21:35 GMT

That is correct indeed. I might misunderstood your question previously. It is obvious as you stated your self, if you are initializing beacon to normal mode, gap and conn params are not initialized, so you can't connect to the device, cuz you skipped configuration for doing that.

RE: error in ble_app_beacon sample when modyfing advertising parameters

Revo — Tue, 19 Apr 2016 19:09:59 GMT

Well, as you can see, in the function beacon_setup, if the beacon is NOT in config mode (which is normal mode, just turning it on) it just executes the advertising_init and not the initialization of connection parameters, gap parameters and so on, so i think it can't obviously connect like this. This is probably the problem right?

RE: error in ble_app_beacon sample when modyfing advertising parameters

Artucas — Tue, 19 Apr 2016 13:57:13 GMT

Well i obviuosly might be missing something, but after quick skim i didn't see anything wrong with the code. Did you try to look where your code hangs up? Does it end in app_error_handler or somewhere else? Hard to say something more from just looking at the code, can't test it right now.

RE: error in ble_app_beacon sample when modyfing advertising parameters

Revo — Tue, 19 Apr 2016 13:15:33 GMT

I added the code, however i think i found out the solution; in the initialization of the beacon, if in normal mode there is only advertising_init called, instead in the config mode there is everything (in config it always worked, connection included). Now i just substituted the config mode with the normal mode, deleting the "if" statements. Please confirm!

RE: error in ble_app_beacon sample when modyfing advertising parameters

Artucas — Tue, 19 Apr 2016 13:03:49 GMT

post full code of main.c

RE: error in ble_app_beacon sample when modyfing advertising parameters

Revo — Tue, 19 Apr 2016 12:52:22 GMT

I checked the functions advertising_init, gap_params_init, conn_params_init, the only difference i found between the two codes (besides the already cited NONCONN of course) is in conn_params_init:

cp_init.start_on_notify_cccd_handle    = m_hrs.hrm_handles.cccd_handle;; // what there is in the heart rate example

cp_init.start_on_notify_cccd_handle    = BLE_GATT_HANDLE_INVALID; // what i have in my code

However i don't think this is important, at this stage i don't want to send any data but just set up the connection between devices.

RE: error in ble_app_beacon sample when modyfing advertising parameters

Artucas — Tue, 19 Apr 2016 12:39:20 GMT

I don't remember now, but i think there is a lot more info put there in advertisement packet in that beacon example (UUID for example). You can use debugger actually to see what is put inside. As for gap_params, i don't remember that beacon example had those params set. Take a close look at the provided example. Are you sure you are setting gap_params and conn_params correctly?

RE: error in ble_app_beacon sample when modyfing advertising parameters

Revo — Tue, 19 Apr 2016 12:20:50 GMT

Yes i know that but it can't be that since the name included in the example is by default (BeaconConfig in particular), it's just not shown because in the parameters there is NO_NAME by default. However i also tried to change this name to a single letter to make it as short as possible and it doesn't change anything, it still doesn't advertise (note, just by changing the name OR changing the connection parameters). I'm having a bit trouble understanding where is the problem ^^

RE: error in ble_app_beacon sample when modyfing advertising parameters

Artucas — Tue, 19 Apr 2016 12:16:34 GMT

This might happen if your device name is too long. Keep in mind that your advertisement packet size is only 31 byte. I have asked some time ago about structure of advertisement packets. You can read about it here advetisement-packet-structure. That should make things a little clearer for you.

RE: error in ble_app_beacon sample when modyfing advertising parameters

Revo — Tue, 19 Apr 2016 12:06:31 GMT

Thanks. I see also that if i change the field of my beacon's name, which in the code is NO_NAME, to FULL_NAME, it happens the same thing, is for the same reason? I can't modify these parameters like this? I am going to check shortly the example you posted!

EDIT: i am looking at the heart rate example, the gap_params_init and adv_init seems pretty similar to the one in the ble_app_beacon example, where should i look to see how make my code connectable?

RE: error in ble_app_beacon sample when modyfing advertising parameters

Artucas — Tue, 19 Apr 2016 12:01:58 GMT

Changing m_adv_params.type = BLE_GAP_ADV_TYPE_ADV_NONCONN_IND;to m_adv_params.type = BLE_GAP_ADV_TYPE_ADV_IND; is not enough. This example doesn't allow to do connections.

See ble_app_hrs example. That has all the configurations you need to do connections -> ble_app_hrs