dark0707
/
px4-firmware
forked from Archive/PX4-Autopilot
1
0
Fork 0
Code Pull Requests Activity
px4-firmware/msg/tune_control.msg

39 lines
1.4 KiB
Plaintext
Raw Normal View History

libtunes: handle tune override
2017-02-27 12:18:36 -04:00
# This message is used to control the tunes, when the tune_id is set to CUSTOM
# then the frequency, duration are used otherwise those values are ignored.
add timestamp field to uORB msgs; sync timestamp whenever possible
2018-08-06 21:30:05 -03:00
uint64 timestamp # time since system start (microseconds)
drivers/tone_alarm and tune_control small improvements/cleanup - drivers/tone_alarm: move to ModuleBase and purge CDev (/dev/tone_alarm0) - drivers/tone_alarm: only run on tune_control publication (or scheduled note) rather than continuously - drivers/tone_alarm: use HRT to schedule tone stop (prevents potential disruption) - msg/tune_control: add tune_id numbering - systemcmds/tune_control: add "error" special case tune_id - move all tune_control publication to new uORB::PublicationQueued<> - start tone_alarm immediately after board defaults are loaded to fix potential startup issues - for SITL (or other boards with no TONE output) print common messages (startup, error, etc)
2020-10-05 22:39:26 -03:00
uint8 TUNE_ID_STOP = 0
uint8 TUNE_ID_STARTUP = 1
uint8 TUNE_ID_ERROR = 2
uint8 TUNE_ID_NOTIFY_POSITIVE = 3
uint8 TUNE_ID_NOTIFY_NEUTRAL = 4
uint8 TUNE_ID_NOTIFY_NEGATIVE = 5
uint8 TUNE_ID_ARMING_WARNING = 6
uint8 TUNE_ID_BATTERY_WARNING_SLOW = 7
uint8 TUNE_ID_BATTERY_WARNING_FAST = 8
uint8 TUNE_ID_GPS_WARNING = 9
uint8 TUNE_ID_ARMING_FAILURE = 10
uint8 TUNE_ID_PARACHUTE_RELEASE = 11
uint8 TUNE_ID_SINGLE_BEEP = 12
uint8 TUNE_ID_HOME_SET = 13
uint8 TUNE_ID_SD_INIT = 14
uint8 TUNE_ID_SD_ERROR = 15
uint8 TUNE_ID_PROG_PX4IO = 16
uint8 TUNE_ID_PROG_PX4IO_OK = 17
uint8 TUNE_ID_PROG_PX4IO_ERR = 18
uint8 NUMBER_OF_TUNES = 19
tune_control: update comment
2017-08-08 05:20:49 -03:00
uint8 tune_id # tune_id corresponding to TuneID::* from the tune_defaults.h in the tunes library
drivers/tone_alarm and tune_control small improvements/cleanup - drivers/tone_alarm: move to ModuleBase and purge CDev (/dev/tone_alarm0) - drivers/tone_alarm: only run on tune_control publication (or scheduled note) rather than continuously - drivers/tone_alarm: use HRT to schedule tone stop (prevents potential disruption) - msg/tune_control: add tune_id numbering - systemcmds/tune_control: add "error" special case tune_id - move all tune_control publication to new uORB::PublicationQueued<> - start tone_alarm immediately after board defaults are loaded to fix potential startup issues - for SITL (or other boards with no TONE output) print common messages (startup, error, etc)
2020-10-05 22:39:26 -03:00
bool tune_override # if true the tune which is playing will be stopped and the new started
libtunes: handle tune override
2017-02-27 12:18:36 -04:00
uint16 frequency # in Hz
uint32 duration # in us
Rename tune_control_s strength to volume to match Nuttx and Linux standard nomenclature for audio (loudness) control.
2019-02-18 18:13:56 -04:00
uint32 silence # in us
uint8 volume # value between 0-100 if supported by backend
tune_control: added define for tune strength This adds a define for the tune strength instead of hard-coding it with a magic number.
2018-02-22 06:31:32 -04:00
Rename tune_control_s strength to volume to match Nuttx and Linux standard nomenclature for audio (loudness) control.
2019-02-18 18:13:56 -04:00
uint8 VOLUME_LEVEL_MIN = 0
uint8 VOLUME_LEVEL_DEFAULT = 40
uint8 VOLUME_LEVEL_MAX = 100
tune_control: use orb queue advertisement consistently
2019-07-16 08:55:59 -03:00
fix: uORB topics lost messages when publications overflow
2020-09-25 12:11:55 -03:00
uint8 ORB_QUEUE_LENGTH = 4