Is discrete input signal still raw after it is debounced ?

naseeam
naseeam used Ask the Experts™
on
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?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Principal Software Engineer
Commented:
After discrete input signal is debounced or a state change is latched, is discrete input signal still raw value?

This question pretty much answers itself.  The signal has been conditioned; it is no longer a raw value.

Should Electronic Control Unit (ECU) low level software debounce discrete inputs or just read the real time state of discrete input?

Some signals need to be debounced and some do not.  Mechanical switches tend to be electrically dirty, electronic switches such as Hall effect tend to be clean.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial