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

Accelerometer calibration leads to config reset on Omnibus F4 Pro V3 board (INAV 2.2) #4891

Open
etulupov opened this issue Jul 1, 2019 · 6 comments

Comments

Projects
None yet
5 participants
@etulupov
Copy link

commented Jul 1, 2019

Current Behavior

Accelerometer calibration leads to config reset.

Steps to Reproduce

  1. Start accelerometer calibration process
  2. Perform several calibration steps.

Calibration is not completed. Observed FC restart and after boot up configuration is empty. It's restored to the factory defaults.

Expected behavior

Calibration should be successful and config should be persisted.

Additional context

INAV 2.1 works as expected.

@issue-label-bot issue-label-bot bot added the BUG label Jul 1, 2019

@issue-label-bot

This comment has been minimized.

Copy link

commented Jul 1, 2019

Issue-Label Bot is automatically applying the label BUG to this issue, with a confidence of 0.96. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@rrk1

This comment has been minimized.

Copy link

commented Jul 1, 2019

I can confirm that was happened once with 2.1 too. INAV 2.1 + configurator 2.1.4

Exactly, config was reset to default after acc calibration attempt initiated in configurator page. May be I have tried to calibrate different sides not in default sequence. Target was DYSF4PROV2 (or maybe MATEKF405)

@teckel12

This comment has been minimized.

Copy link
Contributor

commented Jul 1, 2019

I believe you need to do it in the correct sequence or it won't work.

@sam2b

This comment has been minimized.

Copy link

commented Jul 2, 2019

@teckel12 and the config reset? That is the actual problem stated.

I had the exact same problem (a config reset) during the accelerometer calibration with 2.2.0 on a new Matek F722SE flight controller.

@rrk1

This comment has been minimized.

Copy link

commented Jul 2, 2019

Additional problem with acc calibration sequence (possibly worth opening another issue) is that steps 3 and 5 are hard to do properly on asymmetrical hex frame like RD290 because it does not have a good axial reference. Wiki says 'the algorithm does not care about exact positions as long as they are close to 90 degree apart' but it was never stated how close to 90 degrees is okay,

@giacomo892

This comment has been minimized.

Copy link
Collaborator

commented Jul 2, 2019

The configuration reset happens when you start the procedure but you don't finish it.
That might have to be fixed indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.