(13-May-2017, 05:43 PM)Tom BD Bad Wrote: Check this guy out, just gimme half an hour..!

I'm a software developer by trade Tom, so it's not really rocket science for me. The fact that I run Linux on my computers and don't have to jump through hoops to use them also helps.

I tested it but now the buzzer is not working at all.

(13-May-2017, 08:57 PM)oleeg Wrote: I tested it but now the buzzer is not working at all.

That's not good.

Can you see, or otherwise confirm if pin 4 of the STM32 is connected to the FET that the buzzer is connected to? (The FET is a little black device with two legs on one side and one on the other.)

Does the LED behave differently now?

There is no change regarding with the LED. I made a picture (sorry for the quality) and checked the connection between the FET and the STM32 with a multimeter. The pink line shows this connection and as I see the FET is connected to pin 4.

Well, I'm really puzzled as to why making a new hex with the pin assignment corrected doesn't make it work properly.

Seeing as I hate a mystery, one of these flight controllers will soon be starting the journey from China to me! With one in my hands I can get an oscilloscope on it and see what's really happening. As soon as I have the board and have worked out the problem, I'll post the fix here.

I'm having the same issue with a machine I just built.
I'll tackle that next week end, I'll check if there's a fix on github already, if not I should be able to fix it by myself ...

(01-Jun-2017, 02:24 AM)goebish Wrote: I'm having the same issue with a machine I just built.
I'll tackle that next week end, I'll check if there's a fix on github already, if not I should be able to fix it by myself ...

How nice to see you here goebish! Welcome to the forum!

My flight controller has just arrived, so hopefully I'll have some time to look at mine this weekend as well.

(01-Jun-2017, 07:09 AM)unseen Wrote: How nice to see you here goebish! Welcome to the forum!

My flight controller has just arrived, so hopefully I'll have some time to look at mine this weekend as well.

Such a good news unseen

I'm on holiday and I brought my "pepperf1sh" with me. It was so fun flying in the garden until I crashed it. Unfortunately my base plate broke and one motor wire was tore down from the esc... I glued the base plate and I need to solder but I have only an "emergency" soldering iron now.

regards,

o

OK, working beeper time!

Here's a revised version of the TINYFISH target. Please flash with Full Chip Erase so that the firmware loads the new default settings for the beeper.

Obviously, you'll need to set it up again if you are not already running 3.1.7, otherwise, reload your dump. Whichever way, check that a 'get beeper' shows the following settings:

beeper_inversion = ON
beeper_od = OFF

I also changed 'bat_detect_thresh' from 55 to 33, so that Betaflight doesn't think that you don't have a battery connected when running on 1S.


  betaflight_3.1.7_TINYFISH.hex.zip (Size: 223.52 KB / Downloads: 81)

Please let me know if it works for you, or if it doesn't. Once I have a few confirmations that it works, I'll make a pull request and get the changes merged.

It's working here, thank you very much

Excellent!

Thanks for reporting back so quickly.

Thank you so much unseen! I will test it tomorrow and hopefully I will get my new frame as well.
By the way what was the problem?

It's wasn't just that the pin assignment was incorrect, the defaults for the two settings I listed were also incorrect.

The second LED still does nothing (not that it did anything before either), so I'll see what that is actually connected to and if the code even uses it. If there's a correction to be made there, I'll make a new HEX file with the changes.

The second (blue) LED works here with your HEX, when I switch to acro mode.

(03-Jun-2017, 11:42 PM)goebish Wrote: The second (blue) LED works here with your HEX, when I switch to acro mode.

Ah, that's good!

I guess the blue LED on mine is dead then. Saves me having to waste time finding out there was nothing wrong with my changes. Thanks!