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.

Kpfd and vco cap

I have 2 questions:

1) What is Kpfd in Pllatinum sim software. Basically, it is in mA. PFD normally provided up and down value. If we give a Kpfd of 14 mA, does that mean that the current in Charge pump is 14mA. Can you please clarify

2) What is VCOcap in Pllatinum sim software. I read it is vco tune pin. Does it mean that it is the fixed mos varactor cap or what is it. 

  • 1. Kpd it the charge pump gain and is in mA. So if the value is 15 mA, this means the charge pump can source 15 mA or sink 15 mA. For +2pi phase error, it souces 15 mA, for -2pi phase error it sinks 15 mA, so the time averaged value is (15--15)/(2pi--2pi) = 15 mA/2pi. The 2pi is disregarded because the charge pump gain multiplies the VCO gain, which multiplies by 2pi.

    2. VCO cap is the inherent input capacitance of the VCO. This is a fixed value and not a design parameter. This is due to the varactor diode.

    REgards,
    Dean
  • Thanks for the reply.

    Regarding, Kpd, does it mean that when I design a charge pump it has to have 15mA current source. In other words, from circuit point of view how much current I have to use. Is it 15mA or 15mA/2*pi

    Typically, the current in Charge pump is of the order of uA but here it is  of the order of 15mA. Kindly, advise.

    Also, for a SERDES 28 GBPS, I have a PLL which operates at 14 GHZ and 28Ghz. Your tool PLLatinum SIm is valid upto 15GHZ. Any suggestion what I should do for 28 GHZ clock as. Any tool for estimating jitter and LPF components at 28GHZ.

    Thirdly, .what do you mean by inherent cap of VCO. Does it mean the fixed cap we have in VCO. In other words, we have a fixed cap and mos varactor. Can we leave VCOcap as zero or will there be a problem later in simulations if we choose VCOcap as zero

    The jitter value that PLLatinum sim spits out is the total jitter of VCO or does it include PFD, lLPF, /N and VCO. I hAve a jitter budget of 0.3185ps and the jitter achieved using the tool is 0.08ps. So, I am in good shape. Kindly, advise.

  • Pankaj,

    1. Kpd: If the part is programmed to 15 mA, this means that if the charge pump is on fully with 100% duty cycle, it will source or sink 15 mA. Some charge pumps are in the 100's of uA range, especially those for low bandwidht PLLs like in jitter cleaners, but this is in the mA range.
    But realize that the duty cycle of the charge pump is typically very low in the locked state, so the majority of the time this charge pump is off.

    The current sourced when the charge pump is on is 15 mA, not 15 mA/(2pi). Now if you want to convert this to current/radian, you divide by 2pi. But I discourage doing this because the VCO gain is multiplied by 2pi to convert from Hz to radian, so the 2pi just cancels out.

    2. 15 GHz: PLLatinum sim can be used DC to daylight and certainly above 15 GHz. Now if you choose a part that does not go above 15 GHz, it might warn you and turn boxes red, but you do not have to heed these warnings. Also, you can do the custom PLL. The math or the tool does not break down above 15 GHz just because that's our highest frequency VCO.

    3. VCO Cap: This is an inherent property of the VCO. Telling the tool that it is 0 because it is inconvenient does not change the actual silicon. PLLatinum sim will model whatever you say, so it is the job of the user to give it the right information. Maybe it would be simpler if this VCO capacitance was locked from the user being able to choose, but sometimes these simplifications can frustrate users. For instance, if you have your own external VCO, you can find this parameter in the VCO datasheet. Or perhaps you want to see the impact on your design if the VCO capacitance was to vary from default value. Or perhaps you are seeing some strange effect and want to see if the VCO capacitance could be a plausible explanation. We have no guarantee or high confidence measurements for VCO capacitance. This is an estimate from design.

    4. Jitter: The jitter is calcualted from the phase noise. In the graph, you can see it includes PLL, VCO, and loop filter. You can go to the phase noise tab and add your input reference noise if you like; if you don't PLLatinum sim assumes noiseles input reference. The "PLL" portion includes noise from the N divider, R divider, input path, and charge pump. These are all lumped together in to the parameters of PLL flicker noise and PLL figure of merit.

    Regards,
    Dean
  • Hi Dean,

    I am getting a jitter of 80 fs for the custom PLL. However, the caps are C1=18pF and C2 = 2700pF and R=68 ohms. For on-chip LPF won't the value of components be too big or it's correct. Also, because R is low, therefore, jitter is low.

    The Charge Pump gain is 6.5mA. Does this mean that I have to put the current source and sink to be 6.5 mA in Charge pump respectively. Also, when you say duty cycle is 100%, does that mean in steady state when both source and sink i.e vdd and vss are shorted. Also, when in lock the phase err or is very small so the net current flow will flow for sometime. I am not clear what you mean by duty cycle very clearly. Can you please respond.

    thanks for your time.
  • Pankaj,

    So if you tell PLLatinum sim that C1 = 18 pF and VCO input capacitance is 0, then what you will likely find is that when you actually build it, you get a much narrower loop bandwidth than you designed before because the VCO input capaciance is not zero, but much higher. Also, there is a minimum high order capacitance, that the tool is probably warning you about. If the capacitor next to the VCO is < 3.3 nF, then the VCO phase noise degrades. The tool defaults to 1.5 nF limit which leads to about 1 nF degradation. In other words, don't ignore these.

    To get around this, you need to maximize the phase detector frequency and also the charge pump gain. You can use the advanced mode to design minimize jitter. Also, click on the "design tips" on the loop filter.

    For your change pump current, you would put 6.5 mA in your case, but you should really increase to 15 mA to help with the issue of the small. As for the duty cycle, it is 100% only in the extreme cases of being unlocked, in the locked condition, it is <1% in the steady state.

    When the PLL is locked, the charge pump sources current very briefly and then it goes high impedance. Then it sinks current very briefly and goes high impedance, then it repeats.

    Regards,
    Dean
  • Hi Dean,

    Thanks for detailed reply. I noticed the same thing that when we change VCOcap the loop Bandwidth changes.

    You are mentioning that 3.3nf is the capacitor next to VCO. But, I am getting good jitter specs of 80 fs from the caps and resistor that are C1=18pF and C2 = 2700pF and R=68 ohms. So if the jitter specs is what I want then why should i choose 3.3nF when I can get the performance from lower cap next to VCO.

    you missed one keyword while typing the reply below: from previous reply: "small" / what is it jitter or something else. see below

    For your change pump current, you would put 6.5 mA in your case, but you should really increase to 15 mA to help with the issue of the "small". As for the duty cycle, it is 100% only in the extreme cases of being unlocked, in the locked condition, it is <1% in the steady state.
  • 7411.LMX2594 Minimum High Order Cap for Vtune.pdfPankaj,

    PLLatinum sim does not model all effects and does not model the effect of violating the recommendation of going below the 3.3 nF.  On the loop filter design tab, click on the filter design tips button and it talks all about this.  Also see attached report.

    As for the "small", I am talking about the small loop filter capacitor next to the VCO  18 pF is really small.  Not only will it be swamped out by the VCO input capacitance, but it will lead to high VCO pahse noise that is not modeled by PLLatinum Sim.  But if you double your charge pump gain, this capacitance doubles and it helps a little, although 36 pF for C1 is still way too small.

    Regards,

    Dean

  • Let us say I use 3.3nF capacitor for C1. WIll I have to do a ON-CHIP or OFF_CHIP Loop Filter. Because, on chip -cap will be huge in terms of area. Kindly, advise.
  • Also, does PLLatinum sim account for variation of gm of transistor. How much is the variation of specifications of jitter in percentage wise in PLLatinum reported jitter values and actual jitter achieved in circuit including inductor noise, gm of transistors etc

  • what is the offset frequency or what do you mean by the same  in the table below.

    Alos, if my Kpd is 15 mA as discussed  and my VDD is 1v, what is the power dissipation of CP. Is it 15e-03 * 1volt or depends on duty cycle. Please advise

  • Pankaj,

    This offset is offset from the carrier. So for instance, if C3_LF is 120 pF, the impedance is 997 ohm and the phase noise degradation at 100 kHz offset is 4.4 dB.

    As for current from the charge pump, it depends on duty cycle. Duty cycle is pretty low, like 1%, so more like 15e-03*1volt*1%

    Regards,
    Dean
  • Could you please share your thoughts with me regarding 2 design questions or could you give pointers.

    Let us say I use 3.3nF capacitor for C1. WIll I have to do a ON-CHIP or OFF_CHIP Loop Filter. Because, on chip -cap will be huge in terms of area. Kindly, advise.

    Also, does PLLatinum sim account for variation of gm of transistor. How much is the variation of specifications of jitter in percentage wise in PLLatinum sim reported jitter values and actual jitter achieved in circuit including inductor noise, gm of transistors etc Any thoughts and suggestions.
  • Hi Pankaj,

    See feedback on the other post.