OpenTX Updates und Versionen

  • Set dem 15.09.2016 ist OpenTX in der Version 2.1.9 verfügbar.


    Changes:


    [Taranis]

    • Fixed USB driver changed interrupt grouping which affected interrupt priorities (fix suggested by Michael Blandford), this should fix the SBUS Trainer issue #2999 (#3178)
    • ADC Jitter Filter improvements, option added in Hardware settings to turn it on/off (#3432)

    [9XR-PRO]

    • Fixed: Trainer inputs >TR4 not working (#3203)
    • External module output type setting was not visible

    [Lua]

    • Fixed playTone() crash when called with abnormal parameter values (#3462)
    • Return proper values for Cels- and Cels+ (#2826)
    • Fixed lcd.drawNumber() display when INVERS flag was used (#3569)

    [All]

    • Fixed: calculated sensors had persistent value set to zero at every shutdown when persistent option was not active (#3454)
    • Show persistent option only for calculated sensors (#3454)
    • Fixed: sensors with active filter had invalid negative values (#3463)
    • Enabled DSM protocols on several raios (#3471)
    • Better representation of negative mixer weight in offset bar widget (#3476)
    • Fixed several bugs in curve preset function (#3451)
    • Fixed flight modes rotary encoders initialization when creating new model (only for radios with rotary encoders) (#3473)
    • Fixed: show value of persistent sensor after power on, before the telemetry is received (#3595)
    • Fixed: LSs weren't selectable as input source (#3632>/a>)

    [Companion]

    • SD sync fixes (#3351)
    • Fixed: Telemetry mode "FrSky D (cable)" choice was missing for Taranis (#3372)
    • Show persistent option only for calculated sensors (#3454)
    • Fixed Flight mode clear command (#3214)
    • Fixed a problem with Rotary encoders linked to flight mode (could freeze Companion) (#3459, #3470)
    • Telemetry simulator improvements: added fuel quantity sensor, increased RPM range (#3505, #3506)
    • Implemented minimal support for the DYI Multimodule (#3526)
    • Fixed: GVar combo-box not being refreshed when GV check-box (re-)selected (#3518)
    • Fixed: Heli inversion not correctly shown/saved from Companion on Radios without virtual inputs (#3510)
    • Implemented print functions for the Heli setup screen (#3554)
    • Fixed: Flight modes linked trims display value (#3547, #3568)
    • Fixed: New model global variables and rotary encoders initialisation (#3473)
    • Fixed: Prevent circular linked global variables and rotary encoders (#3472)
    • Fixed wrong log replay speed issue in Telemetry simulator (#3708)
    • Various texts and translations corrections
  • Moin zusammen,


    inszwischen ist ide Open TX 2.2.0 RC10 raus. Da es sich aber noch um eine release candidate handelt warte ich noch auf die Final.... sollte aber bald kommen:


    http://www.open-tx.org/2017/01/27/opentx-2.2.0RC10


    We are happy to bring you the 10th release candidate of OpenTX 2.2.0, with support for the production version of the FrSky Horus radio!

    PLEASE NOTE the following important information before hastily jumping on it:

    • This is pre-release software. We’ve done our best to ensure its quality with main focus on the new Horus platform, with second priority on all Taranis versions (few changes from 2.1), then the other supported platforms, but we still expect there will be issues. As it is the purpose of a release candidate, we need your feedback to report things we may have missed.
    • There is currently no documentation other than this page, so get yourself a good coffee to wake up, and refer to the the great communities for help e.g. openrcforums here, RCGroups and threads like this one. You can pop in our chat room where other users and/or devs may be available.
    • Check during companion install that it installs itself in the correct directory, usually you want “Companion 2.2”. A bug that will still show up on this update may cause it to install itself in “Companion 2.1”, potentially overwriting your 2.1 install.
    • Companion supports reading and writing Horus firmware when the radio is powered off and then connected to USB, using dfu-util and the libusb drivers installed by Zadig, exactly like for the Taranis. See the “Flashing your Taranis Radio” section in this manual. Companion can back up existing firmware (see note below in known issues) including the stock FrSky one (save as .bin), and can flash the FrSky DFU bootloader so that no other tool and/or driver swapping is needed. You might need to disable the “Check hardware compatibility” checkbox in the flashing dialog.
    • SD card contents can be found here. Download the correct archive for your radio type, extract it to the root of an empty SD card and you’ll have all needed files. Please note that all existing OpenTX sound packs won’t work due to changes in the naming strategy, so you’ll likely want to use those that are included in this archive until popular 3rd-party packs are adapted.
    • OpenTX does not touch the internal flash of production Horus radios. Its contents do not need to be backed up and are not accessible in any way when OpenTX firmware is loaded.
    • There is no bootloader on Horus at this point. The SD card can be accessed while the radio is powered on, providing you selected the “massstorage” firmware option.
    • If you are using a beta Horus and are not starting fresh (i.e. you keep your models and settings from a previous OpenTX nightly) you will need to reconfigure pot types on the Radio->Hardware page and recalibrate your sticks and pots.

    Known issues:

    • The radios will report an incorect firmware number (2.2.02.2N362 instead of 2.2.0N362)

    • Companion installer may try to install itself in the wrong directory, see above.
    • The progress bar in companion when reading firmware from a Horus is broken and will reach 100% at only 25% progress. Just wait, the window will close when the process is finished.

    A rough view of the changes in OpenTX 2.2 can be found here.

    Download and install Companion and use it to retrieve and transfer the latest OpenTX firmware to your radio after configuring the proper radio type. You need to check “Use OpenTX firmware nightly builds” in companion settings to be able to download firmware, and “Use companion nightly builds” to be notified of further companion release candidate updates.

    Horus production version and beta version use different hardware. Companion defaults to production hardware, for beta radios check the “pcbdev” firmware option in the profile settings.

    General information

    As we are getting closer to 2.2.0 release, we are now focusing on fixing the remaining issues rather than adding new features. As a result, you might see more frequent release of RC until we are ready to release 2.2.0.

    If you are working on sound packs or other firmware addons or would like to contribute translations for either the firmware or companion, now is a great time to get ready for 2.2 release. (Translators, you can contact us on rocket.chat if you need assistance)

  • Open-TX ist jetzt seit dem 30.05.17 aus dem release candidate raus... somit jetzt endlich eine offizielle Version:

    http://www.open-tx.org/2017/05/30/opentx-2.2.0


    werde ich die Tage mal ausprobieren, neu ist:


    We are happy to bring you the release version of OpenTX 2.2.0, with support for the production version of the FrSky Horus radio and Taranis Q X7!

    PLEASE NOTE the following important information before hastily jumping on it: Please back up your models and settings before upgrading so that you can go back to your previous version should you not like 2.2 or find issues that make it unsuitable for you. Use the “backup radio to file” companion feature for this to have an exact copy of what was on your radio.

    • As a new major release a new data format has been put in place, existing models and settings will be upgraded keeping things compatible as much as possible, but not everything can be converted. Only OpenTX 2.1 and later settings can be upgraded by the radio, if you currently run an even older firmware version you have to either go through 2.1 first before flashing 2.2, or do the conversion within companion. It is absolutely necessary to go through all your models after the upgrade, check they are operating properly and fix the potential issues before flying or applying motor power.

    • This is a .0 release. A lot of testing has been done by developers and beta testers, but inevitably some issues only pop up with large scale use and particular use cases, if you’re not very adverturous hold off for a few releases until things are well ironed out.

    • The manual has not yet updated to include all Horus documentation/OpenTX 2.2 changes, so get yourself a good coffee to wake up, and refer to the the great communities for help e.g. openrcforums here, RCGroups and threads like this one. You can pop in our chat room where other users and/or devs may be available.

    • Check during companion install that it installs itself in the correct directory, usually you want “Companion 2.2”. If you used 2.2 release candidates a bug may cause it to install itself in “Companion 2.1”, potentially overwriting your 2.1 install.

    • Companion supports reading and writing Horus firmware when the radio is powered off and then connected to USB, using dfu-util and the libusb drivers installed by Zadig, exactly like for the Taranis. See the “Flashing your Taranis Radio” section in this manual. Companion can back up existing firmware (see note below in known issues) including the stock FrSky one (save as .bin), and can flash the FrSky DFU bootloader so that no other tool and/or driver swapping is needed. You might need to disable the “Check hardware compatibility” checkbox in the flashing dialog.

    • SD card contents can be found here. Download the correct archive for your radio type, extract it to the root of an empty SD card and you’ll have all needed files. Please note that all existing OpenTX sound packs that where designed for 2.1 won’t work due to changes in the naming strategy, so you’ll likely want to use those that are included in this archive until popular 3rd-party packs are adapted.

    • OpenTX does not touch the internal flash of production Horus radios. Its contents do not need to be backed up and are not accessible in any way when OpenTX firmware is loaded.

    • There is no bootloader on Horus at this point. The SD card can be accessed while the radio is powered on, providing you selected the “massstorage” firmware option.. Selecting massstorage disables Joystick support (for all radio).

    • Due to changes introduces by Horus, image, sound, and script file names for ALL radio are restricted to 6 characters in most places.

    WARNINGS:

    • Companion now offers assistance for model conversion from one radio type to another. The transferred models NEED to be completely checked and validation before being used, as some things like switches assignments may not get converted properly. The proper way to transfer models form one radio to the other is to: Select a profile for the destination radio, read the settings from the destination radio, open the source file or read the source radio, drag models onto the destination radio’s window, write destination radio.

    • FrSky X9E users: Previous version (2.1 or 2.2 before RC17) were reading additional toggle or 2pos switches incorrectly: those switches were toggling between middle (which should not exist for a 2pos/toggle) and either up or down (depending on how they are wired). This was generally not seen as an issue because Companion was not able to display/manage those and the functionality seemed ok, but it was a real issue. This has been corrected, and as a result, ALL USAGE OF ADDITIONAL 2POS and TOGGLE needs to be carrefully checked.

    Known issues:

    • If you get an “Invalid Language” error when trying to download firmware after upgrading from 2.1 open the profile settings and reselect your radio type, even if it is already correct.
    • The progress bar in companion when reading firmware from a Horus is broken and will reach 100% at only 25% progress. Just wait, the window will close when the process is finished.

    Download and install Companion and use it to retrieve and transfer the latest OpenTX firmware to your radio after configuring the proper radio type.

    Horus production version and beta version use different hardware. Companion defaults to production hardware, for beta radios check the “pcbdev” firmware option in the profile settings.

    Changelog

    Much improved and overhauled Companion software

    • New .otx file format
    • High DPI Display support
    • Show custom names for switches/knobs/channels/etc throughout user interface
    • Many performance and stability improvements
    • Improved Simulator integration
    • Fully re-worked “SD Sync” feature with options dialog, faster and reliable copying between any two folders
    • Chinese language support (Companion only)
    Improved simulator

    • New startup options dialog for standalone Simulator to select radio profile, data file, SD path, etc. (also new command-line options)
    • New main user interface using docking sub-windows, improved radio simulator UI, and many improvements for other UI widgets
    • Added/improved full support for FrSky X9E, X7, & X12S radios, including custom radio “skins” for each
    • Improved debug output console, now with configurable filters
    • New back-end interface to firmware code, fixes many possible performance/timing issues, reduced CPU consumption, and enhances UI responsiveness
    • Custom hardware configurations loaded from the actual radio settings
    Improved UI for 128x64 ARM based radios (X7 / Sky9X / 9X-PRO / AR9X)

    • Model backups now have date and time stamps
    • Virtual inputs
    Lua

    • Support for communication over Sport, examples: S6R/S8R script, Crossfire and Betaflight configuration scripts
    • Allow adding/setting telemetry sensors from Lua scripts
    • Add support for generating/loading pre-complied Lua scripts (.luac) to improve memory consumption and loading times
    • Text and number alignment reviewed and fixed in many places. This may break layout of existing 2.1 scripts
    Taranis

    • SWR is no longer a telemetry value and can be accessed as RAS under analogs
    • X9E: hardware FPU has been enabled
    • mixersmon option is now always present (removed from option choice)
    • Significant improvement to FR translations, thanks to LapinFou
    Radio protocols

    • Allow optional binding mode for X6R, X8R and XSR (“bindopts” firmware option, needs current XJT firmware on X9D+/X7D and receivers require beta firmware)
    • D16: Default to 16 channels output and display refresh rate
    • Support of DIY Multiprotocol Module
    • Support for latest TBS Crossfire protocol, including telemetry
    • Spektrum telemetry parser
    • FlySky AFHDS2A telemetry parser
    Miscellaneous

    • Improved Mac OS X disk images
    • dfu-util and avrdude included in Mac OS X Companion app
    • SD Card version check to ensure correct SD Card content
    • Countless bug fixes and minor improvements
    • BMP folder renamed to IMAGES
    • FIRMWARES / EEPROMS folders renamed to FIRMWARE / EEPROM
    • Curve names shortened to 3 characters (was 6)
    • GVAR names shortened to 3 characters (was 6)
    • 64 Logical Switches (was 32)
    • tada.wav has been renamed to hello.wav

    For more details, see here.

    Changes since 2.2.0 RC18

    • FrSky X7: fix custom function screen when volume and adjust gvar is displayed [#4880]
    • FrSky Horus: Fix input line numbering, now correctly starting at 1 [#4966]
    • FrSky Horus: Fix crash when deleting a main view page [#4909]
    • FrSky Horus: Fix extended limits handling in Channel monitor widget [#4968]
    • FrSky Horus/lua: fix path buffer overflow when widget dir name exceeds max allowed length (13 chars) [#4839]
    • 9x: fix TELEMETREZ not compiling
    • Simulator: Revert logic switch names in Radio Outputs view to numbers-only
    • Companion: rework and improve SD Sync feature [#4837] [#4848]
    • Companion: Fix battery voltage and current calibration changes not saving
    • Companion: Fix custom failsafe no-pulse and hold options not being saved properly [#4904]
    • Companion: Fix crash/corruption when loading 9XR-Pro settings in some cases [#4961 #4959]
    • Companion: Match Logical switch names to radio (Lxx)
  • This is a .0 release. A lot of testing has been done by developers and beta testers, but inevitably some issues only pop up with large scale use and particular use cases, if you’re not very adverturous hold off for a few releases until things are well ironed out.


    Also noch immer Beta ;)

    Lieber die .1 abwarten wenn man wirklich sicher sein möchte.

  • Nö, war alles ganz in Ordnung. Der Updateprozess war etwas schwierig und die Telemetrie musste ich neu einstellen.

    Das war je nach Modell etwas umfangreicher.


    Das Update des SD-Contents fand ich etwas unübersichtlich weil nirgends steht wie und was und warum...

  • Moin zusammen,


    die letzten Versionen verschlafen, hatte bis dato aber auch keine Probleme:

    Jetzt aber zur aktuellen 2.2.2RC5

    http://www.open-tx.org/2018/07/16/opentx-2.2.2RC5


    OpenTX 2.2.2 RC5 Improving your Tx

    We are happy to bring you this release candidate of OpenTX 2.2.2, with support for the FrSky X-Lite radio!

    We expect this to be the last of the 2.2 series, with the exception of any serious issues being discovered after release.

    PLEASE NOTE the following important information before hastily jumping on it: Please back up your models and settings before upgrading so that you can go back to your previous version should you not like 2.2.2 or find issues that make it unsuitable for you. Use the “backup radio to file” companion feature for this to have an exact copy of what was on your radio.

    • This is pre-release software. We’ve done our best to ensure its quality but we still expect there may be issues, as is the purpose of a release candidate we need your feedback to report things we may have missed.

    • The manual has not yet updated to include all Horus documentation/OpenTX 2.2 changes, so get yourself a good coffee to wake up, and refer to the great communities for help e.g. openrcforums here, RCGroups and threads like this one. You can pop in our chat room where other users and/or devs may be available.

    • Check during companion install that it installs itself in the correct directory, usually you want “Companion 2.2”. If you used 2.2.0 release candidates a bug may cause it to install itself in “Companion 2.1”, potentially overwriting your 2.1 install.

    • SD card contents can be found here. Download the correct archive for your radio type, extract it to the root of an empty SD card and you’ll have all needed files. Please note that some existing OpenTX sound packs that where designed for 2.1 won’t work due to changes in the naming strategy, so you’ll likely want to use those that are included in this archive until popular 3rd-party packs are adapted.

    • OpenTX does not touch the internal flash of production Horus radios. Its contents do not need to be backed up and are not accessible in any way when OpenTX firmware is loaded.

    • Due to changes introduces by Horus, image, sound, and script file names for ALL radio are restricted to 6 characters in most places.

    WARNINGS:

    • By default, the setting for companion is to download release only firmware, you NEED to go to settings/settings/application settings and set it to “Use releases and release candidates (testing)” to get new radio firmware or simply 2.2.2 RC firmware.

    • Companion now offers assistance for model conversion from one radio type to another. The transferred models NEED to be completely checked and validated before being used, as some things like switches assignments may not get converted properly. The proper way to transfer models from one radio to the other is: Select a profile for the destination radio, read the settings from the destination radio, open the source file or read the source radio, drag models onto the destination radio’s window, write destination radio.

    • The first versions of Frsky X10/X10s misuse the USB-C port for charging its internal battery. Do not plug anything else in there. For more details see here: FAQ for X10/X10s USB-C port

    Known issues:

    • If you get an “Invalid Language” error when trying to download firmware after upgrading from 2.1 open the profile settings and reselect your radio type, even if it is already correct.
    • The progress bar in companion when reading firmware from a Horus is broken and will reach 100% at only 25% progress. Just wait, the window will close when the process is finished.

    • Horus X12S production version and beta version use different hardware. Companion defaults to production hardware, for beta radios check the “pcbdev” firmware option in the profile settings.

    Download and install Companion and use it to retrieve and transfer the latest OpenTX firmware to your radio after configuring the proper radio type.

    MUST READ : Xlite : Xlite

    Xlite uses a ‘+’ pad for trims. One set of trims can be accessed directly with the ‘+’, the second set needs ‘+’ and pushing ‘shift’ at the same time. Depending on your radio mode, this can be convenient or not at all. We have introduced a solution that enable Aileron and Elevator of your actual radio mode to be always the default ‘+’ usage. Unfortunately, the firmware that FrSky included in their first batch of Xlite does NOT include this feature, so this is a fairly big usage difference between shipped firmware and actual OpenTx 2.2.2.

    It is highly recommended to update xlite shipped version to this version or a later opentx version.

    MUST READ : HORUS : Horus bootloader

    Thanks to the work by Raphael Coeffic and Arne Schwabe, a bootloader is now availble for Horus. It allows you to flash a Horus firmware much faster by using the bootloader. There are now 3 methods for flashing OpenTX:

    • by turning on your radio in bootloader mode (by first holding T4 and T1 toward the center, then pressing the power button), connect to USB and then flash with Companion
    • by putting the firmware on the SD card, then start bootloader mode (by first holding T4 and T1 toward the center, then pressing the power button), select write firmwware, navigate to it and press ENTER
    • by connecting the HORUS to usb in the off state and use dfu-util (through Companion) like before

    MUST READ : R9M : R9M EU-LBT

    FrSky has released a new firmware version (180428) for R9M-EU modules, that is NOT compatible with previous OpenTx versions. OpenTX version 2.2.1 : only firmware up to 180329 are ok OpenTX version 2.2.2 : only firmware 180428 or later are ok

    Main changes since 2.2.2RC4

    • All radios : WARNING for cross trim users : we had to remove the Throttle Trim fix when cross triming as it was generating a bigger bug.
    • All radios : do not load globbl function scripts if global functions are disabled
    • All FR supporters : ** !!!!
    • FrSky Xlite : enable BT auto detection
    • 128x64 radio : fix flight modes and “Tele” unreachable in logical switches
    • LUA : fix setting x values < 0 for custom curves
    • Companion : better refresh of logical switches just after their creation
    • Companion : fix simulator GPS precision when loaded from CSV log
    • we expect this RC5 to be the same as, or very close to, the 2.2.2 release, so we encourage wide testing of it!

    RC4 release notes

    RC3 release notes

    RC2 release notes

    Main changes since 2.2.1

    • All Radio : fix setFailsafe special function (was overwriting GV0)
    • FrSky Xlite : support for the new radio
    • FrSky Horus : both modules are now turned off on model changes
    • FrSky Horus : add bootloader to Horus (see above)
    • FrSky Horus : allow splash image on Horus start (put image as /IMAGES/splash.png)
    • FrSky Horus : improve rotary encoder overall response
    • FrSky Horus : add glider support to model wizard
    • FrSky Horus : fix Timer display widget (do not display timer number if a name is defined)
    • FrSky Horus : display first persistent timer in model select screen
    • FrSky Horus : add mixer warning feature
    • FrSky Horus : rework backlight (mode OFF : screen nevers turn completely off, it goes to min backlight (5 for x12, 45 for x10), mode keys/controls : if off setting is set to absolute min, then screen goes fully dark)
    • FrSky Horus : fix T5 & T6 trim reuse
    • FrSky Horus : add receiver ID check feature
    • FrSky Horus : add more language support to Horus fonts
    • FrSky Horus : relaod all models on USB disconnect
    • FrSky X10 : mute audio when no audio is played
    • FrSky X9E : fix center beeps for LS -FrSky X9E : fix crossfire scripts for X9E navigation
    • FrSky X9E : review BT ui
    • FrSky X9 : rename trainer Master/Battery to Master/Serial
    • FrSky X7/X7S : add CPPM and SBUS trainer mode
    • FrSky X7/X7S : fix custom scripts output display
    • FrSky X7/X7S : add PREC and unit GVAR support
    • FrSky X7/X7S : fix R9M power cannot be changed
    • FrSky X7/X9 : fix display for timers over 99 hours
    • FrSky X7 : fix PPM center display
    • FrSky X7 : switch warning UI has been improved
    • FrSky Xlite/X7/X10 : fix a freeze when volume was set to 0 while bgmusic was playing
    • FrSky Xlite/X7/X10 : improve PWM reading latency with PWM stick are used
    • FrSky Xlite/X7/X10 : display stick type in analog screen
    • FrSky radios : display model notes before modules are activated (allow display of comments like ‘add external antenna’ before emission starts)
    • FrSky radios : add capability to set all custom failsafe channels at once
    • FrSky radios : improve R9M UI support
    • FrSky radios : fix broken UUID display
    • FrSky : telemetry support for new devices : Dual SBEC & High Power ESC (FrESC32_80A) and Gas Suite sensors
    • FrSky S6R : fix for LUA script when S6R do not show Quick Mode on last receiver firmware
    • FrSky S8R : fix for LUA calibration script showing wrong values on last receiver firmware
    • FrSky R9M : see notice above
    • All radios : fix GPS logs for small negative values
    • All radios : fix throttle warning for reverse POTS/SLIDERS too
    • All radios : allow the display of RAS on capable 128x64 radios
    • All radios : fix center trim beeps when cross trimming
    • All radios : apply THR trim feature also when cross trimming
    • All radios : Review FAI modes : now disables all telemetry sensors except RSSI and RXBT (also works with Crossfire)
    • All radios : backlight is forced ‘on’ for splaash and switch warning screens
    • All radios : individual trims that are disabled in FM settings are no longer visible on main view
    • All radios : don’t reinitialise last flight mode on flight reset
    • All radio : fix possible timer mode overflow
    • All radio : do not show hidden files on SDCard
    • ARM 9x : remove ‘nofp’ option which was conflicting with too many things
    • LUA : add getRtcTime() function
    • LUA : add getTxGPS() function for radio with internal GPS
    • LUA : add gtimer support (read using getGeneralSettings(), clear using resetGlobalTimer())
    • Crossfire : add support for text sensors like Flight mode
    • Crossfire : improve python crossfire parser to handle GPS data
    • Crossfire : fix X9E wheel navigation
    • Companion : do not display RC99 for ‘release’ version of firmwares
    • Companion : custom functions sound playblack fix
    • Companion : radio conversion improvements #5534
    • Companion : adjust source value ranges and editors in LS/CF/Telemetry #5437
    • Companion : fix new LS not available until model editor is reopened, and other minor editor propagation issues
    • Companion : small fixes and improvements to Inputs and Mixes editors #5942 #5029 #5957
    • Companion : log viewer Google Earth export fixes #5937
    • Companion : improve model print and compare #5568 #5645 #5866
    • Companion : add context menu to Outputs editor #5665
    • Companion : curve editor enhancements #5947
    • Companion : wizard now use mixer instead of override for throttle cut
    • Companion : ignore hidden files on SD sync
    • Companion : fix RF Output Power setting getting reset
    • Companion : fix disappearing mixer lines after an invalid line is removed
    • Companion : prevent crash on X9E simu when interacting with BT settings
    • Companion : Improve French and German translations
    • Simulator : telemetry widget now remembers last used log folder
    • Simulator : add mixer outputs to Radio Outputs widget #5811

    Download links:

    SDCard content for 2.2.2 RC5

    SDCard changes since 2.2.1 :

    • 128x64 Crossfire lua have been modified to also support xlite (thx DieHertz)
    • add missing German audio files
    • change french telemko audio file
    • fix russian audio files that had too long names
    • add support for FrSky Xlite radio
    • update SxR scripts to support latest receiver firmware
    • add glider wizard for Horus
    • review some Horus graphics (mask_iconback)

    OpenTX Companion 2.2.2 RC5 - Windows Installer If you get an error about “api-ms-win-crt-runtime-I1-1-0.dll missing” install MS VC++ runtime.

    OpenTX Companion 2.2.2 RC5 - Mac OS X Disk Image

    OpenTX Companion 2.2.2 RC5 - Linux DEB Package 64-bit

    OpenTX Companion 2.2.2 RC5 - Ubuntu PPA (i386 and amd64) m

  • Hi,

    da ich mir jetz CF einabauen möchte und diese gut über das LUA Script einstellen kann, die ja auf OTX 2.2 schon dabei ist, müsste ich meine Funke jetz von 1.9 updaten.

    Da ich ja bereist verschiedene Modelle für berschiedene Copter bereits drinnen eingespeichert habe, möchte ich diese nachher nicht nochmal alle konfiguieren.

    Wenn ich also die neue Firmware bzw. auch den neuen Bootloader flashe, bleiben dann die Modelle erhalten, oder muss ich die in eine Art Backup auf dem PC sichern und nachher wieder draufspielen?

    Lg

  • Bin mir nicht mehr ganz sicher. Aber normal sollte das gehen.

    Kritisch kanns werden, wenn du jetzt Seiten hinzufügst. Bei einer Version haste nen Reiter mehr. Ab da wo es das LUA script gibt.

    Ich bin jetzt auch schon seit 1.8 oder früher dabei und hab immer nur updates drauf gebügelt.

    Musste bis jetzt die Modelle noch nicht löschen und neu anlegen, nur bei einer Version mal die Sensoren löschen und neu einlesen. Aber das sollte kein Akt sein.


    Würde aber einfach mal nen Backup mit OpenTX machen. Zurück auf die alte FW ist ja auch kein Problem.


    Solltest probleme haben, eventuell alle updates hintereinander machen. Aber da wirst schneller sein, wenn du die Modelle neu anlegst.

  • Moin zusammen,


    Open TX 2.3 hat nachgelegt und auch ein paar neue Funken mit ins Programm genommen. Unter anderen auch die T12:
    Nicht vergessen, neuer SD-Content !!!

    http://www.open-tx.org/2019/09/27/opentx-2.3.0

    New radios
    • X-Lite Pro
    • X9 Lite
    • X10(S) Express
    • X9D+ 2019
    • T12
    All radios
    • A new TOOLS screen has been added to radio section. This screen provide a shortcuts to either build in tools, or lua scripts located in /SCRIPTS/TOOLS directory
    • Version screen now allow you to see the options included in your radio firmware
    • Radio logs now logs all switches declared in hardware menu
    • Radio with power button have now adjustment of on/off timing
    • Radio based wizard have been refreshed (Thx LapinFou)
    • When creating a new model, both modules are now defaulted to “OFF”
    • Improve rotary encoder handling on all radios
    • Improve Czeck translations (Thx Jannek)
    • Improve German translation (Thx SHezinger)
    • Improve Italian translations (Thx mzambrini)
    • Improve Japaneese translations (Thx ku2works)
    • Fix GPS distance calculation on some coordinates
    • RTC Voltage monitoring + alarm (thanks to Mike B)
    Frsky
    • Latency for existing XJT modules (internal or external) has been significantly improved
    • Support for Neuron lines ESC telemetry
    • Support for .frsk firmware files. Those contains identification of target hardware, preventing flashing wrong device with wrong firmware type errors
    • Add RTC battery status
    • Radio with external antenna have now choices ‘per model’ or global settings, with associated updated warnings
    Taranis
    • Taranis now allow up to 40 sensors (up from 32)
    • Support for additional switches for X7 on PAD400 and PAD401
    • ‘full size’ modules available on small size external bay as an option
    • X9E : prevent timer display overflow on top LCD
    • X9E : fix key diagnostic display
    • X9E : all sliders are now added correctly after EEprom reset
    • 128x64 : fix trims display
    • 128x64 : protect against negative x drawing
    Horus
    • Horus now allows up to 60 sensors (up from 32)
    • Support for additional switches and pots for X10 and X12
    • X12S internal GPS data are now used only when a decent positionning has been achieved
    • Remplacement Express internal module supported using Companion ‘internalaccess’ option
    • Internal module firmware can now be flashed from OpenTX
    • Add screenshot special function
    Sky9x
    • Add R9M flex option to Sky9x
    • Support for Sky9X REVA removed (wasn’t compiling since 2.2)
    • Fix for PPM2 not properly initialised
    Radio protocols
    • ACCESS protocol added
    • Support up to 24 channels on ACCESS modules when using ACCESS protocol
    • Spektrum analyser and power meter on compatible ACCESS modules
    • New registration and bind mechanism for ACCESS devices
    • Support for OTA updates for upcoming compatible hardware
    • Add Crossfire telemetry mirror on serial port
    • Add Crossfire telemetry mirror on bluetooth
    • Add iNav vario sensor to Crossfire
    • Support for module Multiprotocol 1.2.1.51 (Thx MRC3742 and PascalLanger)
    • Disable RxNum checks for D8 protocol
    • Mixer to pulse synchronisation improved
    • Improves FlySky RSSI handling (starts at 100, failsafe arround 30)
    • Display FlySky volts as signed values (Thx CapnBry)
    Lua
    • Fix TIMEHOUR handling on 128x64 screens
    • Telem 1 to (40/60) items added
    • Lua mix scripts outputs added
    • Fix DIY first ID to 0x5100
    • Introduction of virtual navigation keys
    • Added string type to Horus widget
    • global functions scripts do no run anymore if global functions are disabled in model config
    • GPS data now have a delay attribute
    • chdir function added
    • fix 1bit bitmap draw on 128x64 displays
    Companion
    • Multimodule, Crossfire and luac options are included by default in all firmware
    • Fix for Negative GVAR precision (Thx Elecpower)
    • Add receiver number to model list (Thx Elecpower)
    • Add Japaneese translation (Thx Ku2works)
    • Improve french translation (Thx LapinFou)
    • Fix Companion wizard
    • Companion now informs when radio are not currently available
  • OpenTX ist jetzt in der Version 2.3.1 verfügbar:

    https://www.open-tx.org/2019/10/05/opentx-2.3.1

    • All radios: fix handling of conflicts between external module and trainer settings
    • All radios: some have reported incorect reading of RTC bat. While this gets investigated, a way to disable the alarm has been added in hardware screen.
    • Companion: fix shift in sources for X9DP-2019
    • Companion: fix handling of topbar choices
    • Companion: add handling of ACT switch
    • Companion: add missing module choices for various
    • Companion: telemetry baudrate setting is now retained during import/export
    • X12S: fix incorect RTC voltage
    • 212x64 radios: SD browser now properly handles .frsk files
    • X9D: fix navigation in hardware screen
    • X9D: fix lua navigation event for scripts included on our SD Pack. External script like Betaflight will need to be adapted by their authors
    • X7: fix additional switches SI/SJ handling
    • T12: fix navigation issue sometimes prevent access to bind button
  • die Versionen 2.3.5 und 2.3.6 total verpennt...

    Inzwischen ist 2.3.7 verfügar: https://www.open-tx.org/2020/03/28/opentx-2.3.7


    We are releasing this bugfix version of OpenTX 2.3.7. Download and install Companion and use it to retrieve and transfer the latest OpenTX firmware to your radio after configuring the proper radio type.

    PLEASE NOTE

    • If you are using a color LCD radio and are still using a version between 2.3.0 and 2.3.4 please upgrade! See 2.3.5 release notes for more info
    • If you are coming from a previous major version (e.g.2.2.x) please back up your models and settings before upgrading so that you can go back to your previous version should you not like 2.3 or find issues that make it unsuitable for you. For color LCD radios make a copy of the entire SD card, for B/W radios additionally use the “backup radio to file” companion feature to have a full backup of your radio.

    Known issues:

    • If you get an “Invalid Language” error when trying to download firmware after upgrading from a previous major version open the profile settings and reselect your radio type, even if it is already correct.
    • The progress bar in companion when reading firmware from a Horus is broken and will reach 100% at only 25% progress. Just wait, the window will close when the process is finished.

    NIGHTLY USERS / RC Users : You will need to reset your companion release type to Stable to get release firmware (Companion/Settings/settings/Application Settings/Release channel)

    New since 2.3.6

    ColorLcd
    • remove FrSky OTA lastest change as it crashes SD Manager

  • Hallo ich hab grade nach langer Zeit versucht versucht meine Firmware der Funke upzudaten ..... und hab dabei alles gelöscht :thumbsup: jetzt bekomme ich meinen r xsr nicht mehr gebunden. Ich blicke auf der frsky Homepage auch irgendwie nicht durch..... Auf der Taranis qx 7 hab ich jetzt die Open tx. Version 2.2.4

    Dann habe ich xjt mit der Version v 2.1.0 lbt geflashed. Jetzt wollte ich noch den r xsr flashen ....welche Firmware nehme ich denn da?Access Firmware oder die Accst d16? Wenn ich den R xsr anstecke mit gedrückten Binde Knopf leuchtet rot grün und blau dauerhaft....

  • Den r-xsr hab ich einmal geflashed kann mich nicht dran erinnern was ich da draufgeflashed habe. Konnte nur zwischen fcc und lbt Version wählen. Was ist denn der Unterschied zwischen Access und Acct? Die Software für den r xsr kann ich doch nur von der frsky Homepage laden? Oder?

  • Also die Soft für die FrSky gibt es auch von denen. (Funke)

    Die ist aber nicht so umwerfend. Von daher sollte auf die Funke OpenTX


    Für die Empfänger, brauchst die Software von FrSky....


    Da gibt es halt jetzt


    FCC

    LBT

    ACCST

    ACCES


    Egal was du nimmst, es muss halt immer das gleiche System sein.


    Aber ganz ehrlich.... ne Tango 2 kostet 180 Euro und die Crossfire Nano nur noch 28 Euro.


    Kein scheiß mit den Protokollen und nie wieder failsafe...

    Autobind und Emfpänger updaten, ohne sie auszubauen (Daten werden über Wireless übertragen)