Debounce: Difference between revisions
Jump to navigation
Jump to search
(Created page with "*Example from Arduino - [https://www.arduino.cc/en/tutorial/debounce] - Too complicated for CEB case. *In OSE's CEB press - is a debounce of the high pressure sensor really ne...") |
No edit summary |
||
| Line 2: | Line 2: | ||
*In OSE's CEB press - is a debounce of the high pressure sensor really necessary? | *In OSE's CEB press - is a debounce of the high pressure sensor really necessary? | ||
*It appears that whenever high pressure triggers - there is a delay in the system because other steps are happening, which take time. Thus, as soon as any trigger happens - it doesn't matter if it's pressed once or multiple times during a short period - therefore - debounce should not be necessary. All we need to know is that a trigger event happened. Whenever a trigger event happens that would only be during the full expansion/retraction - and at brick pressing step. Anything else would be mechanical stuckage, and should be addressed not by debounce but by a mechanical fix. | *It appears that whenever high pressure triggers - there is a delay in the system because other steps are happening, which take time. Thus, as soon as any trigger happens - it doesn't matter if it's pressed once or multiple times during a short period - therefore - debounce should not be necessary. All we need to know is that a trigger event happened. Whenever a trigger event happens that would only be during the full expansion/retraction - and at brick pressing step. Anything else would be mechanical stuckage, and should be addressed not by debounce but by a mechanical fix. | ||
*At the same time - including debounce would not do anything negative to the system | |||
Latest revision as of 22:31, 27 January 2019
- Example from Arduino - [1] - Too complicated for CEB case.
- In OSE's CEB press - is a debounce of the high pressure sensor really necessary?
- It appears that whenever high pressure triggers - there is a delay in the system because other steps are happening, which take time. Thus, as soon as any trigger happens - it doesn't matter if it's pressed once or multiple times during a short period - therefore - debounce should not be necessary. All we need to know is that a trigger event happened. Whenever a trigger event happens that would only be during the full expansion/retraction - and at brick pressing step. Anything else would be mechanical stuckage, and should be addressed not by debounce but by a mechanical fix.
- At the same time - including debounce would not do anything negative to the system