Help with pic 12f629

[Acetronics2]

Hi,

oooooomg!!!! you did it!!! it works!!!

Keep cool ... there's no miracle in that ...

If you need faster response ... forget about your pushbutton !!! Button bouncings will give a totally random functionning ...
another "detector" type has to be used.

Now, modified code reacts for 2 pushings only ???

The obscure reason is you use PM as an assembler and not MPASM with your Microcode IDE ...

Alain

[gutisie]

Hi,



Keep cool ... there's no miracle in that ...

If you need faster response ... forget about your pushbutton !!! Button bouncings will give a totally random functionning ...
another "detector" type has to be used.

Now, modified code reacts for 2 pushings only ???

The obscure reason is you use PM as an assembler and not MPASM with your Microcode IDE ...

Alain

Hi thanks for your response, much appreciated.

The compiler, i use is Pbasic?..with Mplab ide....these are at least the software names.
Do you need a screen capture of the compiling results?

And about the button...what type would you use?...I am absolutly clue less.....and desperate...and tyre...and bald....and...etc...

Any way....Ir sensors?...proximity switches?....

I once more depend on your wisdom master....

[Acetronics2]

Some testings show the minimum time for 3 pushes is ... around 78 ms !!! @ 10ms debounce time and a Pause 0 for scanning ...

so, I really doubt any finger could do that !!!

And about the button...what type would you use?...I am absolutly clue less.....and desperate...and tyre...and bald....and...etc...

Any way....Ir sensors?...proximity switches?....

so What moves the button ???

Alain

[gutisie]

Hi Ace,

Thanks for your reply.

The button is pressed by the piston on a gear box. As i said on other post, my actual reading is 15 to 20 cycles per sec. And i need to stop the piston, after 3 cycles.

I have some Ir sensors. But putting them inside the gearbox or some where around, it is not a good idea.

Hence, buttons is the best for my application i think.

Thanks.

[Acetronics2]

Hi Ace,

, my actual reading is 15 to 20 cycles per sec. And i need to stop the piston, after 3 cycles.

Thanks.

20 c/s is 50 ms ... 3 cycles are 150 ms ...

electronics works for 80 ms per 3 cycles ...

SO ... if your switch is a good quality / low inertia one... it Works !!!

but, of course ... if it works in oil ... ( gear box ...)

magnetic detector looks to be THE thing ... I think telemecanique also have nice proximity switches that can reach 50 or 100 Hz ... ( I have some home ...)

at least it's no more an electronics problem ...

Alain

[mackrackit]

Why not a mag/prox sensor on a connecting rod or gear.
Maybe even find a gear that is 3/1??

[gutisie]

20 c/s is 50 ms ... 3 cycles are 150 ms ...

electronics works for 80 ms per 3 cycles ...

SO ... if your switch is a good quality / low inertia one... it Works !!!

but, of course ... if it works in oil ... ( gear box ...)

magnetic detector looks to be THE thing ... I think telemecanique also have nice proximity switches that can reach 50 or 100 Hz ... ( I have some home ...)

at least it's no more an electronics problem ...

Alain

Thanks guys for your reply.

So Alain, telemec?...ummm....I think they dont sell m5 or less like omron...any way...there are a bit expensive.

Could you guys put me a link of a good button for this application?, Ebay?...thanks.
Regards.

[gutisie]

Hello All,

After trying with different sensor, and switches, I have found out that the reason for the strange behaviour, or mal functioning of the code, it is due to the excess of current supply.

I have notice that when you have the "finger" on any of the conections, the systems works!!, but if you remove the finger, starts to go nuts again.

So at the moment i am supplying from 3v = 2xAA bateries. I will put a LM317 to allow only 250ma to go through.

See if that helps.

I will post my results.

Best regards.

And thank you all for your help.