Mesh relay enable/disable

RE: Mesh relay enable/disable

Mttrinh — Mon, 25 Oct 2021 15:15:41 GMT

Hi,

It is hard to tell what the exact reason is but it is related to the clock source on the module device(Minew).

Increasing the margin should not create any other problems than potentially decreasing the performance of the node a bit. Having a longer margin would mean that a longer timeslot would be needed. Which might make throughput a bit lower, or might not. So if peak throughput is not an issue then you will probably not notice any effects from increasing the margin.

There have been a long discussion in a similar thread, not sure if it is the same issue but might be worth to have a read.

RE: Mesh relay enable/disable

Peter Gombos — Fri, 22 Oct 2021 13:03:28 GMT

Hi!

Tried with 200 us no success. But the next step (300 us) eliminates the assertion. It works!

What could be the reason? How does this modification impact the performance?

RE: Mesh relay enable/disable

Mttrinh — Fri, 22 Oct 2021 09:21:58 GMT

Hi,

Looking into the assert you get, it means that the SoftDevice got an unexpected radio interrupt which is typically because the application used the radio outside of the timeslot. You can try to increase TIMESLOT_END_SAFETY_MARGIN_US in steps of 100 us upto 1000 us and see if that helps.

Though it seems strange that you get the assert as well if you disable the proxy by the "#define MESH_FEATURE_PROXY_ENABLED 0".

RE: Mesh relay enable/disable

Peter Gombos — Thu, 14 Oct 2021 16:30:52 GMT

Hi,

It doesn't help.

As I wrote earlier the module _has_ LF oscillator. This is not the issue.

It is so strange. If I disable the proxy by the "#define MESH_FEATURE_PROXY_ENABLED 0" I have the same assert.

I tried the light switch server example and it behaves the same. The assert happens after couple of seconds.

RE: Mesh relay enable/disable

Mttrinh — Thu, 14 Oct 2021 14:43:03 GMT

Hi,

Try this.

RE: Mesh relay enable/disable

Peter Gombos — Tue, 12 Oct 2021 16:47:20 GMT

The module made by Minew. The doc says: "Integrated DCDC inductor and an external 32.768K crystal oscillator reduce design complexity and BOM cost."

RE: Mesh relay enable/disable

Peter Gombos — Tue, 12 Oct 2021 16:33:08 GMT

Honestly I don't know much about the clock source of the module.

Shall I change the bootloader sdk_config.h? I did so but nothing changed 😞

#define NRF_SDH_CLOCK_LF_SRC 0
#define NRF_SDH_CLOCK_LF_ACCURACY 1

RE: Mesh relay enable/disable

Mttrinh — Tue, 12 Oct 2021 14:51:36 GMT

Hi,

The chip variants are very much alike, so it shouldn't cause any issues, Is there a external 32kHz crystal on the "noname modul"?

If you don't you can try switching to the RC Oscillator to test to see if that is the issue?

RE: Mesh relay enable/disable

Peter Gombos — Mon, 11 Oct 2021 20:29:00 GMT

Hi again!

The recommended proxy related functions work fine in my Rigado BDM-300 module.

However if I use the exactly same firmware on a noname module with the same chip, I have a softdevice assert.

Both type of modules work fine as long as the proxy is enabled. If I disable or stop the proxy from RTT then I get the following assert after couple of seconds: Softdevice assert: 88080:0

The Rigado does not assert and the proxy function disabled fine.

The only difference between the modules is the chip variant. Good is AAE1, bad is AAE0.

(chip is 52832, Mesh v5.0.0, SDK 17.0.2)

Please advise.

RE: Mesh relay enable/disable

Mttrinh — Tue, 28 Sep 2021 14:00:19 GMT

Hi,

You can use these function to enable/disable proxy functionality during run time:

proxy_enable() and proxy_disable(), they both call mesh_opt_gatt_proxy_set().

RE: Mesh relay enable/disable

Peter Gombos — Tue, 28 Sep 2021 10:39:23 GMT

Yes, I would like to disable the gatt proxy feature. However I would do it runtime. Compile time define is not suitable for me because I have to use the same firmware in every devices.
How can I enable/disable the proxy functionality at startup?

RE: Mesh relay enable/disable

Mttrinh — Tue, 28 Sep 2021 10:27:57 GMT

Hi,

[quote user="Peter Gombos"]What is the recommended way to stop advertisement but remain the member of the mesh?[/quote]

By "stop advertising" I assume you mean disabling the proxy functionality? You can disable proxy by setting this define MESH_FEATURE_GATT_PROXY_ENABLED to 0.

RE: Mesh relay enable/disable

Peter Gombos — Mon, 27 Sep 2021 17:30:37 GMT

Hi, thank you for your answer. I see it is possible to enable/disable the relay and tune the retransmission parameters. I will play with them.

I would like to disable the proxy functionality too. I don't need thousands of proxy nodes. The relay nodes should have proxy and the normal nodes shouldn't be discoverable. What is the recommended way to stop advertisement but remain the member of the mesh?

RE: Mesh relay enable/disable

Mttrinh — Mon, 27 Sep 2021 15:38:05 GMT

After discussing with our developer it seems using network_opt_get/set directly is not supported, as these are internal APIs. Applications should use mesh_opt_core_adv_set/get with role = CORE_TX_ROLE_RELAY and the correct options struct (enabled = false, or enabled = true in the struct of course to re-enable the relay role). mesh_opt_core_*_get/set are declared in in mesh/core/api/mesh_opt_core.h, and are part of the public, supported API for application use.

RE: Mesh relay enable/disable

Mttrinh — Fri, 24 Sep 2021 14:40:41 GMT

Hi,

Your approach seems to be fine. Not having all your nodes in the network beeing a relay node is an intended way of doing it. Like you mentioned, having too many relays will cause a huge load on the network and disturbance between the nodes.

As for your question regarding the API for enabling/disabling the relay feature, I think you can use it but not entirely sure. I will have to discuss this with the mesh team and come back to you with an answer on Monday.