search

nerocide / jhe42b_buzzer_firmware

firmware for autonomous buzzer JHE42B
GNU General Public License v3.0
4 stars 1 forks source link

Strange behavior after flashing #3

Open master0id opened 6 months ago

master0id commented 6 months ago

Flashed two JHE42B_S boards with firmware - everything flashed successfully. But after powering up buzzer - it is beeping all the time - in fast pattern. Also it is not reacting to button press or if powering it up from 5v connector also no reaction..

Checked 2 working buzzers - result is the same.. Now I have 2 not working buzzers :)

nerocide commented 4 months ago

I just pushed a new tag/release that works for JHE42B. Many things were broken since ...

Additionnally in your case JHE42B_S pinout might be different. Ididn't checked this board yet.

You should have a look at https://github.com/nerocide/jhe42b_buzzer_firmware/releases/tag/0.1

master0id commented 4 months ago

will flash and let you know, thanks!

master0id commented 4 months ago

tested, it is turning on now, even playing melody :) but when I'm turn the external power off - nothing is happening...

recorded video: video

nerocide commented 4 months ago

Thanks for the extensive testing. Can you confirm you board model? It seams like a JHE42B on video

I think there is some misunderstanding on how the buzzer gets armed and disarmed.

After powering up, you pressed the onboard button which disarmed the system. Edit: actually you touched near the red LED and it got disarmed...i'll check on my side

In order to rearm after disarming, you need to power cycle the buzzer.

Also, Red LED ON means armed, and OFF when not.

You can refer to https://github.com/nerocide/jhe42b_buzzer_firmware?tab=readme-ov-file#user-manual for details on how to use the buzzer.

master0id commented 4 months ago

The red LED is turning off automatically after 10-15 seconds or so. I tested differently, with pressing button, and with not touching buzzer at all.

nerocide commented 4 months ago

I was able to reproduce the behaviour, for me moving a finger close to the area where the button triggers disarm.... i have no idea what's happening here.

Appart from that you should be able to use the buzzer normally.

Can you confirm what board model you are using? And maybe take close up pictures from both side of the board.

Did you try to reflash it ?

nerocide commented 4 months ago

ok, found a workarround and pushed it , can you try https://github.com/nerocide/jhe42b_buzzer_firmware/releases/tag/0.2

disarm procedure with button changed, you now need 3 long press https://github.com/nerocide/jhe42b_buzzer_firmware?tab=readme-ov-file#user-manual

master0id commented 4 months ago

ok, found a workarround and pushed it , can you try https://github.com/nerocide/jhe42b_buzzer_firmware/releases/tag/0.2

disarm procedure with button changed, you now need 3 long press https://github.com/nerocide/jhe42b_buzzer_firmware?tab=readme-ov-file#user-manual

will test today.

master0id commented 4 months ago

now it is working as expected.

The only thing - it is beeping too long - when it got beeps from betaflight (or when control wire is pushed to the ground), beeps must have length = as long as control wire is pushed to the ground.

Aslo, the boards I have: IMAGE 2024-07-09 09:18:38

nerocide commented 4 months ago

Good, and that confirms it works on JHE42B_S too (center and right on picture) Did you tried the firmware on both of them?

Board on the left doesn't look to use STM8S003F3 chip.

When SIGNAL is applied, the buzzer alarm will run for 1s then repeat as long as SIGNAL is maintened.

But i see what you mean, here is a modification with a different sound pattern for signal alarm(much faster). > https://github.com/nerocide/jhe42b_buzzer_firmware/releases/tag/0.2.1

nerocide commented 4 months ago

Is this new release working as you expect?

master0id commented 4 months ago

Is this new release working as you expect?

will check today.

master0id commented 4 months ago

Is this new release working as you expect?

1) Well, it is beeping with short beeps now - for the period while you're holding control wire on ground. It's kinda "ok", but original buzzer behavior is: to beep continously (one beep, without interruptions) - all the time while control wire is on ground. (That is used for example in betaflight flight controllers to give sound messages to pilot).

2) In all other scenarios it is working as expected, but sometimes - I still facing the issue - that I'm not pressing button, but just touching buzzer with my finger (checked several times) - and it acts like I've pressed the button (it turns off). Somehow it is working like touch sensitive thing :) That's what you've seen in video (you thought that I PRESSED the button, but I just TOUCHED the beeper, nothing more).

nerocide commented 1 month ago
  1. [...] original buzzer behavior is: to beep continously

Due to sound generation implementation (using arduino framework for STM8 missing tone(), not native STM framework), a continuous beep is not desired. Connecting signal wire to ground is already making buzzer play sound and should work with betaflight

  1. In all other scenarios it is working as expected, but sometimes - I still facing the issue - that I'm not pressing button, but just touching buzzer with my finger (checked several times) - and it acts like I've pressed the button (it turns off). Somehow it is working like touch sensitive thing :) That's what you've seen in video (you thought that I PRESSED the button, but I just TOUCHED the beeper, nothing more).

From tag 0.2 this behaviour should have reduced at least. I didn't noticed this happening again when testing.