215 Hopper – Build 2


I have been a bit slow in getting this report together but I am pleased to say the as of late last sunday evening my second build of the 215 hopper design is airborne. For anyone keeping track that is just a 6 day turnaround from lost to flying again. There are a couple of things that worked in my favour to achieve this.

  1. Firstly the 3D printer from the workshop of SteelCity Electronics is currently on holiday to my workbench, as such I was able to start printing replacement parts immediately (more on this topic in the near future, I’ve got a big build cooking).
  2. The guys over at NextFPV actually had stock of every replacement part I needed. I expected I would need to order various bits from multiple sources internationally but discovering everything was stocked locally was a pleasant surprise. On top of that the service they offer is exceptionally fast. I am a very happy repeat customer of theirs. I the future I will gladly purchase through them whenever possible (hopefully there is an FPV setup in my future).
  3. When ordering parts for the first build I doubled (or more) quantities of the various bits of hardware so all of that was on hand. The PCBs were taken care of as DirtyPCB’s supply 10 per order by default.

With the rebuild I got the chance to address a few of the shortfalls of the first build. Changes included:

  • Shortening ESC signal/ground wires so that there was less wire bulk in the body. it was a bit challenging squeezing everything in to the first build.
  • Direct connection of motors to ESC’s. On the first build I needed to join the motor wires with the ESC wires as the motor wires were cut to short from the Spidex 220 build. In reality this is still not a very practical solution as the wires first need to be passed through the side plates. However for the sake of minimalism I stuck with it.
  • Externally accessible USB. This is the most valuable change from the first build and is thanks mostly to the change in location of the port on the Naze32 Rev. 6 board. I also printed a unique side plate with an opening to suit.215H2-3
  • The upgrade to the Nae32 Rev. 6 also allowed for very tidy connections all around (no more soldering wires directly to the board). Seen in the photo below is the way I have installed the pin headers on the Naze32. 90° headers are used on all connections. The ESC outputs are installed in a fairly typical configuration. The RC input connections are under and towards the centre of the board and the extra features (Vbatt, buzz etc.) are directed back across the board.215H2-4
  • SmartPort telemetry. Rather than trying to fit a buzzer inside (which becomes surprisingly large in such a small space) I connected the SmartPort on the X4R-SB to a soft serial port on the Naze32. A buzzer will fit inside but for now I am relying on the telemetry to know the status of my battery. The photo below shows how tidy this setup is. Also note that for clearance to the ESC connections on the Naze32 I have to trim the top row of headers from the X4R-SB.215H2-1

The only quirk with this build, and I find it strange given that it is newer hardware, is that LuxFloat can’t run reliably ( I had no problems with it on Rev. 5 hardware). It may in fact be the extra processing load from the soft serial so I will have to check into that further.

Next on my agenda for this copter is to get the GoPro mount(s) sorted. Then put together a more thorough look at the design and build process with a full bill of materials and files if you would like to build you own.

Given that the design of the 215 Hopper was inspired by the FliteTest VersaCopter I thought a family photo was a fitting way to end this post.


VersaCopter Motor Mounts

Through the cumulative effect of multiple crashes and initially over tightening I managed to snap one of the G4 plates that make up the motor mount tube clamps on the Flite Test VersaCopter. Unfortunately at the time I ordered the crash kit for the VersaCopter it didn’t twig that these plates were sold separately. As such I was faced with either making a very small order with Flite Test for replacements or coming up with my own solution.

I took this as an opportunity to test my tube clamp motor mounting method and the folks over at 3dprint-au.com both of which are critical elements of the MultiChase project. I knocked up a very quick model of a direct replacement part for the Flite Test designed tube clamps and sent it off for printing. 3Dprint-AU use an SLS printer which I hope will provide better dimensional accuracy and a more homogeneous structure than a FDM style printer.


The results are not as spot on as I expected but I generally found the parts are oversize rather than undersized. For example the bottom edge of the clamp, as shown above on the right, is raised rather than rounded as designed. A quick touch up with sandpaper (applied only to the motor side) brought the overall measured height down to the designed number. Also interesting to note here is that the ‘black’ material offered is actually just the white material dyed black on the outside. I’m not sure of the specifics of this process, if it is done by the print head or if it is done as a post process but it is something to bear in mind.


