This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Mesh latency during 2nd node configuration

Hello,

I have a little issue during the mesh configuration of my network.

First my provisioner (called master) provision and configure a first node (called slave), this step works well and my slave will send a custom message every minutes "surveillance message".

My problem comes with the second node : Provisioning is fine but configuration stops after the "Adding appkey" step on provisioner (at time 00:04:04 in provisioner logs). The slave is receiving the message and responds to it after having added the appkey (dsm_appkey_add line 48 of slave 2 logs) with opcode 0x8003. The provisioner does not receive this message and tries to send multiple times the "adding appkey" message . After more than 3 minutes of retries, the provisioner finally receives the response (0x8003 at 00:07:48, line 326 on provisioner logs) and performs the end of the configuration. Then both slaves nodes are able to send their surveillance message every minutes.

I would like the configuration step of the second node to be as fast as for the first one instead of during 3 minutes.

I tried the same setup powering off the first node after its provisioning and configuration, and the problem disappeared : provisioning and configurations only lasted a few seconds for the second node ! However, in the first case, the first node is not sending any messages while the other is being configured or it seems not to because i do not receive any "RX: [aop: " logs.

Thanks for helping,

Provisioner (master) logs :

First node (slave) logs :

Second node (slave) logs :

Parents Reply
  • Hi,

    I am sorry for the delays on this one. It is partly due to the recent holiday season. I will look into this tomorrow.

    Regards,
    Terje

Children
No Data