Vector Network Analyzer


#61

First, thanks for the feedback! That is in fact true as I am working with 915MHz ISM band equipment (LoRa radios), so with very little thought applied I changed the LNA to LNAL figuring that was an easy fix. I just ran the test using the stock settings (with changes outlined in the blog post) on a 2.4GHz wifi antenna and I see the results I would expect.

This then leads to the question - can your team offer any guidance as to how one might best perform the same function at 900MHz? The blog post suggests:

Is that to suggest that it simply can’t happen? Or that it needs a bunch of changes to the script to make it work?

edit: confirmed on the phase noise when running LNAH @ 900MHz:


I’m not sure if this is going to help my tune my antenna or tell my my horoscope :smiley:


#62

A new measurement script for 800 - 1000 MHz range has been uploaded to GitHub VNA example:


Documentation has also been updated to show the setup for new script:
https://github.com/myriadrf/pyLMS7002M/blob/master/examples/VNA/doc/LMS7002M_VNA.pdf
In short, TX1_1 and RX1_L are used to transmit/receive.

Please try the new measurement script and post results.


#63

THANK YOU SO MUCH!

This new script works a lot better for the low range RX/TX. Plots actually make sense and the values are within the ranges I would expect.



This was a quick test running under less-than-ideal conditions (namely, antenna laying on my concrete floor in a room with several other active radios all blasting out traffic in the test frequency band), but given that I think I can actually use this as a tool moving forward.

Thanks!


#64

Great, I’m glad that it worked.
S11 and VSWR are consistent, but Smith chart plot looks a bit strange.
The trace on Smith chart is almost entirely outside of VSWR<2 circle, but according to VSWR plot the trace should go very close to the center.
Have you used the version of pySmithPlot linked in PDF document or a newer one?
Python 2 or 3?


#65

You are absolutely correct in that I have the 2.0 version of pySmithPlot installed. I downloaded the linked release and I cannot seem to get that running under Python 3.6.5 on Windows. I spun up a new Win 10 VM, installed python-3.6.5-amd64.exe into C:\Python36, ran setup.py on the pySmithPlot release linked above (which worked), downloaded the latest pyLMS7002M-master branch, ran setup.py there (also worked), then attempted to run calculateVNA_900M.py against the test data from the measurements shown above. I also ran this on my existing PYthon 3.6 installation, and have tried it in a new venv before spinning up the VM all in attempt to start from a “clean” environment. In all cases, I get the following error when attempting to execute “python calculateVNA_900M.py vna_test900-01 plot”:

C:\Download\pyLMS7002M\examples\VNA>python calculateVNA.py vna_test900-01 plot
Traceback (most recent call last):
  File "calculateVNA.py", line 25, in <module>
    import smithplot
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 656, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 626, in _load_backward_compatible
  File "C:\Python36\lib\site-packages\pysmithplot-0.1.0-py3.6.egg\smithplot\__init__.py", line 2, in <module>
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 951, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 894, in _find_spec
  File "<frozen importlib._bootstrap_external>", line 1157, in find_spec
  File "<frozen importlib._bootstrap_external>", line 1131, in _get_spec
  File "<frozen importlib._bootstrap_external>", line 1112, in _legacy_get_spec
  File "<frozen importlib._bootstrap>", line 441, in spec_from_loader
  File "<frozen importlib._bootstrap_external>", line 544, in spec_from_file_location
  File "C:\Python36\lib\site-packages\pysmithplot-0.1.0-py3.6.egg\smithplot\smithaxes.py", line 1262
    def _moebius_xy((x, y)):
                    ^
SyntaxError: invalid syntax

pip list returns the following:

cycler (0.10.0)
Cython (0.28.1)
kiwisolver (1.0.1)
matplotlib (2.2.2)
numpy (1.14.2)
pip (9.0.3)
pylms7002m (1.2.0)
pyparsing (2.2.0)
pyserial (3.4)
pysmithplot (0.1.0)
python-dateutil (2.7.2)
pytz (2018.4)
pyusb (1.0.2)
setuptools (39.0.1)
six (1.11.0)

I’ll see if the process fares any better under Ubuntu 16.04 LTS.

edit: build results under 16.04 gives the same error for the same line while building the suggested release of pySmithPlot via python3 setup.py install:

byte-compiling build/bdist.linux-x86_64/egg/smithplot/smithaxes.py to smithaxes.cpython-34.pyc
  File "build/bdist.linux-x86_64/egg/smithplot/smithaxes.py", line 1262
    def _moebius_xy((x, y)):
                    ^
SyntaxError: invalid syntax

Executing on that 16.04 instance yields an error nearly identical to the Windows version:

