# After latest update to v0.12.0-98, M300 (beeper) doesn't work properly

**URL:** <https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523>\
**Category:** General Discussion\
**Created:** [January 26, 2024, 2:03pm UTC](https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523 "2024-01-26T14:03:38Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![DukeLander](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@DukeLander](https://klipper.discourse.group/u/DukeLander)\
**Post date:** [January 26, 2024, 2:03pm UTC](https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523/1 "2024-01-26T14:03:38Z")

</div>

After today update from v0.12.0-88 to v0.12.0-98, whatever value I give to M300 command, beeper sound ( pitch) is always the same.  
Rolled back to v0.12.0-88, everything works fine.

Anybody else?

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [January 26, 2024, 6:32pm UTC](https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523/2 "2024-01-26T18:32:25Z")

</div>

Hello @DukeLander !

Do you think an attached klippy.log - as it was requested - can help to find the issue?

---

<div class="post-metadata">

**Author:** ![DukeLander](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@DukeLander](https://klipper.discourse.group/u/DukeLander)\
**Post date:** [January 26, 2024, 8:35pm UTC](https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523/3 "2024-01-26T20:35:30Z")

</div>

Actually no, because everything is working fine except beeper pitch, its always a same whatever frequency I give.  
But if you think its gonna help, I can update back to newest version to take log file.

---

<div class="post-metadata">

**Author:** ![jakep\_82](https://avatars.discourse-cdn.com/v4/letter/j/ea666f/32.png) [@jakep\_82](https://klipper.discourse.group/u/jakep_82)\
**Post date:** [January 26, 2024, 8:52pm UTC](https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523/4 "2024-01-26T20:52:10Z")

</div>

Some changes were recently merged that change how an output\_pin works. Seeing a log will be necessary to determine how you have the beeper configured, and what might be causing the issue.

---

<div class="post-metadata">

**Author:** ![DukeLander](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@DukeLander](https://klipper.discourse.group/u/DukeLander)\
**Post date:** [January 26, 2024, 8:57pm UTC](https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523/5 "2024-01-26T20:57:14Z")

</div>

Understood. I will do it as soon I have little free time. Tnx

---

<div class="post-metadata">

**Author:** ![satyrlire](https://avatars.discourse-cdn.com/v4/letter/s/ee7513/32.png) [@satyrlire](https://klipper.discourse.group/u/satyrlire)\
**Post date:** [January 28, 2024, 4:04am UTC](https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523/6 "2024-01-28T04:04:26Z")

</div>

HI

I have the exact same situation.

This happened on 2 of my printer that I’ve updated/flashed recently.

One is a Fysetc Spider V3 Mainboard, with a Mini12864 from Fysetc  
&  
The other one is a Btt Manta M8P mainboard with a Mini12864 from Btt.

Each of those had a different song playing at the end of print since a while, then after the update it doesn’t work properly.

I’ve uploaded the log from the Btt one, since it’s smaller than the other one

[klippy-10.log](https://klipper.discourse.group/uploads/short-url/jM5jkFTBeQDvHRROQav4m2ohmjZ.log) (4.0 MB)

Thanks

---

<div class="post-metadata">

**Author:** ![BreeOge](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/breeoge/32/9812_2.png) [@BreeOge](https://klipper.discourse.group/u/BreeOge)\
**Post date:** [January 28, 2024, 5:30am UTC](https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523/7 "2024-01-28T05:30:10Z")

</div>

Found the issue…

After the recent update

> [output\_pin \_BEEPER\_pin]  
> pin = EXP1\_1  
> pwm = True  
> value = 0  
> shutdown\_value = 0  
> cycle\_time = 0.001

now needs to be

> [pwm\_cycle\_time \_BEEPER\_pin]  
> pin = EXP1\_1  
> value = 0  
> shutdown\_value = 0  
> cycle\_time = 0.001

The change is it now needs to be pwm\_cycle\_time instead of output\_pin

---

<div class="post-metadata">

**Author:** ![Luigisvc](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@Luigisvc](https://klipper.discourse.group/u/Luigisvc)\
**Post date:** [January 28, 2024, 1:33pm UTC](https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523/8 "2024-01-28T13:33:55Z")

</div>

Thank you, I was having the exactly same issue after update few minutes ago.

---

<div class="post-metadata">

**Author:** ![DukeLander](https://avatars.discourse-cdn.com/v4/letter/d/eb8c5e/32.png) [@DukeLander](https://klipper.discourse.group/u/DukeLander)\
**Post date:** [January 28, 2024, 4:29pm UTC](https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523/9 "2024-01-28T16:29:36Z")

</div>

This worked. Thank you for solution

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [February 28, 2024, 2:29am UTC](https://klipper.discourse.group/t/after-latest-update-to-v0-12-0-98-m300-beeper-doesnt-work-properly/13523/10 "2024-02-28T02:29:43Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
