ADIsimFrequencyPlanner enables fast, accurate simulation and elimination of integer boundary spurs from Analog Devices PLL synthesizers. The tool analyzes the user's output requirements, and then optimizes the PFD frequency for each output step to give the best integer boundary spur performance. The optimum PFD frequency is selected by changing the output divider of the clock generation chip (e.g. HMC7044) and changing the reference input divider of the PLLVCO (e.g. ADF5355, HMC830).
Typical results are better than -100 dBc for integer boundary spurs across output frequencies from 55 MHz to 13.6 GHz.
I turned off a protection setting. I am now able to install the app.
However, I now have encountered an exception when I hit "generate
settings". I am trying to use the cascaded PLLVCO tool.
On Mon, May 15, 2017 at 12:47 PM, rbrennan <
That's good. Thanks for figuring it out.
Can you expand the Details of the error message and send me the text? And/or take a screenshot of the settings that cause the error so I can recreate it.
I attached the configuration file. I get the exception when I hit 'generate
settings'. I do not get any outputs in the spur power window. I get a phase
noise plot. (first two error blocks) But when I try to set a new frequency,
it throws another exception. (last two error blocks)
[image: Machine generated alternative text: ADlsimFrequencyPlanner (beta) X
Unhandled exception has occurred in your application, li you *** Continue,
the application will ignore this error and attempt to continue, Il you ***
Quit, the application will dose immediately. Arithmetic operation resulted
in an overflow. a Details Continue Quit See the end of this message for
details on invoking A ¡ust’in4ime (J IT) debugging instead of this dialog
box. Exception Text Systern.OverflowException: Arithmetic operation
resulted in an overflow. at
IBS_Planner.Mainjorrn.GenerateButton_Click(Qbject sender, EverrtArgs e) in
C at System .Windows.Forms Control .OnClick(EventAis e) at System
.Windows.Forms.Button .OnClick(EventArgs e) at System Windows. Forms.
Button On Mouse Up(MouseEventArgs mevent) at
System.Wìndows.Forms.Control.WmMouseUp(Message& m, MouseButtons buttc y (
in an overflow. a Details Continue Quit at
System.Windows.Forms.Button.OnClick(EventAxgs e) A at System Windows.
Forms. Button On Mouse Up(MouseEventAips mevent) at System
.Windows.Forrns.Coritrol.WmMouseUp(Message& m, Mouse Buttons buttc at
System .Wìndows.Forms Control .WndProc(Message& m) at System
.Wmndows.Forms.Button Base .WndProc(Messageš m) at System
.Windows.Forms.Button .WndProc(Message& m) at System .Windows.Forms Control
Control Native Window.On Message(Message& m: at System .Windows.Forms
Control .Control Native Window.Wnd Proc(Message& m) at
System.Wmndows.Forrns.NativeWìndow.CaHbadcQritPtr hWnd, 1nt32 msg, lntPtr’.
Quit, the application will dose immediately. Attempted to divide by zero. a
Details Continue Quit Exception Text A System.OEvideByZero Exception:
Attempted to divide by zero. at System.Decimal.FCallDivide(Decimal& dl.
Decimalš dZ at System.Decimal.opjYvision(Decimal dl, Decimal dZ at
IBS_Planner.PhaseNoise.GeneratePhaseNoise(1nt32 R, Decimal fvco, Decimal f
at IBS_Planner.Mainjom, Generate Phase Noise Plot With Spurs(Decimal fvco.
Deci at IBS_Planner.Main_Form.SetCarrierFrequencyButton_Click(Object
sender, Event, at System .Windows.Forms Control .OnClick(Event,%gs e) at
System.Windows.Forrns.Button .OnClick(EventArgs e) at System Windows.
Forms. Button On Mouse Up(MouseEventkgs mevent) y ),]
Details Continue Quit at System.Windows.Forrns.Button.OnClick(EventAzgs e)
A at System Windows. Forms. Button On Mouse Up(MouseEventAips mevent) at
System .Windows.Forrns.Coritrol.WmMouseUp(Message& m, Mouse Buttons buttc
at System .Wìndows.Forms Control .WndProc(Message& m) at System
.Wìndows.Forms.Button Base .WndProc(Messageš m) at System
System.Wmndows.Forrns.NativeWìndow.CaHbackQritPtr hWnd, 1nt32 msg,
On Mon, May 22, 2017 at 2:26 PM, rbrennan <
Hi. The error seems to be caused by your configuration of the first PLLVCO in the cascade (ADF4351).
The actual error you're seeing happens because the 'Available frefs' box is empty. This means no acceptable Fref is available.
Hi, in my application, the tool does not seem to take account of the minimum VCO frequency. Please see attached txt file for configuration. Can the tool be made to acknowledge the minimum VCO frequency?