~/pyLMS7002M/examples/VNA$ python3 calculateVNA_900M.py test900-01 save
Traceback (most recent call last):
  File "calculateVNA_900M.py", line 25, in <module>
    import smithplot
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 958, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 664, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 634, in _load_backward_compatible
  File "/usr/local/lib/python3.5/dist-packages/pysmithplot-0.1.0-py3.5.egg/smithplot/__init__.py", line 2, in <module>
  File "<frozen importlib._bootstrap>", line 969, in _find_and_load
  File "<frozen importlib._bootstrap>", line 954, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 896, in _find_spec
  File "<frozen importlib._bootstrap_external>", line 1139, in find_spec
  File "<frozen importlib._bootstrap_external>", line 1115, in _get_spec
  File "<frozen importlib._bootstrap_external>", line 1096, in _legacy_get_spec
  File "<frozen importlib._bootstrap>", line 444, in spec_from_loader
  File "<frozen importlib._bootstrap_external>", line 533, in spec_from_file_location
  File "/usr/local/lib/python3.5/dist-packages/pysmithplot-0.1.0-py3.5.egg/smithplot/smithaxes.py", line 1262
    def _moebius_xy((x, y)):
                    ^
SyntaxError: invalid syntax

Python modules:

:~/pyLMS7002M/examples/VNA$ pip3 list
chardet (2.3.0)
command-not-found (0.3)
cycler (0.10.0)
kiwisolver (1.0.1)
language-selector (0.1)
matplotlib (2.2.2)
numpy (1.14.2)
pip (8.1.1)
pycurl (7.43.0)
pygobject (3.20.0)
pyLMS7002M (1.2.0)
pyparsing (2.2.0)
pyserial (3.4)
pysmithplot (0.1.0)
python-apt (1.1.0b1+ubuntu0.16.4.1)
python-dateutil (2.7.2)
python-debian (0.1.27)
python-systemd (231)
pytz (2018.4)
pyusb (1.0.2)
requests (2.9.1)
setuptools (20.7.0)
six (1.10.0)
ssh-import-id (5.5)
ufw (0.35)
unattended-upgrades (0.1)
urllib3 (1.13.1)
virtualenv (15.0.1)
wheel (0.29.0)

Here is the source data if it would be of any help:
vna_test900-01_short_800000000.0_1000000000.0_201.txt
vna_test900-01_DUT_800000000.0_1000000000.0_201.txt


#66

The VNA code has been developed and tested with Python 2.7 and the pySmithPlot library linked in the PDF file.
Please use these versions, as this is known to work.

I’ve plotted your measurement data with code from GitHub, and the Smith chart now makes sense.
Maybe there is a bug in new version of pySmithPlot?


#67

That’s exactly what I was hoping to see from this! I’ll keep working on my side trying to sort this out and I’ll report back when I have it working. I bought the LimeSDR as a test/measurement device and this is my number one use case, and I’m thrilled to see it actually generating usable output. I really appreciate all your help here!


#68

Scripts generate Touchstone file (.s1p) which can be viewed in online S parameter tool, such as
http://www.magimaji.com
This could save you the trouble of figuring out why the new version of pySmithPlot is not producing correct results.


#69

Allright I finally have this working under Windows and Python 2.7.13 and pySmithPlot 0.1.0. The problem I eventually ran into was related to matplotlib: version 2.2.x has removed support for axes.color_cycle (deprecated in 1.5.0) which is used in pysmithplot, and so things were failing until I reverted to an older version via pip install matplotlib==2.1.2. This appears to be the last version of matplotlib that will work with pysmithplot 0.1.0. matplotlib 2.2.0 is also noted to be the last version that will support python 2.7.

So, with Python 2.7, matplotlib 2.1.2, and pysmithplot 0.1.0 this collection of scripts works as expected. Thanks again for your guidance here, I think I have what I need!


#70

Really good to see this work! I’m looking forward to testing it myself.

Just a comment - I’m trying to learn some of the pyLMS7002M usage, but it’s tough sledding.
For instance - the script has:

# Make ADC and DAC clocks equal
lms7002.CGEN.EN_ADCCLKH_CLKGN = 0
#in CGEN Control Diagram, forward divider
# and CGEN config memory, 0x0086 bits 11:
# EN_ADCCLKH_CLKGN: Selects if F_CLKH or F_CLKL is connected to FCLK_ADC
# (F_CLKH and F_CLKL are the two internally generated clocks.
# A MUX will connect one of them to FCLK_ADC and the other to FCLK_DAC.).
# 0 – FCLK_ADC from F_CLKH / FCLK_DAC from F_CLKL
# 1 – FCLK_ADC from F_CLKL / FCLK_DAC from F_CLKH (default)
#
lms7002.CGEN.CLKH_OV_CLKL_CGEN = 2
# in CGEN same forward divider
# and CGEN config memory, 0x0089, bits 12-11
# CLKH_OV_CLKL_CGEN[1:0]: FCLKL here is ADC clock. FCLKH is the clock to the DAC and if no division is added to the ADC as well.
# Default: 0
# FCLKL=FCLKH/2^(CLKH_OV_CLKL)

