This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AMC3336: AMC3336 DC-offset problem

Part Number: AMC3336
Other Parts Discussed in Thread: SN65C1167E

Tool/software:

Dear Sir or Madam,

we encountered functionality problem with your delta sigma ADCs. We used it in our application for measuring AC grid voltage between phases. We were forced to lower frequency from 20MHz to 12.5MHz clock frequency but our device at 12.5Mhz measure votlage with DC offset (see attachments). At 10Mhz the problem dissapeared. It seems the more I get close to 12.5Mhz the more si probability after power-up that ADCs add some DC offset (means device should sending 50% zeros/ones but sending at 0V input 75% or 35% etc.) I get out of possible solution at 12.5Mhz but we wanna use this ICs even more so I need to find source of this problem. Do you have any ideas what could cause this? The DC offset is random constant and looks like modulator fail.

kind regard Thomas HW Engineer

  • Hi Tomas,

    Since the offset changes based off of clock frequency, I suspect it may be due to timing mismatch of clock and data at your SDFM. 

    Can you please probe your SDFM channels (with short pig-tail GND) at the pins of the controller to verify the setup and hold timings are not violated? 

    This document provides an in-depth overview of the issue and recommended fixes: https://www.ti.com/lit/an/sbaa607a/sbaa607a.pdf

     What other testing have you conducted for the design and do you plan to conduct? 

    I assume by the common-mode choke that EMC testing will be included, please see this document if you have not already: https://www.ti.com/lit/an/sbaa515a/sbaa515a.pdf

    I do see that the HGND and DCDC_HGND trace is connected with a via. This is not recommended. If a board change is required, I recommend amending the high side layout to match the design shown in the sbaa515 document. 

  • Dear Alexander,

    thanks for your quick response. The first document you send is something we encountered. We have FPGA sin3filter demodulator and send clock from FPGA and receive data at FPGA. But we have big delay between clock and data and we encountered time violation and thats why we lower the clock from 20Mhz to 10Mhz now it works fine, but we test also 12.5Mhz and we encountered something different I guess, because from the osciloscope it seems like the data from adc "skipping ones" you can see it on attached photos below. From our measurement and calculation at 12.5MHz there is no time hazard.
    What I do i just unpluging and plugging connector between control PCB(theres FPGA and diff.lines+connector) and measurement PCB (connector+diff.lines+ADCs) and problem sometimes occure. It even happens at power up in our converter where we used these

    Here you can see normal operation at 12.5Mhz(yellow=clock/green=data_from_adc):

    Here is problem occured(yellow=clock/green=data_from_adc):

  • Just adding some info: When data error occur power on secondary side=3.48V and after LDO=3.21V and its the same voltage levels as in correct data operation. Shorting primary_power/secondary_power/clock to GND fix it (guess power-up restart). Its not latch-up but It certainly something with the CLK. Could it be some problem that CLK is logic HIGH during power up? Is it necessary to held CLK in low level during power-up by some pull down? I couldn find anything in datasheet for CLK pin, only just RC filter for trace impedance optimization. But it strange that it works on 20Mhz/15Mhz/10Mhz and not in 12.5Mhz. Disappointed

  • Hi Tomas,

    Applying the clock before low side (VDD2) power up violates the absolute maximum ratings of the device. Is this what you mean by secondary side? 

  • I mean when rising VDD voltage(orange) the clock pin voltage(blue) also rising with it to logic high and after some time the clock appear with first pulse going logic low (the signals are undersampled on osciloscope the pulses are real nice squares=ignore green/blue like noise on pics). Should I kept CLK low during power up? The clock pin is driven by diff. line IC SN65C1167E without default state on input (undefined output). I could try give pull up+pulldown on IN_P/IN_N pins so when power-up clock stays logic low. What do you think? Kind regards Thomas

  • Hi Thomas,

    I would recommend keeping CLK low until DVDD has properly established. Any luck the last few days? 

  • Dear Alexander,

    Even if I keep CLK low during power up it did not help. Sometimes the first clock from Diif.line.driver SN65C1167E seems not to keep duty cycle 50%/50% but starts at 38%/62% duty cycle and after few clock it stabilize to 48%/52% but looks like it do something to ADC and ADC then sending data with offset. I think I need to some impedance trace adjustment. Because One diff. line driver output feed four ADCs with clock on one trace. Do you suggest to have for every ADC some own clock driver and trace? Could it be something with the impedance trace adjustment with bad reflection?

    Kind regards Thomas

  • Hi Tomas,

    I am not a clocking expert, you may try posting another thread with this device to get into contact with the best support. 

    However, if detailed management of the clock and data lines is not ideal, you may consider a driver/buffer to help stabilize the clock.