LibrePilot Forum
General Category => General Discussion => Topic started by: MARCMARC on February 13, 2019, 11:21:10 pm
-
Hello everybody !
I've got a puzzle problem. I CANNOT SAVE ANYTHING IN MY CC3D. (i have read lot of topics but i didn't find a solution)
What's happening ? :
*I configure my CC3D until the final test (without propellers). I activated the always armed mode for this test. But my level is not good, so i decided to restart all configuration.
I click on VEHICLE SETUP WIZARD, and at the end i can't save my settings.
I check the ESC are disarmed. I reinstalled librepilot on my windows 10. I rescue my CC3D. Erase all, and upgrade it.
So please, help me :'(
-
We have a lot of people complaining "Can't save settings on CC3D" :(
It is likely that some cloners are making them without the correct external flash chip, to save money. Most other firmware brands (e.g. Cleanflight and Betaflight) do not use the external flash chip to save settings, they use the CPU NV memory for that, and so they work fine. If that is the case, then you need to go to CF/BF/etc. The following assumes this is not the case and we will try to figure out how to fix it.
There are many threads about this on the LP forum. Many threads just stop with no reply as to whether or not the issue was fixed. One or two users say they finally gave up. One says he found a fix, but no one has posted a reply.
Please try this and please reply here when you finally fix it :) or finally give up. :(
Update: The following has been tried and did not fix the issue. Need to try Cleanflight V1.10 flash_erase command which fixed it for one user.
Unplug the board, go to Firmware page, press Rescue, then plug board in, (this is called Manual method in wiki) it will show you Firmware Tag, "git commit hash", and CRC for both the onboard firmware and the firmware bundled with the GCS. If all these match, then you are already running exactly what the GCS expects, so that isn't an issue. If something doesn't match then the firmware version and GCS version do not match, and you must upgrade the firmware to match the GCS but please continue reading.
If Firmware Tag (e.g. 16.09) matches exactly but the others don't, there may be custom firmware on it that you don't want to erase. Then you may want to post a screen capture and ask for advice before proceeding (flashing anything, bootloader or firmware). In any case, take a screen capture and post it if anything does not match. The information may help us, and the information is gone once you flash anything.
This Firmware page will also tell you what bootloader version you are running. You need bootloader version 4. If it is not version 4 then upgrade to version 4 using instructions below. Note that a normal bootloader upgrade from a bu_something.opfw file erases the firmware, leaving just the bootloader, so after upgrading the bootloader, you must upgrade firmware and you must use the Manual method to upgrade the firmware:
Please make a screen capture (of Firmware page while using the Rescue button / Manual method) before upgrading. :)
To upgrade bootloader:
https://librepilot.atlassian.net/wiki/spaces/LPDOC/pages/5669026/Firmware+Tab
To upgrade firmware after updating bootloader use Manual method on same page.
Unplug the board, go to Firmware page, press Rescue, then plug board in, press Erase Settings (then OK) and within 25 seconds, it will reconnect and FlightTime will start counting (from about 23) again. Wait till it gets up to at least say 120 (to make sure the erase is complete) and disconnect the board. (Waiting this long should not be necessary under normal circumstances.) This should erase the settings and there should be no error messages. Unplug the board and plug it back in to reboot it.
After that, go to Configuration -> Hardware. Change GPS Speed to 38400 and press Save. The Save button should turn into a Save button with a green check mark. Unplug the CC3D and plug it back in. When it connects in a few seconds (less than 10 for me) you should see that GPS Speed is still 38400. If it is 38400, you have proven that you can save and remember settings.
After Erase Settings, you could also try simply doing File -> ExportUAVSettings to a temp file, then File -> ImportUAVSettings from that same temp file (and press Save To Board Flash). Save To Board Flash takes a little less than 1 minute on my setup but you can see it count up during that minute.
Did it work? Was there an error somewhere? What error? There are other things to try.
-
İ have the same problem. I make the explained procedures step by step.Nothing changed. This problem started after 16.09 upgrade. İn 15.09 I havent this problem. For the test my board .I loaded 'betaflight_CC3D_OPBL.bin' fw by rescue-openfile-flash on the 16.09 libre. After I connect my board to the betaflight. It see the board and connected. I make some conf and I save my cc3d board. İt saved. I disconect the board after ı close the betaflight. I restart the beta ı connect the board all the conf ok.
Another test.
I turn back the 16.09 again. Re flash the board. Firmware tab says system healty. Board running but not save any conf. When ı am on the conf tab I changed gps and telemety speed 38400.I Saved. My save button red cross.But on the screen speeds is 38400. I export the uav settings to the Test.uav file . I opend the file by word pad. I check the gps and telemetry speed it is 38400. I import this file to my gcs .When importing İt says Writing to flash . When it come to %100 ı close the import tab. I check the gcs it is
38400. I disconnect the board and reconnect. gcs read the board settings and the values turn the 57600.
1-gcs says I am not able to save (red cross) but when I save the conf to the uav file new values (38400).New values saved to file. I see it in the word pad and the gcs conf tab.
2-When I import the uav file.gcs says I am writing the flash but dont write the flash
There is a chip close the mini port 'winbond 25016' ı think this the flash.
3-Betaflight can write the conf to the flash chip. We connot say chip is defected.
4-may be some wrong conf writing procedures in the Gcs. İt comes with the 16.09 release.(may be).This problem started on my board with 16.09.
5-Additional information: Board with 16.09 fw and boat loader .Runs on 15.09 and 15.02.02. 15.09 and 15.02 says this not my fw may be you have problem bla bla...
On this situation in the firmware tab compass running and says system healty.
both version connot save any conf to board.
6-After the 16.09 upgrade my board can run only 16.09 fw . 15.09 and 15.02.02 fw cannot run the board. No cominication.I tryed many thing Bl files bu files bin files.I have no cominication with the board except 16.09.
-
I make the explained procedures step by step.Nothing changed.
What was the first error that you saw?
I make the explained procedures step by step. ... For the test my board .I loaded 'betaflight_CC3D_OPBL.bin' fw by rescue-openfile-flash on the 16.09 libre.
I do not know if this bootloader is correct. We did not make it. The explained procedure uses the bu_cc3d.opfw bootloader file from the LibrePilot wiki (link in the explained procedure above) so that we know the bootloader is correct. I do not know that the bootloader you used can cause this problem, but I request that you use the bootloader that LibrePilot made for these tests.
After I connect my board to the betaflight. It see the board and connected. I make some conf and I save my cc3d board. İt saved. I disconect the board after ı close the betaflight. I restart the beta ı connect the board all the conf ok.
Another test.
I turn back the 16.09 again. Re flash the board. Firmware tab says system healty. Board running but not save any conf.
...
Sorry. It seems you didn't follow the instructions which say to Erase Settings before testing any kind of save settings. If you would please try again and follow instructions exactly. :)
There is a chip close the mini port 'winbond 25016' ı think this the flash.
3-Betaflight can write the conf to the flash chip. We connot say chip is defected.
Most other firmware brands (e.g. Cleanflight and Betaflight) do not use the external flash chip to save settings, they use the CPU NV memory for that, and so they work fine.
Also, I think that is probably 'Winbond 25Q16' from some Google searches. That is good information. Mine is a different brand 25P16... chip. The important part is 2516. It might be a bad run of chips, but at least it is supposed to be the correct chip. I think that Cleanflight/Betaflight use this chip for in flight logging so another test would be to run CF/BF and test the in flight logging.
It is quite common and possible for some versions of LibrePilot/OpenPilot to partially work when GCS and firmware are mismatched. It is also quite common and possible for some versions of LibrePilot/OpenPilot to fail to work when GCS and firmware are mismatched.
It would help if you would please try again, in order, using the instructions to:
- flash LibrePilot bootloader with file from LibrePilot wiki as described
- Upgrade firmware using Manual method as described
- Erase Settings as described
- Try to change and save baud rate as described
(with nothing else in between these tests)
This may or may not fix it. If it does not fix it, where did it first fail? There are other things we can test and ways around whatever failed. I thank you for your help in trying to fix this issue. :)
-
I make the explained procedures step by step.Nothing changed.
What was the first error that you saw?
I tested speed changing and I saw `red x` . before ı write.
Quote from: batur can on February 27, 2019, 12:47:54 pm
I make the explained procedures step by step. ... For the test my board .I loaded 'betaflight_CC3D_OPBL.bin' fw by rescue-openfile-flash on the 16.09 libre.
I do not know if this bootloader is correct. We did not make it. The explained procedure uses the bu_cc3d.opfw bootloader file from the LibrePilot wiki (link in the explained procedure above) so that we know the bootloader is correct. I do not know that the bootloader you used can cause this problem, but I request that you use the bootloader that LibrePilot made for these tests.
Yes you did not make it. Betaflight made it for the betaflight software. For test my board under betaflight software I loaded. I tested my boad with BF. İt runs withouth Problem. After I returned back the bu_cc3d.opfw . All my lıbre test done with this bootloader.
Quote from: batur can on February 27, 2019, 12:47:54 pm
After I connect my board to the betaflight. It see the board and connected. I make some conf and I save my cc3d board. İt saved. I disconect the board after ı close the betaflight. I restart the beta ı connect the board all the conf ok.
Another test.
I turn back the 16.09 again. Re flash the board. Firmware tab says system healty. Board running but not save any conf.
...
Sorry. It seems you didn't follow the instructions which say to Erase Settings before testing any kind of save settings. If you would please try again and follow instructions exactly. :)
I do it may be 10 times. Ereas without erase . I tried every posibility . I will do it again for you :)
Quote from: batur can on February 27, 2019, 12:47:54 pm
There is a chip close the mini port 'winbond 25016' ı think this the flash.
3-Betaflight can write the conf to the flash chip. We connot say chip is defected.
Quote from: TheOtherCliff on February 14, 2019, 04:43:18 am
Most other firmware brands (e.g. Cleanflight and Betaflight) do not use the external flash chip to save settings, they use the CPU NV memory for that, and so they work fine.
I think Libre must use the same place (cpu nv memory).Because conf security is important. There is a faisafe tab (option) on the software. But conf is not saving a failsafe area :). Conf file is important. Without conf ,Failsafe and other tabs is not important. Because board it not work without settings. If CF BF using the cpu NV. You use both (Cpu NV and external flash). Redundancy is the best. Especially for the settings.
Also, I think that is probably 'Winbond 25Q16' from some Google searches. That is good information. Mine is a different brand 25P16... chip. The important part is 2516. It might be a bad run of chips, but at least it is supposed to be the correct chip. I think that Cleanflight/Betaflight use this chip for in flight logging so another test would be to run CF/BF and test the in flight logging.
It is quite common and possible for some versions of LibrePilot/OpenPilot to partially work when GCS and firmware are mismatched. It is also quite common and possible for some versions of LibrePilot/OpenPilot to fail to work when GCS and firmware are mismatched.
I will try again fallowing order. And I will return back to you.İn Addition I will buy one pieces 25q16 chip ant I will try replace the chip.
It would help if you would please try again, in order, using the instructions to:
- flash LibrePilot bootloader with file from LibrePilot wiki as described
- Upgrade firmware using Manual method as described
- Erase Settings as described
- Try to change and save baud rate as described
(with nothing else in between these tests)
This may or may not fix it. If it does not fix it, where did it first fail? There are other things we can test and ways around whatever failed. I thank you for your help in trying to fix this issue. :)
-
Hi I made your procedure again result is same . RED X . I attached some pictures.
I found an error I think. After save and responce red X .Same time system healty display give some errors. It escape from my attention before. I am sending to you. I booted the board manualy errors lost from the system healty display. I save conf again . İt come back to system healty display.
-
I buy the chips :). My scenario for errors: When I push the save button. In the background board trying boot operation 3 times. If ıt cant handle this boot operation. Sytem healty panel give this errors.Trying boot ıs ıt normal ı dont know. May be natural for set the new config. But this is strictly related with this saving error.
-
Hi I replace the chip . And I do your procedure again. Result is same.
-
I faund another similar error on the system healty screen. All is green except input and output. This normal in my stuation. When I try the erease setting button. Red boot alert coming again. I tink this mean is software or fw cannot write access to flash. Or cannot boot the board. Board manualy booting and running with new flash.
-
Boot alarm is normal, every change in hardware need a reboot.
Input and output in red are also normal because nothing configured.
Try formatting the "SD card" used for logging when you are running Cleanflight/Betaflight and go back to LP.
-
Why it says `system has failed to boot more than three times:system defaults have been set`?.
-
Why it says `system has failed to boot more than three times:system defaults have been set`?.
This is misleading. It can be caused by watchdog causing "system has failed to boot more than three times" or it can simply mean that you changed settings and should reboot.
I buy the chips :). My scenario for errors: When I push the save button. In the background board trying boot operation 3 times. If ıt cant handle this boot operation. Sytem healty panel give this errors.Trying boot ıs ıt normal ı dont know. May be natural for set the new config. But this is strictly related with this saving error.
Normal LED for my CC3D is blink status LED a little faster than once per second. When I press Save (38400 baud), there is absolutely no change in LEDs.
Are you saying that yours seems to reboot (like power on LEDs) 3 times when you press Save?
There is a watchdog timer in the CPU. If the main firmware code does not reset this watchdog every 250 milli seconds then the CPU will be rebooted. If the watchdog reboots the CPU over and over, then after the 3rd reboot it will temporarily load default conf settings and boot up with default settings. You can see this if you watch the status LED when you power on the CC3D. If you get a long blink then short pause and it does this over and over (3 times), then the watchdog is temporarily resetting the conf on each boot.
And here are some close up pictures of my CC3D so you can compare IC part numbers. I would especially look at the CPU part number and make sure there are no solder blobs or broken traces. Some CC3D cloners have been known to use a cheaper CPU type or to use early CPU revisions that have known bugs.
-
BF says your fw not support to logging. I am using 3.2.5 betaflight fw. If we do this for testing the flash. This is new flash chip. This board before running 15.09 after 16.09 I have this mistake. İf you strongly believe this an hardware error. I will change the cpu next week. Cpu driving the flash .We cahanged the flash .
-
Why it says `system has failed to boot more than three times:system defaults have been set`?.
This is misleading. It can be caused by watchdog causing "system has failed to boot more than three times" or it can simply mean that you changed settings and should reboot.
Yes. But it is not able to boot and loading the default settings. Why it is not booting . İs it software or hw error. This card is not new it is upgrade from 15.09 to 16.09. If I will able to run this card.İ will not load again16.09 İ will continue with 15.09.
Quote from: batur can on Today at 02:56:27 pm
I buy the chips :). My scenario for errors: When I push the save button. In the background board trying boot operation 3 times. If ıt cant handle this boot operation. Sytem healty panel give this errors.Trying boot ıs ıt normal ı dont know. May be natural for set the new config. But this is strictly related with this saving error.
Normal LED for my CC3D is blink status LED a little faster than once per second. When I press Save (38400 baud), there is absolutely no change in LEDs.
Are you saying that yours seems to reboot (like power on LEDs) 3 times when you press Save?
There is a watchdog timer in the CPU. If the main firmware code does not reset this watchdog every 250 milli seconds then the CPU will be rebooted. If the watchdog reboots the CPU over and over, then after the 3rd reboot it will temporarily load default conf settings and boot up with default settings. You can see this if you watch the status LED when you power on the CC3D. If you get a long blink then short pause and it does this over and over (3 times), then the watchdog is temporarily resetting the conf on each boot.
Ok . system healty monitor says:`help me watchdog reboots me over an over . I am returning the default ` and red alert. Why the watchdog doing this. Because software says reboot it.I dont thing an hw error for this secenario. you write main fw code do this. if you are an development partner in this project please talk this situation with the responsible person.
And here are some close up pictures of my CC3D so you can compare IC part numbers. I would especially look at the CPU part number and make sure there are no solder blobs or broken traces. Some CC3D cloners have been known to use a cheaper CPU type or to use early CPU revisions that have known bugs.
I write before This not a new card. I check the cpu it is st32f103 .Flash is difrent 25q16. I write the f5soh user if you believe this is an hardware error i will change the cpu next week. And i will try to check write protection leg (leg3) of the flash chip.
-
BF says your fw not support to logging. I am using 3.2.5 betaflight fw.
Look this post (https://forum.librepilot.org/index.php?topic=4492.msg30885#msg30885) for 'flash_erase' command, using CLI console.
-
I returned to libre now. i will test it. Thanks.
-
Another test:
On the vehicle tab I made a simple Car configuration.One motor and one servo. I saved. nuturaly red x. I dont care it. I continue with output conf. I saw motor and servo slider came to the output tab. I made a min max setup.And I saved .
I have red x again on the save button. I dont care it. I connected esc and servo to the configured channels.On the output tab. I clicked live test. I tested the sliders for the motor and servo. Motor and servo running without problem. I can say this an saving to flash isue. Who created this İsue . I dont know.May be Fw maybe Murphy. I hope Murphy do it. I will change cpu next week. Because i changed flash before. I checked flash leg connections all is ok.
-
Hi I am writing this for the f5soh user. You give an procedure to me for erease the flash under BF. I have a `st flash loader` utl. Before I load the fw by this utl I erease the flash more 10 times. I think This is same with the BF flash erease. İf you are thinking not same. I can do it again with BF.
-
Erasing flash using the ST-Util do nothing to the 2516 flash device i think, only CPU related...
BF flash erase will format the 2516 device, if you look the post i linked this solved the issue.
-
Ok. I will do it.
-
I do your suggestion. But result is same. I attached the pics. This libre 16.09 dont write the flash.
-
It is interesting that flash_info says that size is zero.
BF says your fw not support to logging.
In your flash_erase test did you use the exact Cleanflight GCS and firmware version (V1.10) from successful user pointed at by @f5soh?
(Since you already replaced the flash chip) It seems that one of these is probably true:
- solder blob
- connection not soldered
- bad / broken trace
- incorrect board traces design
- bad CPU chip
- wrong or missing components (such as flash CS pullup or voltage regulator)
- your version of BF does not access the external flash chip
- bad voltage regulator
After using Cleanflight V1.10 I would probably use CC3D schematic and a volt ohm meter to check the CPU to flash connections (or I think you maybe already did) and a few other things like flash CS pullup value (R17 should be 10K) and VCC. CC3D schematic can be found at "hardware/Production/CopterControl 3D/CopterControl 3D Schematic.pdf"
(not saying the following is the problem, just information for you) Some Sparky2 FC boards have a problem with baro chip. It turns out that the reason is that clone board maker used different voltage regulator. That would have been OK, but the different voltage regulator needed a different capacitor for it's precision voltage reference source and made bad power with the incorrect capacitor.
-
Ok . This is hw error I think. I will check some of these . If I have not find anything else.I will buy a new board. I will use it with 15.09. I am not clear about 16.09 fw. Thank you for your information.
-
OK. Thank you for your testing. I am guessing that you didn't use Cleanflight V1.10 flash_erase, so someone still needs to test that.
-
Flash_erase command says erasing and wait aprox 2 sec.After it says done. I think it is erasing the flash. But ı will try to test with 1.1 .
-
It may or may not make a difference, but please make sure to use Cleanflight V1.10 like the guy who had success. :)
Not Betaflight V1.1
And indeed V1.10 usually comes after v1.9 and I am guessing that is what that guy meant.
-
Even my CC3d could not save. I performed the albertferraz procedure:
1 - Download Firmware Cleanflight V 1.10.
2 - Install the drivers indicated for your card
3 - Connect with Cleanflight
4 - At the command line of the CF type "flash_erase"
5 - Return to LibrePilot and do the normal process of installing the firmware
To be precise, I used the Cleanflight configurator version 1.10 and showed the Gyro and Accel icons in red. The cc3d has now saved the configuration. Thank you
-
Hello everybody !
I've got a puzzle problem. I CANNOT SAVE ANYTHING IN MY CC3D. (i have read lot of topics but i didn't find a solution)
What's happening ? :
*I configure my CC3D until the final test (without propellers). I activated the always armed mode for this test. But my level is not good, so i decided to restart all configuration.
I click on VEHICLE SETUP WIZARD, and at the end i can't save my settings.
I check the ESC are disarmed. I reinstalled librepilot on my windows 10. I rescue my CC3D. Erase all, and upgrade it.
So please, help me :'(
Tengo exactamente el mismo problema Se queda en guardando configuración y se bloquea. Actualmente tengo tres placas cc3d y a todas les pasa lo mismo
-
Please try the albertferraz procedure just above your first post. And please please let us know if it fixes your problem or not.
Also very important! What other firmware did you run, and what settings, that broke it this way (so developers can make the problem happen and program the fix).
-----------------------------------------
Vía el traductor de Google
Por favor, intente el procedimiento de albertferraz justo por encima de su primera publicación. Y por favor, háganos saber si soluciona su problema o no.
¡También muy importante! ¿Qué otro firmware ejecutó y qué configuración se rompió de esta manera (para que los desarrolladores puedan resolver el problema y programar la solución)?
-
Please try the albertferraz procedure just above your first post. And please please let us know if it fixes your problem or not.
Also very important! What other firmware did you run, and what settings, that broke it this way (so developers can make the problem happen and program the fix).
-----------------------------------------
Vía el traductor de Google
Por favor, intente el procedimiento de albertferraz justo por encima de su primera publicación. Y por favor, háganos saber si soluciona su problema o no.
¡También muy importante! ¿Qué otro firmware ejecutó y qué configuración se rompió de esta manera (para que los desarrolladores puedan resolver el problema y programar la solución)?
Disculpe pero no se quien es alberferraz. He hecho todas las pruebas que se exponen en este foro y sigue igual. Hay que comentar, que todas las placas funcionaron en una primera prueba. Al efectuar la segunda ocurrio el problema y ya no se resolvió. El soft de arranque es el cc3d BL 4 y el firmware el 16.09 de la pagina oficial de librepilot. He probado con la version 15.09 y ninguna de las placas la acepta
-
In the post just above your first post there is a set of instructions in English that I quoted.
In these instructions is the name albertferraz.
Two people with your problem have fixed it by following those instructions.
------------------------------------------
Vía el traductor de Google
En la publicación justo arriba de tu primera publicación hay un conjunto de instrucciones en inglés que cité.
En estas instrucciones se encuentra el nombre albertferraz.
Dos personas con su problema lo han solucionado siguiendo estas instrucciones.
-
In the post just above your first post there is a set of instructions in English that I quoted.
In these instructions is the name albertferraz.
Two people with your problem have fixed it by following those instructions.
------------------------------------------
Vía el traductor de Google
En la publicación justo arriba de tu primera publicación hay un conjunto de instrucciones en inglés que cité.
En estas instrucciones se encuentra el nombre albertferraz.
Dos personas con su problema lo han solucionado siguiendo estas instrucciones.
Gracias. Lo intento e informo del resultado
-
Via Google Translate
I have already been able to carry out the tests he told me on two of the three plates I have. At the moment they work correctly, saving the initial changes of the configuration. It is necessary to install it in the model, make all the programming and see how it works.
Thank you very much for the solution provided
------------------------------------------
Ya he podido efectuar las pruebas que me comento en dos de las tres placas que tengo. De momento funcionan correctamente, guardando los cambios iniciales de la configuración. Falta instalarla en el modelo, efectuar toda la programación y ver que tal funciona.
Muchas gracias por la solución aportada
-
Via Google Translate
I have already been able to carry out the tests he told me on two of the three plates I have. At the moment they work correctly, saving the initial changes of the configuration. It is necessary to install it in the model, make all the programming and see how it works.
Thank you very much for the solution provided
------------------------------------------
Ya he podido efectuar las pruebas que me comento en dos de las tres placas que tengo. De momento funcionan correctamente, guardando los cambios iniciales de la configuración. Falta instalarla en el modelo, efectuar toda la programación y ver que tal funciona.
Muchas gracias por la solución aportada
Via Google Translate
I have already been able to try the third plate that I have. All of them have recovered again after following the albertferraz procedure.
What now happens in all of them, is that they work well the first time, a second time too, but from there, in a third or fourth test they become blocked, having to redo the procedure to make them work. I do not know what else can happen to them?
What I do not know, if at first I load the configuration that I want and install it in the model, if it can give me some flight problem, or only affect the initial configuration procedure. Is there any response?
----------------------------------------------------------------------------
Ya he podido probar la tercera placa que tengo. Todas ellas se han vuelto a recuperar después de seguir el procedimiento de albertferraz.
Lo que ahora pasa en todas ellas, es que funcionan bien una primera vez, una segunda también, pero a partir de ahi, en una tercera o cuarta prueba se vuelven a quedar bloqueadas, teniendo que volver a efectuar el procedimiento para que funcionen. No se que mas les puede pasar?
Lo que no se, si en una primera vez cargo la configuracion que deseo y la instalo en el modelo, si me puede dar algun problema de vuelo, o sólo afecta al procedimiento de configuracion inicial. ¿Hay alguna respuesta al respecto?
-
Via Google Translate
It seems that the problem is finally solved, or this I hope and that nothing else comes out.
As I said, when applying the albertferraz procedure, the blocked plates work correctly again.
The fact that they were blocked again after a couple or three attempts, I discovered that it happened because in each test towards the upgrade, without necessity. It is possible that the flash memory will be filled and blocked until the unblocking procedure is performed again.
Now you just need to make the final configuration and perform the flight test
-------------------------------------------------------------------------------------------------
Parece que por fin esta resuelto el problema, o esto espero y que no salga nada más.
Como decía, al aplicar el procedimiento de albertferraz, las placas bloqueadas vuelven a funcionar correctamente.
El hecho de que se volviesen a bloquear al cabo de un par o tres de intentos, he descubierto que pasaba porque en cada prueba hacia el upgrade, sin necesidad. Es posible que se llenara la memoria flash y quedara bloqueada hasta de nuevo hacer el procedimiento de desbloqueo.
Ahora sólo hace falta hacer la configuración definitiva y efectuar la prueba de vuelo
-
There are two things I have heard can cause failure to save settings in CC3D in LibrePilot:
1 - Enabling flight side logging in LibrePilot (not common).
2 - Running some specific other brand of flight software and doing some thing with it (that writes some data to the external flash chip) that LibrePilot does not like.
Did you do either of these?
-
Via Google Translate
No, he had not done either of these two actions.
The problem appeared to me when testing the plate several times making the upgrade in each test, until the second or third test was blocked and without possibility of use.
When offering me the solution of the flash_erase of the Cleanflight, the plates returned to work, I loaded the firmware of Librepilot again, I made only an upgrade and every time I have tried them again they work correctly, keeping the data that I have configured.
Thanks for the solution provided
---------------------------------------------------------
Pues no, no había efectuado ninguna de estas dos acciones.
El problema me aparecía al probar la placa varias veces efectuando en cada prueba el upgrade, hasta que a la segunda o tercera prueba quedaba bloqueada y sin posibilidad de uso.
Al ofrecerme la solución del flash_erase del Cleanflight, las placas volvieron a funcionar, cargue de nuevo el firmware de Librepilot, hice solo un upgrade y cada vez que las he vuelto a probar funcionan correctamente, guardando los datos que he configurado.
Gracias por la solución aportada
-
The next time the problem happens, try using LibrePilot "Firmware -> Halt" then "Erase Settings" then "Reset" to see if it corrects the problem. After pressing OK, in "Erase Settings" it is especially important to wait for the board to restart. Restart takes about 30 seconds and then you will see that the board reconnects to USB / GCS. Pressing "Reset" after that clears the red Boot alarm.
Please please once you have the problem again, post back to tell us if this LibrePilot erasing fixes the problem or not.
Information:
There are only a limited number of flash data blocks. They can each be used once. After changing many settings several times, they run out and you must Erase Settings to make them fresh again.
-------------------------------------------------------
A través de Google Translate con un poco de ayuda
La próxima vez que ocurra el problema, intente utilizar LibrePilot "Firmware -> Detener (Halt)", luego "Borrar configuración" (Erase Settings) y luego "Reiniciar" (Reset) para ver si corrige el problema. Después de presionar OK, en "Borrar Configuraciones" es especialmente importante esperar a que el tablero se reinicie. El reinicio tarda aproximadamente 30 segundos y luego verá que la placa se vuelve a conectar a USB / GCS. Al presionar "Restablecer" (Reset), se borra la alarma de Arranque (Boot) roja.
Por favor, por favor, una vez que tenga el problema otra vez, contáctenos para informarnos si este borrado de LibrePilot soluciona el problema o no.
Información:
Sólo hay un número limitado de bloques de datos flash. Cada uno puede ser usado una vez. Después de cambiar muchas configuraciones varias veces, se agotan y debe borrar las configuraciones para que se actualicen de nuevo.
-
I have caused the blockage of the plate based on the wizard twice and in each of them perform the upgrade.
Following this new procedure, which in each step is done correctly, when doing the wizard again, when you reach the screen (configuration ready to save) and want to save (save) a message (preparing mixer settings), until this message turns red and the plate is blocked again.
I understand that I should redo the albertferraz procedure, which although it is more laborious, if it gives good results
-------------------------------------------------------
He provocado el bloqueo de la placa en base a efectuar el wizard 2 veces y en cada una de ellas efectuar el upgrade.
Siguiendo este nuevo procedimiento, que en cada uno de los pasos lo efectua correctamente, al volver a efectuar el wizard, al llegar a la pantalla de (configuration ready to save) y querer guardar (save) sale un mensaje (preparing mixer settings), hasta que este mensaje se pone de color rojo y vuelve a quedar bloqueada la placa.
Entiendo que debere de volver a efectuar el procedimiento de albertferraz, que aunque es mas laborioso, si que da buenos resultados
-
I believe you are saying that you tried the LibrePilot Erase Settings procedure that I suggested and that it did not fix the problem. At that point you used the albertferraz procedure and it did fix the problem.
-
Via Google Translate
That's right, with the LibrePilot Erase Settings it does NOT work for me. Using the albertferraz works OK
-------------------------------------------
Así es, con el Librepilot Erase Settings NO me funciona. Usando el de albertferraz funciona OK
-
You have 3 boards that do this?
Did you buy them recently?
Where did you buy them?
I want to buy one so that I can try to program a fix for LibrePilot. I am guessing that we are not erasing for a long enough time.
Thanks for all your help with this.
-
Via Google Translate
The same thing happens to me in the three plates that I have.
I bought them about 1 month ago.
Two of the plates are from the company LHI POER purchased through Amazon. The first one was blocked and they kindly sent me another one without charge, which also got blocked.
The third of the company UP UP 3C DIGITAL STORE purchased through Aliexpres that also blocked.
What I appreciate when doing the procedure, is that when you give the OK to effecue the deletion, it does not take even 10 seconds to have communication with Librepilot again.
If you need any other proof, I am at your disposal.
----------------------------
Me pasa lo mismo en las tres placas que tengo.
Las compre hace aproximadamente 1 mes.
Dos de las placas son de la empresa LHI POER compradas a traves de Amazon. La primera se me bloqueo y ellos muy amablemente me enviaron otra sin cargo, que tambien se bloqueo.
La tercera de la empresa UP UP 3C DIGITAL STORE comprada a traves de Aliexpres que tambien se bloqueo.
Lo que aprecio al efectuar el procedimiento, es que al darle al OK para que efecue el borrado, no tarda ni 10 segundos en volver a tener comunicacion con Librepilot.
Si precisan de alguna otra prueba estoy a su disposicion.
-
Is this the one you bought from Amazon?
https://www.amazon.co.uk/LHI-Openpilot-Source-Controller-Processor/dp/B015SRUI38
-
Si es esta misma la que compre yo a través de Amazon
-
Hi I've found a solution to CC3D not saving the settings.
It does not save if the FC is armed. In my case "always armed" option unabled me to save at all.
What worked for me was switching to "always disarmed" mode when doing any changes to be saved.
-
Indeed, it's a known design consideration that you can't change settings when it's armed. That has caused me minor heartburn in the past too. :)
I verified that you can still Erase Settings when it is set to Always Armed (and actually armed; you need a valid input set up for instance for it to actually arm when set to Always Armed) (you have to use Rescue in this case), so this isn't the cause of the original issue of "CC3D can't Erase Settings and CC3D mixer error when running setup (caused by can't Erase Settings)"
Under some very untypical conditions, the CC3D settings memory gets full and the only way to make changes is to first erase the current settings. I have tried to fill CC3D settings memory and have not been successful.