System functions cover the configuration, status and control of a number of miscellaneous and loosely coupled features. These are managed by the system variables and other commands and variables, as follows:
Configuring WiConnect Command Mode and Response
WiConnect commands can be entered manually via a WiConnect terminal or by a host MCU system.
There are optimizations for human and machine control.
- system.cmd variable group:
Power consumption can be minimized, and battery life extended, by a number of strategies.
Commands and variables:
- sleep command
- system.wakeup.events - see also Peripherals, GPIO functions, wake capability
See also Wi-Fi power management variables:
Sleeping and Waking
When the module is not required to be active, you can put it into a low-power sleep mode with the sleep command, but don't forget to configure a wake mechanism before putting the module in a sleep state. This wake can be either a timeout (system.wakeup.timeout) or a GPIO level change event (system.wakeup.events).
The module may also be awoken from sleep with a power cycle.
It is also possible to set the module to go to sleep after a specified time by setting system.gotosleep.timeout.
System powersave mode allows the module to power down when idle, with a rapid power up in response to activity. See system.powersave.mode. Powersave mode is on by default.
Monitoring System State
System state can be monitored via visual indication by LED, system messages and GPIO level indication.
State monitoring variables:
- system.indicator.gpio - see also Peripherals, System Indicator Functions
Sub-system states can also be associated with GPIOs. See Peripherals.
For a detailed snapshot of system state get the values of all the WiConnect variables:
Controlling the Boot Application
Boot application commands and variables:
- system.safemode - see also Upgrade and Recovery, Safe Mode
- reboot command
- factory_reset command - see also Upgrade and Recovery, Factory Reset
The boot application is by default wiconnect.exe, but may be changed for various reasons.
If exceptions occur due to misconfiguration, the module may switch to safe mode, changing the boot application to upgrade_app.exe. See Upgrade and Recovery, Safe Mode.
System Identification and Version
Commands and variables:
- version command - this gives the same result as