Beiträge von DrFrantic77

    Betaflight 4.1RC5 verfügbar:


    Major features:

    • new and improved feed forward 2.0 (#8623, #8736);
    • reworked bidirectional Dshot (#8554, #8779);
    • dynamic idle management using RPM telemetry (#8604);
    • fully configurable VTX control with VTX tables (#7251).

    Minor features:

    • support for the Spektrum SRXL2 serial protocol (#8606);
    • support for board-specific custom defaults (#8707);
    • support for arbitrary gyro and mag alignment (#8474).

    Changes from the previous Release Candidate:

    Fixes:

    • fixed issue with yaw being included in ff_max_rate_limit limiting (#8926);
    • fixed issue preventing ESC initialisation when ESC beacon active at startup (#8927);
    • fixed compile errors when USE_DSHOT is not defined (#8928);
    • fixed the power level for vtx_low_power_disarm on Unified Targets (#8936);
    • added information about Unified Target manufacturer / board name / custom defaults to the diff header to facilitate debugging (#8937);
    • fixed pit mode for SmartAudio 2.1 devices (#8940);
    • fixed application of custom defaults with missing trailing newline (#8942);
    • fixed possible lockup on defaults nosave when RX_SERIAL is enabled (#8946).

    Moin zusammen,


    da ich selbst nen bisschen suchen musste und auch die Bezeichnungen etwas verwirrend sind.... hier mal eine kleine Tabelle zu den Unterschieden.
    Vorab, die FC wo mehr kann ist die F405. Auch wenn man von der Nummer her meinen könnte, es sei die kleinere FC.


    Bei FPV24:

    Matek F405 Wing

    Matek F411 Wing


    Bei Banggood:
    Matek F405 Wing

    Matek F411 Wing


    Marke / Modell
    Matek F405 Wing
    Matek F411 Wing
    Formfaktor 30,5 x 30,5 mm
    20 x 20 mm
    Anwendungen Fixed Wing Flugzeug
    Fixed Wing Flugzeig
    Größe H x B x T in mm
    13 x 36 x 56 10 x 41 x 28
    Gewicht 25 gr. 7 gr.
    Veröffentlicht April 2018
    Juni 2018
    CPU
    F4 - STM32F405
    F4 - STM32411
    MPU MPU 6000
    MPU 6000
    Barometer BMP 280
    BMP 280
    PWM Eingänge
    9 7
    UARTs gesamt
    6 2
    Inverted UARTs
    1 1
    SofSerial Input
    1 1
    I2C Input
    ja ja
    Buzzer Anschluss
    ja ja
    LED Ausgang
    ja ja
    Currentsensor Analog
    nein nein
    RSSI Analog Eingang
    ja nein
    VBAT Eingang
    ja (6S - 25V)
    ja (6S - 25V)
    5V Regulator
    ja - 3A
    ja - 2A
    Schaltbarer VTX UBEC
    ja - 9V oder 12V 2A
    ja - 5V oder 6V 3A
    Softmout ja nein
    OSD ja
    ja
    Current Sensor
    ja - 100A
    ja - 78A
    SD Karte
    ja nein
    PDB maximalbelastung
    100A 78A


    So hoffe das hilft ein wenig weiter bei der Entscheidung.


    Hier noch das Matek F405:
    Matek_F405-Wing.jpg


    Das Matek F411

    Matek_F411-Wing.jpg


    Beide mal im Vergleich:

    F405_vs_F411.jpg

    Betaflight 4.1RC4 ist verfügbar: https://github.com/betaflight/betaflight/releases


    Changes from the previous Release Candidate:

    Fixes:

    • fixed potential resource conflict with bitbanged Dshot (#8893);
    • fixed bug in Dshot code (#8897);
    • fixed problem causing lockups of VTX control with some VTX (#8903);
    • fixed problems with setting power on IRC Tramp VTX (#8907);
    • fixed bug causing lockups in the STM32F745 target (#8914);
    • added missing definition for SPI5 on STM32H7 (#8920);
    • fixed UART DMA for F4 (#8924).

    Target Updates:

    • added new target AIRF7 (#8748);
    • added new target IFLIGHT_H7_TWING (#8896).

    Dann wollen wir mal mit dem Cinewhoophype mit gehen.




    Entschieden habe ich mich für den Rimzler Dison, da ich fast alle Teile da hab.

    https://www.thingiverse.com/thing:3492360

    Mamba Stack MK1 20x20

    1507 3600KV Brotherhobby Avenger


    Alternativ gibt es dazu noch einen verbesserten Frame von Oli, wurde aber erstmal den originalen testen:

    https://www.thingiverse.com/thing:3767696


    Dann fangen wir mal mit dem Druck an, die neue Prusa Firmware 3.8 will getestet werden....


    Frame ist schon mal gedruckt, nach knapp 7 Stunden.


    Und macht schon mal einen stabileren Eindruck als gedacht.


    Ich habe jetzt doch nochmal den Frame von Oli gedruckt. Da dort die 20x20 Löcher vorhanden sind. Diesmal aber mit 50% infill.


    Also zwischen 50% Infill und 100% Infill sind gerade mal 8gr Unterschied. Die Steifigkeit ist jedoch um eingiges besser bei 100%


    Den Mamabstack verschraub und ersten Testlauf:


    Propeller hab ich dann dort noch einschleifen lassen, in den Duct geht es sehr knapp zu, ein kurzer Gasstoß löst das Problem. Danach noch ein wenig mit Schleifpapier nachbearbeiten.


    Flugfertig wird das ganze dann so aussehen und hat vorläufig erstmal ein Abfluggewicht von 495gr.

    Betaflight GUI Version 10.6RC1 ist verfügbar:
    https://github.com/betaflight/…r/releases/tag/10.6.0-RC1


    Release Notes

    This release contains all of the changes necessary to support version 4.1 of the Betaflight firmware. If you are using firmware 4.1, it is essential that you upgrade to this version, in order to get support for configuring the new features of 4.1. For a list of other new features that were added see 'New Features' below.

    If your platform is not supported, but can run a recent version of Chrome, please follow these instructions to install the Betaflight Configurator from the Chrome web store.

    We have tried to make this release as bug free as possible. If you still find a bug, please report it back to us by opening an issue here.

    If you want to talk about Betaflight, ask configuration questions, or just hang out with fellow pilots, you can do this in our Facebook group.

    Betaflight also has a presence in the Slack messaging platform. Register here, and then come join us in Slack. Most developers hang out there, so this is a great place to talk about the things you are tinkering with in Betaflight, or get help with really complicated configuration problems.

    New Features

    • added client-side autocomplete to CLI (#1329);
    • added voltage and amperage scale calibration based on meter readings (#1439);
    • added dark mode (#1473);
    • changed the OSD elements to be listed in alphabetical order (#1485);
    • added 'Video Transmitter' tab to configure a VTX (#1569, #1612, #1650);
    • added support for flashing Unified Targets with custom board configurations (#1585, #1587, #1626, #1651);
    • added sliders for PID / filter tuning (#1598, #1638, #1653).

    Fixes:

    • fixed the flashing progress bar (#1385);
    • fixed the PID tab layout (#1584);
    • various other UI fixes.

    New GUI support for the following firmware features:

    • added visualisation of rate limit settings to the PID tuning graph (#1368);
    • improved the arming disabled flags display (#1426, #1448, #1479);
    • added iterm_relax cutoff (#1564);
    • added debug modes (#1566, #1577);
    • added custom gyro alignment (#1580);
    • added Dshot telemetry information display to the motors tab (#1602);
    • added RPM based filtering (#1621);
    • new OSD display / statistics elements.

    Inzwischen sind auch die 4.1 RC1 bis RC3 verfügbar.


    RC1:

    Major features:

    • new and improved feed forward 2.0 (#8623, #8736);
    • reworked bidirectional Dshot (#8554, #8779);
    • dynamic idle management using RPM telemetry (#8604);
    • fully configurable VTX control with VTX tables (#7251).

    Minor features:

    • support for the Spektrum SRXL2 serial protocol (#8606);
    • support for board-specific custom defaults (#8707);
    • support for aribtrary gyro and mag alignment (#8474).


    RC2:

    Major features:

    • new and improved feed forward 2.0 (#8623, #8736);
    • reworked bidirectional Dshot (#8554, #8779);
    • dynamic idle management using RPM telemetry (#8604);
    • fully configurable VTX control with VTX tables (#7251).

    Minor features:

    • support for the Spektrum SRXL2 serial protocol (#8606);
    • support for board-specific custom defaults (#8707);
    • support for aribtrary gyro and mag alignment (#8474).

    Changes from the previous Release Candidate:

    Fixes:

    • fixed bug allowing dynamic notch to go into 'high' mode (#8796);
    • fixed serial ESC feedback when bitbanged Dshot is enabled (#8828);
    • fixed bug causing unused LEDs in an LED_STRIP to become 'stuck' after a configuration change (#8830);
    • fixed bug in SPI bus driver code (#8835);
    • fixed bug breaking Dshot commands when using bitbanged Dshot (#8839);
    • fixed spike suppression in feedforward boost (#8842);
    • fixed bitbanged Dshot for Dshot600 (#8843);
    • fixed problem with "" as pre-existing manufacturer id (#8848);
    • fixed 'sd_info' in CLI showing incorrect information when SD card support is not configured (#8849);
    • fixed bug allowing multiple timer allocations with bitbanged Dshot (#8852);
    • fixed problems with bitbanged Dshot on F411 targets (#8853);
    • added missing labels for dynamic notch to the blackbox header (#8856);
    • fixed timer selection on STM32F411 (#8860);
    • fixed potential resource conflicts with bitbanged Dshot (#8861);
    • fixed problems with feedforward boost on yaw (#8864);
    • fixed incorrect timer allocation with bitbanged Dshot (#8865);
    • fixed lockups when configuring VTX control port without a VTX table loaded (#8866);
    • fixed random activation of VTX pit mode when configuring VTX in configurator (#8869);
    • fixed problems with runaway takeoff prevention activating when GPS rescue is active (#8870).


    RC3:

    Major features:

    • new and improved feed forward 2.0 (#8623, #8736);
    • reworked bidirectional Dshot (#8554, #8779);
    • dynamic idle management using RPM telemetry (#8604);
    • fully configurable VTX control with VTX tables (#7251).

    Minor features:

    • support for the Spektrum SRXL2 serial protocol (#8606);
    • support for board-specific custom defaults (#8707);
    • support for arbitrary gyro and mag alignment (#8474).

    Changes from the previous Release Candidate:

    Fixes:

    • fixed problematic parameter ranges for crash recovery (#8871);
    • fixed bug in the altitude calculation (#8874);
    • fixed bug causing lockups when enabling bidirectional Dshot (#8886).

    Seit ein paar Tagen ist die 4.0.6 verfügbar:


    https://github.com/betaflight/betaflight/releases

    Fixes:

    • fixed formatting and help text of vtxtable in CLI (#8646, #8663);
    • made SD card report as 'not supported' on targets with no configured SD card slot (#8656);
    • fixed the UART pin definitions for STM32F411 (#8659);
    • fixed compilation errors if USE_ABSOLUTE_CONTROL if defined but USE_ITERM_RELAX is not (#8683);
    • fixed incorrect reporting of SD card capacity (#8703);
    • fixed lockups in FrSky SPI RX when using SmartPort telemetry (#8702);
    • fixed lockup when trying to use Dshot with missing DMA assignments (#8705);
    • fixed display of date / time when no valid time is set (#8731);
    • fixed compilation warning when USE_TASK_STATISTICS is not defined (#8765, #8782).

    Target Updates:

    • added new targets MERAKRCF405 and MERAKRCF722 (#8621);
    • added new target MAMBAF411 (#8644);
    • added target HAKRCF411 to Betaflight 4.0 (#8655);
    • added barometer support for target FURYF4OSD (#8771);
    • added new target TMOTORF7 (#8776).

    Moin zu sammen,


    die ersten Updates und Fehlerbehebungen für das TBS Fusion. Hier mal per copy and paste:


    Extensive Fusion update! After moving office and starting to slowly settle in, here's a quick list of things that we have identified that may help you get your Fusion up and running. First, the good is that the issues are far and between considering how many we shipped. Nevertheless, we strive for perfection and perfection is what we will deliver! We thank all of our customers that are having issues on the patience that they have shown. This here is meant as a first, exhaustive list of all problems and how you can help us address them as quickly as possible.

    As with all issues, if you require one-on-one support, please contact our Customer Service either by slipping into DM with Mike Chin here on FB, or opening a support ticket. Any products that need to be replaced will require a support ticket, just to keep some kind of traceability. You can open up these support tickets with your point of sale, or with TBS.

    Now, to the meat of the post:

    * Rebooting / Black Screens: Remember that you need the power board even without the Crossfire connectivity on all goggles except HDO/HD2-T2. You will need the power board connected on ALL goggles once we do make the Crossfire connectivity available (and you intend to use it). So for HDO/HD2-T2 users there's no hurry, but we do recommend installing the power board at some point in time. Next generation Orqa and Fatshark goggles will work completely without power boards.

    * Update problems: There are 2 kinds of update problems. First is bootloader related issues. Agent-X needs to be on the latest version (2.0.21). Uninstall and download if it doesn't auto-update. When on the latest version and still not working, hold down the joystick while plugging in the Fusion, then update. Second issue, reboots or flickers during update. Your USB isn't providing enough power. The easiest fix here is to update while your goggles are running. And remember, after updating you always need to re-calibrate!

    * Camera issues: Some FPV cameras are resulting in a black vertical line down the middle, or jumping screen at the edge of reception. This is caused by some form of incompatibility between the Fusion algorithm and the camera. It's fixable, we just need a bit of time. To assist us in finding the problem, please give us a list of your setup (Camera, OSD, VTx) to help us in pinpointing the problems faster.

    * Screens not sticking down: No two ways about it, we should have caught this. It's a glue/double-side tape issue. The good news is, once you've got the covers on, it's no longer a problem. If your screen popped off, simply push it back down, and put the cover on. Be careful, don't apply force to the outer edges, as the screens are fragile. We're finding a better tape, and will send these out free of charge to anyone affected if necessary. Aligning the screen is simple. Put it down so you can only see the last line of text on the wifi module, that will center it nicely with the cover.

    * Reception: We've seen some people having worse than expected reception and/or lines in feed. First thing to check is for shorts between the GND and signal pads of the modules. Second thing is calibrating the receivers (Settings -> Calibration). If the issue persists, please contact our customer support, or open a support ticket. Even if you are not dissatisfied with your reception, we will hopefully have some good news in the coming days (along with a very economic upgrade route). Stay tuned!

    * Joysticks not "clicking" in a certain direction: Our assumption here is that it only happens with the case on. In that case, it would be a tolerance issue between the socket of the goggles and the position of the stick. A bit of "tough love" helps in this case.

    * Manual: Jenni and I are working on the manual. it's coming, but Jenni has been on a trip and I've been moving office and home. Excuses, excuses. We're behind, but getting to it.

    I will expand on this list as more surface, and rest assured we are doing everything possible that the very few cases of this will disappear as shipping continues. And on that note, more Fusions are shipping out today and we expect to fill all backorders before end of this week.


    Genau kann man das hier nachlesen: https://www.facebook.com/group…ermalink/678580349294405/


    In Facebook wurde eine Testversion der 1.40i veröffentlicht.


    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


    Findet man in dieser Gruppe:
    https://www.facebook.com/groups/907549762675568/