To ensure a nice clean holes for the mounting bolts I actually printed the hole under size and drilled them out as appropriate, they are shown here as printed.


The installation process was simpler than the flight test motor mounts as there are less pieces to hold together. I also think it looks cleaner than the original pieces.


Strength wise I have no doubt that this well be less susceptible to the same style of failure as the original design. Everything is nice and snug with no visible deflection when tightening. That does however raise some concerns about the next failure. My mounts fit much more tightly around the tube and seem much less inclined to rotate as the originals would in a crash. This could make the frame itself or the arm tubes more vulnerable. Despite the much bulkier appearance these mounts only add 1.7g per corner. Each printed half weighs 4g for a total of 8g per corner whereas the Flit Test design weighs in at 6.3g per corner.

Now it’s time to get this rig back in the air, it has been several weeks since I broke flew it last.

VersaCopter & Spidex 220 Rebuilt

After receiving my crash kits for the VersaCopter I have rebuilt it without any further drama. The only change made on the rebuild was to flip the orientation of the capacitors across the power input on the two ESC’s adjacent to the flight controller. They now rest back over the top of the ESC rather than poking out along the wires. As previously mentioned they were causing interference problems with the USB connector and various other connections on the flight controller. No such problems exist now.

Also rebuilt over the weekend was the Spidex 220, when I last flew that I took off aggressively thinking it was in angle mode when in fact it was in rate mode. Needless to say the quad flipped on its head and smashed in to the ground. Thankfully nothing beyond the propellers was actually broken but the force of the crash was enough to pull it to pieces so I thought a full workbench rebuild was a wise choice to ensure there wasn’t any hidden damage.

Now having them both built I could get a photo of them together for a size comparison.


I also tried to get a buzzer working on the CC3D mini in the Spidex 220 whilst it was on the bench again but so far have not had success. The best way I have seen to achieve this is to move the buzzer output to motor channel 6 with a custom build of Cleanflight and a transistor to switch the buzzer. After having put everything in place as required it doesn’t work but I am unsure at the moment which piece of the puzzle is at fault. More investigation will be required. For now an external battery monitor on my new higher discharge rate batteries will suffice.


VersaCopter – Crash Kit Required

Up until now I had managed to avoid inflicting any serious damage on the VersaCopter despite a couple of unexpected visits to the ground. The first time it came down was when I clipped a post, judging depth and plotting a course is tough when flying around obstacles! From that a couple of small cracks developed in the side plates but everything could still be straightened and flown again.
The second crash came when I fumbled the sticks whilst a couple of meters from the ground and couldn’t recover. Again, straighten out the alignment, replace broken props and it was back in the air. This illustrates the strength of the clamp-on-tube ethos. Allowing mounts to rotate certainly takes energy out of the crashes and also reduces the chance of motor damage.

This crash was more severe. Essentially I ran out of talent, I was pushing limits further than I had previously and at the time I crashed I was flying high speed figure 8 circuits In very close proximity to the ground, less than 1m AGL for the most part. Upon rolling left to execute a turn I dipped the front motor to low and it caught the ground. The VersaCopter then proceed to tumble along on its side bouncing of the end of each boom for 4-5m.

The first photo below illustrates what I was greeted with when I went to collect it. Everything was still together but evidently some more serious damage had occurred.  The front boom was at an odd angle and the rear boom had shifted significantly. The motors had rotated to all sorts of interesting angles.

Closer inspection revealed that all of the vertical plates around the front tube were broken and the displaced boom had bent the side plate in.

VC-6 VC-7

Similar damage also happen to the rear end during the tumbling however everything stayed in essentially the right place. All of the vertical Delrin plates will need replacing to get this back in the air.


Spread out on the table the this is what the damage looks like. Unsurprisingly the cracks all occurred at very thin sections of the frame.


Thankfully, in anticipation of just such a circumstance I ordered a couple of crash kits several days ago so soon enough I will have the replacement Delrin parts to get it back in the air. I’m also interested to see what the Flite Test crew comes up with for the ‘stronger upgrades’ they are working on.

Flite Test VersaCopter

