ble_app_multilink_central on PCA10001

[jeff]

Hi,

I'm attempting to use 'S120/experimental/ble_app_multilink_central' running on a pca10001 to better understand the central / peripherial comm sequencing on the nrf51.

Using the ble_app_multilink_central with no changes except for the TARGET_DEV_NAME can someone help me understand the peripherial configuration details that will cause the central in this default configuration to generate events?

Thanks,

Jeff

[jeff]

Hi Erik.

Thanks for your reply. I'm not having any issues with the S120 central configuration as such, but was asking, perhaps not as clearly as possible, for suggestions on a peripheral configuration that will work with this default S120 central on a PCA10001.

I have a TI SensorTag device (sorry Nordic) and changed the TARGET_DEV_NAME in the ble_app_multilink_central to 'SensorTag' expecting that the PCA10001 loaded with this central app and the S120 would see/respond the TI device. Alas, nothing.

What am I missing? I'm still fairly new with these devices and wanted to use this as leanring for the central/peripheral configurations.

Thanks again Erik for your help!

[Erik Sanchez]

OK, well in that case you would probably want to change TARGET_DEV_NAME like you did and also change the following in client_handling.c to match your sensor tag service UUIDs:

MULTILINK_PERIPHERAL_BASE_UUID and MULTILINK_PERIPHERAL_SERVICE_UUID so that the central will attempt to connect to the service you're advertising.

Also, MULTILINK_PERIPHERAL_CHAR_UUID so that it will find an the appropriate service during discovery and enable notifications.

The central makes some assumptions about the notification size and format (sizeof:1) but you can make whatever changes you need in the on_evt_hvx() function in client_handling.c.

Hope this helps.