The first option switches DAC/ADC from FCLKL/FCLKH easy enough.
The 2nd looks like it’s setting FCLKL to FCLKH / 4 ? I don’t see how that makes them equal.

You can see that in the GUI also not equal but in a different way:

Which leads to the next comment - it’s going to be sort of limiting if we have to hire an LMS7002M programmer to have the LimeSDR do what we want, whereas the popular but expensive NI gear you just use it :slight_smile:


#71

python code lms7002.CGEN.CLKH_OV_CLKL_CGEN = 2 uses chip register value (as in 0,1,2,3), while in GUI the combobox displays values of 2^CLKH_OV_CLKL (as in 1,2,4,8)


#72

Ok thanks - I see that in the source now:

txtFrequencyCLKL->SetValue(wxString::Format(_("%.3f"), cgenFreq / pow(2.0, cmbCLKH_OV_CLKL_CGEN->GetSelection())));

from https://github.com/myriadrf/LimeSuite/blob/master/src/lms7002_wxgui/lms7002_pnlCLKGEN_view.cpp

For a positive note, what I was attracted to in the LimeSDR is you really get a lot for your $$, or this thing has more nerd knobs than I have brain cells left.

Will continue digging in and putting the puzzle pieces together.


#73

Getting the hang of this and it’s really working great. I designed a small PCB for a 1090MHz bandpass SAW filter and being able to test with the LimeSDR really makes a difference (surprisingly, the filter appears to work). Using a 10dB filter here, but looks like I should be using 20dB so further testing is on hold until that arrives.


#74

Now my question would be will this work with the Limesdr mini?


#75

First step would be pyLMS7002M support:


#76

Hello @andrewback .
I just ported the package to Python 3.
The repository is available here: https://github.com/mariocannistra/pyLMS7002M

Most of the changes (95%) have been made automatically running 2to3.py (standard python) and few others directly by me. Most of them are about module imports.

Please note that like many others I’m using Python 3.x, Jupyter notebooks and several scientific packages that benefit from lots of new stuff available in Python 3.x.

IMHO, you should consider this upgrade to this important package ever since it would enlarge the involved user base.
There’s a big movement around the push to phase out python 2.7… http://python3statement.org/

Another important topic:

I would kindly ask your team to check if it can be possible to leverage inside measureVNA.py the same tuning operations that allow soapy_power and the various radio listening sw (GQRX, SDR Console, etc) to tune below the 240 MHz limit. With those programs it is possible to listen AM, HF, FM and air frequencies…

Being able to test filters and antennas at HF (but not only) would be a real plus.

I already have 4 devices to test and… I can’t because of this limitation… I remember that in the past also other forum members like @M0GLO , @marukqs , @Axeman were asking questions about this topic…

I’ve seen lots of changes/improvements/refactoring in the release notes … I’m wondering if those could be leveraged in the VNA scripts…

mario


#77

Hi @mariocannistra,

Many thanks! I’ve just forwarded details to the team and asked for clarification on Python 3 and use <240MHz.

Although originally just intended as an example/demo, the VNA application does seem to be reasonably popular.

Andrew


#78

Thank you @andrewback .
Please find below the script I’ve prepared and run for the automated portion of the porting.
I’ve run this directly in the package subfolder where the scripts are.
This was a .bat on windows but can obviously become .sh on Linux changing the path to the .py script.

python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w __init__.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w ADF4002.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w boardUSB.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LimeSDR.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LimeSDR_FPGA.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_AFE.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_base.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_BIAS.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_calibration.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_CDS.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_CGEN.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_CHIP.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_DCCAL.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_EVB.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_GFIR.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_GFIR1.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_GFIR2.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_GFIR3.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_IO.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_LimeLight.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_mSPI.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_NCO.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_RBB.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_regDataStructs.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_REGDESC.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_REGDESC_MR3.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_RFE.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_RxTSP.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_SX.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_TBB.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_TRF.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_TxTSP.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w LMS7002_XBUF.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w QSpark.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w QSpark_FPGA.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w Si5351.py
python C:\ProgramData\Anaconda3\Tools\scripts\2to3.py -w weakproxy.py

