Faking Sensor Readings

[James Feist]

On 12/6/19 3:32 AM, rgrs wrote:
> Hi,
> 
> I dont see any new service even after adding dbus-sensors.
> Please can you point to any platform in upstream that I can refer to?

https://github.com/openbmc/meta-intel/blob/daa333d956ad9391abcbb85468d9bc9f26ee1190/meta-common/recipes-intel/packagegroups/packagegroup-intel-apps.bb#L43

https://github.com/openbmc/meta-facebook/blob/master/meta-tiogapass/recipes-fbtp/packagegroups/packagegroup-fb-apps.bb

If you do a ps do you see any of the sensor daemons running?

root at intel-obmc:~# ps | grep -i sensor
   332 root      6008 S    /usr/bin/adcsensor
   333 root      6356 S    /usr/bin/cpusensor
   334 root      5784 S    /usr/bin/exitairtempsensor
   335 root      5696 S    /usr/bin/fansensor
   336 root      5608 S    /usr/bin/hwmontempsensor
   337 root      5660 S    intrusionsensor
   339 root      5716 S    /usr/bin/ipmbsensor
   340 root      5512 S    /usr/bin/mcutempsensor
   341 root      5868 S    /usr/bin/psusensor
   588 root      2776 S    grep -i sensor
root at intel-obmc:~#


If so then you'll need to add entity-manager configurations like these:

https://github.com/openbmc/entity-manager/blob/7d807754cc9153b04b599804464edd9654d7a81e/configurations/WFT%20Baseboard.json#L2023

Thanks

James




> 
> Thanks,
> Raj
> 
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Wednesday, December 4, 2019 10:40 PM, James Feist <james.feist at linux.intel.com> wrote:
> 
>> On 12/4/19 1:39 AM, rgrs wrote:
>>
>>> Hi James,
>>> I tried busctl set-property, but the values didn't change.
>>> Are the steps below correct?
>>> (test with both 'field mode' enabled and disabled)
>>> root at obmc:~# busctl introspect xyz.openbmc_project.Hwmon-2439434288.Hwmon1 /xyz/openbmc_project/sensors/temperature/INLET_TEMP xyz.openbmc_project.Sensor.Value --no-pager
>>> NAME TYPE SIGNATURE RESULT/VALUE FLAGS
>>> .MaxValue property x 0 emits-change writable
>>> .MinValue property x 0 emits-change writable
>>> .Scale property x -3 emits-change writable
>>> .Unit property s "xyz.openbmc_project.Sensor.Value.Unit.… emits-change writable
>>
>> This looks like phosphor-hwmon, not dbus-sensors
>> https://github.com/openbmc/dbus-sensors.
>>
>>> .Value property x 18500 emits-change writable
>>> root at obmc:~# busctl --no-pager set-property xyz.openbmc_project.Hwmon-2439434288.Hwmon1 /xyz/openbmc_project/sensors/temperature/INLET_TEMP xyz.openbmc_project.Sensor.Value Value x 50000
>>> root at saber:~# busctl --no-pager get-property xyz.openbmc_project.Hwmon-2439434288.Hwmon1 /xyz/openbmc_project/sensors/temperature/INLET_TEMP xyz.openbmc_project.Sensor.Value Value
>>> x 18500
>>> root at obmc:~#
>>> Thanks,
>>> Raj
>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>> On Wednesday, December 4, 2019 1:34 AM, James Feist james.feist at linux.intel.com wrote:
>>>> On 12/3/19 5:49 AM, Alexander Amelkin wrote:
>>>>
>>>>> 03.12.2019 15:06, rgrs wrote:
>>>>>
>>>>>> Hi,
>>>>>> How do I fake sensor readings in OpenBMC?
>>>>>> We're trying to fake temperature sensors and make sure fans ramp up/down
>>>>>> accordingly.
>>>>>
>>>>> We ended up patching the kernel driver to fake the readings by request.
>>>>> I'm not aware of any ready interface in OpenBMC for that.
>>>>
>>>> If you're using d-bus sensors, the sensor property is writable. It is
>>>> also supported by patching the sensor value in redfish.
>>>>
>>>>> With best regards,
>>>>> Alexander Amelkin
>>> /james.feist at linux.intel.com
> 
>