commit | d98174e9c83d1eb585b58aa0c7c24e745b4a9688 | [log] [tgz] |
---|---|---|
author | George Liu <liuxiwei@ieisystem.com> | Fri Oct 25 15:48:16 2024 +0800 |
committer | George Liu <liuxiwei@ieisystem.com> | Fri Oct 25 15:48:16 2024 +0800 |
tree | 1f038d8aa9ab84626f4f4fc55767bc2cde6077ae | |
parent | 2030a56a6e5be0e957d17eb329c8231952f3ea2e [diff] |
Add the main.cpp file Separate the main method from virtualSensor.cpp and add it to the main.cpp file. Change-Id: Ife3dd9bb6dee552d944399bcc769fc6c4ba54a4b Signed-off-by: George Liu <liuxiwei@ieisystem.com>
phosphor-virtual-sensor reads the configuration file virtual_sensor_config.json
from one of three locations:
/var/lib/phosphor-virtual-sensor
/usr/share/phosphor-virtual-sensor
By default the repository will install a sample config into (3).
There are two types of data in this file.
See virtual_sensor_config.json
in this repository for an example. Sensors added this way can use any expression that is accepted by exprtk.
For example:
{ "Desc": { "Config": "D-Bus", "Type": "ModifiedMedian" } }
Sensors added this way can only use a set of restricted calculations. Currently supported types are Average
, Maximum
, Minimum
, Sum
and ModifiedMedian
.
The virtual sensor configuration information needs to be added into the relevant hardware configuration file in entity-manager. This method of adding a virtual sensor allows a recipe that builds for different hardware configurations to have different virtual sensors for each configuration.
The virtual sensor configuration in entity manager follows a different format to the JSON in virtual_sensor_config.json
(specified in entity-manager/schemas/VirtualSensor.json).