External Buzzer

@maxakker I have just added initial support for external buzzers to version 2.0 beta 02. It will be included with the official plugin release next week, or you can access the beta version to try immediately from this thread.

Buzzer control with our printers is very simple, but due to Covid restrictions, I am working from my home office, and don’t have a buzzer for testing. Of course I will ensure that this is correctly tested before official release, but if you have any feedback it would be appreciated.

Hi Lawrence,

Thanks for your fast beta version. I’ve tried it and love the new features. Very nice.
About the buzzer functionality; It doesn’t work yet. There’s no buzzer sound triggered before printing. (I did use the setting on the settings page).

Regards,
Max

@maxakker
Thanks for testing and giving feedback. Our testers have reported it working so I’m surprised you are having trouble. Could you let me know which printer model and buzzer unit you are using?

Also, do you know if your buzzer has any custom wiring? Our printers have two lines for sending signals on the peripheral connector to a buzzer, cash drawer etc. Typically by default devices will be connected to line 1, which is what is used by the plugin currently. But it may be that your buzzer has been connected to the second circuit, or you have some custom wiring to enable both a cash drawer and a buzzer to be connected together?

Hi @lawrenceowen,

Great to hear it works for you guys.
I have the following setup: mc-print2 with this buzzer:
https://www.bypos.nl/star-buzzer-09990641

I’ve tested the buzzer with drivers for windows and then it works fine.

Hope this is the info you needed.

Regards,
Max

@maxakker Yes, this is what I needed. Sorry you are having trouble, I would have expected that to work. I’m arranging for a buzzer to be sent to me for testing and will test/debug everything myself. Assuming I can locate the issue, I’ll release an update and let you know via the forum.

Hi we are experiencing the same issue and have the same buzzer – was there a fix for this? Thanks. We have installed verison 02 beta 01 as we needed the shipping status, not sure if that helps or not.

@maxakker & @getmeleads

Please try the 2.0.3 beta 01 version from the 2.0 beta releases page. This should resolve the compatibility issue with buzzers on mC-Print. Any feedback would be appreciated.

@getmeleads this beta includes the Shipping Method fix from 2.0.2.

@lawrenceowen Yes, it works like a charm ?? Thanks for this functionality!

@maxakker thanks for letting me know, I have a few other minor modifications to make and will make an official release of 2.0.3 soon (most likely Monday 8th).

Hi,

I’ve the same buzzer, but with the MC-3 printer.
It wont work. Is this correct and do I need an another buzzer?

Thanks!

@cmderks93 Are you using the 2.0.3 pre-release version of the plugin? In that case you combination should work fine, as long as you have enabled the buzzer option in the plugin settings.

@lawrenceowen hi,
I’m using the latest official version. I think it was 2.0.2?

I’ve also ordered the 39594002, hopefully this will work.

• This reply was modified 3 years, 8 months ago by cmderks93.

@cmderks93
ok, if you can update to the 2.0.3 sample from the 2.0 betas page then your issue should be resolved. Apologies for that, but the initial version of 2.0.x, which added buzzer support, had a bug when used with mC-Print printer models which is fixed in 2.0.3.

I had hoped to release 2.0.3 officially on Monday, other projects caused some delay to that, but it should be released officially soon. Our testing hasn’t shown any new issues with 2.0.3 so my suggestion is to install the beta, it is very safe.

@lawrenceowen Great! It’s fixed.

Would also be nice to keep the previously used settings when updating. Or is this on purpose with the beta?

Thanks a lot!

@cmderks93 Great, glad it’s working.
The settings are managed by WordPress rather than Stars code, and should transfer over automatically when you update a plugin. Although I think on the download pages I wrote a recommendation to uninstall the old plugin first, which does clear the existing settings. This is just a precaution for the betas as you guessed, but isn’t strictly necessary.