Skip to content

[Feature Request] Auto-calibration overwrite manual calibration and causes excessive EEPROM writes, option to disable in launcher #470

@ArkeDev

Description

@ArkeDev

Feature Request Type

  • Core functionality
  • Add-on hardware support (eg. audio, RGB, OLED screen, etc.)
  • Alteration (enhancement/optimization) of existing feature(s)
  • New behavior

Description

Hello, I already created a post explaining that when manually calibrating the Hall effect sensor values, they work perfectly, but auto-calibration causes these values ​​to be affected, including the actuation point or the fast trigger, due to changes. After analyzing the code, I want to raise an additional concern regarding EEPROM wear:

The automatic calibration in auto_calibration_check() is quite aggressive and causes frequent calls to save_calibration_value() and save_calibration_values(). This results in:

  • Writes to the external physical EEPROM using he_eeprom_write_block() (in EXTERNAL_EEPROM_OFFSET)
  • Writes to the emulated EEPROM using analog_matrix_eeprom_update() + eeprom_update_block()

Under heavy use (gaming/fast writing), this can easily lead to tens to over 100 writes per hour when auto-calibration reaches a confidence level >= 12 and detects small changes in sensor values.

Even with wear leveling, writing to both EEPROMs so frequently can significantly reduce their lifespan, potentially leading to calibration data corruption within 1.5 to 3 years of normal use.

The Feature Request I am submitting is to add an option to the firmware that allows the web launcher to disable auto-calibration, leaving manual calibration performed by the user and thus also preventing EEPROM wear.

Auto-calibration issue: #469

Thank you.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions