Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Issue with Aux/Mode CLI restore. #229

Closed
oleost opened this issue May 19, 2016 · 13 comments · Fixed by iNavFlight/inav-configurator#7
Closed

BUG: Issue with Aux/Mode CLI restore. #229

oleost opened this issue May 19, 2016 · 13 comments · Fixed by iNavFlight/inav-configurator#7

Comments

@oleost
Copy link
Contributor

oleost commented May 19, 2016

When restoring from CLI dump the Aux / mode is not correctly restored.

What I need to do to get it restored correctly is copy and save cli dump, and then copy aux only and save.

This has been for awhile. atleast back to April 02.

Board = SPRACINGF3
How to try it yourself.

Try and copy and save this CLI dump http://pastebin.com/6awLdti6 (Airplane mixer)

Watch your missing some modes. In my case I only had NAV POSHOLD, NAV RTH and PASSTHRU set aftert first restore.

Paste in only the Aux channels: http://pastebin.com/J6GDXuH2

And hit save, and then the rest of the modes are there aswell. (Arm, Horizon, Airmode)

I know I'm not the only one, here is another guy aswell: http://www.rcgroups.com/forums/showpost.php?p=34422766&postcount=4622

@theArchLadder
Copy link
Contributor

I have also had this problem, but for me it's even worse:
Some of the settings are not set when i paste in a full dump. I have not noticed any patterns yet, what settings are not set seems a bit random.

Is the configurator to fast so the FC can't keep up or something?

@DzikuVx
Copy link
Member

DzikuVx commented May 19, 2016

I also had similar issue. Also modes config. Also SPRF3

@oleost
Copy link
Contributor Author

oleost commented May 19, 2016

@theArchLadder Think thats an different issue. Had it once and after a reflash that issue was gone. The symptons was that it was slow when I copied it in CLI. Normally its lighting fast when coping stuff into CLI.

@theArchLadder
Copy link
Contributor

theArchLadder commented May 19, 2016

@oleost I have had it multiple times.
My aux/flight modes has sometimes been only partially restored

EDIT: Good to know that it was slow when it happend, i will remember that to next time.

@sppnk
Copy link
Contributor

sppnk commented May 19, 2016

I dont know if it is the same issue, but with cc3d and naze, sometimes after a reset (no after a flashing or restotring) I lost all the mode configurations.

And other times everything go sloooow, I have to reset and then everything go fine.

@stronnag
Copy link
Collaborator

This is a well known feature of all CF firmware variants, the firmware cannot process mode changes fast enough, the buffer overflows, data is lost. This is why the mwptools cf-cfi (cli backup / restore tool) uses a baud rate and context aware inter-line delay. Slower than pasting into a terminal, but reliable.

Otherwise paste in small batches, particularly for the aux section.

@theArchLadder
Copy link
Contributor

@stronnag How about adding something similar to the iNav configurator?

@stronnag
Copy link
Collaborator

You are the second person to ask! I really don't do javascript. But it is possible that something simple like a fixed 25ms delay after each new line would help.

@theArchLadder
Copy link
Contributor

sudo @stronnag do javascript 😜
Have you tried if only using a lower baud rate helps?

@stronnag
Copy link
Collaborator

not tried that. lowering the baud rate becomes a real mess, both to flash and after as it's back to 115200, so you have to remember to change it on the FC, then in the tool.

@DzikuVx
Copy link
Member

DzikuVx commented May 20, 2016

@stronnag @theArchLadder @oleost please give a try to iNavFlight/inav-configurator#7

@oleost
Copy link
Contributor Author

oleost commented May 20, 2016

I just tested and confirm it worked. nice fix!

@DzikuVx
Copy link
Member

DzikuVx commented May 20, 2016

OK, since this seems to be configurator issue after all, I'm closing this one. Please refer to iNavFlight/inav-configurator#6 for further discussion

@DzikuVx DzikuVx closed this as completed May 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants