M300 Beep in DWC

Phaedrux

browser?

Diamondback

browser?

Chrome 103.0.5060.114 on desktop and Chrome 103.0.5060.71 on Android.
In both cases I executed a Macro that only had a beep command in there, so the tab was actuve, the screen on, etc.

OwenD

@diamondback
You said you used to use a PanelDue
Just a guess here, but do you still have M575 configured the same way?
What happens if you set it to say M575 P0 B57600 S2,or comment it out altogether if you aren't using serial comms.

Diamondback

@owend Oh wow, good point! Printer is printing atm, but will try that afterwards. The M575 is indeed still in my config (I left it in in case I need the PanelDue for some freak accident debugging where Wifi wouldn't work anymore...)

OwenD

@diamondback
I did a bit of digging in the firmware and while I only have a basic grasp of C , I can see that if you define a PanelDue in config.g then the M300 will NOT get sent to the browser.
The first section checks if a PanelDue is configured and sends the beep.
It then sets "bleeped" to true as the job was done.
The second section will only run if "bleeped" is false.

I imagine sending to both interfaces would introduce undesirable delays as M300 is typically followed by a G4 command.

if (platform->IsAuxEnabled(0) && !platform->IsAuxRaw(0))
	{
		platform->PanelDueBeep(freq, ms);
		bleeped = true;  
	}

	if (!bleeped)  
	{
		beepFrequency = freq;
		beepDuration = ms;
		beepTimer = millis();
		StateUpdated();
	}
}

Diamondback

@owend Thanks a lot, with the PanelDue support commented out, it works fine now!

Diamondback

Hmm, it's very hit & miss though, it seems that DWC can't play a rapid succession of beeps? I used to have a little three tone jingle, each aboutm300ms long with 300ms pauses inbetween. That doesn't work well at all and simply play one beep instead.

Emitting beeps from the console also shows that there is apparently a significant recovery time after each beep before DWC plays a second one?

Example:

M300 S300 P300
G4 P300
M300 S400 P300
G4 P300
M300 S500 P300

Phaedrux

Glad you got it figured out. The DWC behaviour for beeps is not going to the be the same as the hardware in a PanelDue. Even between PanelDues the behaviour can vary. You may have to change delays and durations to get something you can work with.

Diamondback

@phaedrux said in M300 Beep in DWC:

Glad you got it figured out. The DWC behaviour for beeps is not going to the be the same as the hardware in a PanelDue. Even between PanelDues the behaviour can vary. You may have to change delays and durations to get something you can work with.

Thanks. As a possible alternative, is there a reasonably simple option to add a standlone piezo buzzer to the Duet2/Duex hardware?

Diamondback

@phaedrux said in M300 Beep in DWC:

Glad you got it figured out. The DWC behaviour for beeps is not going to the be the same as the hardware in a PanelDue. Even between PanelDues the behaviour can vary. You may have to change delays and durations to get something you can work with.

It appears that no matter the delay, I cannot get a single macro to play more than one beep via DWC. I'm not sure if this is just unavoidable, but as is, it appears broken from a user POV.

Do I need to change the way I realize the delays? If I let it execute more than one M300, it simply skips them all except for the last one.

Phaedrux

Moved to the wishlist for further consideration by @chrishamm