Implement buzzer sounds

[johnwalicki]

Currently the buzzer will sound an earthquake alert sound if a shake is detected or if the device receives a MQTT message from the regional network declaring an alarm.

Not exactly "music" but we can make the sensor beep different status messages too.

[johnwalicki]

There are a variety of GitHub repositories and tutorials on the Internet which use the Arduino tone() function to play short / crude tunes on the piezo buzzer.
The best repository I found was here: https://github.com/robsoncouto/arduino-songs

[johnwalicki]

The gotcha is that esp-idf does not implement the arduino tone() function
https://esp32.com/viewtopic.php?f=13&t=16839&sid=fe47120147b9794023ba8d59e07c1aa9

[johnwalicki]

The relevant esp-idf docs are here:
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/peripherals/ledc.html

[johnwalicki]

The buzzer code is really simplistic.

// Generate Buzzer sounds
void AlarmBuzzer() {
  ledcWrite(channel, 50);
  delay(100);
  ledcWrite(channel, 500);
  delay(100);
  ledcWrite(channel, 2000);
  delay(100);
  ledcWrite(channel, 4000);
  delay(100);
}

[johnwalicki]

If someone wanted to experiment with the buzzer sound, it would be a good hardware issue to tackle.

[johnwalicki]

Do we want to tag this for the v1.5.0 firmware and Caribbean deployment?
We might push this to the backlog if it's not in the critical path.

[neilh10]

What if the audible is tied to the system states, #7 that would define what states need an audible component and keep it integrated with the major visual status. It simplifies testing.

When a device/product is successful it is often because there are user interface components that are configurable - the tones - so potentially (for the future) an extensible framework that could allow tone configuration. (ouch sorry seems like just needs one pleasant sound for the first pass !)

One of the issues with audible is a user "cut-off" ~ "thanks I heard, now turn off".
This was standard requirement for all telecom equipment that had an Infiniti of notifications for the technicians to be alerted.

The cut-off was both messaging, the virtual (MQTT?), and also the physical in front of the device.
Could a "double tap" on the side of the device be detected,(and separated out from earthquake readings) for an audible cutoff.

[andygrillo]

I really like the idea of the double tap ! I think we would need to run that by Vaclav and get seismology input first! Please note that the buzzer isnt very loud, and should likely only be on during an earthquake when its necessary and people are preparing for shaking.

…

On Thu, 1 Apr 2021 at 09:51, neilh ***@***.***> wrote: What if the audible is tied to the system states, #7 <#7> that would define what states need an audible component and keep it integrated with the major visual status. It simplifies testing. When a device/product is successful it is often because there are user interface components that are configurable - the tones - so potentially (for the future) an extensible framework that could allow tone configuration. (ouch sorry seems like just needs one pleasant sound for the first pass !) One of the issues with audible is a user "cut-off" ~ "thanks I heard, now turn off". This was standard requirement for all telecom equipment that had an Infiniti of notifications for the technicians to be alerted. The cut-off was both messaging, the virtual (MQTT?), and also the physical in front of the device. Could a "double tap" on the side of the device be detected,(and separated out from earthquake readings) for an audible cutoff. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#7 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABP5GHJ7ZJ6BEPJG2EQCKLTTGSI7NANCNFSM42GDTUFA> .

-- Andres Meira *m* +52 (55) 12246468 *skype *andresmeira