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 :

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
<00:00:00>,...I N D O O R O U T D O O R A N C H O R F I R M W A R E (ADM-F-P40-5.0)...
<00:00:00>,...This version was compiled at 12:07:10 Dec 12 2019
<00:00:00>,[SYSCONFIG] Generic reset cause : 0xE
<00:00:00>,[SYSCONFIG] Specific reset cause : 0
<00:00:00>,[SYSCONFIG] Reset caused by watchdog
<00:00:00>,[SYSCONFIG] Reset caused by soft reset
<00:00:00>,[SYSCONFIG] Reset caused by CPU lock-up
<00:00:00>,[SYSCONFIG] Master Anchor
<00:00:02>,[DWMNGR] Init OK
<00:00:02>,[DWMNGR] Anchor Address: 0XC886 (51334)
<00:00:02>,[Mesh DRV] Init Anchor as Master & Provisioner
<00:00:02>,Initializing and adding models
<00:00:02>,[FLASH DRV]Flash manager added for app data
<00:00:02>,[FLASH DRV]Unable to add flash manager for anchor config
<00:00:02>,[FLASH DRV]Unable to add flash manager for server info
<00:00:02>,[SYSCONFIG] Anchor not configured by BLE
<00:00:02>,[MESH DRV]Server Info :
Base @ : .localeez.adveez.com
UDP @ : staging.api.fama
Port @ : 9998
<00:00:02>,[SYSCONFIG] Building ID: 0 => Adveez 0 | Master Anchor 0XC886(51334) config Grp 0, Mode 2
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

First node (slave) logs :

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
<00:00:00>,...I N D O O R O U T D O O R A N C H O R F I R M W A R E (ADM-F-P40-5.0)...
<00:00:00>,...This version was compiled at 12:07:10 Dec 12 2019
<00:00:00>,[SYSCONFIG] Generic reset cause : 0xE
<00:00:00>,[SYSCONFIG] Specific reset cause : 0
<00:00:00>,[SYSCONFIG] Reset caused by watchdog
<00:00:00>,[SYSCONFIG] Reset caused by soft reset
<00:00:00>,[SYSCONFIG] Reset caused by CPU lock-up
<00:00:00>,[SYSCONFIG] slave Anchor
<00:00:02>,[DWMNGR] Init OK
<00:00:02>,[DWMNGR] Anchor Address: 0XDA17 (55831)
<00:00:02>,[Mesh DRV] Init Anchor as Slave
<00:00:02>,Initializing and adding models
<00:00:02>,[FLASH DRV]Flash manager added for app data
<00:00:02>,[FLASH DRV]Unable to add flash manager for anchor config
<00:00:02>,[SYSCONFIG] Anchor not configured by BLE
<00:00:02>,[SYSCONFIG] Building ID: 0 => Adveez 0 | Slave Anchor 0XDA17(55831) config Grp 0, Mode 2
<00:00:02>,PB-ADV: context at 0x200206E8 added to bearer
<00:00:02>,Device UUID (raw): 060CCF5DF136794BB9C717C85D397E91
<00:00:02>,Device UUID : 5DCF0C06-36F1-4B79-B9C7-17C85D397E91
<00:00:02>,[FLASH DRV]Flash manager added for anchor config
<00:00:02>,[FLASH DRV]Flash write complete
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Second node (slave) logs :

Fullscreen
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
<00:00:00>,...I N D O O R O U T D O O R A N C H O R F I R M W A R E (ADM-F-P40-5.0)...
<00:00:00>,...This version was compiled at 12:07:10 Dec 12 2019
<00:00:00>,[SYSCONFIG] Generic reset cause : 0x4
<00:00:00>,[SYSCONFIG] Specific reset cause : 0
<00:00:00>,[SYSCONFIG] Reset caused by soft reset
<00:00:00>,[SYSCONFIG] slave Anchor
<00:00:02>,[DWMNGR] Init OK
<00:00:02>,[DWMNGR] Anchor Address: 0XD523 (54563)
<00:00:02>,[Mesh DRV] Init Anchor as Slave
<00:00:02>,Initializing and adding models
<00:00:02>,[FLASH DRV]Flash manager added for app data
<00:00:02>,[FLASH DRV]Unable to add flash manager for anchor config
<00:00:02>,[SYSCONFIG] Anchor not configured by BLE
<00:00:02>,[SYSCONFIG] Building ID: 0 => Adveez 0 | Slave Anchor 0XD523(54563) config Grp 0, Mode 2
<00:00:02>,PB-ADV: context at 0x200206E8 added to bearer
<00:00:02>,Device UUID (raw): 54D66EF7D216B34DBBFAA188F8D60ADE
<00:00:02>,Device UUID : F76ED654-16D2-4DB3-BBFA-A188F8D60ADE
<00:00:02>,[FLASH DRV]Flash manager added for anchor config
<00:00:02>,[FLASH DRV]Flash write complete
<00:00:02>,[BLE]-> Fast advertising
<00:00:03>,PB-ADV: Link opened.
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX