matching_network
Solve L-section lumped parameters matching networks in a wink. (See How to use section)
Shunt-series config.
Series-shunt config.
| Jupyter Notebooks |
|---|
| L-section_matching_calculations (Initial Jupyter notebook implementation) |
| Calculations (Matlab pre-calculations) |
Installation
pip install matching_network
How to use
From the CLI
matching_network --from 100 --to 20+43j --freq 13.56e6 # both impedances in Ω.
From (100+0j) Ω to (20+43j) Ω
normalized starting impedance = (100+0j)Ω / (20+43j)Ω = 0.88928-1.912j
#solutions: 4
shunt-series
Shunt Inductor:
X = 50 Ω ⇔ B = -20 mS
L = 586.85 nH (@ 13.56 MHz)
Series Inductor:
X = 3 Ω ⇔ B = -333.33 mS
L = 35.211 nH (@ 13.56 MHz)
shunt-series
Shunt Capacitor:
X = -50 Ω ⇔ B = 20 mS
C = 234.74 pF (@ 13.56 MHz)
Series Inductor:
X = 83 Ω ⇔ B = -12.048 mS
L = 974.18 nH (@ 13.56 MHz)
series-shunt
Series Inductor:
X = 35.285 Ω ⇔ B = -28.341 mS
L = 414.14 nH (@ 13.56 MHz)
Shunt Inductor:
X = 62.571 Ω ⇔ B = -15.982 mS
L = 734.4 nH (@ 13.56 MHz)
series-shunt
Series Capacitor:
X = -35.285 Ω ⇔ B = 28.341 mS
C = 332.64 pF (@ 13.56 MHz)
Shunt Inductor:
X = 44.929 Ω ⇔ B = -22.257 mS
L = 527.33 nH (@ 13.56 MHz)
matching_network --from "24.3+8.3j mS" --to 1.1+9.3j # default in Ω unless specified, using `mS`.
Inside Python
>>> import matching_network as mn
>>>
>>> impedance_you_have = 90 + 32j # Ω
>>> impedance_you_want_to_have = 175 # Ω
>>>
>>> frequency = 900e6 # Hz
>>>
>>> mn.L_section_matching(impedance_you_have, impedance_you_want_to_have, frequency).match()
From (90+32j) Ω to 175 Ω
normalized starting impedance = (90+32j)Ω/175Ω = 0.51429+0.18286j
#solutions: 2
series-shunt
Series Inductor:
X = 55.464 Ω ⇔ B = -18.03 mS
L = 9.8082 nH (@ 900 MHz)
Shunt Capacitor:
X = -180.07 Ω ⇔ B = 5.5533 mS
C = 982.04 fF (@ 900 MHz)
series-shunt
Series Capacitor:
X = -119.46 Ω ⇔ B = 8.3707 mS
C = 1.4803 pF (@ 900 MHz)
Shunt Inductor:
X = 180.07 Ω ⇔ B = -5.5533 mS
L = 31.844 nH (@ 900 MHz)
>>>
Metadata
Release files for matching-network 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| matching_network-0.1.6.tar.gz | 5.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| matching_network-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.5 kB
Release files / matching_network-0.1.6.tar.gz
| Download URL | matching_network-0.1.6.tar.gz |
|---|---|
| Size | 5.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e89feab35d7bdf10434df864736caeed6000394c54143085429fc1599131c35f
|
|
BLAKE2b-256 checksum How to use checksums |
74b7a063dcdd8ee3fb76d168bb3fe6e209df23493a7859e32fef30e3666d33df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.6 CPython/3.8.9 Darwin/18.7.0
|
Release files / matching_network-0.1.6-py3-none-any.whl
| Download URL | matching_network-0.1.6-py3-none-any.whl |
|---|---|
| Size | 6.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6eb888910c09b6910bfcdca3a07961b93c5b69be7af78c7c79a777c52e9e4ea2
|
|
BLAKE2b-256 checksum How to use checksums |
5e657d2d92f33f2fd43cafee4da7fc6e9b08dec33685b1aa1c0c17111ba8bcfb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.1.6 CPython/3.8.9 Darwin/18.7.0
|
Security for matching-network 0.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.