Thermal network

The Thermal Network component implements a signal processing model of a thermal system that can be parametrized with either Cauer or Foster thermal model data.

Component Icon

Figure 1. Thermal network icon

Description

This component represents any number of general thermal networks, each with a model order defined by the length of the thermal resistance property. The represented models can be parametrized with either Cauer or Foster thermal model data. Cauer model parameters have physical meanings, representing thermal resistance and thermal capacitance of an object seen in Figure 2. The Foster model type is a purely mathematical representation of a thermal system. Parameters of this type can be obtained from real measurements, but the voltages of each terminal no longer represent any particular physical value. The electrical equivalent model seen in Figure 3. Therefore, if the model is parametrized as Foster network type, the given parameters will automatically be translated to a Cauer thermal model before the start of the simulation. The number of resistances and capacitors in the electrical equivalent circuit for both models depends on the length of the Thermal resistance parameter.

Figure 2. Cauer thermal network electrical representation
Figure 3. Foster thermal network electrical representation

Inputs and outputs can be either scalars or vectors. This depends on the component's Number of thermal networks property. If the number of thermal networks is equal to 1, inputs and outputs are scalars. If the number of thermal networks is greater than 1, inputs and outputs are vectors with length corresponding to this property.

If the check box Ambient temperature input is ticked, the equivalent electrical circuit will be represented as in Figure 4. If the Foster network is simultaneously enabled, the new ambient temperature change will only be applied after the parameters are translated to the Cauer model type.

Figure 4. Electrical representation of Cauer thermal network with an ambient temperature input

Ports

  • Pin (in)
    • Power input to the Thermal network(s) in [W]
      • Supported types: real.
      • Vector support: yes.
  • Tref/Ta (in)
    • Reference temperature for Thermal network(s) in [°C] or [K]
      • Supported types: real.
      • Vector support: yes.
    • Ambient temperature for Thermal network(s) in [°C] or [K]
      • Supported types: real.
      • Vector support: yes.
  • Pout (out)
    • Output power from the Thermal network(s) in [W].
      • Supported types: real.
      • Vector support: yes.
  • Tout (out)
    • Output temperature from the Thermal network(s) in [°C] or [K] (inherited from Tref).
      • Supported types: real.
      • Vector support: yes.

Properties

  • Number of thermal networks
    • Number of thermal networks that will be internally created. This number also defines the vector size of the input and output signals. All created thermal networks will be parametrised with the same values inserted on the mask of the component. This parameter must be an integer greater than 0.
  • Network type
    • Defines the type of thermal network(s)
  • Thermal resistance
  • Thermal time constant/ Thermal capacitance
    • Thermal time constant values when the Foster network type is selected. The number of elements must be the same as for the Thermal resistance parameter.
    • Thermal capacitance values when the Cauer network type is selected. The number of elements must be the same as for the Thermal resistance parameter.
  • Ambient temperature input
    • Defines the type of thermal network(s)
  • Execution rate
    • Type in the desired signal processing execution rate. This value must be compatible with other signal processing components of the same circuit: the value must be a multiple of the fastest execution rate in the circuit. There can be up to four different execution rates, but they must all be multiple of the basic simulation timestep. To specify the execution rate, you can use either decimal (e.g. 0.001) or exponential values (e.g. 1e-3) in seconds. Alternatively, you can type in ‘inherit’ in which case the component will be assigned execution rate based on the execution rate of the components it is receiving input from.