Led blink in mesh network

[Manjunath]

Hi all,

I can able to blink led in mesh synchronously, but some time it fails in synchronization. when a new node enters into mesh it takes current mesh value, but for me it should not happen. when i send data through this function rbc_mesh_value_set(1, mesh_data, 1) it is calling often 30 seconds, then only new node should receive value( led start blink with mesh synchronously), otherwise it is in rest state.

But problem here when new node enters into mesh, it immediately updated, if not even call this rbc_mesh_value_set() also. I do not know from where it is updating.

my requirement is, it should not update unless until i send message packet.

I tried to stop radio, fifo and i made version to constant at that time this application is not working. how to sop this functionality.

can anyone please help on this.

Regards Manjunath N N

[Trond Einar Snekvik]

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.

[Manjunath]

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.

[Trond Einar Snekvik]

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

[Manjunath]

NO, i tested by commenting rbc_mesh_value_enable().

[Trond Einar Snekvik]

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.