[dataAPI] Missing generic function to store calibration parameters for SPIN.

[jalinei]

Dual problem in the existing Data API:

• Function data.setTwistChannelsUserCalibrationFactors() is based on console interaction with the user.
• We need the counterpart of data.setTwistChannelsUserCalibrationFactors() for a generic data acquisition using SPIN.

We need to add a function in data API to store permanently the parameters (defined through setParameters) in the NVS. It has to be implemented both for twist and for SPIN.

We may also adapt interaction based function to SPIN as it is a nice feature to tweak parameters on the fly.

[luizvilla]

I have created a function to do this. You can find it here :

https://gitlab.laas.fr/lflavado/core/-/tree/power_test_boot?ref_type=heads

In the DataAPI.h you will find:

    /**
     * @brief Use this function to write the gain and offset parameters of the board to is non-volatile memory.
     *
     * @note  This function should be called after updating the parameters using setParameters.
     *
     * @param channel Name of the shield channel to save the values.
     */
    int8_t saveParametersInNVS(channel_t channel);

    /**
     * @brief Use this function to read the gain and offset parameters of the board to is non-volatile memory.
     *
     * @param channel Name of the shield channel to save the values.
     */
    int8_t getParametersFromNVS(channel_t channel);

This commit allows finding the update for saving to the NVS: 83a65477246b7cc5ae312cc55c7f6b0efd0a14e7

This commit allows finding the update for getting from the NVS: b165b83342cf8b4da5877b838317eb0ad40a716e

This is only implemented for the TWIST board, but it is not difficult to generalize from here if needed.

[jalinei]

I propose the following :

1. Draft a PR based on these two commits. From what I understand It it already complementary to existing data.setTwistChannelsUserCalibrationFactors() which is fully manual and based on console interaction. (Which is not suitable in many contexts) @luizvilla
2. Let's discuss how to adapt is to a generic form for SPIN. @luizvilla @jalinei
3. Merge.
4. Add section to documentation @jalinei

[luizvilla]

Sounds good to me. I can prepare a PR.

[jalinei]

34 Is closing this issue right ?