14.2.3.2 ConfigServer Component Usage
BitCloud provides an extensive set of configuration parameters which determine different aspects of network and node behavior. These parameters are accessible for an application via the Configuration Server interface (ConfigServer or CS for short).
CS parameters can be divided in a set of categories according to different criteria. For example, one can distinguish persistent and non persistent parameters. Persistent parameters are stored in flash memory and their values stay unchanged after the node HW reset. Non persistent parameters are stored in RAM memory and upon HW reset are reinitialized with their default values as per csDefaults.h. Other criteria mark out parameters that can be set only at compilation time, such as the parameters that are used to calculate an amount of memory to be allocated by the application, and the parameters that can be changed only when the device is out of network since they determine certain network related aspects of node behavior.
Note that if a parameter is persistent, this automatically means that it can be modified at run time, because there is no need to store in flash parameters that can not be changed between two HW resets.
The sections below describe typical cases of CS parameters usage accompanied with explanations on how they affects the application's or node's behavior.
References
- CS functions
- CS parameters defaults
- How to get or set a CS parameter
- Using parameters influencing network start
- Sleeping end device's time spans
- Configuring fragmentation
- Understanding table sizes
- Security keys