How to streamline sensor data over Mesh

[Meh]

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 :)

[AHaug]

Hi,

You can always use a struct to define custom user data types in C. But you're referring to "...outside the enum?" Do you refer to a specific enum or just an enum in general?

Kind regards,
Andreas

[Meh]

There are data types for each parameter, and when I started digging into the example, I realized there might be some impacts on presenting a given data based on the data type enum. I'm creating something with mainly chemical and biological sensors, and it seems like the picking of the data type could might arrange them differently

[AHaug]

Hi,

Meh said:

There are data types for each parameter, and when I started digging into the example

Which function calls and/or parameters are you referring to? Is it the SENSOR_DATA_TYPE in model_handler.c in the sensor_server sample (l.21 for nRF52DK) which is defined as a sensor_channel enum in sensor.h?

Meh said:

Although tutorials like the  BLE Custom Service series would be the perfect solution for this question

As for this, we agree. We will look into creating a similar guide for this purpose, but the timeline for when the potential guide will be finished is currently indefinite. 

Kind regards,
Andreas