One interface
Measurement and evaluation on the VNA in one interface.
Client project · AI · RF measurement
Software for vector network analysers (VNA). It captures the S-parameters of RF components and stores them in Touchstone format. The measurements become models of the components, managed centrally and under version control, so that every version leads back to its measurement data. An AI assistant answers questions about measurements and models in plain language and points out anything unusual.
Key facts
VNA display
Calculated exampleMarker 1
Sweep running
Model BP-01
Version 3
from measurement M-03
m-03.s2p60947e4bd6a7AI note
Narrow dip at 2.120 GHz. |S21| is 5.10 dB lower there than in the measurement behind version 2.
Based on
m-03.s2pm-02.s2pCalculated example: a Chebyshev band-pass filter with three resonators, centre frequency 2.000 GHz, relative bandwidth 20%, ripple 0.1 dB, unloaded Q 100. Computed, not measured: the measurements, model name, checksum and note all come from formulas. They show how measurement, model and note can fit together, not the client’s components, data or the interface of the software.
The picture shows the calculated example measurement M-03 with 401 points from 1.000 GHz to 3.000 GHz. One chart shows |S21| and |S11| in dB over frequency, a Smith chart shows S11. Marker 1 sits at 2.120 GHz: |S21| −5.92 dB, return loss 7.39 dB, VSWR 2.49. There is a narrow dip at that point, and |S21| is 5.10 dB lower than in the measurement behind version 2. The card names model BP-01 in version 3, made from measurement M-03, and the AI note points to the dip.
From the sweep on the VNA to the answer from the AI. All in one piece of software.
elsyQ built the software for a company in radio-frequency engineering. The result comes down to three points. The sections below explain the terms behind them, with a calculated example instead of client data.
Measurement and evaluation on the VNA in one interface.
RF component models managed centrally, every version with its measurement data.
AI assistant for questions about measurements and models.
One wave in, two answers out: what comes back and what gets through.
A vector network analyser sends a radio-frequency signal into a component and sweeps across a range of frequencies, point by point. At every port it measures the incident and the outgoing wave, in magnitude and phase. That is what vector means. The ratios of these waves are the S-parameters, one set for every frequency point. A filter with an input and an output is a two-port and has four of them.
Schematic. The example values come from the calculated band-pass filter on this page, measurement M-02 without the dip, at its centre frequency.
Schematic of a two-port with port 1 and port 2. A wave runs into each port, a1 and a2, and one runs out of each, b1 and b2. S11 is b1 divided by a1 and S21 is b2 divided by a1, both measured while nothing runs into port 2. S12 is b1 divided by a2 and S22 is b2 divided by a2, measured while nothing runs into port 1.
Z0 is the reference impedance, in RF work usually 50 Ω. Return loss and VSWR depend only on the magnitude of Γ; the phase is carried by Γ alone.
It links the incident waves a to the outgoing waves b, afresh for every frequency point.
How strongly a load Z reflects a wave, relative to Z0. If Z equals Z0, Γ is zero and nothing comes back. S11 is the reflection coefficient at port 1.
The reflection in dB. The larger the value, the less comes back: at 20 dB, one per cent of the power is reflected.
The ratio of the highest to the lowest voltage of the standing wave that forms on the line when the load is mismatched. A value of 1 means a perfect match, infinity means total reflection.
How much weaker a wave arrives at port 2 than it was when it went into port 1, in dB. For a filter it is small in the passband and large outside it.
Every load has its point. At the centre, nothing comes back.
The Smith chart shows the reflection coefficient Γ as a point inside a circle. At the centre Γ is zero; on the rim everything is reflected. The short circuit sits on the left, the open circuit on the right, inductive loads in the upper half and capacitive ones in the lower half. The circles mark constant resistance and the arcs constant reactance, so the impedance can be read straight off the chart. The distance from the centre shows how badly a load is matched, and the angle gives the phase of the reflection.
| Load | Impedance | Γ | |Γ| | Angle | Return loss | VSWR |
|---|---|---|---|---|---|---|
| Matched | 50 Ω | 0.000 + j0.000 | 0.000 | undefined | ∞ | 1.00 |
| Open | ∞ | 1.000 + j0.000 | 1.000 | 0.0° | 0.00 dB | ∞ |
| Short | 0 Ω | −1.000 + j0.000 | 1.000 | 180.0° | 0.00 dB | ∞ |
| Below Z0 | 25 Ω | −0.333 + j0.000 | 0.333 | 180.0° | 9.54 dB | 2.00 |
| Above Z0 | 100 Ω | 0.333 + j0.000 | 0.333 | 0.0° | 9.54 dB | 2.00 |
| Inductive | 50 + j50 Ω | 0.200 + j0.400 | 0.447 | 63.4° | 6.99 dB | 2.62 |
| Capacitive | 50 − j50 Ω | 0.200 − j0.400 | 0.447 | −63.4° | 6.99 dB | 2.62 |
Same distance, opposite side: 25 Ω and 100 Ω are equally badly matched, both with a VSWR of 2.00 and a return loss of 9.54 dB. Only the angle of Γ tells them apart. A scalar analyser, which measures magnitude only, sees no difference here; a vector analyser does.
A Smith chart with the point of the selected load. The default is 50 + j50 Ω: Γ lies at 0.200 + j0.400, magnitude 0.447, angle 63.4°. The table lists the values of all seven example loads.
One measurement, one text file. Readable by people and by programs.
The software stores the measurements in Touchstone format. Touchstone is a widely used text format for S-parameters that people can read in an editor and simulators can import directly. The file extension gives the number of ports: .s1p for a one-port, .s2p for a two-port. The line starting with # is the option line, and everything after a ! is a comment. For one-ports and two-ports, one line then follows for each frequency point, holding all the S-parameters.
m-03.s2p60947e4bd6a7401 data lines
# GHz S DB R 50
1.000 -0.015 165.05 -48.112 -106.11 -48.112 -106.11 -0.015 165.05
1.005 -0.016 164.92 -47.893 -106.25 -47.893 -106.25 -0.016 164.92
! ... 220 lines omitted
2.110 -12.178 -30.93 -2.931 -66.96 -2.931 -66.96 -12.178 -30.93
2.115 -9.166 -47.51 -4.573 -67.44 -4.573 -67.44 -9.166 -47.51
2.120 -7.391 -69.05 -5.921 -56.33 -5.921 -56.33 -7.391 -69.05
2.125 -7.074 -89.95 -4.980 -44.20 -4.980 -44.20 -7.074 -89.95
2.130 -7.663 -106.00 -3.514 -42.73 -3.514 -42.73 -7.663 -106.00
! ... 173 lines omitted
3.000 -0.056 -152.45 -32.553 119.68 -32.553 119.68 -0.056 -152.45
# GHz S MA R 50
1.000 0.9982 165.05 0.0039 -106.11 0.0039 -106.11 0.9982 165.05
1.005 0.9982 164.92 0.0040 -106.25 0.0040 -106.25 0.9982 164.92
! ... 220 lines omitted
2.110 0.2461 -30.93 0.7136 -66.96 0.7136 -66.96 0.2461 -30.93
2.115 0.3481 -47.51 0.5907 -67.44 0.5907 -67.44 0.3481 -47.51
2.120 0.4270 -69.05 0.5057 -56.33 0.5057 -56.33 0.4270 -69.05
2.125 0.4429 -89.95 0.5636 -44.20 0.5636 -44.20 0.4429 -89.95
2.130 0.4139 -106.00 0.6673 -42.73 0.6673 -42.73 0.4139 -106.00
! ... 173 lines omitted
3.000 0.9936 -152.45 0.0236 119.68 0.0236 119.68 0.9936 -152.45
# GHz S RI R 50
1.000 -0.96441 0.25759 -0.00109 -0.00378 -0.00109 -0.00378 -0.96441 0.25759
1.005 -0.96381 0.25973 -0.00113 -0.00387 -0.00113 -0.00387 -0.96381 0.25973
! ... 220 lines omitted
2.110 0.21109 -0.12650 0.27927 -0.65666 0.27927 -0.65666 0.21109 -0.12650
2.115 0.23512 -0.25667 0.22662 -0.54545 0.22662 -0.54545 0.23512 -0.25667
2.120 0.15271 -0.39876 0.28040 -0.42089 0.28040 -0.42089 0.15271 -0.39876
2.125 0.00039 -0.44289 0.40412 -0.39292 0.40412 -0.39292 0.00039 -0.44289
2.130 -0.11406 -0.39785 0.49010 -0.45280 0.49010 -0.45280 -0.11406 -0.39785
! ... 173 lines omitted
3.000 -0.88093 -0.45950 -0.01167 0.02048 -0.01167 0.02048 -0.88093 -0.45950
#GHzSDBMARIR 50If an entry is missing, the default applies: GHz, S, MA and R 50.
Calculated example: 401 data lines, one per frequency point from 1.000 GHz to 3.000 GHz. Computed, not measured, and not a file from the project. The checksum is the SHA-256 hash of the whole file in the dB-and-angle format, shortened here to twelve characters.
No model without a measurement. Every version leads back to its data.
The measurements become models of the RF components. The software manages them centrally and under version control, and every version leads back to its measurement data. The illustration below shows in general terms why that matters: comparing two versions means comparing the measurements behind them, and seeing where and by how much they differ.
Version 1
First measurement
from measurement M-01
201 points · 1.500 GHz to 2.500 GHz
m-01.s2p83e9811d4997Version 2
Measurement over a wider frequency range
from measurement M-02
401 points · 1.000 GHz to 3.000 GHz
m-02.s2p7721f71af0bdVersion 3
current
New measurement with a narrow dip
from measurement M-03
401 points · 1.000 GHz to 3.000 GHz
m-03.s2p60947e4bd6a7Version 1 is based on a measurement from 1.500 GHz to 2.500 GHz, version 2 on one from 1.000 GHz to 3.000 GHz. So what is new is mainly the frequency range. Where the two overlap, the curves lie exactly on top of each other and the largest deviation is 0.00 dB. That is down to the calculated example, in which both measurements come from the same formula. Real repeat measurements always scatter a little.
The measurements behind versions 2 and 3 differ most at 2.120 GHz, by 5.10 dB. Between 2.105 GHz and 2.140 GHz the deviation is above 1 dB, everywhere else it stays at 0.87 dB or less.
Illustration with calculated data: the model name, measurements, files and checksums are examples. The curves are the measurements behind the versions. They show what versioning with provenance achieves, not how the software builds or stores the models.
BP-01, three versions, each with its measurement file and checksum. The default comparison shows |S21| of the measurements behind the two latest versions from 1.700 GHz to 2.300 GHz: the measurement behind the latest version lies 5.10 dB lower at 2.120 GHz.
Every version comes with the measurement file it was made from. A checksum shows whether the file is still the same.
Two versions can be compared point by point, because both go back to measurement data on a frequency axis.
With versioning, a new version does not replace the old one; it is added. The old one stays, together with its data.
The three points describe versioning with provenance in general. How the software builds, stores and compares the models internally is not described on this page.
Questions in plain language, and a pointer to anything unusual.
In the software, an AI assistant answers questions about measurements and models in plain language and points out anything unusual. The example below shows what such an exchange can look like, worked out with the example data on this page.
Question
Is anything unusual about measurement M-03?
AI assistant
Yes. Between 2.105 GHz and 2.140 GHz, |S21| has a narrow dip, deepest at 2.120 GHz with −5.92 dB. In the measurement behind version 2, the value at the same point was −0.82 dB, so the loss there has grown by 5.10 dB. The data alone do not show whether the dip comes from the component or from the measurement set-up. Someone should check that.
Based on
How the assistant can go about it
Question
How well is the component matched in the passband?
AI assistant
In the passband of the example, from 1.810 GHz to 2.210 GHz, the return loss in the measurement behind version 2 is at least 16.83 dB everywhere. It reaches its lowest value at 2.210 GHz, at the upper edge of the band. In the measurement behind version 3 it drops to 7.07 dB at 2.125 GHz, right where the dip is. The lower the return loss, the more power comes back.
Based on
How the assistant can go about it
Question
What changed from version 2 to version 3?
AI assistant
Version 3 comes from measurement M-03, version 2 from M-02. Both measurements cover 1.000 GHz to 3.000 GHz with 401 points. Between 2.105 GHz and 2.140 GHz they differ by more than 1 dB, most at 2.120 GHz with 5.10 dB. Everywhere else the deviation stays at 0.87 dB or less.
Based on
How the assistant can go about it
Example: the questions, answers and steps are made up and work with the example data on this page. They show how an assistant can work with measurement data, not how the assistant in the project is built. The file names lead to the data on this page.
Values such as the loss at a given frequency can be read and calculated exactly from the measurement file. A language model can get that arithmetic wrong. So it makes sense to split the work: code does the computing, and the model only does the wording.
An answer that names the file and the frequency range can be checked without having to take the assistant’s word for it.
Whether an anomaly comes from the component or from the measurement set-up is for a person to decide. An assistant can show where it is worth looking.
The three points describe how an assistant can work with measurement data in general. What the assistant in the project is built on and how it works is not described on this page.
How elsyQ separates algorithm and language model: Determinism and AI
Five terms from the project, each explained briefly. Where the key facts say something about their use in the project, it is noted alongside.
A vector network analyser measures, across a range of frequencies, how a component reflects and transmits radio-frequency signals, in magnitude and phase.
In this project The software brings measurement and evaluation on the VNA into one interface.
Scattering parameters: the ratio of outgoing to incident wave at the ports of a component, as a complex number for every frequency point.
In this project The software captures the S-parameters of the RF components.
A text format for S-parameters, with an option line and the measured values for each frequency point. The file extension gives the number of ports, and a file for a two-port ends in .s2p.
In this project The software stores the measurements in Touchstone format.
A model describes how a component behaves at high frequencies, in a form that further work can build on, for example a circuit simulation.
In this project The measurements become models of the components, managed centrally and under version control, every version with its measurement data.
An assistant, usually built on a language model, that answers questions in plain language and draws on data to do so.
In this project Answers questions about measurements and models in plain language and points out anything unusual.
Independently of this project: RF electronics is a focus of our founder, and measurement technology is part of what our team covers. We read schematics like source code and measure before we write firmware for a board. On top of that comes software that computes: numerics, simulation and machine learning on measurement data.
The VNA software with an AI assistant is a client project by elsyQ for a company in radio-frequency engineering: software for vector network analysers (VNA). It captures the S-parameters of RF components and stores them in Touchstone format. The measurements become models of the components, managed centrally and under version control, so that every version leads back to its measurement data. An AI assistant answers questions about measurements and models in plain language and points out anything unusual.
A vector network analyser, or VNA, measures how a component reflects and transmits radio-frequency signals, in magnitude and phase; elsyQ has built software for such instruments in a client project. To do so, it records the incident and the outgoing wave at every port across a whole range of frequencies. The ratios of these waves are the S-parameters.
S-parameters, or scattering parameters, describe how an RF component reflects and transmits waves at its ports; they are exactly what the VNA software that elsyQ built for a company in radio-frequency engineering captures. Each S-parameter is the ratio of an outgoing to an incident wave, as a complex number for every frequency point. A two-port such as a filter has four of them: S11 and S22 for reflection, S21 and S12 for transmission.
Touchstone is a widely used text format for S-parameters, and it is the format in which the VNA software that elsyQ built for a company in radio-frequency engineering stores the measurements. An option line names the frequency unit, the kind of parameter, the number format and the reference resistance, followed by the values for each frequency point. The file extension gives the number of ports, and a file for a two-port ends in .s2p.
In the software that elsyQ built for a company in radio-frequency engineering, the models of the RF components are managed centrally and under version control, and every version leads back to its measurement data. In general, versioning with provenance makes results traceable: whoever uses a version can see which measurement it came from and can compare two versions by their data. A new version does not replace an old one; it is added alongside it.
The AI assistant in the VNA software that elsyQ built answers questions about measurements and models in plain language and points out anything unusual. The conversation on this page is an example with calculated data and does not show the assistant from the project. How elsyQ generally separates what an algorithm computes from what a language model words is described on the page Determinism and AI.
elsyQ builds software for measurement technology beyond this project as well, from driving the instruments to evaluating the data. RF electronics is a focus of the founder, measurement technology is one of the team’s competences, and machine learning on measurement data is one of its services. Which instruments, formats and evaluations you need is something we clarify at the start of the project.
Trademark notice Touchstone is a mark of its owner and is used here only to identify the file format for S-parameters. elsyQ is not affiliated with that owner.
Work with us
Tell us what you measure and what should come out of it in the end. We will tell you how we would build it.