This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

mesh sensors

Hi 

I building a mesh network of sensors that will be spread across a building. 

One node will have a cellular modem and will send the data to the cloud ( gateway ).

Data from each sensor is around ~40 Bytes.

From Mesh perspective - my understanding is the each node is a mesh server that publish the data, The gateway is the client. correct ? 

Also - when do you plan to add sensor model support to your SDK ? I don't see how other model can fit here at all. 

Thanks, 

Ran 

Parents
  • Hi,

    Yes, server models can publish data values periodically. This is actually part of the Bluetooth mesh specification, that models can be configured to publish periodically.

    The simplest solution for "one firmware, two uses" would be have both client and server model on the node, but when you configure the node you configure only the part that you need. You may need to add a separate model for configuring which role the node should have, however, depending on the use case.

    If the decision whether to be client or server is a one-time decision, you could write a value to UICR and use that value for deciding which model to use.

    nRF OpenMesh is an early mesh solution very similar to Bluetooth mesh, and the nRF5 SDK for Mesh is a continuation of that project. nRF OpenMesh is discontinued, and for new projects you should use nRF5 SDK for Mesh instead.

    Regards,
    Terje

Reply
  • Hi,

    Yes, server models can publish data values periodically. This is actually part of the Bluetooth mesh specification, that models can be configured to publish periodically.

    The simplest solution for "one firmware, two uses" would be have both client and server model on the node, but when you configure the node you configure only the part that you need. You may need to add a separate model for configuring which role the node should have, however, depending on the use case.

    If the decision whether to be client or server is a one-time decision, you could write a value to UICR and use that value for deciding which model to use.

    nRF OpenMesh is an early mesh solution very similar to Bluetooth mesh, and the nRF5 SDK for Mesh is a continuation of that project. nRF OpenMesh is discontinued, and for new projects you should use nRF5 SDK for Mesh instead.

    Regards,
    Terje

Children
No Data
Related