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

General Discussion
1

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?

2

Hello @DukeLander !

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

1 Like
3

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.

4

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.

5

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

6

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 (4.0 MB)

Thanks

7

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

8 Likes
8

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

9

This worked. Thank you for solution

1 Like
10

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