Hauke Petersen

could you give a specific example for your proposal? But if I understand it correctly, I like this!

I think I like this as proposed. How about a simple `Usage` as section name?

Yes, it is indeed not easy to find. Take a look at `nimble/controller/syscfg.yml`: ``` BLE_LL_CFG_FEAT_DATA_LEN_EXT: description: > This option enables/disables the data length update procedure in the controller. If enabled,...

of course: ``` _adv_params.scannable = 0; _adv_params.own_addr_type = nimble_riot_own_addr_type; _adv_params.channel_map = BLE_GAP_ADV_DFLT_CHANNEL_MAP; _adv_params.filter_policy = 0; _adv_params.itvl_min = _config.advertiser_itvl_min; _adv_params.itvl_max = _config.advertiser_itvl_max; _adv_params.tx_power = 127; _adv_params.primary_phy = BLE_HCI_LE_PHY_1M; _adv_params.secondary_phy = BLE_HCI_LE_PHY_1M;...

Quick update: yesterday and tonight my 24h experiment was running for a second time. From the logfiles of the experiment I can see, that exactly 65565 seconds after the nodes...

Unfortunately #1114 did not fix this issue: I did run another 24h experiment on Saturday using the latest NimBLE master and it showed the same behavior as described above: after...

Yes, I published everything as part of the artifact evaluation of our paper: https://github.com/ilabrg/artifacts-ccr-ipbleadv The code for the app is under `ea/app_jelling/`. For our initial experiments, we were using the...

Forgot to mention: I can see this behavior (almost) independent of the advertising interval and payload size. I tested advertising intervals in [20, 50, 100, 200, 500, 1000, 2000]ms and...

> We use the same phy for both nRF52832 and nRF52840 so it should behave pretty much the same I know, also the RIOT code suporting that CPU is almost...

Hej, I was running in similar issues when running a node with many multiple connections. I got it to work, by increasing NimBLE's buffer space -> as I was running...