6.30 Control 1.5.0 - Array of SetPoints | Redfish Specification Forum

lucashorigan
Minnow

Posts: 14

6.30 Control 1.5.0 - Array of SetPoints Apr 8, 2024 13:52:11 GMT

Quote

Post by lucashorigan on Apr 8, 2024 13:52:11 GMT

Referencing the Redfish Data Model Specification 2023.3 here

Under the property 6.30 Control 1.5.0

Having an array of Setpoints would be beneficial. While there are other attributes that are read-write such as SettingMin, DeadBand, ControlMode these are not appropriate for the redundancies that are common for controls. As an example there are multiple humidity sensors that are each addressable for having their setpoint changed. If a CDU has four humidity controllers, then 4 unique URI's need to be created as follows:

HumdityControl1
HumdityControl2
HumdityControl3
HumdityControl4

Each URI is almost exactly the same, with the exception of the SetPoint variable changing and the index number of the humidity control. This leads to unnecessary clutter that makes the template less readable. Would it be possible to create some solution that can condense these controls to one simple URI of HumdityControl while also allowing for all 4 unique controls to be addressed with a read-write?

{

    "@odata.type": "#Control.v1_3_0.Control",

    "Id": "HumidityControl",

    "Name": "Humidity Control",

    "@odata.id": "/redfish/v1/Chassis/1234/Controls/HumidityControl",

    "Status": {

        "State": "Enabled",

        "Health": "OK",

        "Oem": {}

    },

    "Location": {

        "@odata.type": "#Resource.v1_3_0.Location",

        "Placement": {},

        "PostalAddress": {},

        "Oem": {}

    },

    "Actions": {

        "Oem": {}

    },

    "Oem": {},

    "SetPoint": {
      "SetPoint1": "<Humdity-Control1>",
      "SetPoint2": "<Humdity-Control2>",
      "SetPoint3": "<Humdity-Control3>",
      "SetPoint4": "<Humdity-Control4>"

}
}

Last Edit: Apr 8, 2024 13:53:05 GMT by lucashorigan

jautor
Administrator

Posts: 505

6.30 Control 1.5.0 - Array of SetPoints Apr 15, 2024 23:47:15 GMT

Quote

Post by jautor on Apr 15, 2024 23:47:15 GMT

There is a "SensorGroup" that allows for redundant sensors to be accessed as if they were a single sensor, but that doesn't work for a Control (but it certainly could be applied to the sensor(s) that are providing the feedback loop for a Control). I'm not sure how that would work as you're showing different SetPoint values for the 4 controls. Is each of those tied to a specific humidity sensor? Is the user setting 4 individual values, because that would really feel like separate controls. But if this is just exposing the "gory details" behind the scenes - can this be represented by a single SetPoint with a set of associated Sensor(s)?

There are many cases in the model where multiple devices produce almost identical JSON payloads. But it's those few differences that are the critical values. In your example, though, there's no "context" for those 4 humidity controllers. How does a user, in an interoperable / vendor-independent manner, discover what controller #3 is doing vs. #4? It's those ties to the rest of the model that would be the difference between 4 Control resources. This is no different than 8 otherwise identical DIMMs in a server - the only differences in payload may be the serial number and the socket #...

Jeff

lucashorigan
Minnow

Posts: 14

6.30 Control 1.5.0 - Array of SetPoints Apr 24, 2024 15:46:13 GMT

Quote

Post by lucashorigan on Apr 24, 2024 15:46:13 GMT

Apr 15, 2024 23:47:15 GMT jautor said:

There is a "SensorGroup" that allows for redundant sensors to be accessed as if they were a single sensor, but that doesn't work for a Control (but it certainly could be applied to the sensor(s) that are providing the feedback loop for a Control). I'm not sure how that would work as you're showing different SetPoint values for the 4 controls. Is each of those tied to a specific humidity sensor? Is the user setting 4 individual values, because that would really feel like separate controls. But if this is just exposing the "gory details" behind the scenes - can this be represented by a single SetPoint with a set of associated Sensor(s)?

There are many cases in the model where multiple devices produce almost identical JSON payloads. But it's those few differences that are the critical values. In your example, though, there's no "context" for those 4 humidity controllers. How does a user, in an interoperable / vendor-independent manner, discover what controller #3 is doing vs. #4? It's those ties to the rest of the model that would be the difference between 4 Control resources. This is no different than 8 otherwise identical DIMMs in a server - the only differences in payload may be the serial number and the socket #...

Jeff

Fair enough, if the end-user is better off with more URI's so they're made aware of how many individual sensors there are it can be left as is then. I'll close this feature request then.