How to streamline sensor data over Mesh

Hey DevZone Community and Nordic Engineers :)

I'm trying to configure a multiple sensors board to BLE Mesh / COEX Mesh & BLE (If the solution you'd offer to the regular Mesh is also relevant to the COEX case, it would be superb. Otherwise, I'll open a different ticket later).

As far as I tried, the examples on the SDK are mainly with the sensor library. My sensors are not part of the Sensor.h, and thus, I don't know what is essential and what is replaceable - and how.

I'm using NCS v1.9.1 with nRF52840/32 and sometimes nRF21540dk (52840 based).

As far as I noticed, all the tickets relating to Mesh are way old and irrelevant to my current setup.

What do I need to adjust at the mesh_sensor to a regular peripheral (i2c\spi\adc etc.) sensor(unsupported by NCS sensor.h)

Thanks for all the helpers :)

Parents
  • As mentioned,, I know about the observer, client, server, and even the COEX and regular mesh LBS samples. I searched every existing solution possible before reaching out here. NONE IS VALID FOR MY CASE.

    I have tried the drivers with a regular BLE shell, and IT WORKS AND TRANSMITS!

    However, WHEN IT COME TO MESH, I DON'T KNOW ANY EXISTING SAMPLE TO DO THE SAME TRANSMITTING FUNCTION AS THE BLE BUT OVER MESH.

    The current samples deal with NCS native sensors and don't include anything parallel to non-NCS-supported sensors. Can you provide one who does?

  • Hi,

    Meh said:
    The current samples deal with NCS native sensors and don't include anything parallel to non-NCS-supported sensors. Can you provide one who does?

    Unfortunately we don't have any other samples illustrating how to use the Sensor server API other than what I supplied in my previous reply,

    The Sensor server sample contains function calls to bt_mesh_sensor_srv_publish which can be seen in model_handler.c, namely in the callback function "button_handler_cb", and in the function "end_of_presence".  Any callback function is typically connected to a button press, while the end_of_precense function is coupled with a timer. Depending on if you want your data to be triggered by a button or a timer, you should find what you need w.r.t function calls in these two functions. The sensor server documentation also contains an example for how you can initialize the sensor server with a bt_mesh_sensor.

    I know this is not the reply you want, but nonetheless it is what we have available at this point in time. I will however make a note that the sample/guide for how to do this with a non-NCS-supported sensors has been mentioned as a feature request.

    Kind regards,
    Andreas

Reply
  • Hi,

    Meh said:
    The current samples deal with NCS native sensors and don't include anything parallel to non-NCS-supported sensors. Can you provide one who does?

    Unfortunately we don't have any other samples illustrating how to use the Sensor server API other than what I supplied in my previous reply,

    The Sensor server sample contains function calls to bt_mesh_sensor_srv_publish which can be seen in model_handler.c, namely in the callback function "button_handler_cb", and in the function "end_of_presence".  Any callback function is typically connected to a button press, while the end_of_precense function is coupled with a timer. Depending on if you want your data to be triggered by a button or a timer, you should find what you need w.r.t function calls in these two functions. The sensor server documentation also contains an example for how you can initialize the sensor server with a bt_mesh_sensor.

    I know this is not the reply you want, but nonetheless it is what we have available at this point in time. I will however make a note that the sample/guide for how to do this with a non-NCS-supported sensors has been mentioned as a feature request.

    Kind regards,
    Andreas

Children
No Data
Related