Did you know that you can enjoy many members-only features simply by quickly registering (no CAPTCHA!)?
Registering gives you access to our giveaways, forum features, increased search performance, access to our Download Library, create your own blog & gallery, and more!
Once you have registered, stop by in 'Hello World', and introduce yourself.
Doorbell too fast
Posted 09 May 2018 - 03:16 AM
My Omnipro II running firmware 4.0B and generally functioning correctly monitoring smoke detector, movement sensor and door switches, etc etc.
The issue is when I try to add my doorbell in the following way...
+ the physical push button is connected to a Zone
+ the physical bell is connected to a relay driven by one of the Omnipro outputs
+ some basic code....
WHEN doorbell NOT READY
Then LOG Front doorbell
Then doorbell timer on for 1 second
The issue I have is it only works 30% of the time as most people dont press the door bell long enough for the Omnipro to register the event.
I would like to keep the above methodology, i.e. Omnipro detects event and drive bell, as opposed to button directly drive bell and omnipro just log. This is so I can keep other features like do not distub, but this said a functioning doorbell is more important :-)
Any ideas how to speed up omnipro, or slow down the doorbell?
Posted 09 May 2018 - 05:09 AM
Welcome to the Cocoontech forum deang.
Here utilize the combo ELK doorbell and ELK debounce board for my doorbell (ELK 930/960)
Power supply is 12VDC from Omni Pro 2 panel and AC door bell transformer (24VAC?)
elk.jpg 209.53K 14 downloads
The ELK 960 debounce circuit is adjustable.
This drives a CCTV / camera view pop up event (and other stuff) on the OmniTouch 5.7 legacy touch screens.
Posted 09 May 2018 - 12:34 PM
Hello and welcome.
The OPII has a response time of 300ms on zones. this is designed to prevent false alarms from things like lightning, but it can cause problems as you have discovered. Unfortunately this can't be turned off.
I'm assuming you have the doorbell button directly connected to a zone. As Pete mentions above, ELK makes a doorbell interface that certainly will work, but it might be overkill in your application and since the button doesn't connect to an actual doorbell, it may not work. The ELK circuit is designed for an operational doorbell, but you just have a button, and are using a relay to trigger the doorbell. I have another idea if you are willing to experiment a bit. I would try putting a 10 uf to maybe 50 uf across the button/zone and see if that solves your problem. Make sure the polarity so that the positive is connected to the capacitor positive and negative to negative. And you may need to experiment a bit to get the correct size capacitor.
So the capacitor is slowing the response. When someone presses the button, the capacitor is discharged, and when the button is released, it slowly charges up. Extend it past 300ms and you are in business. Capacitors are cheap, so with a bit of trial-and-error, you should get this problem solved.
Posted 09 May 2018 - 06:23 PM
In addition to Ano's suggestion, the other one would be a time delay relay - so the momentary press of the button actually gets held for more like a half a second.
In the Elk world for anyone else reading - you'd set the particular zone to Fast Loop Detection to solve this same problem.
Posted 10 May 2018 - 02:46 PM
Connect a 555 momentary latching timer to the doorbell button which will detect the closure of the doorbell button switch and can be set to latch long enough to always be detected by the OP. The 555 IC with all the necessary components should be under $5.
Posted 10 May 2018 - 03:00 PM
This can also keep people from going crazy on the doorbell button if you get creative with the 555 circuit you can setup a re-triggerable output with delay (wait x amount of time before allowing a retrigger)...
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users