Hello FliteTesters!
I watched Josh and Eric's Naze32 video and I was very intrigued by his angled-arm design. I almost exclusively fly the Naze, so I all but ignored most of the config and tutorial, and instead focused on his miniquad. I had to have one! I ordered the kit right away, and made sure my stash of spare parts was ready for the hit. Problem was, there were no articles or any details on Eric's build aside from the Naze setup, and apparently nobody else has tried the angled approach yet. So here we are, I guess the burden falls to me! lol

As soon as everything arrived, I started to dig in. That's a Naze32 Acro in a 3D printed case, DYS 1806 2300kv motors, 12A Afro ESC's (obviously lol), and the FliteTest parts.
Step one, cut the arms

I went with 96mm arm segments based on photos of Eric's machine. From the "bend" outward, the arms extend far enough past the bracket to accomodate motor mounts, and that's about it. As you'll see later, I end up changing my mind about having the segments equal length.
Once the mounting screw holes were marked and drilled, it was time to attach the new angle brackets. Problem was, I knew the 1806 motors weren't going to be able to handle a ton of weight, and it looks like Eric used 2204's or 2206's, so I was already at a power disadvantage. Although FliteTest typically frowns upon it, I went for glue over screws. In a good crash these brackets are likely going to be the first part to break anyway, so what difference does it make if they're glued! Besides, upon some zoomed in inspection, it looks like Eric ditched screws too!


Next step, slap on some motors.

However, I ran into an issue. My first thought was to use the standard FliteTest motor mount discs like Eric and many of us have used and love. But, fun fact: while M3x20mm screws are very easy to come by, M2x20mm are nearly impossible to find near me. I sourced them on Amazon and they were ridiculous... in the area of $7 for 8. Forget that. Time to fire up the 3D printer!
A buddy of mine and I came up with this

2.5mm thick, 24mm diameter with a 5mm hole in the middle, and 2 2.5mm holes that are 16mm apart center to center. On the ends are 12mm wide, 5mm long protrustions with a little nub on the tips. As you can see, they fit like they were made for the 1806 motors. Go figure! (PS, I have the 3D file available for anyone who wants it. As soon as we get an account created, my buddy and I are going to stick it up on thingiverse too)

As you can see, I used the button head screws that came with the motor, rather than countersunk flush mount screws. I did this so the screw heads would grip tightly to the wood beam and prevent side to side wiggle. With those screw heads protruding and 2 40lb zip ties, these motors aren't going ANYWHERE!




Now that the arms are built, time to do some soldering on the Electrohub plate and get the basic assembly screwed together.


It was at this point that I paused, leaned back and said, dang, this thing is way bigger than I thought it'd be. I sat a ZMR250 frame on top, and it was totally dwarfed.

Then I did the same thing with a T4 250mm mini that we just scraped off the bed of the 3D printer, and it felt equally tiny.

Bottom line is, it's too big. This isn't a mini race quad, this a mid size copter with teeny motors. So, let's blow it apart and break out the saw again!
I decided to lop off 42mm from the inside segment, which brought the beam right up to the edge of the bracket.

Once the mount holes were re-drilled, and everything was reassembled, it was much more reasonable size.


As it sits now, the shaft to shaft diameter is in the neighborhood of 320mm. Not exactly a "mini racer", but who's judging lol!
Upon futher zoomed-in close up inspection of Eric's build, it looks like he took a similar approach. I can't tell if his inner segments are shorter than the outside, or if he just has the whole deal mounted further in, but his brackets are "inside" the Electrohub disc just like mine now are.

