Led blink in mesh network

RE: Led blink in mesh network

Trond Einar Snekvik — Tue, 31 May 2016 08:42:01 GMT

You might want to investigate disabling handles. If you set the TX-event flag (by calling rbc_mesh_tx_event_set()), you will get an event each time your value is transmitted. You can use this event to safely disable the handle you just transmitted (with rbc_mesh_value_disable()). This stops the handle from being retransmitted forever, and you can safely know that whenever you receive a message, it's been set quite recently. If you experience messages dropping off or disappearing when you do this, consider waiting for at least 2-3 tx-events per handle before disabling. A disabled handle will automatically be reenabled for each new value it receives.

RE: Led blink in mesh network

Manjunath — Wed, 25 May 2016 12:58:47 GMT

NO, i tested by commenting rbc_mesh_value_enable().

RE: Led blink in mesh network

Trond Einar Snekvik — Wed, 25 May 2016 12:53:07 GMT

I see. Are you calling rbc_mesh_value_enable() at any point?

RE: Led blink in mesh network

Manjunath — Wed, 25 May 2016 12:51:46 GMT

thanks for reply Each time i needs to send same data for every 30 seconds. then it always go to RBC_MESH_EVENT_UPDATE_VAL not to RBC_MESH_EVENT_NEW_VAL. So at this time, how can i control led synchronisatzation. So can you please tell me what to do.

RE: Led blink in mesh network

Trond Einar Snekvik — Wed, 25 May 2016 11:44:25 GMT

Hi, the mesh will keep broadcasting it current state for each handle forever. So when one of your devices do rbc_mesh_value_set(1, mesh_data, 1), mesh_data will be broadcasted until someone calls value_set again with new data. The node that wakes up, will see these broadcasts, and propagate an event to its application. The first time you see a value, the event will have type RBC_MESH_EVENT_NEW_VAL. When you get an update to a value you already know, the event will be RBC_MESH_EVENT_UPDATE_VAL. You can use this difference to make sure you only accept data that has changed.

Also make sure you don't call rbc_mesh_value_enable() first, as this will make the first broadcast you see an update. This is because value_enable sets the value in your database, and therefore counts as the "new" value.