MULTILINK CENTRAL WITH NUS SERVICE

[Thomasthomas]

HI..i am trying to implement multilink central with nus service..but it is getting error at lbs_c_init();.what is the reason..can anyone help..i also changed the central link count..still no change

[Jared]

Hi,

 What error are you getting? 

Jared

[Thomasthomas]

Hi..now am trying ble_central and peripheral connection..ble_central sending data over ble_nus_c_string_send and it is receivd at peripheral and after that am sending a packet from peripheral to central and it is not receiving(BLE_NUS_C_EVT_NUS_TX_EVT,not receiving anything in central side)

[Thomasthomas]

Hi jored, i hav solved the issue myself..my current problem is,is there amy way to identify from which peripheral the data is received when we hav multiple connections..thanz for ur help

[Jared]

You can find the connection handle in the ble_nus_c_evt_t event structure after a BLE_NUS_C_EVT_NUS_TX_EVT event is generated. 

[Thomasthomas]

Actually not connection handle..i need the peripheral bluetooth id or device id something like that..so that i need to transfer the value received from peripheral to central and from central to server..

[Jared]

Hi, 

The Peer address can be stored after a BLE_GAP_EVT_CONNECTED has been generated. You can find the peer address in the ble_evt_t event structure. Note that most SoftDevice functions do not use the peer address to refer to the peer but rather the connection handle. The connection handle is assigned to the link of the peer during a connection event. 

regards

Jared 

[Thomasthomas]

So we have to add peer manager init()??

[Jared]

What exactly do you need the peer address for? Is there a specific function call where this is necessary to pass as a parameter? The peer manager is used bonding, pairing etc and is not necessary to use for storing the peer address. As I wrote in my previous reply: 

 

Jared said:

The Peer address can be stored after a BLE_GAP_EVT_CONNECTED has been generated. You can find the peer address in the ble_evt_t event structure. Note that most SoftDevice functions do not use the peer address to refer to the peer but rather the connection handle. The connection handle is assigned to the link of the peer during a connection event.