About nRF52840 communication scenario

RE: About nRF52840 communication scenario

Hung Bui — Thu, 15 Aug 2019 12:07:42 GMT

Thanks for the information. In that case if your number of sensor nodes wouldn't exceed 20, you can use normal BLE with one central and up to 20 peripherals. The peripherals can either keep the connection all the time, or can sleep most of the time and wakeup, establish a connection, transfer data and sleep again.

If you want to simplify the protocol, you can think of using ESB. It will be lower power consumption, but there isn't any channel hopping, of time synchronization.

No need for mesh here.

RE: About nRF52840 communication scenario

Ekmekci — Thu, 15 Aug 2019 11:49:47 GMT

Dear Hung,

Thank you for your attention, you are totally right. I gave small information for describe environment.

Let me try another way,

I have room, room is rectangular. I have also temperature sensor nodes which located different point inside of the room.

I just want to collect these temperature datas via central (master) unit.

Communication will be both direction because when slave send data if master receive correctly, master will send ack data.

All slaves in the room, indoor but there is no obstacle.

Best regards,

RE: About nRF52840 communication scenario

Hung Bui — Thu, 15 Aug 2019 11:23:35 GMT

Hi Ibrahim,

Could you give some more information about the environment ? You mentioned 60m from the furthest slave, but it's outdoor or indoor ? Is there any obstacle, wall ? The range can vary a lot due to the environment.

How is your slave located ? What is the distance between them ?

I assume the communication is only from a slave to the master (both direction ? ) not between slaves ?

From what you described, I don't think mesh topology would be ideal. Mesh would require you to have a number of nodes with main-powered to act as the back-bone of the network.

You can think of using normal BLE star topology with +4dbm or +8dbm output power. Or can think of using proprietary ESB protocol for example.