# Difference between revisions of "Discrete Filter"

(→Model) |
(→Model) |
||

Line 32: | Line 32: | ||

The "firstOrderFilter" function is defined generically in terms of filter coefficients A, B, C, and D and values for the previous input and previous output, as shown in the image below. This Function can be referenced by the output table called Discrete_Filter. | The "firstOrderFilter" function is defined generically in terms of filter coefficients A, B, C, and D and values for the previous input and previous output, as shown in the image below. This Function can be referenced by the output table called Discrete_Filter. | ||

+ | ===First Order Filter Function=== | ||

Use the approach as follows: | Use the approach as follows: | ||

[[Image:firstOrderFilter_ttm.jpg|center|TTM firstOrderFilter]] | [[Image:firstOrderFilter_ttm.jpg|center|TTM firstOrderFilter]] | ||

− | + | ===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. | |

+ | |||

+ | |||

+ | |||

[[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. | |

+ | |||

+ | ===How to Use=== | ||

+ | |||

+ | If someone wanted to know how it would be possible to model debounce functions for the followign example: | ||

+ | |||

+ | :"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. |

## Revision as of 13:20, 20 February 2007

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).

## Contents |

## Function

For a general first order filter specified like this

Discrete filter: A.z + B ------- D.z + C where A, B, C, D are real numbers The output of the function is defined as Oz0 = A/D*In.z0 + B/D*In.z-1 - C/D*Out.z-1 Where In.z0 : current input In.z-1: previous input

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).

## Model

The "firstOrderFilter" function is defined generically in terms of filter coefficients A, B, C, and D and values for the previous input and previous output, as shown in the image below. This Function can be referenced by the output table called Discrete_Filter.

### First Order Filter Function

Use the approach as follows:

### 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.

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.

### How to Use

If someone wanted to know how it would be possible to model debounce functions for the followign example:

- "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.