using MPLAB X IDE v5.35 PIC16LF19176

I used PIC ADC analog inputs several times, the conversion always gives me the proper results. Looking at the input with the scope confuses me.


The scope channel one is attache to the power source for the sensor:

enter image description here

The scope channel two is attached to the sensor output wire indirectly - via analog multiplexer. Multiplexer is at that point switched permanently to channel 5 and enabled (no control signal changes during testing). The scope is attached to the top of the R5 resistor, which is at that point in parallel with the sensor output, thus loading the sensor with 7k87 resistor. Left multiplexer 'brings' the 3V excitation to the sensor via signal MUX5_A (test point TP1), and sensor returns its output via right multiplexer via signal MUX5_B (TP2):

enter image description here

The attached active sensor has three wires: power +3V; GND; and output 0..3V. The sensor output is connected to PIC analog input, which is used for ADC conversion. The sensor power is turned ON-OFF by the PIC via dedicated DC/DC regulator.

After the sensor power is turned ON, I start the PIC ADC conversion. As soon as the GO bit is set (conversion start), the input pin gets grounded for about 10 msec. Then the input is 'released', sensor shows proper values. Conversion is still active for another 17 msec and it appears to return proper result.

In the case you wonder, I did try to debug the code and put various delays. The grounding effect is only when the conversion starts.

The attached picture shows two consecutive conversions (I am calculating an average), both of which start with unwanted pin grounding.

I do not wish to put the sensor's output to this stress. Can someone tell me, why is the PIC input pin grounded this way?

The ADC conversion was actually generated by MPLAB:

adc_result_t ADCC_GetSingleConversion(adcc_channel_t channel)
// select the A/D channel
ADPCH = channel;

// Turn on the ADC module
ADCON0bits.ADON = 1;

//Disable the continuous mode.
ADCON0bits.ADCONT = 0;    

// Start the conversion
ADCON0bits.ADGO = 1;
// Now the scope shows signal gets grounded...

// Wait for the conversion to finish
while (ADCON0bits.ADGO)
    // in the middle of this conversion, signal goes back up...
// Conversion finished, return the result
return ((adc_result_t)((ADRESH << 8) + ADRESL));

It might be useful to see the ADC initialization routine:

 * ADC is initialized to highest possible accuracy at the cost of slowness (conversion time 37 msec)
 * During the initialization the GIE must be disabled
 * We are set to:
 * - basic mode
 * - clock source FOSC/ADCLK
 * - clock FOSC/128
 * - result is aligned to right
 * - reference voltage used is VDD of the processor
void ADCC_Initialize(void)

// ADC Interrupt disable, clear all its flags:
    PIE1bits.ADTIE = DISABLED;             
    PIR1bits.ADTIF = 0;
    PIR1bits.ADIF = 0;

// set the ADCC to the options selected in the User Interface
// ADLTH 0; 
ADLTHL = 0x00;
// ADLTH 0; 
ADLTHH = 0x00;
// ADUTH 0; 
ADUTHL = 0x00;
// ADUTH 0; 
ADUTHH = 0x00;
// ADSTPT 0; 
ADSTPTL = 0x00;
// ADSTPT 0; 
ADSTPTH = 0x00;
// ADACC 0; 
ADACCU = 0x00;
// ADRPT 31; 
ADRPT = 0x1F;
ADPCH = ADC_pin_U_BAT_HALF;   // Input channel switched to RC3
// ADACQ 255; 
// ADACQ 31; 
ADACQH = 0x1F;
// ADCAP Additional uC disabled; 
ADCAP = 0x00;
// ADPRE 255; 
// ADPRE 31; 
ADPREH = 0x1F;
// ADDSEN disabled; ADGPOL digital_low; ADIPEN disabled; ADPPOL Vss; 
ADCON1 = 0x00;
// ADCRS 0; ADMD Basic_mode; ADACLR disabled; ADPSIS RES; 
ADCON2 = 0x00;
// ADCALC First derivative of Single measurement; ADTMD disabled; ADSOI ADGO not cleared; 
ADCON3 = 0x00;
// ADMATH registers not updated; 
ADSTAT = 0x00;
ADREF = 0x00;   // Vref = Vdd (because external DC/DC RT9013-3V3 accuracy is +-2%, internal Vref +-4% => Vdd is more accurate than internal Vref)
// ADACT disabled; 
ADACT = 0x00;
// ADCS FOSC/128; 
ADCLK = 0x3F;   // slowest setting, but most accurate // conversion took about 37 msec
// ADGO stop; ADFM right justified; ADON disabled; ADCS FOSC/ADCLK; ADCONT disabled; 
ADCON0 = 0x04;
  • \$\begingroup\$ Explain what scope1 is and what scope 2 is connected to. \$\endgroup\$
    – Andy aka
    Aug 23 '20 at 10:36
  • \$\begingroup\$ Do you know the output impedance of the sensor's output pin? \$\endgroup\$
    – anrieff
    Aug 23 '20 at 11:25
  • \$\begingroup\$ @anrieff: I believe the sensor has an opamp buffer, because when I simply power the sensor with 3V power supply, and it outputs let's say 1V, I can load it with any resistor, like 1kOhm and the output doesn't change. I am aware I am loading it with 7.87kOhm - but I checked that doesn't change its output when powered up separately. \$\endgroup\$ Aug 23 '20 at 11:59
  • \$\begingroup\$ Who’s design was this? \$\endgroup\$ Aug 23 '20 at 15:24
  • \$\begingroup\$ Design is mine, but only after I followed exactly the sensor manufacturer detailed requirement with their schematics - I have added the CPU. Now, I will not be offended... you can freely go and say what you wanted in the first place :) \$\endgroup\$ Aug 23 '20 at 16:03

