multiple server on one client - light switch demo

[vnagy]

Hellou. I'm developing application, which is modifiaction of light switch demo. I need use 128 servers and one client. But when I redefine in SERVER_COUNT to 128 in client application, it is no posible connect to servers (servers are not promisioned). I was read somewhere its needed change ACCESS_FLASH_PAGE_COUNT and DSM_FLASH_PAGE_COUNT . But I didn't find how many pages are needed for example 128 servers. My question is how many bytes are needed for writing data to ACCESS_FLASH and how many bytes are needed for writing data to DSM_FLASH by promisioning for 1 server. When i know how many bytes ist needed for 1 bytes, its enoght multiple by SERVER _COUNT(exactly 128) and from this calculate hoe many pages is needed for ACCESS_FLASH_PAGE_COUNT and  DSM_FLASH_PAGE_COUNT. 

Thank you for answer. 

[vnagy]

Hello,

Our project consists of one gateway device in the distribution box and up to 128 node devices located inside luminaires. We need only single model for communication between the gateway device and node devices – there is our propriatery protocol integrated inside the data which are sent between the devices. Could you please make a recommendation for us which topology is the optimal for the application in regards of memory requirements? Should the gateway device be a server or a client?

[Hung Bui]

Hi, 

 

The server/client model is more about where the data is stored. The data is to be stored on the server. If you have data on the gateway and the node need to acquire data from the gateway, then you can set the server on the gateway and client on the node. If you have data (like sensor data) on the node , or you have something you need to control on the node, you use the node as the server, and put the client on the gateway. 

I don't think the model configuration has something to do with memory requirement. The memory allocation is on access layer, not on the model which in application layer. 

 

Note that the data about each node ( devkey, address) doesn't need to be stored on the gateway, it just need to be stored on the provisioner, which doesn't have to be the gateway. It could be a phone or PC. 

[vnagy]

OK, i understand this. I our projects is gateway also provisioneer, so it need store data about nodes. How many nodes its posible connect on gateway, which is also provisioneer? 

[Hung Bui]

Ok, so the minimum data need to be stored on the provisioner about a node is: unicast address, number of elements, device key, network key index 

We currently don't store those information on flash on the provisioner. You are free to choose how you want to store them. They are just a dozens of byte per node, so it's not the flash size would be the limit. A few hundred nodes shouldn't be problem. But you will need to think of how you organize , and search for a node when you want to reconfigure them. 

Also on the provisioner, if you want to do black listing, using key refresh, you would need to update the database about black listed node. 

Here is some information about the flash usage on a node (but not about the provisioning database):

http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v2.0.1/md_doc_getting_started_how_to_nordicSDK.html?cp=4_1_0_3_6

And

https://raw.githubusercontent.com/NordicSemiconductor/nRF5-SDK-for-Mesh/master/doc/introduction/mesh_hw_resources.md