-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RTTL Buzzer #5048
Comments
Is this some active buzzer, which generates a beep of a specific freq. when the pin is high? GPIO-0 is pulled high as it needs to be high during boot or otherwise the ESP will enter flash mode. If it is a buzzer which only acts on changes of the pin state, then I honestly have no idea what might be wrong here |
If it is set to low, it boot without beep, but after playing rttl sequence it beeps endless. The other does ESP not. Same release. It looks like GPIO-0 keeps high after playing rttl. |
I have seen buzzers do this, on different GPIO pins. But this should be solved when using the new RTTTL library, introduced a couple of months ago. NB: This would have been a great question for the forum... 🤔 👼 |
Both use:
|
@tonhuisman Have you a "normal" build with the new library? |
Of course this could be a library issue, but it could also be that an "active" buzzer (with built in oscillator) is being used. Keep in mind that the RTTL Buzzer plugin expects a passive speaker/piezo (without osc) device with a driver circuit. That is to say, the active type will continue to produce a tone on a steady logic level. Their trigger states vary, some beep on logic high level, some on logic low level. I suggest you post photos of the buzzer module(s) your are using. Or provide links to their online catalog page. This will allow someone to confirm you have the required type of buzzer. |
Hi Devs,
I have 2 ESP8266 and a wired rttl buzzer on each. One of them send a permanent beep after boot, the other correct only play rttl rythms.
Any idea what could be the difference?
Buzzer is wired to D3 (GPIO-0)
The text was updated successfully, but these errors were encountered: