Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

Register Log in

Is discrete input signal still raw after it is debounced ?

Status
Not open for further replies.
J

jani12

Advanced Member level 4
Full Member level 1
Joined
Oct 30, 2014
Messages
108
Helped
0
Reputation
0
Reaction score
1
Trophy points
1,298
Visit site
Activity points
2,536
Consider a typical Automotive Embedded Software System.

A discrete input signal is 0 or 1. An example of discrete input is ignition ON or OFF.

After discrete input signal is debounced or a state change is latched, is discrete input signal still raw value?

Second question: Should Electronic Control Unit (ECU) low level software debounce discrete inputs or just read the real time state of discrete input? Are there any exceptions meaning some discrete inputs should be debounced, whereas others don't need to be debounced?
 

What do you mean by "raw" ?

Second question: Should Electronic Control Unit (ECU) low level software debounce discrete inputs or just read the real time state of discrete input? Are there any exceptions meaning some discrete inputs should be debounced, whereas others don't need to be debounced?
Click to expand...

It depends on the purpose of the signal.

For example - suppose you want to detect any change (even a very short change) in a signal.
If you pass your signal through a debouncer - it will be filtered out and you won't catch the change. So it doesn't make sense.
 
  • Like
Reactions: jani12

    J

    jani12

    Points: 2
    Helpful Answer Positive Rating
Status
Not open for further replies.

Similar threads

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top