-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
Mavlink PLAY_TUNE message does not play tune #12309
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi @wluker , if I issue the command I think we can close this issue, but if I am not understanding your issue or this is still an issue for you would you please re-open? Thanks! |
Hi @mcsauder Thanks for looking into this. This issue is not in I was trying to send that message via an offboard controller, but no tones were being played even though I could tell PX4 was receiving the message. Maybe I am misunderstanding the intended use of the |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
Fix coming in #13158. |
This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions. |
Fixed in #13158. |
In your face @Stale bot! Thanks @julianoes 🎵🎶🎵🎶 |
Describe the bug
Sending a tune string "MFT200CDEFGAB" via a PLAY_TUNE mavlink message does not produce any sound on the drone.
From the fix for #12059 I can produce sound with "tune_control play -m "MFT200CDEFGAB" ".
The PLAY_TUNE mavlink handler is implemented in https://github.com/PX4/Firmware/blob/4831a4b0cfde499eb1a20257cc46b130e6554e3a/src/modules/mavlink/mavlink_receiver.cpp#L1627 and I am sending the correct message because this triggers, but it doesn't produce sound.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A tune should be played.
Drone (please complete the following information):
The text was updated successfully, but these errors were encountered: