Getting Parse Error while simulating Power Amplifier using ADS

Status
Not open for further replies.
P

pusparaga

Full Member level 4
Joined
Oct 19, 2013
Messages
197
Helped
4
Reputation
8
Reaction score
4
Trophy points
1,298
Activity points
2,988
I have created sub-circuits for input and output matching of Power Amplifier and also included Optimization. I am getting Parser Error as it is showing Parser Error at line 50. How to remove this Parser Error and how to find out line number in 50 in ADS.
 

Attachments

  • Input_Matching.jpg
    98.7 KB · Views: 105
  • Output_Matching.jpg
    84.2 KB · Views: 94
  • ERROR_Getting.jpg
    112.7 KB · Views: 97
  • Schematic.jpg
    152.3 KB · Views: 100

Sort by date Sort by votes
Hi,

Have you defined your variables for optimization?
Use in menu Simulate-> Generate Netlist for seeing your Netlist.

Regards
 

    P

    pusparaga

    Points: 2
    Helpful Answer Positive Rating
Upvote 0 Downvote
psach27 said:
Hi,

Have you defined your variables for optimization?
Use in menu Simulate-> Generate Netlist for seeing your Netlist.

Regards
Click to expand...
Yes, I have generated Netlist. In the error message, it is showing error in the line number 15. I went and searched line number 15 parameters. Even I checked and changed MSTEP:Step2 N__6 N__10 Subst="MSub1" W1=0.835 mm W2=1.5 mm. But I couldn't able to remove error. I have attached netlist report, error message, schematic, symbol generated for input and output matching, input matching, and output matching.
 

Attachments

  • Error_Message.jpg
    96.6 KB · Views: 140
  • Schematic.jpg
    194.2 KB · Views: 93
  • Input_Matching_Ckt.jpg
    93.1 KB · Views: 92
  • Output_Matching_Ckt.jpg
    89.5 KB · Views: 95
  • Symbol for_Input_Output_Matching.jpg
    68.5 KB · Views: 93
  • Netlist_Port.jpg
    385.1 KB · Views: 92
  • Netlist.pdf
    243.9 KB · Views: 123

Upvote 0 Downvote
BigBoss said:
Correct "Hu" value in MSUB definition.
Click to expand...
As you mentioned, I corrected Hu and simulated. But I am not getting problem from Hu. Later I am getting example MLIN2 TL12. Once again I corrected problem of MLIN2 TL12. Next time I am not getting problem from TL12, but am getting TL11. Once I corrected TL11, next time I am getting problem from TL10. It keeps on going for TL10, TL9, TL8, TL7............
I am really confused. Just I have followed Anuragh Bhargav's Page No. 14, 18, and 20 YouTube RF -Power Amplifier Design Tutorial-17 (Attached Below). Is there any problem in input matching or output matching or main schematic. I am not really understanding. Guide me how to simulate this without any error.
 

Attachments

  • Error_Message_2.jpg
    105.5 KB · Views: 94
  • Anurgha_Bhargav_RF_Design_17_Tutorial.pdf
    3.4 MB · Views: 118
  • Netlist_for_Message_2.jpg
    239.7 KB · Views: 95
  • Netlist_ for_Message_1.jpg
    228.3 KB · Views: 94
  • Error_Message_1.jpg
    106 KB · Views: 111

Upvote 0 Downvote
 

Upvote 0 Downvote
Your netlist PDF has some extra line breaks that confuse when searching for the "true" netlist line 45 that causes the error.
 

Upvote 0 Downvote
volker@muehlhaus said:
Your netlist PDF has some extra line breaks that confuse when searching for the "true" netlist line 45 that causes the error.
Click to expand...
How to avoid some extra line breaks that cause error. When we go and search line 45 or 50. There are no errors at all.
How to overcome this parse error.
I have simulated once again and attached below the error messages and netlist pdf also.
 

Attachments

  • Error_Message.jpg
    104.3 KB · Views: 131
  • Error_Message_Finding_Line_Number_50.jpg
    338.7 KB · Views: 96
  • Netlist_PDF.pdf
    249.7 KB · Views: 135

Upvote 0 Downvote
pusparaga said:
How to avoid some extra line breaks that cause error.
Click to expand...
You totally misunderstand things!

The error is not from the line break. The line break that I mentioned is only relevant in finding the error line in your netlist. Your editor breaks long lines, so that the line number seen in your editor is not the true line where ADS reports the error.

You can choose a smaller text font in your editor, to avoid the line break. Then you will hopefully see in editor line 50 the content from ADS netlist line 50.
 

    N

    narayani

    Points: 2
    Helpful Answer Positive Rating
Upvote 0 Downvote
Parse Error is showing in line number 50. But when I went and checked showing error in the line number 50. But it seems to be ok. I couldn't find error in MTEE7.
--- Updated ---

Parse Error is showing in line number 50. But when I went and checked showing error in the line number 50. But it seems to be ok. I couldn't find error in MTEE7.
--- Updated ---

Parse Error is showing in line number 50. But when I went and checked showing error in the line number 50. But it seems to be ok. I couldn't find error in MTEE7.
--- Updated ---

Parse Error is showing in line number 50. But when I went and checked showing error in the line number 50. But it seems to be ok. I couldn't find error in MTEE7.
--- Updated ---

Parse Error is showing in line number 50. But when I went and checked showing error in the line number 50. But it seems to be ok. I couldn't find error in MTEE7.
--- Updated ---

Parse Error is showing in line number 50. But when I went and checked showing error in the line number 50. But it seems to be ok. I couldn't find error in MTEE7.
 

Attachments

  • Error_Message.png
    33 KB · Views: 126
  • Line_Number_50_Error_Line.png
    223.7 KB · Views: 84
  • MTEE_Line_50.png
    30.7 KB · Views: 87

Upvote 0 Downvote
OMG, why is it so difficult to save the netlist into a simple text file and open it in the editor (or post the netlist here)? With your RTF you have messed up the contents again, with all these \par that are not included in the original netlist.

I spotted one mistake in your netlist screenshot, but that's not line 50 in your editor:

 

Upvote 0 Downvote
Problem is solved.
 

Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…