There is an answer for your question but what details you put in your post, and more importantly what you did not put in your post, made finding the correct response a real challenge.

First off you cannot be using any dsPIC, it must be one of the 8-bit controllers. Most likely one of the PIC18FxxQxx types with an ADC function block that supports the Capacitive Voltage Divider (CVD) Feature.

Second the cut and paste job you did of the ADC code you alleged was generated by MPLAB is crap. The initialization sets up the ADC for use in the touch / proximity sensing mode using the CVD feature. This feature does in fact connect the ADC input pin to VSS for a specific period before the conversion begins by setting the ADPRE register to a non-zero value.

Finally the code you posted to setup the ADC conversion clock period is wrong in every possible way it can be wrong and still sort of produce a conversion result.

Did you comprehend any part of the data sheet that describes the ADC function block?

  • \$\begingroup\$ (Question corrected) I am upvoting your answer just for your expertise. You are correct, it is not a dsPIC :( I often use dsPICs, work on many projects in parallel, sorry for my mistake. You could be a bit nicer with your language, but that is just my opinion. Still, your words are helpful. I am going to look at the code in detail again. I probably do not understand all in the documentation, otherwise I would not need to post the question. The code came from MPLABX, I did not write it - that is not an excuse, because I DID set up the MPLAB MCC forms. So indirectly I wrote the code. \$\endgroup\$ Aug 23 '20 at 22:22
  • 1
    \$\begingroup\$ @EmbeddedGuy, I can see that I was blunt in my comments. I do apologize. As an offer of contrition I posted on git hub an MPLABX project created with the MCC that reads an ADC input voltage on pin RC3 then sends an ASCII string of the raw hex value to UART1 at 9600 baud. \$\endgroup\$
    – Dan1138
    Aug 24 '20 at 0:36
  • \$\begingroup\$ This is the best apology - with a gift! I am not only thanking for that, but thank you and Stack exchange: it helps engineers to grow. I learned a lesson and will assume less. The product will be out with a much better code, and will be within the Friday deadline :) I am positive there are others who will do the same mistake - this question will help them, too. \$\endgroup\$ Aug 24 '20 at 9:01

As @Dan1138 suggested, the problem was in initializing the ADC with CVD incorrectly activated. The Microchip manual also states: If there is a device attached to (analog input) pin, Precharge should not be used.

The solution was to set both Precharge registers to 0:

// ADPRE 0; 
ADPREL = 0x00; // was incorrectly 0xFF
// ADPRE 0; 
ADPREH = 0x00; // was incorrectly 0x1F

This corrected the ADC conversion, pin is not grounded anymore, as seen on the scope picture: enter image description here

  • \$\begingroup\$ There are other issues with your ADC initialization code. I suspect that you have set the TAD period for too long a time. This period must be at least 1 microsecond and not longer than 8 microseconds. TAD periods closer to 1 microsecond give better conversion results. A complete ADC conversion requires at least 14 TAD periods, \$\endgroup\$
    – Dan1138
    Aug 24 '20 at 16:44
  • \$\begingroup\$ Yes - I already changed it to be 6 usec. Product works now - thank you for all your help \$\endgroup\$ Aug 24 '20 at 18:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.