Hi all, first time postie so my apologies for any etiquette errors.

I have been on forums and looked at info to try and turn a bunch of parts that i bought into a moving flying machine but so far have only managed to fry 3 naze32 FC's. But each time I'm learning a little (the expensive way).

I basically wanted to assemble a drone which pretty much covered all the elements of different flight modes and telemetry. Rather than think of this as a racing drone I wanted to use it as a learning tool for me and my kids to have some fun with.

At this point I feel its time to call in the help, support and knowledge of the great and good. So If anyone can have a look at my wiring diagram i would be so so so grateful for any and all help that turns the bag of bits into a working model.

I've attached a wiring diagram that I think is a good starting point. 
For clarity. I haven't shown the ESC to PDB connections and also the ESC to motor connections.

The parts I have for my "Drone Number1" are:

Turnigy 9XR Pro with XJT module transmitter
ZMR250 carbon frame 
Realacc HUBOSD power distribution board PDB w/ OSD 
Naze32 rev 6 FULL
Little Bee 20A ESC with BLHeli_S, OneShot125 and Damped Light (2-4S) 
EMAX RS2205 motors
1000 TVL camera
Frskr X8R 
NZ GPS module 
TS5828S 40ch 600mw

Thank you, 
Jason

   

i don't think you can share RC4 between SBUS and GPS.
Maybe just drop the GPS, it's not that necessary in a mini quad. It only makes your build more complicated.

Hi Oscar, thanks for your reply.

I wanted to include GPS to allow this to be used as a learning tool. If it significantly over complicated things I could include it after but either way at some point I would like it to be included.

Thank you for your feedback.
Jason

You can't wire two things in parallel to the same serial port. That simply won't work. To connect your GPS, you'll need to enable SOFT_SERIAL and use software serial port 2 on pins 7 & 8.

The only current firmware that supports GPS functionality like position hold and return to home on underpowered flight controllers like the Naze32 is iNav. They have an excellent Wiki which will tell you about some of the limitations you will have to accept to use an old flight controller: https://github.com/iNavFlight/inav/wiki/...-with-iNav

The biggest problem you might face is getting good data from the compass that is built in to your Naze32. If the flight controller is mounted above the PDB like it probably has to be with the frame you have chosen, the magnetic interference from the high currents flowing in the PDB may make the compass readings completely unreliable. You can't use a GPS on a multirotor craft without an accurate compass.

You'll also need to make sure that you cover the barometer on the board with some foam and black tape to exclude both prop wash and light from the barometer.

If you want to use Smart Port telemetry from your X8R, you'll face another problem.

The only UART that will be left is soft serial port 1. Smart Port runs at 57,600 baud and both software serial ports must run at the same speed. The GPS is probably configured to run at 9,600 baud, so you'd need to reprogram the GPS to run at the higher speed.

The problem with that is that software serial ports require a lot of time from the CPU as they don't have the hardware needed to handle the port without the CPU doing all the work. Running two software serial ports at 57,600 baud on an old F1 CPU may not work reliably.

Hi Unseen

It does like like GPS is a no-no and an over-complication too far. I will remove it from my initial build.
I'm was not too concerned about the accuracy of telemetry for this build at the moment as its just for development and learning.

Re Point taken what you say makes sense about baud rate and wiring two things in parallel to the same serial port. I see the information that i found suggesting this was in relation to a REV5 Naze32. I came across it in several other forum links as well. It did seem odd !
http://www.eurny-rc.fr/wp-content/upload...agram1.jpg

Excellent idea re the foam for the barometer.

I'll update the wiring diagram and repost in a mo.

thank you for your help.

If I were you I would probably take it one step at a time, focus on building a quad that "flies", learn how to tune the quad in the basic level... once you get confident at flying then start worry about other stuff

Whether or not using GPS, F1 flight controller is getting too slow and limiting for the latest FC software... including iNav and Betaflight. I recommend looking into getting a F4 FC as an upgrade in the future. But the Naze32 should be enough for now as a learning platform.

Hi Oscar,

Can you recommend an F4. My quick research has found references to Holybro Kakute F4 AIO being kind to FRSKY users and also the DYS F4 Pro (no usb port?) seems to be popular.

