Get physical source of intermediate relay messages

RE: Get physical source of intermediate relay messages

ovrebekk — Wed, 06 Dec 2017 11:14:43 GMT

Good to hear you found a solution, sounds like a good way to do it :)

RE: Get physical source of intermediate relay messages

Mathias — Tue, 05 Dec 2017 10:42:03 GMT

We ultimately found out that we could use the BLE GAP Advertiser address that is in the metadata of the received packet, to find out which physical source relayed the specific packet. We then used the function in core.tx to change the advertister address for both roles to something more readable. Not fully BLE standard but it's just for measurements. Thanks for your help again Torbjørn!

RE: Get physical source of intermediate relay messages

Mathias — Tue, 05 Dec 2017 10:39:50 GMT

Hi Torbjørn

After some thought, we came to the conclusion that looking at the TTL counter alone could still give situations where a node doesn't know where packets come from. We then looked a bit further still and found a possible solution that I put in the answer below.

RE: Get physical source of intermediate relay messages

ovrebekk — Fri, 01 Dec 2017 13:03:21 GMT

I am happy to help. The best of luck with your project :)

RE: Get physical source of intermediate relay messages

Mathias — Fri, 01 Dec 2017 12:23:33 GMT

Sounds like a great idea, thanks for the answer and clarification!

RE: Get physical source of intermediate relay messages

ovrebekk — Fri, 01 Dec 2017 12:12:44 GMT

Hi Mathias

There is no built in mechanism for this, no. Since there is no routing in the mesh, having this included would add quite a lot of overhead to the communication.

You might be able to add a proprietary system on top, where each node can report that it received a packet, and what the TTL counter was at the time, but this would have to be added in the application.

Best regards
Torbjørn