开云体育

/g/nanovna-users/files/NanoVNA%20PC%20Software/TAPR%20VNA/VNAR4.2.zip

Hello Erik

Just for fun I am trying to install your app using Wine on Linux Mint 19.2 64 bit.

What M$ libraries do I need e.g. VC++ runtime, dot Net etc?

Is your executable 32-bit or 64-bit?

73
Nick

Its 32 bit and you will need dotNet and VC++ 2010 runtime

On 12/09/2019 12:19, erik@... wrote:

Its 32 bit and you will need dotNet and VC++ 2010 runtime

All dotNet versions??

No clue, test?

To all,

I did some work on making the application quicker and more robust and corrected some errors
Updated executable; /g/nanovna-users/files/NanoVNA%20PC%20Software/TAPR%20VNA/VNAR4.2.zip

On Thu, Sep 12, 2019 at 07:43 AM, <erik@...> wrote:

To all,

I did some work on making the application quicker and more robust and
corrected some errors
Updated executable;
/g/nanovna-users/files/NanoVNA%20PC%20Software/TAPR%20VNA/VNAR4.2.zip

Sorry, but it does not work for me. My NanoVNA has latest Hugen firmware not your firmware.

When I start TAPR software it causes NanoVNA to have all white screen. It will not recognize the serial com port.

After several attempts, it gets past the "can't find com port screen", then it says can't find VNA on this com port.

After some more trial and error, including re-booting my NanoVNA several times, the main screen comes on. When I try a sweep, it says there is a time out.

This same stuff happens over and over. There is no problem with NanoSharp or Python version.

Dear Erik,
I am trying to run your ap on my just received NanoVNA. For some reason I don't get a USB SERIAL PORT. On My windows 7 Device Manager I get a
OTHER DEVICES listing with Chiblos/RT Virtural COM PORT when I plug in my NanoVNA. I am trying to scratch my head and figure out what to do now.

M NanoVNA is original firmware. Your software worked good in the mockup mode but doesn't seem to see my NanoVNA when plugged into the USB PORT.

ANY SUGGESTIONS FROM ANYONE?
73 Dave WA5DJJ

Hello Erik,

Thank you very much for adopting the TAPR-VNA program (Windows only) to the nanoVNA.

First I had to add the DLL's: msvcp100.dll and msvcr100.dll.
I found them in the internet by searching.

Your program TAPR-VNA 4.2 works in principle on Windows 10-64, with COM8.
First you get an error message "No VNA connected to the stored port", click on OK.
A window "SerialPort" shows up. The "Port" should be COM8.
Next click on "Cancel".
The main window appears.

First a SOLT calibration must be done. My given file name "nanoVNA.cal" is rebembered after Program restart.
You need also to click on "Apply Fixture Calibration".

Entering a frequency above 200 MHz is not possible in the extra Input window (double click on Stop Frequency).
Just by slowly clicking on the ten's MHz number in the main window you can go above 200 MHz.

I could not found a way to change the vertical dB scale e.g. from -100 dB to -80 dB.

See the attached screen shot TAPR-VNA4.2_784MHz.png.

73, Rudi DL5FA

Hi Eric,
just checked, if your modified TAPR program works on my system with the NanoVNA.
I run the TAPR software under Win10 and I can confirm similar problems at startup as Rudi previously reported.
During calibration I kept getting an error message (attached) which says, that the string command has a wrong format. The "Thru" calibration I had to repeat several times before I got the green check mark. None of the cal standards worked right away due to the error message.
Sometimes I got the same message if I hit the SglSwp button. Beside these issues it seems to work very well.
The DUT is a 200MHz BP-Filter.

Thank you very much for the work done!
I am sure, that you will further improve the program. Handling the NanoVNA with the TAPR software is definitely a big advantage.

73, Norbert, DG1KPN

It is possible to change the start and stop frequency to above 200MHz by hovering your mouse over the number and use the scroll wheel.
The more your move your mouse to the left of the number the quicker is "scrolls"

NanoVNA is giving me a difficult time as the console command response if very unpredictable when done at full speed.

Updated the number entry box to allow up to max frequency
Did some effort to increase robustness of communication.
Sometimes your NanoVNA screen will turn white but it will still function.
/g/nanovna-users/files/NanoVNA%20PC%20Software/TAPR%20VNA/VNAR4.3.zip

I'm new to the group. Do I have to use special firmware in the nanaVNA to use the TAPR application?

Mike N2MS

No

Hi, Eric, what is the dynamic range of Your "dead-bug" setup ? Thanks in advance

- Andrea IW2FDH -

For the SA612/SI5351/dead bug bridge version:
The dynamic range of port 2 is limited by the leakage of the SI5351, just like the nanoVNA.
The biggest difference is above 300MHz where the directivity of the bridge becomes dependent on the quality of the layout, but below 300MHz directivity is equal to NanoVNA
For the ADF4351/IAM81008/ebay bridge version:
Dynamic range of port 2 around 2.5GHz is about 40-50dB and decreases somewhat till 30-40dB at 4.4GHz, but there no shielding at all so this can still be improved.
Directivity is ok till 2.6GHz but the ebay bridge quickly looses performance and basically stops working at 3GHz.
A SI5351/IAM81008/ebay bridge version easily has directivity till 1.2GHz, did not try higher.

Hello Erik

Some progress using Wine 4.0.2 on Mint Linux 19.2.

Created a new 32-bit wine prefix.

Used winetricks to install vcrun2010, dotnet40, dotnet45, dotnet46, dotnet461. Used dotnet_verifier to test dotnet installation.

Created a symbolic link from COM10 to /dev/ttyACM0.

VNAR4.3 runs but cannot connect to the nanoVNA.

What baud rate, # of bits, parity, # of stop bits does VNAR4.3 assume?

Nick

Don't complain about the manual, it is being adapted but not done yet

DOCX was converted to markdown using pandoc, then hacked and posted to GitHub:


This markdown has yet to incorporate nanoVNA content; pull requests
are welcome..

Wiki now includes links to this and Tapr-VNA code:
/g/nanovna-users/wiki/home

Hi Nick -

VNAR4.3 runs but cannot connect to the nanoVNA.

Getting VNAR4.3 connected to nanoVNA is tricky even on Windows

What baud rate, # of bits, parity, # of stop bits does VNAR4.3 assume?

Thpse settings do not affect communication to nanoVNA.

Has anyone used VNAR4.3 with nanoVNA on Windows XP?

This markdown has yet to incorporate nanoVNA content; pull requests are welcome..

VNAR4 manual now has initial updates for nanoVNA:


Some nanoVNA information is missing for equivalent published in Ten-Tec VNA manual:


In some cases, this nanoVNA-specific document has obsolete information;
in other cases, wrong information was simply deleted.
Suggestions and supplementary data are invited..

On Wed, Oct 9, 2019 at 11:39 AM, Oristo wrote:

VNAR4.3 runs but cannot connect to the nanoVNA.

Getting VNAR4.3 connected to nanoVNA is tricky even on Windows

Thanks for your reply Oristo. I have given up trying to make vnar4 and nanovnasharp work on linux via wine.

Both these applications require a windows device driver to provide a virtual com port.

Wine does not support USB so you cannot install a USB windows device driver.

I am now using nanovna-saver with the nanovna.