Okay, I didn't know that. Thanks for the info!

After a bit of a delay I have finally started building my quad!  I have discovered two things:

1. I am horrible at soldering
2. I have no idea what I am doing

I have currently put the base of the Martian II frame together, connected my Betaflight F3 FC to the PDB, and connected my Racestar RS30A ESC's and my FrSKY XM+ receiver to the FC.

In the end I decided to buy all the FPV parts before I fly it anyway, to avoid having to take apart the quad and solder additional wires to the FC at a later time.  This is where I think I have made my first major mistake.  I purchased the following:

Goggles: Eachine VR D2 Pro
Camera: Runcam Eagle 4:3
FPV Antenna: Emax Pagoda 2
VTX: Diatone SP3 5.8G 46CH OSD 0/25/200/600MW

Looking at connecting my VTX to the FC next, and I have read that it was a stupid idea to buy a VTX with OSD when my FC already has OSD?  Is this correct?  I probably should have done more research first.  If this is the case can I still wire it up so it will work bypassing one of the OSD's or will I have to buy another VTX and save my Diatone SP3 for a future build?  Here is what I am thinking:



I am really unsure about the RX and TX cables though.  Can anyone offer any advice on this setup?  Reading somewhere they mentinoed to run this setup I would somehow need to disable the OSD on the VTX and run it through the Betaflight F3 FC somehow...

Thanks!

I'm not very familiar with your vtx you're working with but I'm thinking you'll need to connect the tx/rx from the vtx to a free UART port on the flight controller (I'm sure someone will correct me if I'm wrong). I found this video regarding your vtx and he explains it for a few different FC's .

It's okay, you can ignore the OSD on the VTX and just use the OSD on the FC (which is better IMO)
You don't need to connect RX/TX to the VTX if you are not using the VTX's OSD

The rest of the connection looks fine to me.

(27-Jul-2017, 04:57 PM)Oscar Wrote: It's okay, you can ignore the OSD on the VTX and just use the OSD on the FC (which is better IMO)
You don't need to connect RX/TX to the VTX if you are not using the VTX's OSD

The rest of the connection looks fine to me.

Probably a stupid question, but which cable is sending the OSD data from the FC to the VTX?  If I connect it as per my diagram without any other wires, isn't it like the following:

Yellow wire = Sending video from camera to VTX so it can be transmitted to my goggles
Red wire (Camera to VTX) = Powering the camera
Black wire (Camera to VTX) = Grounding the camera
Red wire (FC to VTX) = Powering the VTX
Black wire (FC to VTX) = Grounding the VTX

Which of the connections on the left side of the VTX do I need to use to get the OSD data from the FC to display on my goggles?

(28-Jul-2017, 01:57 AM)Ritzyy Wrote: Probably a stupid question, but which cable is sending the OSD data from the FC to the VTX?  If I connect it as per my diagram without any other wires, isn't it like the following:

Yellow wire = Sending video from camera to VTX so it can be transmitted to my goggles
Red wire (Camera to VTX) = Powering the camera
Black wire (Camera to VTX) = Grounding the camera
Red wire (FC to VTX) = Powering the VTX
Black wire (FC to VTX) = Grounding the VTX

Which of the connections on the left side of the VTX do I need to use to get the OSD data from the FC to display on my goggles?

You will need to run video out from camera to VIN pin on FC then VOUT pin to video in on VTX.

(28-Jul-2017, 02:26 AM)Snuffypot11 Wrote: You will need to run video out from camera to VIN pin on FC then VOUT pin to video in on VTX.

Thanks mate, that makes sense.  Is this what you mean:

That's it!
I'm not familiar with that VTX, but I assume what you will see is 2x OSD's, you will need to find a way to turn off/disable the VTX OSD.

Hmm.. ok, I'll wire it up and see how I go. Thanks!

Hey Ritzyy,

It just so happens I have this same VTX in my latest quad. While you don't need both it's kind of a personal preference which OSD you go with. Personally I liked the idea that my OSD was built into the VTX rather than sending a signal to my camera, plus I went this route on purpose because it would be harder to build (and it was, and that made it more fun).

If you change your mind and decide that you do want to use the OSD on the VTX then your connections to the UART are wrong. TX goes to RX and RX goes to TX. Otherwise you're good based on what I can see.

From what I can tell if you want to disable OSD on the SP3 you have to hook it up and edit away all the elements. I haven't configured my OSD on mine yet though.

Good luck with it!

(28-Jul-2017, 01:57 AM)Ritzyy Wrote: Which of the connections on the left side of the VTX do I need to use to get the OSD data from the FC to display on my goggles?

OSD data is overlayed on the image from camera. 
If you enable OSD feature in Betaflight, the OSD data will be added to the image and sent out via the Vout pin.

Thanks all! I have wired it up to use the OSD from the FC for now..

I have finally got to the point when I want to plug it in to the computer to configure betaflight but now it won't connect? I downloaded the ImpulseRC Driver Fixer but it just sits there "Searching for flight controller". When I open the Betaflight chrome app it comes up with "Failed to open serial port" and only gives me the "Manual Selection" option in the top right corner.

Any advice?

If it helps, I have Windows 10. I have tried zadig aswell to no avail.

In my experience with it, going to device manager and click view hidden will show you all ports or items connected. You should be able to see which port it's connected to and not functioning at that point. I delete that port including software then disconnect and reconnect your FC. It should show back up as a new com port or similar usb port then you can run zadig or the impulse rc tool to correct the driver for that port. It's sometimes quite a bit of trial and error but there is plenty of other forum posts and videos out there for the vast majority of FC's out there.

(30-Jul-2017, 12:14 PM)Ritzyy Wrote: Thanks all!  I have wired it up to use the OSD from the FC for now..

I have finally got to the point when I want to plug it in to the computer to configure betaflight but now it won't connect? I downloaded the ImpulseRC Driver Fixer but it just sits there "Searching for flight controller".  When I open the Betaflight chrome app it comes up with "Failed to open serial port" and only gives me the "Manual Selection" option in the top right corner.

Any advice?

If it helps, I have Windows 10.  I have tried zadig aswell to no avail.

Has it worked before? What version is your configurator?
Have you tried restarting your computer?
If nothing works, please try to do a firmware flash?

EDIT: FIXED!!! Fairly embarrassing.. but it was just the cable I was using wasn't good enough or something.  The lights on the quad would come on with the old cable but I couldn't connect to betaflight.  As soon as I tried it with a new cable it has worked!

Thanks guys.  Nah it hasn't worked before (I haven't tried connecting it before).  I think it is because I have a new computer which doesn't have the hardware for "Ports (COM & LTP)" in device manager.  Even when I click view hidden it does not appear.  I have to go through Action -> Add Legacy Hardware.  I can get the Ports (COM & LTP) to appear this way but it just sits there with a COM port with a small yellow triangle.

Betaflight Configurator version 3.1.3 and yes I have restarted my computer multiple times.

Reading on other forums one of the readers has come across a similar problem and seems to have concluded that some new computers simply don't have the required hardware.  For the record I have a Dell XPS 15 9560 laptop which is new this year so this may be part of the issue.  When I return home in 1.5 weeks I will remember to bring an older laptop with me to see if that works before I try and firmware flash etc.