M300 - play sound -> does not work

[OndraCerv]

Hi,

Code M300 not play sound.
Please of implementacion into new firmware.

Thanks

[hawwwran]

Yes, this!

[matthewlloyd]

Anyone following this issue may be interested to know that I just released custom firmware that adds support for M300 (play a sound), amongst other goodies:

http://github.com/matthewlloyd/Llama-Mini-Firmware#readme

[fortinmike]

@matthewlloyd Did you consider submitting your changes as pull requests to the original repo? Many (including me) are not interested in installing custom firmware but would still love to see some of the things you implemented built in.

[matthewlloyd]

Did you consider submitting your changes as pull requests to the original repo? Many (including me) are not interested in installing custom firmware but would still love to see some of the things you implemented built in.

Given that Prusa has, to my knowledge, never accepted a pull request to this repo, apart from ones written by members of the Prusa team, I considered that approach to be impractical. Besides, they are IMHO violating Marlin's GPL by not releasing the source code for the bootloader, and I am not inclined to contribute to their open source efforts until they have addressed that issue.

If you dislike how difficult Prusa has made it to install custom firmware, I recommend getting in touch with Prusa directly to let your feelings about the appendix be known.

Meanwhile, you can always purchase a clone Mini or Buddy board, and run whatever firmware suits you on it.

[fortinmike]

Given that Prusa has, to my knowledge, never accepted a pull request to this repo, apart from ones written by members of the Prusa team

I was not aware of that. Are you sure that absolutely no pull request was ever accepted? Did they just ignore them or did they at least give a reasonable reason for refusing to merge? That's a bummer for sure. Still, maybe having pull requests sitting on GitHub might pressure them a bit and possibly help kickstart (possibly internal) development on specific features?

As for the appendix on the Buddy board, seems reasonable to me that they have some kind of way to know if, for example, you broke/bricked your machine because you installed defective, unsupported firmware on it. In the end they pay people to support users and IMHO it's not their job to fix issues you create yourself with modifications. Plus breaking the appendix only voids the warranty on the electronics instead of the whole machine. In essence, for sure no appendix would be better, but the fact that it exists does not bother me much, personally. On the other side of the coin, having a hardware mechanism that ensures only signed firmware is installed is a nice security feature to have.

To me, it's still incredible for a for-profit company to release all of their hardware and software as open source and allow flashing custom firmware, with documentation on how to do it to boot, even if it's not perfect.

As for the bootloader, how do people make MINI clones without access to it?

[foorschtbar]

+1

[Eldenroot]

Any progress?

[Gordontgopher]

M300 is enabled in 4.3.4 but there are reports that it is buggy (#1075 (comment))

[Eldenroot]

I use 4.4.0 firmware.

M300 works fine at least for G-code start.

Not working for G-code end properly...

I just use basic tones... so maybe it is bugged.

Would be really cool to fix this issue, even low cost Chinese printers can do that :)

[Prusa-Support]

Pull Requests about M300 functionality were merged in January 2022 (#1796, #1800), supposedly only after the FW 4.3.4 final release (December 2021).

Same as #1075, thanks for reporting this.

Michele Moramarco
Prusa Research

[bcolledge04]

Any update/progress on this ?

[Prusa-Support]

No news. I'm sorry, FW 4.4.1 was released shortly after the last few messages.
I'm afraid this issue didn't make it to the last firmware release.

Michele Moramarco
Prusa Research

[github-actions]

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

[danopernis]

Let me close this as a duplicate of #3660 although this issue is certainly older. The fix is scheduled for next patch release. Sorry for all the confusion.