List of controllers that we are using in Modelica currently

[TobiasMaile]

We need to have a definite list of controllers that we currently have in our use cases and are thus supporting for now. From what I know we have use the following controllers in use case 1:

• Temperature control in hot water loop (boiler actuates)
• Temperature control in zone (radiator actuates)
• Pump on/off signal (night signal)
• Temperature control in air loop (coil actuates) (air loop use case)

Are there any other controllers that I have missed?

Tobias

[PRemmen]

The Temperature control is not actuated directly by the radiator, but the valve.

Additional controls i figured out:

Use Case 1.2:

• controll of loading/unloading the heat storage (valves actuate)

Use Case 2.1:

• Temperature control in hot water loop (Heat pump actuates On/Off operation)

Use Case 4.1 and 4.2 (Buildings only):

• Temperature control in zone (Fans actuate)

[TobiasMaile]

ControllerVariable:

• Temperature (boiler, coil, radiator/valve, )
• Flow (pump, heatpump, fan)
• StorageEnergy (tank)

ControllerType:

• PID
• Ideal
• OnOff
• OnOffWithHysteresis

[TobiasMaile]

Please review the controller types that we defined today, anything missing?

[PRemmen]

@thorade creates table on how the controls would be intepretated from Modelica side

[thorade]

OK, so after thinking some more and reading on Wikipedia, I do not create a table, but would just like to extend Tobias comment using the terminology and a diagram from Wikipedia: https://en.wikipedia.org/wiki/Feedback#Types

• The systems has a status, e.g. in UseCase 1.1 the thermal zone has a certain temperature,
• the status is measured by a measuring element, e.g. a temperature sensor,
• the measured value is compared to a set point by calculating the error=setPoint-measuredValue
• the error is sent to a controller (can be a PI or PID or OnOff controller),
• the controller sends a command to the effector, e.g. sends a signal between 0-100% to a valve,
• the effector is then influencing the system, e.g. the mass flow in the valve increases (or in other words: the effector gives feedback to the system),
• the system gets the sum of that feedback and some external disturbance as input and the loop starts over again.

The Modelica approach is (usually) very similar to the shown diagram: we have a sensor component, a controller component, an effector component and they exchange information using "connections". But sometimes, e.g. in the case of the ideal heater, the full control loop is integrated in the idealHeater component.

So, in order to build up the Modelica code, we need to know for every controller:

• What is our system (thermal zone, tank, boiler) and what variable gets measured?
• How is the set point defined? Constant, Timetable, SineWave, Ramp?
• What controller type are we using? PID, Ideal, OnOff?
• What component is our effector and what kind of signal does it expect? A signal 0-1, a pump speed in rpm?

Part of that information should be coming from the SimModel, some knowledge is stored in the MappingRules (the XML ones or the mapping via Python code).

[TobiasMaile]

let's add these properties to the controller on the IFC side as Psim_SimController:

• ControllerVariable (enum:Temperature,Flow,StorageEnergy)
• ControllerType (enum:PID,Ideal,OnOff,OnOffWithHysteresis)
• ConstantSetpointValue (double)
• ScheduledSetpointValue (reference to time series schedule)
• MeasuredVariable (enum:Outlet,Space,...)
• Parameters for PID, Ideal, OnOff, OnOffWithHysteresis

[TobiasMaile]

Mapping to SimController:

ControllerVariable.Temperature & MeasuredVariable.Space -> SimController_ZoneControlTemperature_Thermostat ControllerVariable.Temperature & within air loop -> SimController_SupplyAir_Temperature ControllerVariable.Temperature & within water loop -> SimController_SupplyWater_Temperature ControllerVariable.Flow -> SimController_Default_Default (should we introduce a new object here in SimModel?) ControllerVariable.StorageEnergy -> SimController_ThermalStorage_ThermalEnergyStorageTank

[ReinhardWimmer]

Defined the PSims in the IFC-File for the first use case as follows:

• Thermostat: ControllerVariable_Temperature; MeasuredVariable_Space; ControllerType_IDEAL
• Boiler: ControllerVariable_Temp; ConstantSetpointValue_70
• Valve: ControllerVariable_Flow; ControllerType_PID
• Pump: ControllerType_OnOff

[TobiasMaile]

We have done this integration by now and we think we expose these properties/controller objects via the SimModelAPI by tonight (8/4/2016).

Are we getting these proeprties of the controllers on the Modelica side now.

[TobiasMaile]

We are getting the following for the first controller in use case 1.1:

`

70 Variable ` @PRemmen This looks good from my point of view, do you need anything else for the controllers? I uploaded a new SimXML test file (there are still some relationship properties missing, but this controller issue as well as others are resolved now.) Tobias

[PRemmen]

I'll check this before next TelCo

[PRemmen]

@TobiasMaile

The following concerns following file: https://github.com/EnEff-BIM/EnEffBIM_UseCases/blob/master/UseCase1.1/1.1_Architecture%2BHVAC%2BZone_Curve%2BSchedule_korr_ZumTesten.simxml

Besides I can't load this file with the libSimModelAPI, I have two comments:

The controller for the constant flow temperature of the boiler is okay, as you said, the realtionship to the boiler is missing.

I can't find the other controller types the filethe one @ReinhardWimmer mentioned in his post from 18 March), should the file already contains these controllers or am I looking at the wrong file?