• State Not Answered
  • Replies 4 replies
  • Subscribers 87 subscribers
  • Views 573 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 277804
Options

Which module for 1000x unit low range mesh

Pinchy

Hi everyone, I’m have a wired network of 1000 devices (relay switches) that I’ve been tasked to upgrade to wireless.

  • Devices are inside a warehouse, about a pallet apart (~1m). So each device would be ~1m away from at least 4 others, 10m away from at least 40 others, all devices would be within a 100m radius of each other
  • Devices are powered by wired 24VDC.
  • Devices need to broadcast a "heartbeat" at least daily, no acknowledgement required
  • ~50 devices need their state changed (on/off) every minute or so, acknowledgement required
  • Each device is unique, rather than a group, so unicast messaging (or grouping IDs in a multicast message) may be required

I’ve used the nrf52832 before and liked it so would like to explore other Nordic options  

my question is, is the above problem solvable using Bluetooth 5? If so, which would be the cheapest module to use? What are some considerations to explore? Thank you!! 

Parents
  • 0

    Hello Pinchy,

    Good day.

    nRF52840 with nRF5 SDK based Mesh SDK is good enough for your setup until mesh specification V1.0.  As Mesh Specification is based on an older version of the Bluetooth low energy specification (BLE 4.0). You can find the The versions of nRF5 SDK for mesh here in this link (Nordic Semiconductor Infocenter)  you also can look at this devzone case as well about the long range-  nRF52840-DK: Coded PHY (Long-range) Mesh SDK - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com) , Nordic DevZone (nordicsemi.com). 

    One suggestion regarding your network density:-  as the network density seems high if it is needed you can decrease the number of relay nodes. As having too many relay will cause a huge load on the network and disturbance between the nodes. In mesh specification 1.0 - The flooding based approach to message relaying can cause a lot of redundant traffic on air, which may impact the throughput and reliability of the network. Therefore, it is highly recommended to limit the number of relays in a network to restrict this effect. The rate of relay-enabled devices in the network is a trade-off between message route-redundancy and reliability. It should be tuned according to network density, traffic volumes, network layout, and requirements for reliability and responsiveness.

    Suggestion about SoC selection:- If you are open to use NCS nRF Connect SDK , it would be beneficial to use nRF53 to make your network compatible with future requirements and specification.  Though  which SOC you would use, it depends on what features/resources you need and what kind of applications you plan to develop.  You can look at this link: nRF Connect SDK and nRF5 SDK statement - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com). There are more profiles those are supported in NCS Mesh than nRF5 Mesh SDK, so, you can find and select more features to choose from. Some of those features might also help you improving the network stability and node communication.

    Based on the above suggestions, you may have an idea which SoC would meet up your purpose and regarding the most economical one, you can contact Regional Sales Manager(RSM)  Contact us - nordicsemi.com . 

    Hope it helps. Feel free to ask if you need any more information. 

    Best Regards,

    Kazi Afroza Sultana

Reply
  • 0

    Hello Pinchy,

    Good day.

    nRF52840 with nRF5 SDK based Mesh SDK is good enough for your setup until mesh specification V1.0.  As Mesh Specification is based on an older version of the Bluetooth low energy specification (BLE 4.0). You can find the The versions of nRF5 SDK for mesh here in this link (Nordic Semiconductor Infocenter)  you also can look at this devzone case as well about the long range-  nRF52840-DK: Coded PHY (Long-range) Mesh SDK - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com) , Nordic DevZone (nordicsemi.com). 

    One suggestion regarding your network density:-  as the network density seems high if it is needed you can decrease the number of relay nodes. As having too many relay will cause a huge load on the network and disturbance between the nodes. In mesh specification 1.0 - The flooding based approach to message relaying can cause a lot of redundant traffic on air, which may impact the throughput and reliability of the network. Therefore, it is highly recommended to limit the number of relays in a network to restrict this effect. The rate of relay-enabled devices in the network is a trade-off between message route-redundancy and reliability. It should be tuned according to network density, traffic volumes, network layout, and requirements for reliability and responsiveness.

    Suggestion about SoC selection:- If you are open to use NCS nRF Connect SDK , it would be beneficial to use nRF53 to make your network compatible with future requirements and specification.  Though  which SOC you would use, it depends on what features/resources you need and what kind of applications you plan to develop.  You can look at this link: nRF Connect SDK and nRF5 SDK statement - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com). There are more profiles those are supported in NCS Mesh than nRF5 Mesh SDK, so, you can find and select more features to choose from. Some of those features might also help you improving the network stability and node communication.

    Based on the above suggestions, you may have an idea which SoC would meet up your purpose and regarding the most economical one, you can contact Regional Sales Manager(RSM)  Contact us - nordicsemi.com . 

    Hope it helps. Feel free to ask if you need any more information. 

    Best Regards,

    Kazi Afroza Sultana

Children
No Data
Related
Terms of service