1 switch, 1 pin, "single click, double click..."

[erice1984]

I have a PIC12F683
- 1 pin as an input.
- Using a momentary button

I want to be able to push the button once "single click" and have it execute one thing, and also have it if the button is pressed in quick succession "double click" it executes another thing.

I have looked at
-PULSIN - short click vs. long click
-RCTIME - same, short vs long
-COUNT - single versus double click
-IF..THEN - short vs long click

I want the most efficient way to get it done.

thanks
-eric

[Archangel]

I have a PIC12F683
- 1 pin as an input.
- Using a momentary button

I want to be able to push the button once "single click" and have it execute one thing, and also have it if the button is pressed in quick succession "double click" it executes another thing.

I have looked at
-PULSIN - short click vs. long click
-RCTIME - same, short vs long
-COUNT - single versus double click
-IF..THEN - short vs long click

I want the most efficient way to get it done.

thanks
-eric

You might try the Count command, store the count in a variable and compare the variable to what you want to do. You might get some problems from switch bounce that way though.

[erice1984]

MAIN:
low ind
if but = 0 then
pause 8
count but,500,b0
pause 5
goto bpres
else
goto main
endif

Yeah, I had ran through everything, count seems to be the easiest way to go, I added a small pause in there between BUT=0 and COUNT to wait for some bounce to settle. Only other option was looking to aid in the external debounce circuit area. It upped the consistency but sometimes my LED doesnt light when I hit the button, though I think it may be my button since it has a lot of travel.

[Gusse]

I would do it by defining a time window for input signal. After button is pressed you will wait certain time (loop) and if button is re-pressed during that time then excecute "button twice pressed" -task. If time runs out then "button once pressed" -task.

IF -THEN could be used, also to get debounce delay.

Also if button is held down then do check for that too and continue only after button is released. Then you can support both short and long clicks.

BR,
-Gusse-

[mister_e]

Probably thousand different ways to do it, but here's one top of my head.

Detect the first push button press, from there, start a timer, if you get another push-button press before the timer overflow, you have your double-click condition satisfied.
same thing as Gusse i guess... DOH!

[Acetronics2]

Hi, Steve

Might work with two " Button" commands following each other, as debounce time is effective ONLY if condition TRUE ...

he,he ...

Alain

[mister_e]

Maybe... but as you know, I never use Button, so...

Someone could also go crazy and use CLKI + timer interrupt.... this allow 1,2,3,4,5... click triggers for a x period of time, with a real minimum of code line, something <10 code line I guess.

[Gusse]

Hi, Steve

Might work with two " Button" commands following each other, as debounce time is effective ONLY if condition TRUE ...

he,he ...

Alain

I haven't use Button -command too, but couple of IF - THEN with PAUSE works for me.

IF But = 0 then         'Button is pressed and debounce detections starts 
    PAUSE 100           'wait 100ms or some other more suitable time
    IF But = 0 then     'if button is still held down then do something
                        'start timer or loop for 2nd button press detection ...

I think, some time window must be defined otherwise you will be waiting that other press forever...

Also nice to hear that Steve had similar thoughts

BR,
-Gusse-