Re: What are the best settings to de-bounce a switch input?
Posted: Thu Mar 06, 2025 5:39 pm
What I am triggering is a button in the QLC+ software. I have created a virtual console. The physical setup is an interactive display inside a children's hospital. There are large pushbuttons that small children can press and when they do, a section of LEDs lights up on a model of Idaho. When pressed, a positive voltage is applied to the inputs of the ORION. The display stopped working about a year and half ago. The vendor that created the display is no longer in business and we have no contact information for the original creators. I am a software engineer working at the hospital. However, I also have an electrical engineering degree so I was asked to see if I can fix this display. The display had a PC inside running custom software to control the display. That PC had a massive disk failure, and the original program was lost. I am attempting to recreate the functionality using QLC+. I have created a virtual console in QLC+. This console has buttons. The buttons are a "toggle" function. The software is configured to monitor packets from the ORION. When it sends two packets instead of one packet, when the button is pressed it turns off the button immediately after turning it on.
I am sure I am not the only one that has a use case to detect a button press that does not look like a random number of presses. The slope detection function of the ORION would seem logical to send only one packet when the slope is detected but apparently that is not the case.
How can I determine what the sample rate will be? I can try to add additional circuitry to modify the signal of the button press to accommodate the limitations of the ORION so it will only see the voltage for one sample which would hopefully result in only on packet being sent.
This message board only allow photos that have public urls in URLS. I have no such resource otherwise I would share photos
I am sure I am not the only one that has a use case to detect a button press that does not look like a random number of presses. The slope detection function of the ORION would seem logical to send only one packet when the slope is detected but apparently that is not the case.
How can I determine what the sample rate will be? I can try to add additional circuitry to modify the signal of the button press to accommodate the limitations of the ORION so it will only see the voltage for one sample which would hopefully result in only on packet being sent.
This message board only allow photos that have public urls in URLS. I have no such resource otherwise I would share photos