Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
Discontinuities! When you generate a design with microstrip elements you typically need to add discontinuities, TEEs and CROSSes, to create the appropriate layout for simulation in schematic view, or for EM later. When using ideal elements there are no such equivalent components. There will be...
Those are flight lines. They are indicating connections that are interpreted from the layout that no longer agrees with the element schematic connectivity, i.e., difference between schematic and layout. The clue is that you auto-generated the layout from the schematic but then made some changes...
You cannot edit the netlist file, but you can use it to identify the problem that is causing the issue and edit the schematic appropriately and then ADS generates a new (hopefully correct) netlist file when you re-simulate the design.
Main problem is that you did not attach the netlist.log file...
Check the file called "netlist.log" in your workspace directory. This is a text file so it should be easy to identify line #7.
Using the command "Simulate > Generate Netlist" in this schematic should open the default text editor window with this file to read.
What do you mean by ideal mixer block? Do you mean the Mixer2 component? if so what do you have set as the mixer noise figure (default for this is 0db)? More detail about your test circuit would help to diagnose any issue.
As Volker says starting a new workspace would be a useful step to verify what may be happening.
For the existing workspace what you show in the Manage Libraries UI is the wrong end of the list. You should look right at the very top. Typically, the analog_rf.defs is the first item and this is...
It is not possible to interpret what the simulation step size that you are using is (which would determine the number of frequency points) but it needs to be changed. A good starting point would be 101 points (Step-size of 30 MHz for 1GHz to 4GHz sweep) would give a smoother response.
You could always flip the screen, temporarily at least, to portrait orientation instead of landscape orientation.
Easiest if you are using multiple or external monitors but it would also be possible with a single laptop screen but only if you have external mouse and keyboard in operation.
In its resting state a parameter that is set to be optimizable you do only see the nominal value and an indication of the optimizable style on screen:
However, if you want to use on-screen editing simply go ahead and click on the parameter value. As soon as it becomes selected it shows the...
Looking at the first design, Optimization_L_C_R, there are many items entered incorrectly and a couple of these are blocking the simulation from working.
In the second design, Optimization_L_C_R_Modi, you appear to have 'fixed' most of these issues but there is still one remaining. In the...
It is entirely appropriate to define multiple Tune/Opt/Stat/DOE Setup to a single parameter or variable. They are never all used at the same time, but each is active for the different types of simulation. So, ADS allows the user to enable all four concurrently, but the simulator only uses one at...
You initially reported that an error was generated when attempting to perform optimization for this design. I presume that now with better set-up for the optimization variables that this error is no longer the problem.
Now you simply say that "I am not getting output" but this is not helpful to...
As Big Boss mentioned previously you are using the Tuning option in the Simulation Variables Dialog. You should have all these setting in the Optimization Tab (the second tab) to get optimization to work.
What do you have set for the Order in the HB simulation? Your EM simulation frequency range must include all harmonics specified and not just the fundamental frequency.
Try doing something different at the other pin. The fact that you are relying on an area pin and not a point pin may be the issue.
If you use a MTEE instead of that MCORN this would leave an available pin. Not is exactly the same position but it may give you results to get started. You could...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.