Keeping attribute table and model in synchttps://devzone.nordicsemi.com/f/nordic-q-a/13147/keeping-attribute-table-and-model-in-syncI think this is a rather common problem: I want to expose a couple of variables from my model code (members of structs) as characteristics. Is there a simple and elegant way to bind such variables directly to the characteristics so that I do not haveen-USTelligent Community 13Thu, 14 Apr 2016 12:31:00 GMTRE: Keeping attribute table and model in synchttps://devzone.nordicsemi.com/thread/50119?ContentTypeID=1Thu, 14 Apr 2016 12:31:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d3276c5f-7c4f-4c67-88d4-1b6c2ae1e23cbjorn-spockeli<p>You can use the <a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s130.sds/dita/softdevices/s130/radio_notif/radio_notification.html?resultof=%22%72%61%64%69%6f%22%20%22%6e%6f%74%69%66%69%63%61%74%69%6f%6e%22%20%22%6e%6f%74%69%66%22%20">Radio Notification</a> feature to make sure that you&#39;re only using the attribute values after the SoftDevice has updated them.</p><div style="clear:both;"></div>RE: Keeping attribute table and model in synchttps://devzone.nordicsemi.com/thread/50117?ContentTypeID=1Tue, 12 Apr 2016 21:35:01 GMT137ad170-7792-4731-bb38-c0d22fbe4515:afb47160-67a8-42ce-bb16-d55965fcd467Raphael<p>Oh and another thing: How do I make sure that the SoftDevice does not interrupt my code doing calculations with inconsistent data because if e.g. my model code first uses the value of an attribute at timestep 1 and then the softdevice interrupts that code, changing the attribute value and the rest of the interrupted function now uses the attribute value at time step 2.</p><div style="clear:both;"></div>RE: Keeping attribute table and model in synchttps://devzone.nordicsemi.com/thread/50116?ContentTypeID=1Tue, 12 Apr 2016 14:00:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:5ec5efb7-fe41-4eb2-9871-c5f128451588Raphael<p>OK, that sounds like a good idea. What do I need to do to let the SoftDevice know that I changed the variable so that it will propagate the update to the peer?</p><div style="clear:both;"></div>RE: Keeping attribute table and model in synchttps://devzone.nordicsemi.com/thread/50118?ContentTypeID=1Tue, 12 Apr 2016 13:34:00 GMT137ad170-7792-4731-bb38-c0d22fbe4515:cc9fd382-0ef3-4665-b76d-06e7e83dddfdRK<p>Why not just make the characteristic values user memory instead of stack memory, then you can point them directly at the data in the struct and reads will read the latest value and writes will write to the struct directly.</p><div style="clear:both;"></div>