I like your setup, micros and HD gear can be a real issue with jello, I even had to abandon builds due to jello. Actually looking at your footage it's not too bad, pushing your pids will help, and will certainly sharpen the handling.

In your ESC configurator would push the beacon and beep sliders to near max, as it will help find your quad, particularly in long grass. If you're comparing handling to a moblite7 -- that's a whoop with prop guards, which direct thrust, at first your toothpick will feel a bit slidey but once tuned your really going to enjoy it.

(26-Mar-2024, 02:24 PM)mstc Wrote: [...] so if the canopy is from soft TPU, then probably it is too flexy and causing the vibrations. But some HM motors are unbalanced or with bad bearings out of the box. If you are comfortable, you can spun up motors with props one by one in BF (slowly) and check if any one is vibrating excessively. Also enabling rpm filters if you haven't already, will also make it fly smoother.

The red TPU indeed is quite soft. I have a second canopy printed with harder TPU and I'm going to try it. Unfortunately it is black so I hope I wont lose the quad 
The RPM filters are already enabled, but I will also check the motors as you advise.

(26-Mar-2024, 02:24 PM)mstc Wrote: And since you flipped the AIO, I was going to say be sure to change the board orientation in BF but seems you have already done that.

I initially planned to position the FC as it was designed, but I ran into two problems: first, the USB port was in an awkward position, and second, the pigtail would have to be twisted quite a bit to reach underneath: 


Both problems disappeared after flipping the FC upside down. Interestingly, the orientation was already changed in BF.

(26-Mar-2024, 04:34 PM)Cyberess Wrote: In your ESC configurator would push the beacon and beep sliders to near max, as it will help find your quad, particularly in long grass.

I'm not sure how far I can safely push the Beep and Beacon sliders. The ESC configurator says that setting those values too high might damage the motors.
I plan to install a dedicated buzzer anyway, but don't have it yet.

Thanks!

I guess BF sells this board pre-installed on their Pavo Pico/25 pusher drones, and there the setup is the same (upside down) so that is probably why the default is set for that orientation. That works out fine for you, as otherwise the motors would also need to be remapped as well. But yes flipping and turning AIO to find the best fit for your frame/setup is part of building, as seems each AIO has plugs, leads, USB, antennas in different locations. But be careful for the ELRS antenna, if it is coming out the bottom make sure your battery is not blocking or crushing it.

For the motor setting, I never tried maxing that slider, but suspect you won't actually burn it with 2S. However if you are out in the open, those motor beeps are not very loud, and you would have to be very close or have good hearing. A buzzer adds a few grams, but certainly will help you find the drone more easily.

93g is not bad on weight. My first one was over that.

Looks like you made something that flies pretty well. Now just enjoy flying it. Soon it will be summer and lots more flying.

(26-Mar-2024, 09:28 PM)bozon Wrote: I'm not sure how far I can safely push the Beep and Beacon sliders. The ESC configurator says that setting those values too high might damage the motors.
I plan to install a dedicated buzzer anyway, but don't have it yet.

Thanks!

Never burnt out or damaged a motor with the  Beep and Beacon sliders up near max, but I have certainly recover my drone quite a number of times, using the beeps coming from the motors, actually depending on the motors it can actually be quite loud.  One day I will probably locate the drone from the smoke coming motors  .

If using Walknsail another good method method is using the OSD distance measurement between Googles and Drone that's in the goggles, the only issue about that is you usually only get a 2 to 3 minutes before the VTX shuts down to overheating, one good thing usually the motors keep beeping.  

Anyway I would be interested  to hear if anyone has actually damaged a motor due to Beep and Beacon settings.

(27-Mar-2024, 02:34 AM)Pathfinder075 Wrote: 93g is not bad on weight. My first one was over that.

With 3S I have for it - CNHL MiniStar 450 mAh - it is a bit heavier - around 106g

(27-Mar-2024, 04:59 AM)Cyberess Wrote: One day I will probably locate the drone from the smoke coming motors  .

Better this way than never ;D

On the same day after testing the Twiglet, I had a situation with my moblite. After a crash, VTX stopped working and I couldn't find it for a while. I decided to take a risk, turned on the "flip over after crash" mode, and did a quick roll. Then disarm, arm in air mode, and then a short throttle boost. About 10 meters from me I saw my moblite happily jumping out of the grass. I was lucky, if it wasn't a whoop I probably wouldn't have tried.

So I need the buzzer sooner rather than later

When using turtle mode (flip over after crash), sometimes a prop is blocked and this could cause the ESC to draw large amounts of current. Often for 1S whoop boards with smaller sized 5A fets, there is the possibility to damage an ESC, so some people are more cautious turtling in grass. However for micros that have 12a ESCs and in your case the 20A ESC, turtle mode should be no problem even if prop is blocked (but probably still a good idea to apply throttle in short bursts). I turtle in grass all the time with my micros. I turtle my 1S whoops too, but have blown maybe one or two ESCs.

If you flip on turtle and just flick a direction you should hear the motors spin up. So walk in that direction. Then repeat and keep moving towards it until you find it. That's what i do when I can't turtle out of a situation for some reason (stuck in a bush). Even with a beeper it can still be a pain to find a downed quad. I find the noise from a turtle flick is more than a beeper and much higher pitched. But it is pretty easy to lose 2.5" and smaller quads. My longest search was after the failsafe the other month. That included an ejected battery and it took maybe 10-15 mins to find it, but I knew from the DVR roughly where it was and what i hadn't taken into account was forward momentum. When it failsafed it didn't stop dead in the air and fall down, it kept moving forward while tumbling down, so when i walked another 10-15m further I found it pretty quickly. The battery was a bit further away.