https://devzone.nordicsemi.com/f/nordic-q-a/23128/nrf52832-saadc-ain3-bad-readingsUsing nRF52832 I am collecting from 8 SAADC channels using example ble_app_uart__saadc_timer_driven__scan_mode as a guide. AIN3 (P0.05) gives incorrect results. Because P0.05 is nominally UART RTS I have cut sb22 and sb13 as suggested in the documentationen-USTelligent Community 13Thu, 29 Jun 2017 09:53:55 GMThttps://devzone.nordicsemi.com/thread/90974?ContentTypeID=1Thu, 29 Jun 2017 09:53:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:978970a0-2a7d-4041-8cd3-cab42e022c43ColM<p>Thank you. Restoring SB13 fixed the problem and now all 8 channels are sampling nicely.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/90973?ContentTypeID=1Thu, 29 Jun 2017 08:34:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:65053660-3c64-4098-92ee-68c7bdc4c31eJ&#248;rgen Holmefjord<p>Are you sure the pin is not configured for use with any other peripheral? Could you provide an example of what you are reading and what you expect? Can you upload your code for debugging? Also, if you cut SB13, you have disconnected the pin from the pin header. Are you sure you have the input connected to the pin? If not it will be left floating, giving you incorrect readings.</p><div style="clear:both;"></div>