Difference between revisions of "Discrete Filter"

From T-VEC Wiki
Jump to: navigation, search
(Model)
 
Line 1: Line 1:
TTM is a modeling tool that is very generic. It is not really meant for any specific application domain so there is no direct support for things like control/filter expressions that are more naturally specified in a tool such as Simulink. However, the concept of FUNCTIONS, now supported in TTM 3.x and higher, makes it possible to represent things like Discrete Filters. This should allow users to create libraries of TTM models (to be included via the model-includes mechanism).
+
TTM is a generic modeling tool, and although it is not really meant for any specific application domain such as control/filter expressions that are more naturally specified in a tool such as Simulink, the concept of FUNCTIONS, now supported in TTM 3.x and higher, make it possible to represent things like Discrete Filters. This should allow users to create libraries of TTM models (to be included via the model-includes mechanism).
  
==Function==
+
==Example Function==
  
For a general first order filter specified like this
+
For a general first order filter specified as follows:
  
 
<table>
 
<table>
<pre>
+
<div style="text-indent:12">
Discrete filter:   
+
<br>
 
+
Discrete Transfer Function<br>
        A.z + B
+
    A.z + B<br>
        -------
+
    -------<br>
        D.z + C
+
    D.z + C<br>
 
+
where A, B, C, D are real numbers.<br>
where A, B, C, D are real numbers
+
<br>
 
+
Or, alternatively<br>
The output of the function is defined as  
+
<br>
 
+
Discrete Filter:<br>
    Oz0 = A/D*In.z0 + B/D*In.z-1 - C/D*Out.z-1
+
    A + B.z<sup>-1</sup><br>
 
+
    ----------<br>
Where  
+
    D + C.z<sup>-1</sup><br>
 
+
The output of the function is defined as <br>
     In.z0 : current input
+
    Oz<sup>0</sup> = A/D*In.z<sup>0</sup> + B/D*In.z<sup>-1</sup> - C/D*Out.z<sup>-1</sup><br>
     In.z-1: previous input
+
Where <br>
</pre>
+
     In.z<sup>0</sup> : current input<br>
 +
     In.z<sup>-1</sup>: previous input<br>
 +
<br>NOTE: these 2 specifications are equivalent, one form is used by control engineers and the other is used by filter designers. <br>
 +
The output function definition is the same regardless.<br>
 +
</div>
 
</table>
 
</table>
 
+
==Approach==
 
To represent this in TTM it is necessary to state the semantics in terms of a function of current cycle input values and a previous cycle computed state variable (or multiple previous cycle state variables, in the case of z-equations of orders greater than 1). This requires the equation to be in a form similar to the expressions used to perform such a filter computation, computing the primary output and also computing a state variable output that you would also reference as an input (from the previous cycle's output computation).
 
To represent this in TTM it is necessary to state the semantics in terms of a function of current cycle input values and a previous cycle computed state variable (or multiple previous cycle state variables, in the case of z-equations of orders greater than 1). This requires the equation to be in a form similar to the expressions used to perform such a filter computation, computing the primary output and also computing a state variable output that you would also reference as an input (from the previous cycle's output computation).
  
Line 33: Line 37:
  
 
===First Order Filter Function===
 
===First Order Filter Function===
Use the approach as follows:
 
  
 
[[Image:firstOrderFilter_ttm.jpg|center|TTM firstOrderFilter]]
 
[[Image:firstOrderFilter_ttm.jpg|center|TTM firstOrderFilter]]
Line 39: Line 42:
 
===Discrete Filter Condition Table===
 
===Discrete Filter Condition Table===
 
The coefficients are modeled as TTM constants. The state variables representing previous input and previous output are modeled as "inputs" to the model. The model for the output "Discrete_Filter" is specified in terms of these inputs so that they can be considered to be variables that wrap around from the output of one cycle to the input of the next cycle.  
 
The coefficients are modeled as TTM constants. The state variables representing previous input and previous output are modeled as "inputs" to the model. The model for the output "Discrete_Filter" is specified in terms of these inputs so that they can be considered to be variables that wrap around from the output of one cycle to the input of the next cycle.  
 
 
  
 
[[Image:Discrete_Filter_ttm.jpg|center|TTM Discrete_Filter]]
 
[[Image:Discrete_Filter_ttm.jpg|center|TTM Discrete_Filter]]
  
Additional aspects of filter-oriented requirements should probably be added to this model, such as an input representing the current RealTime Clock and the passing of an execution cycle (that is, the passing of a time duration value representing the "sample time" for the filter). But those extra details are would make this email more confusing than is necessary to simply answer your original question.  
+
===Other Comments===
 +
Additional aspects of filter-oriented requirements should probably be added to this model, such as an input representing the current RealTime Clock and the passing of an execution cycle (that is, the passing of a time duration value representing the "sample time" for the filter). But those extra details would make this example more confusing.  
  
 
===How to Use===
 
===How to Use===
  
If someone wanted to know how it would be possible to model debounce functions for the followign example:  
+
If someone wanted to know how it would be possible to model debounce functions for the following example:  
  
 
:"Block X shall compute the signal Y passing the raw signal through a debounce with persistence time of 0.5 seconds"
 
:"Block X shall compute the signal Y passing the raw signal through a debounce with persistence time of 0.5 seconds"
  
A user could define the constants A, B, C, and D with proper values for your specific requirement.
+
A user could define the constants A, B, C, and D with proper values for their specific requirement.

Latest revision as of 16:28, 20 February 2007