I’ve been on the lookout for a small quadcopter kit to put together for some time with an ultimate interest in getting in to FPV flying and racing. The high entry cost for a good quality full FPV setup has put me off a number of appealing options over the last 12-18 months such as the ImmersionRC Vortex. I have however finally pulled the trigger on the VersaCopter created by the crew over at Flite Test. This will allow me to put together a rig piece by piece and offers a compelling value proposition. A couple of days ago my kit arrived so over the weekend I have assembled and flow my VersaCopter.



Delivered from the Flite Test store (as shown above) was:


Delivered from the HobbyKing strore (as shown above) was:

The only missing piece from this shopping list to get off the ground is a radio receiver to suit, in my case, a Taranis X9D. I already had a couple of FrSky X4RSB‘s on hand from a previous order.


One of the reasons I was so eager to jump on this kit was the design style used. The slot together laser cut plates really appeals to my sensibilities and I was curious for a close up look at what laser cut Delrin looked like and offered structurally. I have used similar construction methods in the past for other projects but have always used acrylic (unfortunately Ponoko NZ, whom I usually use, do not offer a Derlin option).


Assembling the VersaCopter from the kit as shown above followed almost exactly as demonstrated in the Flite Test construction videos (both the main video and the NAZE 32 video) with the exclusion of any cameras or FPV equipment and the observations as follows:

  • When installing the motor mounts on to the arm I found it easiest to start only the bolt on the side opposite the slot. This allowed full freedom for the Delrin part to stretch over the tube before adding the 2nd bolt.
  • Aligning the motors on opposite ends of each arm proved more challenging than ensuring the front and rear motors were aligned. I didn’t come up with any clever solution to this beyond align, tighten, check, repeat.
  • The supplied ESC’s seemed to include a much larger input smoothing capacitor which made their length significantly longer. This provided two problems for the installation of the NAZE 32:
    • The wires and capacitor interfere with access to the USB port through the side window.
    • The length meant it was particularly tight trying to fit the ESC between the NAZE and the rear arm, consequently the ESC is in constant contact with the edge of the NAZE board somewhat nullifying the foam isolation mounting of the flight controller.

    Ultimately the compromise was to push the ESC as far back as possible and hold the input wires down as best as possible with an extra cable tie.

  • With about 4-5mm of foam under the NAZE 32 there is not sufficient vertical space within the frame for vertical connectors. This impacts the telemetry, vBatt, buzz and serial ports. Directly wiring JST tails to those I wish to use will be required.
  • As I am using the SBus output from the receiver I had to set serial port 2 on the NAZE 32 to serialRX. I overlooked this detail and spent some time trying to figure out why I was not receiving a signal.
  • I was not happy with how secure the battery felt with just the velcro strap as such I added some Velcro dots to the top of the frame and bottom of the batteries for extra security.

Ultimately the kit went together very well and they have certainly delivered on their aim of putting together a DIY kit that looks professional and tidy when completed.



After running through 6 batteries I can say that I am very happy with the VersaCopter and it delivers all that I had hoped. Specifically a no nonsense quad with decent flying performance, i.e. something that will allow me to practice flying with minimum fuss.

The VersaCopter was stable without making any changes to the PID tuning however for better performance I have made a few initial tweaks. The following settings have changed:

PID Controller: 2 – LuxFloat (all default PID values)
Roll rate: 0.05
Pitch rate: 0.05
Yaw rate: 0.17

On the transmitter I have set:

Roll +25 exponential (faster closer to centre)
Yaw -35 exponential (slower closer to centre)

With this setup flight times of between 7.5 – 8 minutes are easily possible with relatively energetic flying (constantly on the move, regularly at full throttle, flying square or figure 8 circuits) and approximately 10-15% left in the battery.

So far I can not report on the durability of the frame, I haven’t crashed it yet.

MultiChase Project

As a foot note there are a couple of lessons to be taken from this build for my MultiChase project.
Wiring, routing and position of electronics needs to be very serious consideration, wires are not as flexible as imagined in close quarters and all connectors and wire volume needs to be accounted for. I already knew this but this project served to reinforce that knowledge
With a 6″ propellor the difference between a 250mm and 280mm motor centre is probably fairly minor.
The laser cut plates method of construction proved very simple to put together and supported by the fibreglass plates provides a very strong frame, it is probably worth reconsidering for as an option.
Delrin looks to be a great material in this laser cut form, tough but still somewhat flexible. I will however continue with my 3D printing approach for now as that is easily available to me.