Now that the parts of what makes this build special are complete, I won't go through all the details of how to wire ESC's and motors, plug in a receiver or program the Naze32 board (THAT is what Josh and Eric's video was for in the first place!). The only thing that I will mention, however, is that I chose to stick to bullet connectors throughout vs hard soldering because of the "this thing is going to explode on impact" concept of these wooden quads. During a crash they're SUPPOSED to break apart and save your fancy electronics, and in that case, I want my electronics to disengage and fall apart rather than rip motor wires or tear off foil pads. It is far easier to plug in a few bullets and pull out another zip tie than it is to replace a whole ESC or motor. All that said, here's the colorful bits :-D


Non-FPV flight-ready with no battery, we're sitting pretty at 364 grams.

My "Eric Special" is built, the Naze is flashed and tuned and the Taranis is standing by. Now I just need some daylight when it isn't snowing to go play!!!

************Flight Review Time!!!*************
We FINALLY have good weather here in the Baltimore area. In fact, the sky couldn't be bluer, and it is 50 today! I took my little creation outside, it flew for about 10 seconds and crashed hard. I put the battery back on, flew for another 20 seconds, and I barely made it back in one piece. Quickly frustrated, I put this quad down and broke out the orange 250 shown above. It also barely took off and once again went top down onto a mountain of snow after freaking out and oscillating out of control. Ok, must not be me lol. Quick trip back home and I found some solutions.
First, there needed to be a better way to mount the battery on the bottom of the Electrohub. Since I'm flying a 1300mah 3S, there was no good spot to mount it so it'd stay in the center of CG and still be solidly retained. So, my miracle worker designer buddy made me this battery strap holder on his 3D printer, and it works like a champ! It'll hold anything from a 1000mah up to however big the velcro will go, and since it is a flat plate with doublestick 3M tape on the back, it can be mounted to anything... multirotors, foamies, the mailman, whatever!




PS, ignore the servo and rubber band down there... I may or may not have plans to drop some little green army men with parachutes ;-)
So, now that the battery problem is solved (for all future aircraft I build!), time to figure out why both quads went oscillation crazy, freaked out and ate snow. As it turns out, it was the PID controller I chose for my Naze32.
Back up a couple hours to the crashes: I'm running Cleanflight with firmware 1.7.2, and PID controller 1 (rewrite), because forums online said controller 1 was "better" than 0, the original (old) algorithm. In Angle mode, the quad is utterly unflyable. It oscillates wildly and unpredictably. Switch to Horizon mode, and it smooths right out, but does not autolevel. Switch to Acro, and it acts just like Horizon... smooth and stable, but no autolevel. I gained a little altitude, switched back to Angle and attempted an autotune sequence. The board tried to do its self tune, but instead punched the throttle by itself and darn near flew away, tick tocking back and forth the whole trip. I regained control by quickly turning off autotune, flicking into Acro, and coming home safely.
Fast forward back home: I switched the PID controller back to 0 like I've always flown before, went outside to the parking lot and all was well with the world! Angle acts like it should, Horizon is Angle plus flips/rolls, and Acro is all manual deliciousness. I clicked into Horizon, ran through an Autotune session, landed and locked it in.
Here are the default PID's right after flashing the board with the new firmware (ignore the controller 1, the PIDs didn't change when I switched back to 0):

And here is what we ended up with after it self tuned. Fairly dramatic, I must say:

Ok, so now that I have a good flash, a good baseline tune, time to go tear up some sky! I went back to the highschool parking lot where I started hours prior, and I have to say, this little angle arm is a dream to fly! My current config is a 3S 1300mah battery, 1806 motors and 5x3 2 blade props, and it hovers 2 or 3 clicks below 50% throttle. It has plenty of get up and go above mid stick, and does not hesitate to shoot upward when told. Next time out I'm going to experiment with 5x3x3, 5x4, and 6x4.5 props, as well as a 4S battery. I'm sure any of those changes will make this thing a total rocketship. As it stands right now though, it is certainly no slouch. This little machine with PIDs shown above will happily do single or even double flips in any direction (double flips drop about 50'-75' in altitude, so make sure you've got some height in your favor). It flys faster in a straight line than any other mini I've flown, likely because of the increased thrust from the rear blades, and it is sickeningly stable. No matter what I did to it, in any mode, it just said OK. Random gusts of wind had zero impact, and no matter what I tried, I could not get this thing to feel any worse than a feather floating calmly on a still pond. This is the first multirotor of any size that I've ever felt comfortable doing double flips, and the most comfortable I've ever felt flying in Acro/manual. Now all I need is to figure out the best placement and mounts for some FPV gear!!
Eric, you're a genius and you have a winner on your hands!
Here is a quick clip of me testing the craft out. Full disclosure: I can count on 2 hands how many times I've flown something this small, AND it was pretty windy above the trees. So, sorry about the wobbles lol. At least I didn't crash!!
0 comments