Beiträge von DrFrantic77

    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/

    Seit ersten August ist die Version 4.0.5 verfügbar:


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

    Fixes:

    • fixed calibration of the ADC and made (#8427, #8594);
    • added enforcement of upper limits for filter frequencies (#8512);
    • fixed bind button support for SPI RX (#8543);
    • fixed default setting for gyro 2 (#8544);
    • fixed potential problem with the detection of SD cards (#8557);
    • fixed multiple reset after the reset button was used (#8619).

    Target Updates:

    • added new target TMOTORF4 (#8533);
    • fixed LED_STRIP on target BEEROTORF4 (#8540);
    • fixed bug in GPS over BST support on target COLIBRI_RACE (#8555).

    Versionshistory von BF 4.0.4

    Fixes:

    • fixed a typo in CLI help (#8365);
    • fixed OSD display of negative GPS coordinates (#8374);
    • fixed bug in adjustment ranges when failsafe is active (#8386);
    • fixed resource display of UARTs in CLI (#8392);
    • fixed build error on targets without ESC sensor support (#8403);
    • added missing osd_esc_rpm_freq_pos parameter in CLI (#8404);
    • fixed bug affecting SmartAudio 2.1 (#8438);
    • fixed bug affecting the detection of FrSky SPI RX (#8441);
    • fixed invalid upper limit for filters (#8475);
    • fixed MAX7456 OSD support for Unified Targets (#8504);
    • fixed return of MAX7456 detection result over MSP (#8505);
    • fixed build for targets without support for Dshot, LED_STRIP, and transponder (#8506).

    Target Updates:

    • removed unneeded configuration for barometer and compass from target SPRACINGF3NEO (#8332);
    • added support for MPU6000 gyroscope to target KAKUTEF7 (#8375);
    • added support for RacePIT mini to target FF_RACEPIT (#8387);
    • fixed bug in gyroscope configuration and added PINIOBOX defaults to target EXF722DUAL (#8449);
    • updated defaults and added PINIOBOX defaults to target CLRACINGF4 (#8463);
    • updated the hardware configuration for target CLRACINGF7 (#8479).

    Betaflight 4.0.3

    Fixes:

    • fixed inconsistency in the D_min configuration (#8167);
    • fixed USB ID pin support (#8170);
    • fixed crash in CMS (#8222);
    • fixed flash initialisation (#8238);
    • fixed bug causing blackbox header corruption (#8284);
    • fixed setting / printing of 32 bit values in CLI (#8302);
    • fixed printing of DMA options in CLI 'diff' (#8303);
    • changed CLI 'timer' command to use alternate functions (#8305, #8306, #8320);
    • removed RTC6705 VTX clock hack (#8322);
    • fixed bug affecting copying of profiles (#8331);
    • fixed bug corrupting the configuration when setting VTX frequency directly (#8338);
    • fixed bug in flash erasing (#8342);
    • fixed bug allowing distance for descent to go negative in GPS rescue (#8356).

    Target Updates:

    • added gyro support for the Viva F4 AIO board to the DALRCF405 target (#8097, #8349);
    • added new target MAMBAF722 (#8182);
    • removed the FURYF7 target (#8205);
    • added new target AIRBOTF7 (#8208, #8328);
    • added new target XILOF4 (#8209);
    • added new target OMNIBUSF7NANOV7 (#8210);
    • removed unneeded pin definition on NUCLEOF722 target (#8220);
    • added new target TRANSTECF7 (#8243);
    • added new target VGOODRCF4 (#8249);
    • added camera control pin to FURYF4 target (#8264);
    • added support for multi gyro on OMNIBUSF4NANOV7 target (#8267);
    • removed deprecated use of USE_MULTI_GYRO (#8281);
    • removed deprecated ACC_x_ALIGN defines (#8287);
    • added barometer support to SPRACINGF3NEO target (#8321);
    • added barometer, flash, softserial to EXF722DUAL target (#8333);
    • fixed barometer support for SPARKY2 target (#8346).