Hi unseen,

The buzzer is working perfectly! I made a custom frame m2m distance is 86mm and the CF thickness is 1mm:




and here is my mosquito:



AUW is around 37g (my scale's resolution is 2g) with 300mAh battery.


Thank you again for your great help!

My next plan is building a 2S version with the same size

That's great! No more searching for your tiny quad in the long grass.

I like your minimal frame. 37g is very light indeed and it looks like a nice clean build. What motors are you using?

I'm just having fun myself putting one of these frames together:



I'm using the tinyFISH flight controller, tinyPEPPER 4-in-1 ESC, 0703 20,000kv motors and the VM275T camera/VTX. I'm having a few challenges with the build, most of which I've now resolved.

First off, the screws that came with these tiny motors were far too long and who has stock of M1.6 screws in various lengths? I've cut them down to size, but it's almost impossible to get the threads to start properly after cutting the screws and the final result is far from perfect. Then I made the mistake of trusting the silk screen when it came to the motor numbering on the flight controller - it's wrong of course. I also made the mistake of connecting the power leads from the outside of the flight controller rather than the inside and only realised they would foul one of the props once I'd put everything together. Grrr...

The worst mistake was replacing the incorrectly sized antenna wire with a length of solid wire.. As I was taking the quad apart to resolder the motor connections and power leads, I noticed that the antenna was loose and had pulled the tiny pad off the board!

Thankfully, the pad was still connected to the track behind it so I very gently disconnected my solid wire, replaced it with some flexible wire and mixed up some epoxy to hold the wire and loose pad to the board. I'm just waiting for that to set before I put it all back together.

I was very glad for my stereo zoom microscope for that particular repair!

The one thing that's a bit of a shame with the tinyFISH is that the telemetry is implemented as hub telemetry. I have two radios; one tiny Devo 7e and a larger Devo 10. I really like to use my 7e for the micro quads as it takes up very little room in a backpack and all the extra switches and pots on the Devo 10 are pointless for micros. Unfortunately, the Devo 7e is really pressed for memory space and does not implement hub telemetry. So, if I want to use a telemetry alarm for remaining battery power or voltage, I'll have to fly it with my Devo 10. It would have been so nice if the receiver code sent the battery voltage at least as the A2 voltage that's included in the standard telemetry.

Ah well, it'll soon be finished and I'm really looking forward to seeing how it will fly.

The buzzer is important to me because the grass is really long on our field around the runway

I have Racerstar BR1103B 10000kv motors. Honestly the quality of these motors didn't impressed me. I ordered two times 4 pieces. The first 4 motors came with wrong screws. The screws were 1.5mm instead of 2mm. Fortunately I had some spare materials from my previous builds. The second pack had correct screws. But my biggest problem is two or maybe three motors in every packs are running not so smoothly and causing vibration. When I tested the motors in Betaflight the differences were so audible and visible... The first ordered motors were the worst while the latest order is a bit better. Maybe the reason is the bad bearings quality.

I agree with you these small builds are very challenging. I played a lot with the components to find out the best way how to connect the parts together. The motor numbering tricked me also but later I found the proper numbering on pepperf1sh web page I also made a mistake with one soldering pad. I soldered the tiny buzzer directly to the buzzer pads (mistake #1) and when I realized it was in the prop's way I tried to bend it (mistake #2). The negative buzzer pad went off and now I need to connect the buzzer directly to the FET but now with wire

Fortunately the I did not have issue with the telemetry because I have a Taranis radio. But I agree with you although I really like this radio in the 99% percent of my flying I don't need so much switch knobs etc. I need only three switches for arming, flying mode and one for the buzzer. It would be great if Frsky would have a compact radio like Turnigy Evolution with telemetry.

I think that what I'll be doing is buying another Devo 7e and upgrading the MCU to one with more flash and more RAM so that I can make an "Ultimate Devo 7e". The form factor is just so appealing and once fully upgraded, I can use just about any protocol you can think of.

@unseen, try this devo 7e build, I enabled gcc size optimization + EXTENDED_TELEMETRY enabled, full telemetry for FrSky D fits:
https://www.dropbox.com/s/f8qgf8n4qduzis...e.zip?dl=1

No extended telemetry for DSM & FrSky X, but I suppose you don't care ...
It's based on latest nightly, here's the codebase in case you want to update it later (merge with master):
https://github.com/goebish/deviation/tre...nded_telem

Backup everything before trying, I do not have a 7e myself so I couldn't check if it's working

edit: something to know: as SBUS & telemetry hub share the same UART, telemetry works only when armed.

Brilliant! Thanks very much!

I'll load that when I get back home and let you know how it goes. I don't have any full Spektrum receivers and the only models I have the XSR installed in, I'm happy to use the Devo 10 for those as they're not exactly small models.

(05-Jun-2017, 10:38 AM)goebish Wrote: Backup everything before trying, I do not have a 7e myself so I couldn't check if it's working

It works!

I can now get full telemetry and set a telemetry alarm on Cell1 voltage.

Thanks so much goebish. Now I can keep the micro quads with the micro radio! I might still make an Ultimate Devo 7e as you never know when Walkera might stop making them and even with the work involved in replacing the MCU and adding a 4-in-1 module, it's a good investment.

Nice, I'm glad it works

(05-Jun-2017, 12:03 AM)unseen Wrote: ...the screws that came with these tiny motors were far too long and who has stock of M1.6 screws in various lengths? I've cut them down to size, but it's almost impossible to get the threads to start properly after cutting the screws and the final result is far from perfect. 

A tip that I can give unseen, wow, I never thought the day would come!

If you sand/file the very tip of the screw thread, just enough to give it a slight 'bevel' it should go in nice and easy. 

I know that the margin for error with these tiny motors & screws is minimal, so I can understand if you know this and worried about leaving enough 'meat' to thread securely..?

I'll give that a try Tom, thanks!

I've made a pull request for the changes to get the beeper and LED1 working, hopefully they'll be merged at some point.

Are you sure you made the pull request to the right project ?
I can see it in cleanflight github, but not betaflight.

(07-Jun-2017, 12:26 PM)goebish Wrote: Are you sure you made the pull request to the right project ?
I can see it in cleanflight github, but not betaflight.

I thought so. I assumed github made it reflect the project that betaflight is forked from.

It doesn't appear in betaflight github PR:
https://github.com/betaflight/betaflight/pulls

I can see something in cleanflight PR:
https://github.com/cleanflight/cleanflight/pulls
... but even there, the 2 commits aren't yours.
https://github.com/cleanflight/cleanflig...49/commits

Let me know if you want me to handle it, but I'd prefer that your commits are merged as you fixed it first