Motoren starten nicht - CC3D + Cleanflight

[Schöni]

AW: Motoren starten nicht - CC3D + Cleanflight

Mein Setup:
ZMR250 Frame
DYS 30A SN Regler
DYS 1806 1400Kv Motoren
CC3D Evo
12V 3A Stepdown Converter
6S 1200 mah Lipos
D4Rii Empfänger
Spektrum Dx8 Funke

Wie hast Du den den FrSky D4Rii Empfänger mit der DX8 zum laufen gebracht?

Gruß Thomas

[Blade Breaker]

AW: Motoren starten nicht - CC3D + Cleanflight

Wie hast Du den den FrSky D4Rii Empfänger mit der DX8 zum laufen gebracht?

Ich hab ein Frsky Dht-U Modul verbaut. Ist ganz cool geworden, eingestellt wird über die Dx8 und die Daten werden über das Modul gesendet und auch die Telemetriedaten werden beim Modul angezeigt. Jetzt kann ich beide Protokolle verwenden (Dsm2/Dsmx und Accst)

[Schöni]

AW: Motoren starten nicht - CC3D + Cleanflight

Danke für die Info und Bilder, sehr interessant!

Da muss ich mich mal genauer informieren!

[fftunes]

AW: Motoren starten nicht - CC3D + Cleanflight

Was soll die Cleanflight Software den besser können????

ist jetzt hier zwar OT, aber weil's mir auf github grad ins Auge gestochen ist:

[SIZE="1"]This fork differs from baseflight in that it attempts to use modern software development practices which result in:

greater reliability through code robustness and automated testing.
easier maintenance through code cleanliness.
easier to develop new features.
easier to re-use code though code de-coupling and modularisation.

The MultiWii software, from which baseflight originated, violates many good software development best-practices. Hopefully this fork will go some way to address them. If you see any bad code in this fork please immediately raise an issue so it can be fixed, or better yet submit a pull request.
Cleanflight also has additional features not found in baseflight.

Multi-color RGB LED Strip support (each LED can be a different color using variable length WS2811 Addressable RGB strips - use for Orientation Indicators, Low Battery Warning, Flight Mode Status, etc)
Oneshot ESC support.
Blackbox flight recorder logging (to onboard flash or external SD card).
Support for additional targets that use the STM32F3 processors (baseflight only supports STM32F1).
Support for the Seriously Pro Racing F3 board (STM32F303, I2C sensors, large flash, excellent I/O.)
Support for the TauLabs Sparky board (STM32F303, I2C sensors, based board with acc/gyro/compass and baro, ~$35)
Support for the OpenPilot CC3D board. (STM32F103, board, SPI acc/gyro, ~$20)
Support for the CJMCU nano quadcopter board.
Support for developer breakout boards: (Port103R, EUSTM32F103RC, Olimexino, STM32F3Discovery).
Support for more than 8 RC channels - (e.g. 16 Channels via FrSky X4RSB SBus).
Support for N-Position switches via flexible channel ranges - not just 3 like baseflight or 3/6 in MultiWii
Lux's new PID (uses float values internally, resistant to looptime variation).
Simultaneous Bluetooth configuration and OSD.
Better PWM and PPM input and failsafe detection than baseflight.
Better FrSky Telemetry than baseflight.
MSP Telemetry.
Smartport Telemetry.
RSSI via ADC - Uses ADC to read PWM RSSI signals, tested with FrSky D4R-II and X8R.
Autotune - ported from BradWii, experimental - feedback welcomed.
OLED Displays - Display information on: Battery voltage, profile, rate profile, version, sensors, RC, etc.
In-flight manual PID tuning and rate adjustment.
Rate profiles and in-flight selection of them.
Graupner PPM failsafe.
Graupner HoTT telemetry.
Multiple simultaneous telemetry providers.
Configurable serial ports for Serial RX, Telemetry, MSP, GPS - Use most devices on any port, softserial too.
And many more minor bug fixes.[/SIZE]