I have done some research..too many hours to count.

Problem is I have no idea what all the symbols mean on flight controllers,and what uart they correspond to in beta flight.

This is the pic I used to wire up my caddx...Its also the same FC as mine.Kakute v1.5

I just need to figure out what uart # I would choose in beta flight.

uart #6 is being used by my radio....

Second pic how he wired it..first pic is manual....He did not wire his correctly for the fc to talk to the vtx/..or maybe he did?...Why is he using rssi??..I dont really need osd but it may be useful?

Generally, every UART on your flight controller will have an Rx and TX pair and their numbering on the FC will correspond to what you see in the BetaFlight ports tab.

So all you need is a spare uart to connect the RX/TX of your vista unit to. Then configure MSP on that uart in Betaflight.

Now for a vista unit you should not exceed 6s voltage as a matter of fact most prefer to stay around 4s which is why you see a voltage regulator in that voltage stepped down to a safe level for the DJI or Vista unit. The Kakute F7 in that image does not have an onboard 9V or 10V voltage regulator which is why you have to do this.

(06-Aug-2021, 06:54 AM)kafie1980 Wrote: Generally, every UART on your flight controller will have an Rx and TX pair and their numbering on the FC will correspond to what you see in the BetaFlight ports tab.

So all you need is a spare uart to connect the RX/TX of your vista unit to. Then configure MSP on that uart in Betaflight.

Now for a vista unit you should not exceed 6s voltage as a matter of fact most prefer to stay around 4s which is why you see a voltage regulator in that voltage stepped down to a safe level for the DJI or Vista unit. The Kakute F7 in that image does not have an onboard 9V or 10V voltage regulator which is why you have to do this.

Thanks for reply..I have dedicated micro 12 volt reg from rotorgeeks.

But my question is oscar liang wired up the video transmitter incorrectly...see pic...

(06-Aug-2021, 12:57 PM)whatever Wrote: But my question is oscar liang wired up the video transmitter incorrectly...see pic...

Oscar's wiring diagram is correct for wiring an Air Unit / Vista to an FC. What do you believe is wrong with the wiring diagram?

(06-Aug-2021, 01:23 PM)SnowLeopardFPV Wrote: Oscar's wiring diagram is correct for wiring an Air Unit / Vista to an FC. What do you believe is wrong with the wiring diagram?

If you say its correct then my question is answered.

For some reason I thought it was wrong because I get no bat voltage in my dji fpv goggles.

(06-Aug-2021, 01:48 PM)whatever Wrote: For some reason I thought it was wrong because I get no bat voltage in my dji fpv goggles.

Have you switched the "Custom OSD" option on in your DJI FPV Goggles? And do you have MSP enabled on the correct UART? If you believe you have done both of those correctly then it might be worth you running both the "dump" and "diff all" commands in the Betaflight Configurator CLI tab and copy/pasting the results back here for us to check, along with some good clear photos of the actual wiring and connections between your Air Unit / Vista and the flight controller.

I dont know what is the proper uart for the osd.It should be uart 1..but when switching that on ...save reboot it turns offf all uarts indicaring its not correct

uart6 is switched on for my rx though.That works fine.

(06-Aug-2021, 02:25 PM)whatever Wrote: I dont know what is the proper uart for the osd.

uart is switched on for my rx though.

What pads do you have the grey and white wires from the Air Unit connected to on your FC?

We really need to see a CLI "diff all" and "dump" so we can also check for any configuration setting conflicts that you might have accidentally applied.

(06-Aug-2021, 02:28 PM)SnowLeopardFPV Wrote: What pads do you have the grey and white wires from the Air Unit connected to on your FC?

We really need to see a CLI "diff all" and "dump" so we can also check for any configuration setting conflicts that you might have accidentally applied.

---

message too long

If you have it wired like the diagram in your first post, with the white and grey wires going to R1 / T1, and you radio is on uArt 6 then your Ports Tab in BetaFlight should look like this:



'MSP' should be turned on for uArt1, and "Serial RX" should be turned on for uArt 6.

Then click SAVE at bottom right.

Then in your goggles menu, turn on 'CUSTOM OSD".

Then you can go into 'OSD' Tab in BetaFlight and turn on "Average Voltage Per Cell", or however you like to view your bat. voltage.  I use avg per cell, because it is easy to glace at and know when I need to land.

EDIT: I don't know why that pic is showing up so small. Here is a link to it full-sized: https://ibb.co/1vz5S3g

EDIT 2 : if that isn't working for whatever reason, you can choose any other available uArt you want, as long as they are both on the same #. (IE: T4/R4) Then just turn off MSP for uArt 1, and turn it on for whatever uart # you choose.

Thats exactly what i did......but after save and reboot all uarts are turned off.

Do you mean the uArts are completely gone from that page, or they are just no longer selected.

If they have completely disappeared then the FC has probably been flashed with the wrong target firmware.

If they are still there, but they are no longer selected I think it might do that if you try to have multiple columns enabled for the same uArt. Such as trying to enable 'MSP' for a uArt as well as having something selected under "Peripherals"

There should only be 3 things enabled on Ports tap. "USB VCP" and "UART1" enabled under "Configuration / MSP", and "uArt 6" should be enabled under the column "Serial RX". EVERYTHING else needs to be off. You cannot have 2 items selected for the same row. If you try to enable multiple things I think betaflight will reset the ports tab because it can see there is a problem.

If you have that all correct and it is still resetting everything upon saving then I would probably try re-flashing the firmware to make sure that is correct. The firmware target for that board is called "KAKUTEF7"

(06-Aug-2021, 06:10 PM)whatever Wrote: message too long

If you are trying to use the mobile view to post your CLI dump then scroll to the bottom of the page and click on the "Switch to Full Version" link. Then post the test using the method described in the following link...

https://intofpv.com/t-putting-dump-files-inside-code

I forgot to add: Make sure the wires are soldered to the right pads on the flight controller. Often the labeling on the flight controller doesn't exactly line up with the pad.

I just noticed in your first post you asked why Oscar has it wired to RSSI.(in the second pic) He doesn't. RSSI is the pad in between R1 (where he has grey wire) and Ground, where he has black wire.

The letters aren't precisely lined up with the pads, because it is hard to have room to write it. It can be helpful to count down the number of pads you need.

Another issue just started....If I make any changes...I mean any then the quad will not recognize radio.

I need to reset and reload cli then radio inputs are seen and i can arm.

So any changes made..save restart..then radio does not work.....

P.S my wiring is 100% correct as r/multicopter said it is.

I would like to know if its safe to fly stock settings...air mode is enabled,that should not be a problem.

Failsafe works..radio off motors stop.Thats good.

Only thing i wont have is osd...I can do without that.

Any reasons not to fly with stock without making any changes?