Sometimes nrf52840 aadc calibration is wrong

RE: Sometimes nrf52840 aadc calibration is wrong

Karl Ylvisaker — Fri, 04 Sep 2020 10:37:00 GMT

Ah, now I understand, thank you for clarifying.

[quote user="maarten v"]Depending on the sensor and the application we use less or more oversampling.
With oversampling and extra offset correction the accuracy is good enough for our applications.[/quote]

That sounds like a good solution - I am happy to hear that it achieved the required accuracy for your applications.

Please do not hesitate to open a new ticket if you should encounter any issues or questions in the future.

Good luck with your development!

Best regards,
Karl

RE: Sometimes nrf52840 aadc calibration is wrong

maarten v — Fri, 04 Sep 2020 10:16:47 GMT

The required accuracy depends on the application. We have developed some IOT nodes (https://xeelas.nl/producten) with capability of connecting external sensors.

Depending on the sensor and the application we use less or more oversampling.
With oversampling and extra offset correction the accuracy is good enough for our applications.

RE: Sometimes nrf52840 aadc calibration is wrong

Karl Ylvisaker — Fri, 04 Sep 2020 09:22:27 GMT

[quote user="maarten v"]1024 times oversampling reduces the noise by a factor 2^5, which is indeed what i see when i did some experiments with this.[/quote]

You never told me the exact accuracy / precision need of the SAADC for your project, so I not know what your target is.
Does this mean you are able to achieve the required accuracy for your project?

Best regards,
Karl

RE: Sometimes nrf52840 aadc calibration is wrong

maarten v — Fri, 04 Sep 2020 09:11:02 GMT

yes, in 12 bit mode there is about 4 bits noise. That is unfortunate but according spec for the 52840.

1024 times oversampling reduces the noise by a factor 2^5, which is indeed what i see when i did some experiments with this.

RE: Sometimes nrf52840 aadc calibration is wrong

Karl Ylvisaker — Fri, 04 Sep 2020 07:26:48 GMT

[quote user="maarten v"]Thank you for the answer, and my apologies that it took some time.[/quote]

That is no problem, I am happy to help!

[quote user="maarten v"]This is the confirmation i was looking for. Time is not an issue since it only has to be done incidentally and can be scheduled in between other actions.[/quote]

Great, I am glad to hear that!

[quote user="maarten v"]fyi: The remaining offset is compensated with a firmware calculated offset from an average of 1024 samples. This does the trick in keeping the signal stable when the temperature is not changed, so i guess it will also work when it does change.[/quote]

Are you here talking about using a static average to weight the samples? If you are achieving the correct readouts with this approach then I suppose it is fine, but I can not speak for the accuracy of the outcome. As I mentioned I would expect some LSB of noise on the SAADC outputs, depending on the SAADC configuration.

Best regards,
Karl

RE: Sometimes nrf52840 aadc calibration is wrong

maarten v — Thu, 03 Sep 2020 18:18:45 GMT

Thank you for the answer, and my apologies that it took some time.
This is the confirmation i was looking for. Time is not an issue since it only has to be done incidentally and can be scheduled in between other actions.

fyi: The remaining offset is compensated with a firmware calculated offset from an average of 1024 samples. This does the trick in keeping the signal stable when the temperature is not changed, so i guess it will also work when it does change.

RE: Sometimes nrf52840 aadc calibration is wrong

Karl Ylvisaker — Mon, 24 Aug 2020 13:36:21 GMT

Hello again,

Thank you for providing me with the project files.
I have just gotten back from speaking with the SAADC experts, which confirmed for me that setting oversampling for AIN0 does actually increase accuracy of the offset calibration since it too will use oversampling during the calibration. The oversampling will in this case suppress thermal noise - increasing accuracy -, but the calibration will not be more accurate than its internal DAC. The calibration will also take longer, since more samplings will be done.

What accuracy do you require for your project?

Best regards,
Karl

RE: Sometimes nrf52840 aadc calibration is wrong

maarten v — Mon, 24 Aug 2020 11:10:15 GMT

Thank you for the answers.

Attached is the whole project.

devzone.nordicsemi.com/.../aadc_2D00_precision.zip

I did run it on a nRF52840DK.

Looking forward to your findings.

RE: Sometimes nrf52840 aadc calibration is wrong

Karl Ylvisaker — Mon, 24 Aug 2020 10:41:44 GMT

Hello again,

[quote user="maarten v"]I restructured the program to improve showing the calibration problem.[/quote]

Thank you for pinpointing this.
Could you possibly share with me the entire project from which this main.c file is taken from?
Then I will run this on my end and attempt to replicate the behavior - I would love to get a better look at what might cause this change in offset calibration.

[quote user="maarten v"]I now use the gnd reading for an extra compensation. This works quite well but i do not know if reading the gnd as shown is defined behavior.[/quote]

If you are asking whether measuring gnd by setting the pin to pulldown is defined behavior then the answer would have to be that it indeed is undefined, but I do not immediately see any reason why this would not work.
If this is not what you were asking, please elaborate.

[quote user="maarten v"]I want a solution for this offset problem.[/quote]

How big is the fluctuation you are seeing now, in terms of bits of saadc output / mV? And, how frequently is it happening?

[quote user="maarten v"]Is this possible by setting the input to NRF_SAADC_INPUT_DISABLED, while setting the internal resistor network to NRF_SAADC_RESISTOR_PULLDOWN?[/quote]

No, you should instead point it to a specific pin, and then change the configuration of that pin after the channel configuration is complete.
Alternatively you can also just connect the chosen pin to GND with a jumper, for the same result.

Best regards,
Karl

RE: Sometimes nrf52840 aadc calibration is wrong

maarten v — Fri, 21 Aug 2020 15:55:21 GMT

I restructured the program to improve showing the calibration problem.

#include <stdio.h>
#include <stdlib.h>

#include <nrf_delay.h>
#include <nrfx_gpiote.h>
#include <nrfx_saadc.h>


// uncomment this to show the calibration problem without oversampling.
//#define ENABLE_CALIBRATION_BUG


const float v_ref = 0.6;     // internal reference voltage
STATIC_ASSERT(NRFX_SAADC_CONFIG_RESOLUTION == 2);
#define ADC_RESOLUTION 4096u /// 12 bit adc reolution (14 bit is only accomplished with oversampling)

#define CHANNEL_CONFIG(PIN_P, RESISTOR_P, GAIN) (nrf_saadc_channel_config_t)\
{\
    .resistor_p = RESISTOR_P,      \
    .resistor_n = NRF_SAADC_RESISTOR_DISABLED,      \
	.gain       = GAIN,                \
    .reference  = NRF_SAADC_REFERENCE_INTERNAL,     \
    .acq_time   = NRF_SAADC_ACQTIME_10US,           \
    .mode       = NRF_SAADC_MODE_SINGLE_ENDED,      \
    .burst      = NRF_SAADC_BURST_DISABLED,         \
    .pin_p      = (nrf_saadc_input_t)(PIN_P),       \
    .pin_n      = NRF_SAADC_INPUT_DISABLED         \
}

static nrfx_saadc_config_t saadc_config = NRFX_SAADC_DEFAULT_CONFIG;
static volatile bool limit_event;

static float get_gain_factor(nrf_saadc_gain_t gain)
{
	float factor ;
	switch( gain )
	{
		case NRF_SAADC_GAIN1_6: factor = 1.0/6; break;
		case NRF_SAADC_GAIN1_5: factor = 1.0/5; break;
		case NRF_SAADC_GAIN1_4: factor = 1.0/4; break;
		case NRF_SAADC_GAIN1_3: factor = 1.0/3; break;
		case NRF_SAADC_GAIN1_2: factor = 1.0/2; break;
		case NRF_SAADC_GAIN1: factor = 1.0; break;
		case NRF_SAADC_GAIN2: factor = 2.0; break;
		case NRF_SAADC_GAIN4: factor = 4.0; break;
		default:
			ASSERT(false);
			break;
	}
	return factor;
}

static float adc_to_voltage( float adc, nrf_saadc_gain_t gain )
{
	float range = 0.6/get_gain_factor(gain);
	return range * adc/ADC_RESOLUTION;
}

static void saadc_callback(nrfx_saadc_evt_t const * p_event)
{
	if (p_event->type == NRFX_SAADC_EVT_LIMIT)
	{
		limit_event = true;
	}
	else if (p_event->type == NRFX_SAADC_EVT_DONE)
	{
		limit_event = false;
	}
	else if (p_event->type == NRFX_SAADC_EVT_CALIBRATEDONE)
	{
		limit_event = false;
	}
}

static void mcu_adc_init(void)
{
	ret_code_t err_code = nrfx_saadc_init(&saadc_config, saadc_callback);
	ASSERT(err_code == NRF_SUCCESS);
}

static void mcu_adc_uninit(void)
{
	nrfx_saadc_uninit();
}

// sample 1 channel, already configured
// @param *adc [out]: the average of the raw read adc samples.
static void channel_convert(uint8_t channel, unsigned oversample, float *adc_avg)
{
	int adc_sum = 0;
	for( unsigned i = 0; i<oversample+1; i++ )
	{
		nrf_saadc_value_t adc;
		ret_code_t rr = nrfx_saadc_sample_convert(channel, &adc);
		ASSERT( rr == NRF_SUCCESS );
		//printf("    part_adc=%hd\n", *adc);
		adc_sum += adc;
	}
	
	*adc_avg = adc_sum / (float)(oversample+1);
}


void mcu_adc_calibrate(void)
{
	ret_code_t r;
	
	printf("Calibrate\n");
	
	// prepare
	nrfx_saadc_uninit();
	#ifndef ENABLE_CALIBRATION_BUG
	saadc_config.oversample = 8;
	#endif
	r = nrfx_saadc_init(&saadc_config, saadc_callback);
	
	// calibrate
	r = nrfx_saadc_calibrate_offset();
	ASSERT(r == NRF_SUCCESS);
	
	while (nrfx_saadc_is_busy())
	{
	}

	// finalize
	
	// Nordic errata 86 workaround...
	nrfx_saadc_uninit();
	saadc_config.oversample = 0;
	r = nrfx_saadc_init(&saadc_config, saadc_callback);
	ASSERT(r == NRF_SUCCESS);
}

void mcu_adc_read_gnd(nrf_saadc_gain_t gain, unsigned oversample, float *adc)
{
	nrf_saadc_channel_config_t chcfg = CHANNEL_CONFIG(NRF_SAADC_INPUT_DISABLED, NRF_SAADC_RESISTOR_PULLDOWN, gain);

	nrf_saadc_channel_init(0, &chcfg);
	channel_convert(0, oversample, adc);
	nrf_saadc_channel_input_set(0, NRF_SAADC_INPUT_DISABLED, NRF_SAADC_INPUT_DISABLED);
}

void mcu_adc_read_1(nrf_saadc_input_t pin, nrf_saadc_gain_t gain, unsigned oversample, float *adc)
{
	nrf_saadc_channel_config_t chcfg = CHANNEL_CONFIG(pin, NRF_SAADC_RESISTOR_DISABLED, gain);
	
	nrfx_saadc_channel_init(0, &chcfg);
	channel_convert(0, oversample, adc);
	nrfx_saadc_channel_uninit(0);
}

int mcu_adc_read_test(void)
{
	mcu_adc_init();
	nrf_gpio_cfg_input(NRF_GPIO_PIN_MAP(0, 2), NRF_GPIO_PIN_NOPULL);
	
	for(unsigned j=0; j<1000; j++)
	{
		mcu_adc_calibrate();
		for(unsigned i=0; i<3; i++)
		{
			const char *sep = "   ";
			const unsigned oversample = 1023;
			
			for( nrf_saadc_gain_t gain = NRF_SAADC_GAIN1_6; gain<=NRF_SAADC_GAIN1_5; gain++ )
			{
				printf("%s{gain:%0.2f, ", sep,  get_gain_factor(gain));
					
				// zero measurement
				float adcgnd;
				mcu_adc_read_gnd(gain, oversample, &adcgnd);
				
				if(nrfx_saadc_is_busy())
				{
					printf("still busy!\n");
					nrfx_saadc_is_busy();
					{}
				}
				
				float v_adcgnd = adc_to_voltage(adcgnd, gain);
				printf(", adcgnd:{adc:%0.1f, V::%0.3fV}", adcgnd, v_adcgnd);
				
				// ain0 measurement
				float ain0;
				mcu_adc_read_1(NRF_SAADC_INPUT_AIN0, gain, oversample, &ain0);
				
				if(nrfx_saadc_is_busy())
				{
					printf("still busy!\n");
					nrfx_saadc_is_busy();
					{}
				}

				float v_ain0 = adc_to_voltage(ain0, gain);

				printf(", ain0:{adc:%0.1f, V::%0.3fV}", ain0, v_ain0);

				printf(", ain0_corrected:{adc:%0.1f, V::%0.3fV}", ain0-adcgnd, v_ain0-v_adcgnd);

				// FIXME this is a patch for the fact the that ADC does not stop (reason unknonw).
				nrfx_saadc_abort();
				nrf_saadc_task_trigger(NRF_SAADC_TASK_STOP);

				sep = ", ";
			}

			printf("\n");
		}
	}
	
	mcu_adc_uninit();
	
	do
	{} 
	while (1);
}

Oversampling is disabled ENABLE_CALIBRATION_BUG is defined: then reading the gnd voltage differs often between calibrations.
When oversampling is turned on during calibration, the ground reading is almost always stable.

I now use the gnd reading for an extra compensation. This works quite well but i do not know if reading the gnd as shown is defined behavior.

RE: Sometimes nrf52840 aadc calibration is wrong

maarten v — Fri, 21 Aug 2020 09:54:59 GMT

[quote userid="87869" url="~/f/nordic-q-a/64886/sometimes-nrf52840-aadc-calibration-is-wrong/265680"]The deviation seems to be much less frequent ( 1 in 40 ) when you have turned on x256 oversampling, is that what you are saying?
[/quote]

Correct. But that was yesterday. The exact same solution results in much more frequent calibration ofset jumps on a different nrf52840. So perhaps this was just coincidental.

I want a solution for this offset problem.
I was thinking of measuring the 0V adc deviation myself. Is this possible by setting the input to NRF_SAADC_INPUT_DISABLED, while setting the internal resistor network to NRF_SAADC_RESISTOR_PULLDOWN?

RE: Sometimes nrf52840 aadc calibration is wrong

Karl Ylvisaker — Fri, 21 Aug 2020 07:54:22 GMT

Hello,

[quote user="maarten v"]I discovered that turning on oversampling (256x) before doing a calibration reduced the variation in the result of the calibration to about 0.5 bit in the 12bit resolution, instead of 1 bit in the 8 bit resolution.
This is what i would expect and acceptable.[/quote]

That is interesting. I will note this down and attempt to recreate this behavior on my end. To my knowledge, whether you have configured oversampling or not should not affect the offset calibration procedure at all.

Furthermore, depending on your input range configuration I would more or less expect a possible fluctuation in LSB of an SAADC output.
Is this remaining fluctuation an issue for your current project - what is your required resolution?

[quote user="maarten v"]I was too quick: the deviation seems to be much less frequent (about 1 in 40) but still happens now and than: suddenly a jump in the offset after a calibration.[/quote]

The deviation seems to be much less frequent ( 1 in 40 ) when you have turned on x256 oversampling, is that what you are saying?

Best regards,
Karl

RE: Sometimes nrf52840 aadc calibration is wrong

maarten v — Thu, 20 Aug 2020 06:33:46 GMT

[quote userid="87869" url="~/f/nordic-q-a/64886/sometimes-nrf52840-aadc-calibration-is-wrong/265103"]I see the samplings and how they seem to fluctuate, but I do not see any consistent trend between the different calibrations. Are you saying that the SAADC output values are increasing by 2-4 for every calibration?
I am not sure I understand what you are saying here, please correct me if I am wrong.[/quote]

What the code shows is that an adc conversion of a pin connected to ground (or actually the the average of 1000 conversions to exclude noise as a deviation), sometimes suddenly has a different value after a calibration.

I found a possible cause and solution:

I discovered that turning on oversampling (256x) before doing a calibration reduced the variation in the result of the calibration to about 0.5 bit in the 12bit resolution, instead of 1 bit in the 8 bit resolution.
This is what i would expect and acceptable.

Apparently the calibration is performed with the oversampling setting which needs to be set to high value before doing the calibration to have a reliable result.

It is possible i overlooked this in the documentation. Or is this an undocumented feature?

Edit:

I was too quick: the deviation seems to be much less frequent (about 1 in 40) but still happens now and than: suddenly a jump in the offset after a calibration.

RE: Sometimes nrf52840 aadc calibration is wrong

Karl Ylvisaker — Tue, 18 Aug 2020 12:38:24 GMT

Hello,

With GAIN = 4 and using the internal 600 mV reference it seems you get the biggest fluctuation of 12 SAADC values (53 - 41).
Calculating the input range with these parameters using the formula from the SAADC documentation yields the range 0 - 0.15 V. With a resolution of 12 bit there is a total of 4096 possible values, which means that the fluctuation at worst is 0.4 mV.
This does not seem out of the ordinary to me.

[quote user=""]Thisis makes it clear the the calibration jumps between 2 values (some runs it is even 4 different values values)[/quote]

I see the samplings and how they seem to fluctuate, but I do not see any consistent trend between the different calibrations. Are you saying that the SAADC output values are increasing by 2-4 for every calibration?
I am not sure I understand what you are saying here, please correct me if I am wrong.

For future reference, please use the "Insert -> Code" option when attaching code, and upload entire log files instead of copying parts of it, this will drastically increase readability.

Looking forward to getting to the bottom of this!

Best regards,
Karl

RE: Sometimes nrf52840 aadc calibration is wrong

maarten v — Mon, 17 Aug 2020 13:34:37 GMT

I forgot to add: this example is with a 12 bit conversion. The error is less that 1 bit when the conversion is done with 8 bit.