-
-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
determining line impedance with scikit-rf #421
Labels
Feature Request
Wished Feature
Comments
obviously this requires z0 for the s-parameter measurement to be known. 810labs has a closed form solution to that problem (which gives both Zl and Gamma(mostly!)) . i am not aware of a open-source closed form solution, but there certainty could be. i would look into dielectric characterization algorithms. if you want to test it, you can send me the s-parameters and i can send back results. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I came across scikit-rf today and am wondering if it already has the built in functionality to extract the characteristic impedance of an unknown transmission line for which I have s-parameter data. The basic way I would measure this is:
With lab measurements that can work fairly well if you don't get too near integer multiples of a quarter wavelength where the measurement of Zshort and Zopen gets tricky.
So what I'm wanting to do is essentially make this determination starting with s-parameter data that is either measured or simulated. To complicate things a little, what I'd really like is to do this on say a 12-port file where I have 3 differential transmission lines so 6 mixed-mode ports or 12 single ended ports. I've been able to load a
.s12p
file and convert to mixed mode with something like:I can plot my mixed-mode s-parameters, but haven't figured out how to do the open/short calculations in the context of scikit-rf to be able to determine even/odd mode characteristic impedance of the lines. Any suggestions?
Thanks
-Dan
The text was updated successfully, but these errors were encountered: