can't relay message through multiple servers in mesh network.

RE: can't relay message through multiple servers in mesh network.

Hit — Mon, 11 Feb 2019 07:04:24 GMT

Hi,

Did you used same client server code as in SDK V3.0.0 and nRF SDK V15.2.0.

If changed what are the changes.

RE: can't relay message through multiple servers in mesh network.

Hung Bui — Wed, 06 Feb 2019 14:34:30 GMT

OK, we need to check how you tested. Do you see the issue all the time, for any message you send, or just on some messages that they couldn't reach the servers located further away ?

Have you tried to test with the light switch example ? I would suggest to disable proxy after your provisioned the device. Or change the advertising interval to long interval, just to make sure it's not because of the BLE activity that cause the BLE mesh performance to be reduced.

I don't see any reason why the server wouldn't relay the message after it get to 21. The difference between a message being relayed and a message sent from the originator is the TTL inside the packet.

RE: can't relay message through multiple servers in mesh network.

El_Digger88 — Wed, 06 Feb 2019 06:39:42 GMT

Hello Hung Bui,

Yes you got me right.

the relay functionality is working upto few boards (upto 3-4 boards).

And I can't relay message after 3-4 boards. That's the real problem.

Now As I said, I have set the TTL value of 25 which is more than enough I think. And I have set the TTL value by using the nRF-Mesh Android Application by which I have provisioned all boards.

I have also tested the TTL value which is decrement up-to 21 in last server board which I have debugged.

RE: can't relay message through multiple servers in mesh network.

Hung Bui — Tue, 05 Feb 2019 15:40:50 GMT

Hi Jaydeepsinh,

Ok, so the relay feature actually works ?

The problem you are having now is that you can't relay after 2-3 boards.

It could be related to the TTL value.

TTL is the time to live value that included in each mesh message. After each hop that value will be reduced by 1 until it reaches 01, no more relaying.

How did you set your TTL to 25 ? By default the TTL will have the value of ACCESS_DEFAULT_TTL = 4.

RE: can't relay message through multiple servers in mesh network.

El_Digger88 — Tue, 05 Feb 2019 10:42:52 GMT

Dear Hung Bui,

By message, I mean to say is i want to publish a command to a group address.

[quote userid="2121" url="~/f/nordic-q-a/43164/can-t-relay-message-through-multiple-servers-in-mesh-network/168903"]Could you try to test again using only 3 devices.[/quote]

I have already done that and it is running fine.. And I know that the Relay functionality is enabled in server.

But I have 8 server boards which are in series. So that last few boards are not accessible by client. In this configuration, last boards are not responding to the client. Or else, I can say that after 2 or 3 board, other boards could not get the commands from client.

I hope you understand my concern.

Is there anything related to TTL value?

I have set the TTL to 25. But not any success.

My question is something similar to the post below.

https://devzone.nordicsemi.com/f/nordic-q-a/40702/light-switch-demo-relaying-messages-relayed-messages-ttl-limited-to-4

But I can't get the reply from that.

RE: can't relay message through multiple servers in mesh network.

Hung Bui — Thu, 31 Jan 2019 14:33:44 GMT

Hi,

Relay role is enabled by default. Please check in you code if MESH_FEATURE_RELAY_ENABLED = 1 in nrf_mesh_config_code.h

What you described is pretty strange. How do you send the message from client to server ? What was the delay between 2 commands you send from the client ?

Could you try to test again using only 3 devices. One client and 2 servers. What you can do is to start first with one client and one server, and you move the server until it's out side the range of the client. Then you put the 3rd device in between and turn it on. If the mesh network works as it should the first server should be able to receive the command after you turn on the 3rd device to work as a relay.

You can reduce the output power of the chip to make it easier to reproduce (so you don't have to go too far to get out of range) Please change the radio_config.tx_power in set_default_broadcast_configuration() to RADIO_POWER_NRF_NEG8DBM for example.