|
|
Post by lucashorigan on Apr 4, 2024 21:00:14 GMT
Referencing the Redfish Data Model Specification version 2023.3 here
Looking at the property 6.118 Sensor 1.8.1 There is currently no property related to enabling or disabling a sensor. Could such a property be added? This is commonly seen on applications already for turning off sensors that may not be needed for some customers. This property would need to be a read-write so an end-user can remotely disable sensors. |
|
|
|
Post by mraineri on Apr 5, 2024 19:11:32 GMT
Curious about this statement:
> This is commonly seen on applications already for turning off sensors that may not be needed for some customers.
Does this mean that the sensor is shut off as part of building the product? Or does an end user really have this level of control?
Do you also have examples of sensors with this sort of capability?
|
|
|
|
Post by lucashorigan on Apr 8, 2024 12:32:59 GMT
Curious about this statement: > This is commonly seen on applications already for turning off sensors that may not be needed for some customers. Does this mean that the sensor is shut off as part of building the product? Or does an end user really have this level of control? Do you also have examples of sensors with this sort of capability? The controller has a bool variable for turning a sensor on and off. It would not be at the time of the build or assembly. It would be in the middle of a CDU's operation. An example of this is the redundant pressure sensors on a primary loop and return loop. If one of the pressure sensors fails on the primary loop, the CDU is able to continue measuring pressure normally, but the end-user may want to turn off the failing sensor on the primary loop. They can currently enter into the controller to have this failing sensor turned off. If the same functionality could be added to the Sensor in Redfish. This should also be a Nullable property, not every sensor on a device should have the ability to be turned off. |
|
|
|
Post by jautor on Apr 15, 2024 23:54:55 GMT
Ok, I understand that use case - that makes sense especially given redundant sensors that are providing feedback to a control loop... We'll discuss this further.
What should the "Reading" be for a disabled sensor? We could specify that it returns NULL so there's no question that the value is invalid. Or we could specify that Reading is not returned for disabled sensors.
>> This should also be a Nullable property, not every sensor on a device should have the ability to be turned off.
Note that that is not what "Nullable" means in the CSDL schema language - that refers to the ability to return a value of NULL for the property. I think what you meant is that the property is "optional", and not required for every implementation. And that is true of almost all Redfish properties - if the property is not marked as "Required", then it is optional and can (and should!) be omitted from the payload if it is not applicable or supported by the service.
(and certainly the ability to enable/disable a Sensor would be an optional feature!)
|
|
|
|
Post by lucashorigan on Apr 24, 2024 15:42:58 GMT
Ok, I understand that use case - that makes sense especially given redundant sensors that are providing feedback to a control loop... We'll discuss this further. What should the "Reading" be for a disabled sensor? We could specify that it returns NULL so there's no question that the value is invalid. Or we could specify that Reading is not returned for disabled sensors. >> This should also be a Nullable property, not every sensor on a device should have the ability to be turned off. Note that that is not what "Nullable" means in the CSDL schema language - that refers to the ability to return a value of NULL for the property. I think what you meant is that the property is "optional", and not required for every implementation. And that is true of almost all Redfish properties - if the property is not marked as "Required", then it is optional and can (and should!) be omitted from the payload if it is not applicable or supported by the service. (and certainly the ability to enable/disable a Sensor would be an optional feature!) I think a "Reading" of NULL paired with a writeable "State" that gives Disabled for a Sensor sounds good. Hope to see this changes soon! Understood on the Nullable with CSDL schema. |
|
