Ever since EdgeTX 2.5, they switched to saving all the config in the SD card instead of using EEPROM (EEPROM is not used anymore). The only way to backup and restore information saved in this memory is using the EdgeTX Companion. If your EdgeTX version is 2.4 or older, you still have to backup models and radio settings.īefore EdgeTX 2.5, some config is saved to a piece of memory in the radio called EEPROM. But I recommend backing up the whole SD card content (basically all the folders and files) so you won’t lose any sound pack, image files and scripts. More specifically, the models and radio settings are saved in the MODELS and RADIO folders. That means backing up is as simple as copying your SD card content to somewhere on your computer. With EdgeTX 2.5 or newer, all the config are saved in the SD card. There is nothing else you need to backup, you can move on to the next step. Backup Radioįollow instructions here to backup and restore your radio SD Card Content: For EdgeTX 2.5 or newer All models should be there after flashing. Notes: you WILL NOT lose any models after the upgrade, so don’t worry. Scroll to the VERSION tab (7th tab) by pressing the Page buttonīy making a backup of the radio, we can revert to where we started in case of any issue.Check Your EdgeTX Versionīefore flashing, it’s always a good idea to make note of what your current EdgeTX version is. If your radio has an older version of EdgeTX and you wish to update it, continue reading. If your radio has OpenTX, go here for instructions how to migrate. RadioMaster/Eachine TX16S / RadioMaster TX16S MAX / RadioMaster TX16S Mark II.
FrSky X10 / X10S / X10 Express / X10S Express.FrSky QX7 / QX7S / QX7 ACCESS / QX7 ACCESS.Here’s a list of radios that support EdgeTX. EdgeTX is a fork of OpenTX, which means it’s very similar to OpenTX (so the transition is almost seamless), and EdgeTX should work on any OpenTX compatible radios. If you don’t want to wait a long time for new features to be implemented in OpenTX, then you could give EdgeTX a try today. The popular OpenTX project is known to have a slow pace development, so EdgeTX team took it upon themselves and try to bring more rapid radio firmware development to the RC/FPV community. Choose WinUSB (v6.x.x.EdgeTX is an open source firmware for RC radio transmitters.Select STM32 BOOTLOADER in the device list.With the board connected and in bootloader mode (reset it by sending the character R via serial, or simply attempt to flash it with the correct serial port selected in Configurator): The easiest way to do that is to download Zadig. The solution is to replace the ST driver with a libusb driver. A driver should be automatically installed by Windows for the ST Device in DFU Mode but this doesn't always allow access for Chrome. Platform Specific: Windows Ĭhrome can have problems accessing USB devices on Windows.
If you see the ttyUSB device appear and immediately disappear from the list in Betaflight Configurator when you plug in your flight controller via USB, chances are that NetworkManager thinks your board is a GSM modem and hands it off to the ModemManager daemon as the flight controllers are not known to the blacklisted. You can likely add your device ID to a blacklist configuration file to stop ModemManager from touching the device, if you need it for cellural networking, but that is beyond the scope of betaflight documentation. If your system lacks the systemctl command, use any equivalent command that works on your system to disable services. You can add yourself to this group as below: In order for Betaflight configurator to be able to access serial ports, your account needs to be in the dialout group. You need a proper USB cable to connect your board to the Betaflight Configurator. These will power up the board, so the leds light up, but the host computer will not react to the device at all. If you see no signs of life on your host computer when you plug in your board, check your cable with your mobile phone or some other USB device - some charging cables have only the power pins connected. The baudrate checkbox is ignored as it has no relevance to USB. The Full chip erase checkbox operates as normal. The "No reboot sequence" checkbox has no effect as the device will automatically be detected when already in bootloader mode (a DFU device will appear in the connect dropdown if this is the case). The standard flashing procedure should work successfully with the caveat of some platform specific problems as noted below. This is a straightforward process in Configurator versions 0.67 and newer. Some newer boards with full USB support must be flashed in USB DFU mode.