SAADC example unexpected results

RE: SAADC example unexpected results

criznach — Mon, 08 Oct 2018 14:46:44 GMT

That documents what the arduino-compatible pinouts are, but doesn't disambiguate how they are labelled in your APIs. I would argue that the printed board is in the developer's hands and in front of their eyes, so like myself, that appears to be the truth. I had to search for quite a while to see what's really happening. It's not explained in the example code where I looked first being new to the platform. The example documentation mentions GPIO pin 2, which I was unsure about because it doesn't match the p0.02 notation used everywhere else. Thanks for looking into it!

RE: SAADC example unexpected results

MartinBL — Mon, 08 Oct 2018 14:23:48 GMT

It is sort of documented here. I agree with you though, and I have already discussed it with the kit designers once before, but their reasoning is that A0 refers to the pinout of the standard Arduino form factor:

RE: SAADC example unexpected results

criznach — Mon, 08 Oct 2018 13:41:28 GMT

#2 is exactly what happened. Can the docs be updated to explain this? As someone who's new to NRF, the A0 marking on the PCB was much more prominent and convincing than the "Pin assignments" document that I ultimately found through another DevZone post, after a few hours of head scratching.

RE: SAADC example unexpected results

MartinBL — Mon, 08 Oct 2018 08:00:10 GMT

I assume you are using the same pot meter in all the tests? So no chance of a broken pot meter?
Have you double and triple checked that you are using the correct pins? AIN0 is pin P0.02, but I have done the mistake myself and assumed AIN0 is on P0.03 since it is marked 'A0' on the nRF52 DK.
Can you upload your code so I can test it?