multiple peripheral to Single central connection

RE: multiple peripheral to Single central connection

Murugan — Wed, 19 Oct 2016 13:33:56 GMT

I got it From NRF_FICR->DEVICEID[0],NRF_FICR->DEVICEID[1].

Thanks for supporting

RE: multiple peripheral to Single central connection

Murugan — Wed, 19 Oct 2016 12:48:17 GMT

please mention read and display procedure . i get always :ffffff000000

RE: multiple peripheral to Single central connection

Sigurd — Wed, 19 Oct 2016 12:35:18 GMT

device_addr is a ble_gap_addr_t struct that looks like this:

	typedef struct
{
  uint8_t addr_id_peer : 1;       /**< Only valid for peer addresses.
                                       Reference to peer in device identities list (as set with @ref sd_ble_gap_device_identities_set) when peer is using privacy. */
  uint8_t addr_type    : 7;       /**< See @ref BLE_GAP_ADDR_TYPES. */
  uint8_t addr[BLE_GAP_ADDR_LEN]; /**< 48-bit address, LSB format. */
} ble_gap_addr_t;

So the adress is stored in device_addr.addr

RE: multiple peripheral to Single central connection

Murugan — Wed, 19 Oct 2016 12:30:08 GMT

I am using below procedure but cant read mac id.

err_code = sd_ble_gap_address_get(&device_addr); VERIFY_SUCCESS(err_code);

RE: multiple peripheral to Single central connection

Sigurd — Wed, 19 Oct 2016 11:41:53 GMT

You can read out the address using the API call, "sd_ble_gap_address_get(..);"

RE: multiple peripheral to Single central connection

Murugan — Wed, 19 Oct 2016 11:37:14 GMT

Hi, How to get own mac address ???

RE: multiple peripheral to Single central connection

Sigurd — Tue, 18 Oct 2016 11:31:42 GMT

The battery value is not by default a part of the advertisement packet, so you will need to use the ADC to read the battery voltage, and then add it to the advertisement packet. Here is an old example on how it can be done.

RE: multiple peripheral to Single central connection

Murugan — Tue, 18 Oct 2016 08:01:19 GMT

Thank you very much for your great support. Finally i want to read battery value.

RE: multiple peripheral to Single central connection

Sigurd — Tue, 18 Oct 2016 07:28:41 GMT

In the function on_adv_report(), you can get the rssi with this code:

int8_t rssi = p_ble_evt->evt.gap_evt.params.adv_report.rssi;

RE: multiple peripheral to Single central connection

Murugan — Tue, 18 Oct 2016 06:27:45 GMT

I got a slave device id using p_adv_report->peer_addr.addr. Also i need slave RSSI value ??? How can i get this RSSI ????

RE: multiple peripheral to Single central connection

Murugan — Tue, 18 Oct 2016 03:28:38 GMT

Hi, I am using Temite 3.1 terminal. I am using nRF5_SDK11_Changed.rar.

RE: multiple peripheral to Single central connection

Sigurd — Mon, 17 Oct 2016 18:21:20 GMT

Also, if you only want to scan for devices, and display the device name, you can take a look at the nRFConnect application for PC.

RE: multiple peripheral to Single central connection

Sigurd — Mon, 17 Oct 2016 17:11:15 GMT

Are you using the multilink_central example from SDK or the example from nRF5_SDK11_changed.rar? Both uses 115200 baudrate. The SDK-example uses flowcontrol, but the "nRF5_SDK11_changed" is not using flow-control. What PC terminal program are you using? Make sure your terminal on the PC have the correct setting.

RE: multiple peripheral to Single central connection

Murugan — Mon, 17 Oct 2016 16:38:23 GMT

I am not receive any data from uart like "Start scane ....." . I am using ic pak QFAC

RE: multiple peripheral to Single central connection

Sigurd — Mon, 17 Oct 2016 16:23:27 GMT

In nRF5_SDK11_changed.rar, UART data is sent to the peripherals. Is this what you want? Or do want to send the data to the PC? If you only want to send the data to the PC you can use the ble_app_multilink_central example in the SDK. Also, what nRF51422 chip do you have? is it QFAA?

RE: multiple peripheral to Single central connection

Murugan — Mon, 17 Oct 2016 15:45:16 GMT

Thanks for Quick response. All are changed and code was downloaded but still no response.

RE: multiple peripheral to Single central connection

Sigurd — Mon, 17 Oct 2016 13:58:41 GMT

In that project the debugger interface was set to ULINK2. For the nRF51-DK you will need to change to J-LINK. Click on project, go to Options for Target "nrf....." -> Debug. In the dropdown menu change to JLINK / J-TRACE Cortex.

RE: multiple peripheral to Single central connection

Murugan — Mon, 17 Oct 2016 13:40:24 GMT

Please download and check devzone.nordicsemi.com/.../

In Command area nRF5_SDK11_changed.rar

Because it is same as my application.

RE: multiple peripheral to Single central connection

Sigurd — Mon, 17 Oct 2016 13:26:20 GMT

You need to use the project in \SDK_INSTALL_FOLDER\examples\ble_central\ble_app_multilink_central\pca10028\S130\arm5_no_packs. Make sure that you have loaded SoftDevice S130.

RE: multiple peripheral to Single central connection

Murugan — Mon, 17 Oct 2016 13:24:31 GMT

But That example code was not run my nRF51422 SDK.

RE: multiple peripheral to Single central connection

Sigurd — Mon, 17 Oct 2016 13:18:39 GMT

You don't need to change the RAM settings, nRF51822 and nRF51422 uses the same settings.

RE: multiple peripheral to Single central connection

Murugan — Mon, 17 Oct 2016 13:12:11 GMT

I got one more link : devzone.nordicsemi.com/.../

Is this correct example for my application.

Now I want to know the how set memory for nRF51822 to nRF51422 Untitled1.png

Please guide me.

RE: multiple peripheral to Single central connection

Sigurd — Mon, 17 Oct 2016 12:54:22 GMT

Yes, in multilink_central example, in the function on_adv_report() the device name is saved in the variable dev_name. When the device name is found, found_name is true.

RE: multiple peripheral to Single central connection

Murugan — Mon, 17 Oct 2016 12:30:21 GMT

If possible for multilink uart central ????

Do you have any example code ??? I am using SDK11.0.

RE: multiple peripheral to Single central connection

Sigurd — Mon, 17 Oct 2016 12:04:52 GMT

If you are only scanning, and not connecting, you only need the ble_app_uart_c example code. The device name can be found in p_ble_evt->evt.gap_evt.params.adv_report.data.