Is there a beta flight option you would recommend?

Also, is it worth going integrated OSD / PDB ? Integrated OSD / PDB makes everything look so much neater, tidier and less complicated.

Thanks for your insight.

The DYS F4 pro does have a microUSB port.

I just received these today:



Matek have really improved the quality and design of their products recently and this pair of boards provides an F4 processor, 32KHz capable gyro, microSD card for black box logging, ribbon cable connection to the PDB to keep vibration at a minimum, 180A capable current sensor, 500mW VTX controlled through Betaflight, integrated OSD, MMCX antenna connector and lots of hardware UARTs.

It's a great package for the price and I'm going to be using them to replace the BrainFPV flight controller that I have on my Armattan Chameleon. Despite my best efforts, I can't get rid of the really disturbing diagonal lines that the BrainFPV introduces on my FPV picture and therefore it's time to try some other hardware.

(07-Nov-2017, 05:58 PM)unseen Wrote: I just received these today:



Matek have really improved the quality and design of their products recently and this pair of boards provides an F4 processor, 32KHz capable gyro, microSD card for black box logging, ribbon cable connection to the PDB to keep vibration at a minimum, 180A capable current sensor, 500mW VTX controlled through Betaflight, integrated OSD, MMCX antenna connector and lots of hardware UARTs.

It's a great package for the price and I'm going to be using them to replace the BrainFPV flight controller that I have on my Armattan Chameleon. Despite my best efforts, I can't get rid of the really disturbing diagonal lines that the BrainFPV introduces on my FPV picture and therefore it's time to try some other hardware.

Oh no, I don't those will work very well for your application at all, you should just send them to me for disposal

I posted yesterday but for some reason it did not go through. Anyway, everyone already gave you some the advice I wrote.

F1 FC is too dated. Go with F3 or F4 as everyone already suggested. No need for PDB if you are going with AIO FC like the Matek.

As for the TX, if you are considering Turnigy 9XR Pro with module, I suggest you get the Taranis QX7 instead. Pretty much the same price when you add everything up. Turnigy works well and can run Ersky and OpenTX. But if you want to upgrade gimbals, there isn't an option.

X8R is a very large RX. I suggest XSR, XSRM or X4RSB for mini-quad if you want telemetry. XM and XM+ if you don't care for telemetry.

Your bare board camera will be difficult to mount, unless you have 3D printer and can make parts. I suggest a Runcam or Foxeer that has case and mounting hardware to make your life easier.

ESC, you can get ESC that is DSHOT ready for the same price. Why bother trying to take off filter cap later if you all of a sudden want to try DSHOT.

My two cents.

(07-Nov-2017, 06:35 PM)RENOV8R Wrote: Oh no, I don't those will work very well for your application at all, you should just send them to me for disposal

(07-Nov-2017, 08:03 PM)voodoo614 Wrote: I posted yesterday but for some reason it did not go through.  Anyway, everyone already gave you some the advice I wrote.

F1 FC is too dated.  Go with F3 or F4 as everyone already suggested.  No need for PDB if you are going with AIO FC like the Matek.

As for the TX, if you are considering Turnigy 9XR Pro with module, I suggest you get the Taranis QX7 instead.  Pretty much the same price when you add everything up.  Turnigy works well and can run Ersky and OpenTX.  But if you want to upgrade gimbals, there isn't an option.

X8R is a very large RX.  I suggest XSR, XSRM or X4RSB for mini-quad if you want telemetry.  XM and XM+ if you don't care for telemetry.

Your bare board camera will be difficult to mount, unless you have 3D printer and can make parts.  I suggest a Runcam or Foxeer that has case and mounting hardware to make your life easier.

ESC, you can get ESC that is DSHOT ready for the same price.  Why bother trying to take off filter cap later if you all of a sudden want to try DSHOT.

My two cents.

Good advice, but from what I read in Jason's first post, he has already bought the listed parts.

Jason, there is no need to replace any of the things you have bought. If you want a more autonomous craft which can fly by itself, you should look at iNav. If you want a quad that's more for freestyle or racing, drop the GPS and look at older releases of Cleanflight, like 1.12. Both of these run with your hardware and have been used to build great quads.

Oh... Missed that point.