Get temperature and heartbeat data after mesh provisioning

RE: Get temperature and heartbeat data after mesh provisioning

The Boon — Wed, 16 Jan 2019 12:07:34 GMT

You have my thanks Hung Bui.

RE: Get temperature and heartbeat data after mesh provisioning

Hung Bui — Wed, 16 Jan 2019 12:05:47 GMT

Correct, it's a blocking function. It will return after the temperature is measured and put into p_temp.

RE: Get temperature and heartbeat data after mesh provisioning

The Boon — Tue, 15 Jan 2019 16:36:33 GMT

Hi Hung Bui,

Ahh, so the SD_TEMP_GET is the Supervisor Call (SVC) numbers used, it will execute the temperature measurement on SoC. Meanwhile p_temp is the result I need from the temperature measurement. Am I right?

RE: Get temperature and heartbeat data after mesh provisioning

Hung Bui — Tue, 15 Jan 2019 15:12:20 GMT

Hi Boon,

I'm not sure why SES couldn't find it. But if you have a look at the nrf_soc.h file, you can find the SD_TEMP_GET API call defined.

RE: Get temperature and heartbeat data after mesh provisioning

The Boon — Mon, 14 Jan 2019 12:49:52 GMT

Hi Hung Bui,

By 'temperature data' I refer to the data that are collected by the internal sensor of thingy in a Bluetooth mesh network. (Actually my concern is how to retrieve and manage data sent in a mesh network, it could be humidity data as well). Is sd_temp_get() a method in the actual thingy firmware project? I couldn't find the method neither in thingy52 mesh provisioning demo project nor in ble_app_thingy_s132_pca20020.uvprojx.
Thank you! I've got it now. What is needed to be done are programming the subscription of the gateway to the health client and followed by sending of health message from health client to all the subscribers. Okay I will implement it this way.

Thanks again!

Best regards,

RE: Get temperature and heartbeat data after mesh provisioning

Hung Bui — Mon, 14 Jan 2019 12:23:36 GMT

Hi,

1. What do you meant by "temperature data" ? Are you planning to have an external temperature sensor ? Or you want to collect the temperature data from the internal sensor ? If you plan to collect the temperature internally on the chip, you need to call sd_temp_get()

2. You can configure the health client to send the health message to the gateway and it will be forwarded by other nodes to the gateway. But the gateway need to subscribe to that health client. And other nodes wouldn't read that message, they will only forward.

RE: Get temperature and heartbeat data after mesh provisioning

The Boon — Mon, 14 Jan 2019 10:40:35 GMT

Hi Hung Bui,

Thank you for your kind reply and insights. I have some following questions:

If GPIOTE_IRQHandler is responsible for handling the event generated by a button press, then which will it be for access to the temperature data? Do I have to generate UUID, or write on CCCD (Client Characteristic Configuration Descriptor), for forwarding the temperature sensor data?
Thanks for the correction. You are right, Heartbeat msg are for telling whether the node is still active and how far the recipient is from it. As you mentioned about health message, the health_server.c sends the attention about the faults of the node. What is of my concern is that whether is it possible that the node will forward its status of e.g. low battery, let's say less than 5% of battery, using the nodes in the mesh as hopping points to pass the data to the gateway. In the end, the low-battery-node (faulty node) could then be located and replaced before its operation stop.

I appreciate your time Hung Bui. I hope to hear from you again.

RE: Get temperature and heartbeat data after mesh provisioning

Hung Bui — Fri, 11 Jan 2019 13:16:20 GMT

Hi,

In the provisioning demo, if you configure the publication address of the light bulb (the server), it will send a message to the publication address when the state is changed. You can make your own model to do similar thing to report the temperature.

I don't think you can add the battery status to the heartbeat. It meant to have only the initial TTL to know how far a node is to the other.

You can think of using health message instead. But it also has a limitation that the client has to subscribe to the server. Group address is not possible.

In your case I would think of making your own proprietary model to broadcast data about the battery.

Note that the demo was based on an old SDK: v2.2. The current SDK is v3.1 . I would suggest to start your development on a new SDK.