Hello

is adviced do fw upgrade when available ?

i see that on my drone i have 4.2.2 version of betaflight !

after a fw update i will lose all configuration ?


i find a movie on youtube that do that proces for my drone, looks easy:
https://youtu.be/LDysmm3JoN8?t=854

You can safely upgrade from Betaflight 4.2.2 to Betaflight 4.2.9 if you want to. If you do so you will get any bug fixes and small enhancements that were made between Betaflight 4.2.2 and 4.2.9.

First run both the "dump all" and "diff all" commands in the Betaflight Configurator and save the output to files on your computer. Then flash Betaflight 4.2.9 firmware using the GEPRCF405 target ensuring that you have "Full chip erase" switched on. Then connect Betaflight Configurator to your FC and click on the "Apply Custom Defaults" button when the prompt to do so appears. Then go to the CLI tab and copy/paste everything from the "diff all" file you saved into the CLI text box and press <ENTER>. That is all

(07-Aug-2021, 10:53 AM)SnowLeopardFPV Wrote: You can safely upgrade from Betaflight 4.2.2 to Betaflight 4.2.9 if you want to. If you do so you will get any bug fixes and small enhancements that were made between Betaflight 4.2.2 and 4.2.9.

First run both the "dump all" and "diff all" commands in the Betaflight Configurator and save the output to files on your computer. Then flash Betaflight 4.2.9 firmware using the GEPRCF405 target ensuring that you have "Full chip erase" switched on. Then connect Betaflight Configurator to your FC and click on the "Apply Custom Defaults" button when the prompt to do so appears. Then go to the CLI tab and copy/paste everything from the "diff all" file you saved into the CLI text box and press <ENTER>. That is all

thanks for reply

1) does i have to keep in consideration also the configurator vesion ?

already in the past i did the copy of  "dump all" and "diff all" and also of that backup file: "BTFL_backup_20210805_112355.json".

2)what is the difference between these two ways to save configuration ?


3)but when i go to reset i will have "Custom Defaults" , why is necessary restore again "dump all" and "diff all" configuration ? i think that on my drone there is not been a tuning by eachine and so far i didn't made many changes.

i saw some video where people prefer do screenshot and later do any configuration manually.

1) Just use the latest release version of the configurator (10.7.0). It supports the current version and any previous versions of the firmware.

2) "dump all" outputs/saves the complete configuration. "diff all" outputs/saves any differences between the custom default values and the the current configuration (i.e. anything you have changed).

3) Custom Defaults is the base configuration for a specific Betaflight target. If you make any of your own changes such as ports, receiver configuration, OSD, rates, PIDs etc. then doing a reset will clear all of those back to the original Custom Defaults. So if you don't save a "diff all" before doing a reset you will have no way to restore your own changes. So always save a "diff all" before changing anything so you can always restore your previous configuration settings if you need to.

Not all settings are in the Betaflight Configurator GUI. Some settings are only in the CLI, so if you only take screenshots you can miss some settings. A "dump all" will contain a record of ALL the configuration values from both the GUI and the CLI. That is why we generally ask for a dump of your settings instead of screenshots when trying to help with issues.

(07-Aug-2021, 08:05 PM)SnowLeopardFPV Wrote: 1) Just use the latest release version of the configurator (10.7.0). It supports the current version and any previous versions of the firmware.

2) "dump all" outputs/saves the complete configuration. "diff all" outputs/saves any differences between the custom default values and the the current configuration (i.e. anything you have changed).

3) Custom Defaults is the base configuration for a specific Betaflight target. If you make any of your own changes such as ports, receiver configuration, OSD, rates, PIDs etc. then doing a reset will clear all of those back to the original Custom Defaults. So if you don't save a "diff all" before doing a reset you will have no way to restore your own changes. So always save a "diff all" before changing anything so you can always restore your previous configuration settings if you need to.

Not all settings are in the Betaflight Configurator GUI. Some settings are only in the CLI, so if you only take screenshots you can miss some settings. A "dump all" will contain a record of ALL the configuration values from both the GUI and the CLI. That is why we generally ask for a dump of your settings instead of screenshots when trying to help with issues.

Oh thank you so much 

1) But sometimes (maybe not in my case) can happen that when you recive the drone the factory did already some tune to default betaflight settings ?

2) how i have to do to restore the the dump all configuration ? in that case, considering that my current configuration is stock betaflight without any change by eachine i could also don't restore the "dump all" configuration.

(08-Aug-2021, 07:14 PM)Rosssiiii Wrote: 1) But sometimes (maybe not in my case) can happen that when you recive the drone the factory did already some tune to default betaflight settings ?

2) how i have to do to restore the the dump all configuration ? in that case, considering that my current configuration is stock betaflight without any change by eachine i could also don't restore the "dump all" configuration.

1) Yes, sometimes the manufacturer applied custom settings and tuning (PIDs / filters) to their quads.

2) If you are restoring configuration to exactly the same version of Betaflight on the same quad then you can restore either a "diff all" or a "dump all". Restoring a "diff all" is faster and more efficient. If you are restoring to a different revision of Betaflight (i.e. 4.2.4 to 4.2.9) then it is always safest to restore a "diff all". If you are restoring to a different minor version of Betaflight (i.e. 4.1.x to 4.2.x) you need to do a selective restore of parts of a "diff all" that are compatible with that other version.

