<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>RSSI between all nodes in mesh network</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/44661/rssi-between-all-nodes-in-mesh-network</link><description>Hello, 
 
 I am developing an application for location tracking to be run on a Windows computer. The computer will be communicating to a mesh network using the serial interface running on an NRF52-DK board. The mesh network will consist of Light Switch</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 03 Apr 2019 20:33:49 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/44661/rssi-between-all-nodes-in-mesh-network" /><item><title>RE: RSSI between all nodes in mesh network</title><link>https://devzone.nordicsemi.com/thread/180117?ContentTypeID=1</link><pubDate>Wed, 03 Apr 2019 20:33:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:239fbebc-733a-4527-ac1b-edaf0390b7d7</guid><dc:creator>samjaklic</dc:creator><description>&lt;p&gt;Thank you for your response. One follow up question:&lt;/p&gt;
&lt;p&gt;When I try to add the RSSI from nrf_mesh_rx_metadata_t to the event, it tells me:&lt;/p&gt;
&lt;p&gt;&amp;#39;nrf_mesh_evt_t {aka struct &amp;lt;anonymous&amp;gt;}&amp;#39; has no member named &amp;#39;message&amp;#39;&lt;/p&gt;
&lt;p&gt;but when I look up the struct on the infocenter, it says that message is included member? Any solution to this? Is there a simple way to export the metadata so that I can log it through RTT?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RSSI between all nodes in mesh network</title><link>https://devzone.nordicsemi.com/thread/178398?ContentTypeID=1</link><pubDate>Tue, 26 Mar 2019 14:00:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a93acde-edd6-4e05-8a1e-e93225ba2d5d</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi.&lt;/p&gt;
&lt;p&gt;Sorry for the delayed response here.&lt;/p&gt;
[quote user="samjaklic"]Is this something that would work?[/quote]
&lt;p&gt;&amp;nbsp;I haven&amp;#39;t tried it myself, I don&amp;#39;t see any reason why that shouldn&amp;#39;t be possible. Hwoever,&amp;nbsp;I&amp;#39;m afraid we don&amp;#39;t have an example for this.&lt;/p&gt;
&lt;p&gt;You could also take a look at the Heartbeat message.&amp;nbsp;&lt;br /&gt;&lt;span&gt;Heartbeat messages are transmitted by nodes periodically. A heartbeat message indicates to other nodes in&amp;nbsp;&lt;/span&gt;&lt;span&gt;the network that the node sending the heartbeat is still active. In addition, heartbeat messages contain&amp;nbsp;&lt;/span&gt;&lt;span&gt;data which allows receiving nodes to determine how far away the sender is, in terms of the number of hops&amp;nbsp;&lt;/span&gt;&lt;span&gt;required to reach it. This knowledge can be exploited with the TTL field.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;You can also take a look at this thread;&amp;nbsp;&lt;br /&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/39270/ble-mesh-heartbeat-example"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/39270/ble-mesh-heartbeat-example&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Here is a description from Hung Bui who created the example:&lt;/em&gt;&lt;br /&gt;&lt;em&gt;&amp;quot;Attached is&amp;nbsp;a modified version of the lightswitch example to show how to configure heart beat. Please have a look at the node_setup.c file in the provisioner. In the example we will configure the light switch client to send heart beat to address 0xFFFF (all nodes) and the server 1, 2 will subscribe to the client address (0x100) and destination (0xFFFF). The server will print it out as RTT log in&amp;nbsp;mesh_event_cb() in main.c&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;strong&gt;If you want to have RSSI (of the last forwarded packet) you would need to&amp;nbsp;nrf_mesh_rx_metadata_t in heartbeat_opcode_handle() to send the RSSI value to&amp;nbsp;mesh_event_cb as&amp;nbsp;NRF_MESH_EVT_HB_MESSAGE_RECEIVED event&lt;/strong&gt;.&amp;quot;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&amp;nbsp;&lt;br /&gt;Joakim Jakobsen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RSSI between all nodes in mesh network</title><link>https://devzone.nordicsemi.com/thread/176524?ContentTypeID=1</link><pubDate>Fri, 15 Mar 2019 21:34:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:066ea157-f00b-44ad-b2ae-527d7410bd75</guid><dc:creator>samjaklic</dc:creator><description>&lt;p&gt;I am very new to this but it seems like I could accomplish this in 2 steps:&lt;/p&gt;
&lt;p&gt;1 - Send out a message through the pyaci script and a node running the serial interface example that is relayed to all nodes.&lt;/p&gt;
&lt;p&gt;2 - Configure all other network nodes so that when they receive any message, they log the sender ID and RSSI value of the message.&lt;/p&gt;
&lt;p&gt;Is this something that would work?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>