BOS Parameters
BOS parameters are used to adjust BOS settings and tune backend behavior to suit various scenarios. They are stored in the emulated EEPROM and loaded on startup. BOS parameters can be accessed in code as struct members of BOS struct. For example:
BOS.response = BOS_RESPONSE_NONE;
You can then store the new value in the emulated EEPROM using:
EE_WriteVariable(_EE_PARAMS_BASE, ((uint16_t)BOS.trace<<8) | (uint16_t)BOS.response);
BOS parameters EEPROM storage and addresses are available in this article or in BOS_eeprom.h.
You can read/write BOS parameters in the CLI using set/get commands:
set bos.response none
get bos.debounce
When you set BOS parameters in the CLI, they get automatically stored in the emulated EEPROM. Type help params in the CLI to displays a list of available parameters and their CLI values.
Here’s a list of current BOS parameters:
| Description | Parameter in Code | Code Values | Parameter in CLI | CLI Values | Default Value |
|---|---|---|---|---|---|
| Enable response for all messages and remote CLI commands, or for messages only (not for remote commands), or for remote commands only or generate no remote response at all. | BOS.response | BOS_RESPONSE_ALL, BOS_RESPONSE_MSG, BOS_RESPONSE_CLI, BOS_RESPONSE_NONE | bos.response | all, message, none | BOS_RESPONSE_ALL |
| Enable TRACE mode for all messages and their responses, or for messages only or for responses only or turn TRACE mode completely off. When TRACE mode is ON, it helps you visualize message routes in the array (i.e., trace them) by blinking the indicator LED on each module passing the message or it response. | BOS..trace | TRACE_BOTH, TRACE_MESSAGE, TRACE_RESPONSE, TRACE_NONE | bos.trace | all, message, response, none | TRACE_BOTH |
| CLI baudrate. Default is 921600. This affects all ports. If you change this value, you must connect to a CLI port on each startup to restore other array ports into default baudrate. | BOS.clibaudrate | 32-bit integer (default is 921600) | bos.clibaudrate | 32-bit integer (default is 921600) | 921600 |
| Control debounce time for BOS port buttons/switches. This adjusts button noise rejection behavior. | BOS..buttons. debounce | 1 ... 65536 msec | bos.debounce | 1 ... 65536 msec | 30 |
| Control single-click time for BOS port buttons/switches. This adjusts button noise rejection and single-click behavior. | BOS..buttons. singleClickTime | 1 ... 65536 msec | bos.singleclicktime | 1 ... 65536 msec | 50 |
| Control minimum inter-click time for BOS port buttons/switches. This adjusts button single-click behavior. | BOS.buttons. minInterClickTime | 1 ... 255 msec | bos.mininterclicktime | 1 ... 255 msec | 5 |
| Control maximum inter-click time for BOS port buttons/switches. This adjusts button double-click behavior | BOS..buttons. maxInterClickTime | 1 ... 255 msec | bos.maxinterclicktime | 1 ... 255 msec | 250 |
Module Factory Reset
You can restore module factory settings (i.e., default BOS parameters, default time and date, etc.) using two methods:
- Using CLI command
default params. Note, this only restores BOS parameters to their default settings, and does not erase other EEPROM contents. - By connecting TXD (top) of first module port with RXD (bottom) to the last module port during startup. This will completely erase the emulated EEPROM and restore BOS parameters to their default settings.
Note: You can boot up the module in a lower baud rate (115200) by connecting TXD (top) of first module port with RXD (bottom) of second module port during startup. Once you connect to the CLI via one of the module ports, the baud rate for other ports is restored to default settings (921600) so that they’re compatible with other modules. All ports are restored back to normal baud rate once you power cycle and boot up normally.
Module Parameters
Still working on it.
