BLE TO BLE

RE: BLE TO BLE

Simonr — Wed, 23 Mar 2022 07:36:52 GMT

Okay, then you might want some more sophisticated and dedicated peripheral/central devices. You can for example check out the Central UART and Peripheral UART sample projects, which come with more in-depth documentation on how they work. The peripheral UART sample demonstrates how to use the Nordic UART Service, and you can use the advertiser set up with advertising its service and name as a template for the functionality you want.

The Central UART does the same for the central side, where it scans for peripherals with the Nordic UART service by default, you can modify it to scan for I.E. a specific device name or service that you want.

Best regards,

Simon

RE: BLE TO BLE

Yash Shah — Tue, 22 Mar 2022 10:45:43 GMT

Hello,

Basically My requirement is one BLE communicate (Advertiser) is another fixed BLE (Observer).

Example:

Advertiser: Here We can advertise the another BLE (device name or UUID ) and communicate this device.

Scaner (Observer) : Here we can define fixed Device name and match the device name as per we can do some event .

Regards

Yash Shah

RE: BLE TO BLE

Simonr — Tue, 22 Mar 2022 08:47:58 GMT

Please check out our BLE advertising tutorial for information on what the BLE advertisement data can include (note that this one was made for the nRF5 SDK, but the advertising concepts are still the same). This is mainly device name, UUIDs, service data, and perhaps some custom data.

What exactly do you want do advertise, and are you having issues picking it up on the scanning (central) side?

Best regards,

Simon

RE: BLE TO BLE

Yash Shah — Mon, 21 Mar 2022 11:56:55 GMT

Hello,

As per my understanding one BLE is set in broadcasting mode and another one is observer(Central) mode.

So What exactly I can broadcast ? (I have 19 byte Frame ) and How to recieve data on another BLE connection less (scan mode ) But what exactly scan method in observer mode. Please suggest me.

Like this advertise the data

manu_fact_data[0] = 0x01; //Length
manu_fact_data[1] = 0xFF; //AD Type
manu_fact_data[2] = 0x61; //Company Identifier
manu_fact_data[3] = 0x35;
manu_fact_data[4] = 0xAA; // Product ID
manu_fact_data[5] =
manu_fact_data[6] =
manu_fact_data[7] =
manu_fact_data[8] =
manu_fact_data[9] =
manu_fact_data[10] =
manu_fact_data[11] =
manu_fact_data[12] =
manu_fact_data[13] =
manu_fact_data[14] =
manu_fact_data[15] =
manu_fact_data[16] =
manu_fact_data[17] = 0x00;
manu_fact_data[18] = 0x00;
manu_fact_data[19] = 0x00;

advertising_init();

Regards

Yash Shah

RE: BLE TO BLE

Simonr — Mon, 21 Mar 2022 08:41:40 GMT

If you are new to the Nordic development scene I would recommend you get started with the nRF Connect SDK instead of the nRF5 SDK, as new features will only be added to the nRF Connect SDK as per this informational notice.

You can follow our getting started guide for the nRFConnect SDK here, and the Scan and Advertise application I linked to will have example code in the nRFConnect SDK once it's installed.

Best regards,

Simon

RE: BLE TO BLE

Yash Shah — Sat, 19 Mar 2022 06:35:18 GMT

Hello,

Thank you for reply but can you provide Nordic nrf52 example code because I am beginner in nordic

Regards

Yash Shah

RE: BLE TO BLE

Simonr — Tue, 15 Mar 2022 14:17:16 GMT

I think the easiest here would be to use the Bluetooth Scan & Advertise sample application in Zephyr. This application demonstrates a combined BLE broadcaster & observer role. If you flash it onto two devices both should be able to scan the others advertisements for example. You can also use a beacon on one end and turn of the advertiser to only have a scanner.

Best regards,

Simon