(08-Aug-2021, 07:25 PM)SnowLeopardFPV Wrote: 1) Yes, sometimes the manufacturer applied custom settings and tuning (PIDs / filters) to their quads.

2) If you are restoring configuration to exactly the same version of Betaflight on the same quad then you can restore either a "diff all" or a "dump all". Restoring a "diff all" is faster and more efficient. If you are restoring to a different revision of Betaflight (i.e. 4.2.4 to 4.2.9) then it is always safest to restore a "diff all". If you are restoring to a different minor version of Betaflight (i.e. 4.1.x to 4.2.x) you need to do a selective restore of parts of a "diff all" that are compatible with that other version.

i went for the update of the fw but something is not working as i expected !

i selected the fw for my FC:
https://i.imgur.com/pvqSYDp.png

but as soon as i clicked on flash firmware is appeared that Windows Notification:
https://i.imgur.com/BuGyfzc.png

configuration of STM32 bootloader ;

but when is been completed it stucked !

and still remail wrote "inizio del riavvio nel bootloader"  mean  >>"start in rebooting the bootloader"

on drone fc any lights has stopped to work and com7 port used in the past don't looks anymore available :
https://i.imgur.com/zRuTBhS.png

what i have to do ?

maybe disconnect and reconnect the usb from FC, close betaflight and start the process once again ?

disconnect it, press the boot button of the fc, marked in pictures above, !while! connectinng to betaflight configurator.
your fc should be in "dfu" mode than, and you should be able to flash the firmware, or reflash it fresh.

(11-Aug-2021, 10:16 AM)hugnosed_bat Wrote: disconnect it, press the boot button of the fc, marked in pictures above, !while! connectinng to betaflight configurator.
your fc should be in "dfu" mode than, and you should be able to flash the firmware, or reflash it fresh.

So i have to press and keep it and connect to pc, after i can release.



does i have to select "no reboot sequence" i saw in a movie on youtube where for FC like mine where is required go in bood mode they select "no reboot sequence"?

https://i.imgur.com/uLCJcMz.png

After flash is completed does i have to disconnect drone and reconnecto to see it again in configuration mode ?

when completed that bar should be green:
https://i.imgur.com/VwtXR2c.png

Yes, you can release the boot button once the USB cable has been plugged in and the FC is powered up.

When putting the FC into boot mode manually it is usually best to switch off the "No reboot sequence" option.

If the FC hasn't come out of DFU mode after flashing, just disconnect and reconnect the USB cable without the boot button pressed down.

When you first connect Betaflight Configurator to the FC, make sure you click the "Apply Custom Defaults" button when prompted.

(11-Aug-2021, 10:48 AM)SnowLeopardFPV Wrote: Yes, you can release the boot button once the USB cable has been plugged in and the FC is powered up.

When putting the FC into boot mode manually it is usually best to switch off the "No reboot sequence" option.

If the FC hasn't come out of DFU mode after flashing, just disconnect and reconnect the USB cable without the boot button pressed down.

When you first connect Betaflight Configurator to the FC, make sure you click the "Apply Custom Defaults" button when prompted.

ok thank you so much for these informations to all of you !

now i selected "no reboot sequences" but is appeared another option:
https://i.imgur.com/0Yf1sQn.png

flasha alla connessione " > "flashes on connection" , does i keep it off ?

(11-Aug-2021, 10:52 AM)Rosssiiii Wrote: now i selected "no reboot sequences" but is appeared another option:
https://i.imgur.com/0Yf1sQn.png

flasha alla connessione " > "flashes on connection" , does i keep it off ?

Leave that option switched off.

(11-Aug-2021, 11:02 AM)SnowLeopardFPV Wrote: Leave that option switched off.

ok, i connected the fc pushing that botton and the only light (a green) that in the past was blinking now is off !

i used the programm zadig to see if it recognizes the device:
https://i.imgur.com/pHZbTmx.png

and it is been found, before when i connected the drone in normal way that don't was recognized even if i was able to see and connect in configuration using betaflight.

ok let me know if is normal that here there write "NONE" to driver interface:
https://i.imgur.com/wgaWmKP.png

and i will proceed with the flash .

----
edit: i tried to flash but is appeared that error message:

https://i.imgur.com/DXHL899.png

"nessuna risposta dal bootloader, programmazione fallita" >> "no response from bootloader, programming failed"


----
Anyway when i press the botton on FC and i open betaflight it use COM4 and not COM7 as in the past but still don't appear DFU !:
https://i.imgur.com/39pHbGJ.png

DFU will only appear if you press and hold the boot button while plugging in the USB cable.

What button are you pressing on the FC? And are you sure that you're holding it down fully while plugging in the USB cable?

(11-Aug-2021, 11:54 AM)SnowLeopardFPV Wrote: DFU will only appear if you press and hold the boot button while plugging in the USB cable.

What button are you pressing on the FC? And are you sure that you're holding it down fully while plugging in the USB cable?

yes i keep pushed down that botton: https://i.imgur.com/7ZfLDtZ.jpg until i heard the classic sound of windows that indicate you a device connected.

i could try holding it for a little longer.

But instead of COM4 it should be written DFU ?

on the FC there is not any red light that appear