Team Blacksheep – Unify EVO VTX Anschlussplan / Wiringplan

I created this high resolution connection plan for the TBS Unify EVO

This connection plan will be constantly updated.
Please always link to the original image (4641px × 3705px, right click -> save as) so that the latest version is always displayed.

Click the image to enlarge
If you are looking for more wiring plans, go here

Hardware used in this wiringplan

Created by Philipp Seidel
Credits: Icons by rdy_fpv , Albert K and Me 😉

Wenn dir dieser Artikel gefallen hat und du mich unterstützen möchtest, findest du hier drei Möglichkeiten. DANKE!

Auf Patreon findest du auch weitere Infos zu meiner Person und dem Blog

paypal[ät]seidel-philipp.de

Print Friendly, PDF & Email

7 Antworten

  1. Erik LaPlant sagt:

    Hi Phil,

    Thank you for putting this wiring plan together. I’m new to the hobby and am trying to build my first quad. I am using similar components and wanted to know if there wold be anything different in the wiring setup when using the BrainFPV Radix FC, TBS crossfire nano rx, TBS Unify EVO, and the Runcam micro Eagle?

    Thanks again,

    Erik

  2. Christian sagt:

    Hallo Phillip
    Ich versuch de Tbs Evo mit kiss fc v2 zum laufen zu kriegen
    Ich hab rx tx von vtx an tx1 rx1 den flightcontroller gelötet aber kriege keine Daten bis auf die Spannung .
    Kannst du mir weiterhelfen?
    Gruß Chris

    • Phil sagt:

      Hi Chris,

      verwendest du auch die Firmware von Alexander Fedorov? Er hat hier eine Anleitung geschrieben, wie das ganze funktioniert!

      Hi Guys!

      I’ve been working a bit on some improvements for KISSFC, and want to share it with you if you open for some testing. Quite a lot of people buzzed me and already tested it quite well in some hard conditions. So i think its rather safe. Most people say it flies better, well,
      time will tell.

      Keep in mind, that its NOT YET OFFICIAL, and you are on your OWN RISK. Dont blame flyduino ok?

      Download:

      https://drive.google.com/drive/folders/1H9y5Z_mSsajCZN0ZdczPhQKbhxibkSEb

      Whats changed since RC39b (last public release)

      RC40i changes:

      – Added GPS support (yet telemetry/osd only)
      – Runcam pass through added (for SpeedyBee app)
      – GPS pass through (for uCenter connection)
      – Fixed BB gyro scaling and other compatibility issues
      – Add EVO crossfire parameters editor support (latest EVO required)
      – Added crossfire router (first fc that supports routing!)
      – Added turtle mode safety (works after at least one arming)
      – Changed lots in crossfire code
      – Changed RX processing code (should be more sensitive and direct)
      – Disabled StartAssist
      – Added I-term windup killer (no I term until you hit 5% throttle)
      – Unify SA fixes
      – Added VIRTUAL LQ for non crossfire receivers
      – Added Full EVO support for ANY receiver
      – KissFC can be used as ANY-RECEIVER->Crossfire relay station
      – Added digital RSSI for F-PORT receivers

      Small HOWTOs:

      GPS:

      You can use cheap M8N and newer gpses out of the box, some old once may require some manual
      configuration. You will get telemetry to frsky/crossfire and if osd supports it – to OSD.

      GPS can be connected to any serial port, just select GPS in advanced serial configuration.

      EVO:

      This is great VTX and i truly like how it works with kiss / fettec / GPS combo. Evo is fully supported
      with ANY receiver. Stick menus and pid changes etc. Well, some testing will not harm,
      since TBS just released it to public beta.

      You can connect it in 3 ways…

      1. To crossfire receiver. In gui – select TBS crossfire EVO
      2. To Kiss serial. In gui – select TBS crossfire EVO AND assign VTX to evo serial port.
      3. To kiss serial as SA device. In gui – select TBS Smartaudio VTX to evo serial port.

      You have to enable crossfire/SA protocol on evo and define stick channels.

      Yaw left will bring you to EVO osd menu, once more to crossfire parameters editor.

      The firmware is available ONLY in hex for and ONLY here (not in the gui).

      I am really curious about your feedback and suggestions. Thank you all for testing and support.

      Alex AKA FedorCommander

  3. Dave sagt:

    Gibt es einen Vorteil wenn ich den VTX mit CRSF RX und CRSF TX mit dem Nano Verbinde`? Reicht doch eigentlich nur Channel 4 für Smart Audio zu nutzen oder?

    • Phil sagt:

      In der Regel reicht SmartAudio. Allerdings kann der EVO auch mit einem Crossfire RX zum Beispiel kommunizieren, wenn keine FC verbaut ist. Dafür kann man dann RX und TX verwenden.

  1. 2. Mai 2019

    […] iFlight SucceX 50A 2-6S BLHeli_32 4-in-1 ESC […]

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.

Diese Website verwendet Akismet, um Spam zu reduzieren. Erfahre mehr darüber, wie deine Kommentardaten verarbeitet werden.

Nie wieder etwas verpassen…

…dann abboniere mich auf Facebook oder Youtube!