#79

LimeSDR Mini is now supported.
pyLMS7002M library is obsolete, and is replaced by pyLMS7002Soapy, which uses SoapySDR backend.
This should eliminate problems with switching drivers and compiling cyLimeLib.
Please take a look at:

Scalar network analyzer example is added too.
Unless you really need the phase information, we strongly encourage you to use SNA since it is faster.


#80

Hello @dgrujic and thank you for posting this new sw.
I tried the SNA example and got some results but several error messages were shown (see at end of this message).
I first tested an FM antenna using the following setup:

and then replaced the RF bridge with a FM notch filter 88-108 MHz for a second test.
These are the results…
antenna:

notch filter:

I then repeated the first test for the antenna removing the terminator from the REF port of the RF bridge and got this other result that seems closer to what i was expecting:

Here below the errors I got during the processing.
I have the feeling that all the tuning errors produce unexpected values in the output…
Do you have suggestions on how to remove those errors?
Searching the forum I’ve seen that users that got those error when using LimeSuite did not configure either the receiver or the transmitter before calibrating… but i think this is not the case.

Also, I see the TX LPF is automatically set to 100 MHz: in this case where I’m testing between 50 and 150 MHz I’m wondering if this can represent an issue actually attenuating the transmitted signals > 100 MHz for the upper half of my sweep… ?

I’ve used LimeSDR USB (not the Mini) with gateware v2.16 and latest ( v18.04.1, 2018-04-26) Pothos/LimeSuite/Soapy installed.

Not sure why soapy lists it as USB 2 (see below), it’s a USB 3 port (properly reported by LimeSuite).

[INFO] Make connection: 'LimeSDR-USB [USB 2.0] 9060B00462323'
[INFO] Reference clock 30.72 MHz
[INFO] Device name: LimeSDR-USB
[INFO] Reference: 3.072e+07 MHz
[INFO] LMS7002M calibration values caching Disable
[INFO] Filter calibrated. Filter order-2nd, set to 100 MHz
[INFO] TX LPF configured
Connect SHORT. Type y to continue. y
[INFO] Tx calibration finished
[ERROR] Rx calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.050 - 0.053 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.053 - 0.055 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.055 - 0.058 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.058 - 0.060 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.060 - 0.063 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.063 - 0.065 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.065 - 0.068 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.068 - 0.071 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.071 - 0.073 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.073 - 0.076 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.076 - 0.078 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.078 - 0.081 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.081 - 0.083 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.083 - 0.086 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.086 - 0.088 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.089 - 0.091 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.091 - 0.094 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.094 - 0.096 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.096 - 0.099 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.099 - 0.101 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.101 - 0.104 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.104 - 0.106 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.106 - 0.109 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.109 - 0.112 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.112 - 0.114 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.114 - 0.117 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.117 - 0.119 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.119 - 0.122 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.122 - 0.124 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.124 - 0.127 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.127 - 0.129 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.130 - 0.132 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.132 - 0.135 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.135 - 0.137 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.137 - 0.140 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.140 - 0.142 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.142 - 0.145 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.145 - 0.147 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.148 - 0.150 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.150 - 0.153 GHz .................

Connect DUT. Type y to continue. y

[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.050 - 0.053 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.053 - 0.055 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.055 - 0.058 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.058 - 0.060 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.060 - 0.063 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.063 - 0.065 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.065 - 0.068 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
[WARNING] L
Measuring 0.068 - 0.071 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.071 - 0.073 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.073 - 0.076 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.076 - 0.078 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.078 - 0.081 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.081 - 0.083 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
[WARNING] L
Measuring 0.083 - 0.086 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.086 - 0.088 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.089 - 0.091 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.091 - 0.094 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
[WARNING] L
Measuring 0.094 - 0.096 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.096 - 0.099 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.099 - 0.101 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.101 - 0.104 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.104 - 0.106 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
[WARNING] L
Measuring 0.106 - 0.109 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.109 - 0.112 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.112 - 0.114 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.114 - 0.117 GHz .................
[ERROR] Tx Calibration: MCU error 3 (SXR tune failed)
Measuring 0.117 - 0.119 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.119 - 0.122 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.122 - 0.124 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.124 - 0.127 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.127 - 0.129 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.130 - 0.132 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.132 - 0.135 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.135 - 0.137 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.137 - 0.140 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.140 - 0.142 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.142 - 0.145 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.145 - 0.147 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.148 - 0.150 GHz .................
[ERROR] Tx Calibration: MCU error 5 (Loopback signal weak: not connected/insufficient gain?)
Measuring 0.150 - 0.153 GHz .................

thank you,
mario