Phil sagt:

Hallo Stefanos,

der EVO verträgt Spannungen von 6V bis 26V. DU kannst ihn also auch an einem LiPo anschließen, das hat eigentlich nichts mit dem Beacon Mode zu tun.

Die EC´s sind an den FC angeschlossen, würden also keine Power bekommen wenns über den EVO läuft?

Diese Frage verstehe ich nicht. Du musst ESC, FC und VTX natürlich an den LiPo mit ausreichendem Kabelquerschnitt anschließen. Verwende ggfs. ein PDB um den Strom besser verteilen zu können. Achte auf darauf, dass deine FC direkt an den LiPo angeschlossen werden kann. Wenn nicht, schalte einen Stepdown (siehe GPS auf diesem Anschlussplan) dazwischen oder verwende ein PDB mit Stepdown.

Gruß,
Phil

Phil sagt:

Hey Flo,

ja das GPS wirst du so auch im OSD haben. Dieser Schaltplan ist zum Beispiel für Leute, die zum Beispiel Wings ohne FC fliegen!

Gruß,
Phil

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