Right now, when the Breathing Circuit Alarms driver class activates an alarm, it just creates a LogEvent and adds the ID of the resulting event into an internal collection of active alarms. However, the firmware should also use the interface board's buzzers to play an audio pattern corresponding to the type (and maybe severity) of the alarm. When the alarm is deactivated, the sound corresponding to it should stop (and if a different alarm is still active but its sound was masked/overridden, then its sound should start playing).
Right now, when the Breathing Circuit Alarms driver class activates an alarm, it just creates a LogEvent and adds the ID of the resulting event into an internal collection of active alarms. However, the firmware should also use the interface board's buzzers to play an audio pattern corresponding to the type (and maybe severity) of the alarm. When the alarm is deactivated, the sound corresponding to it should stop (and if a different alarm is still active but its sound was masked/overridden, then its sound should start playing).