Configurations (Configs for short) are a complete set of details on how a Pilot device should operate. Configs are stored in a small file and can be emailed or stored like a text file. The contents of the file are in a compact format that allows them to be stored by the Pilot devices. The file should always be edited with the configuration software. You should always keep a copy of your config files on your PC and NOT rely on recovering them from the Pilot which is not always possible.
These are distinct types of work that the Pilot can do e.g. control a CAN Bus or collect heart rate over BLE. To serve any practical purpose the Pilot device must have one or more configuration modules added. Each module is a stand-alone software unit that interact with other modules via streams. Configuration modules are generally either a source of information (i.e. streams of data) or a sink (i.e. they receive data and process or convert it). Some modules can be configured to be both sources and sinks (e.g. CAN bus) and others by their purpose must sink data before providing a new source stream (e.g. the Exertion analyser).
AKA Configuration Items, or just Items. When you use Embedded Setup (the configuration software) to add a module you then have an instance of that module in the config. We call these specific instances "Config Items". For example, there is a BLE Heart Rate module - you can add multiple instances of this module to a config as you may be collecting from multiple wearable items.
Properties and Settings
Settings are individual numbers or options for a given parameter, each config item has lots and lots of settings.