Yes it is, I also don't have any idea, prolly it's attributed to the wrong port assignments?I am still puzzled why both through port and isolated port are at -3dB in the initial post. Does the plot show the correct dataset?
For odd mode, you can connect a port with explicit reference node (Term, not TermG) between the two inputs/outputs.so I wanted to perform odd and even mode analysis on the same coupler
I understand your point and thank you for the feedback. But with my circuit, what could be causing the "error" with the coupling coefficient graph, is it because I'm "omitting" one port ? Or my circuit just won't work cause ideally I'm supposed to use this setup in the schematic to determine the even odd mode analysis of the coupler.For odd mode, you can connect a port with explicit reference node (Term, not TermG) between the two inputs/outputs.
For even mode, you can connect the inputs/outputs in parallel.
Another possibility is the Balun4Port element in palette System-Passive, this has two terminals for the device (mixed mode) and one terminal each for differential mode and common mode. I use that element a lot for testing mode conversion.
I really think you plotted the wrong dataset (results from another other simulation).But with my circuit, what could be causing the "error" with the coupling coefficient graph
I'm pretty sure it was the data display I brought on here, I don't know what was wrong too. I have fixed that but with respect to the new circuit I have added(with the divider and shifter) above in one of the comments . How am I not getting the coupling coefficient graph showing a -10 dB value. Thanks alot.I really think you plotted the wrong dataset (results from another other simulation).
If I reproduce your exact case, including your port numbers, I get meaningful data.
View attachment 188458
Honestly to some extent I actually thought the port numbers didn't matter much until my attention was drawn to it so maybe it's his settings in the ADS allowing him to do that. Maybe jut maybe.Interestingly, the classical convention for Directional Coupler does not fit into this simulation.
Input: Port-1
Output: Port-2
Coupled: Port-3
Isolated: Port-4
But the simulation results of Volker show us this convention is not "unique" for all cases.
OR, s-matrix of Coupled Lines in ADS is different than this convention.
Yhyh I understand your method but from the attachment I have included, see I am supposed to follow specific steps to get the even/ odd mode analysis and that is why I am kind of trying to find the issue with it. I am not denying the effectiveness of your method.I described in #5 the proper way to do arbitrary even/odd mode excitation and termination (!) with the Balun4Port, instead of your divider/phase shifter approach.
The port numbers in ADS don't matter, as long as you interpret things correctly for the actual port configuration. Bigboss was showing a symbolic coupler that where the isolated port is on the other side, that is different from physical realization of a line coupler.
Oh alright then, I did obtain the answers then, I obtained such results as you did as well. Thanks alot. I actually thought since I wasn't getting the -10 dB coupling coefficient I was wrong.@jadnounyah Yes, with that configuration you get the -3dB results from your initial post. You then do NOT get the -10dB coupling, of course, because you drive both lines simultaneously.
Your text says you need to measure the input impedance. You get this in ADS with the data display equation Zin=stoz(S(1,1)) shown below, and find the common mode and differential mode values as input impedance. I think this is what your teacher wants you to see.
View attachment 188677
0 degree phase offset for common mode:
View attachment 188678
180 degree phase offset for differential mode:
View attachment 188679
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?