Request test firmware for large scale testing scenario

[Nagajans]

I was reviewing the Large scale Bluetooth mesh testing - Blogs - Nordic Blog - Nordic DevZone and noticed the statement: "Initialize the network by flashing the test firmware on the nodes." in the test procedure. I’m interested in performing similar latency and reliability tests. Could you please let me know where I can find the test firmware used in your evaluation?

[Nagajans]

Yes, I understand that. I would like to know which configuration parameters play a major role in the observed DFU timing difference. In both NCS versions, I used only the light and light_switch sample applications, with no custom modifications.

It would be very helpful if you could also share a recommended strategy or guidelines for choosing optimal configuration parameters based on network size—for example, what configurations are best suited for 10-node, 50-node, and 100-node BLE Mesh networks.

[Elfving]

Understood. I'll look into what the difference could be there. 

According to a test here, a unicast transfer of 300KB firmware could take about 45-50 mins, group cast transfer of the same firmware takes about 130mins. I know you said that the tests with the two NCS versions where done in the same way, but since the timing matched so well I just wanted to ask: you didn't happen to do the one test on NCS 3.1 using a group address?

Nagajans said:

It would be very helpful if you could also share a recommended strategy or guidelines for choosing optimal configuration parameters based on network size—for example, what configurations are best suited for 10-node, 50-node, and 100-node BLE Mesh networks.

I could give some recommendations based on this, but I would say that my recommendations wouldn't be mainly based on the number of nodes per se, but on the topology. If there are a 100 nodes just sitting on your desk, then relaying would almost not even be necessary. Though if you are placing a hundred nodes on telephone poles along a highway, where one can just reach the next one, that is a different story. For that situation I would for instance argue that a large TTL is important.

Regards,

Elfving