开云体育

Hi Gary,
There's no firmware made specifically for NanoVNA-Saver - the software does
not use any features beyond the default, built in ones.

--
Rune / 5Q5R

CollapsibleBox(QtWidgets.QWidget) would be handy - you can "hide" controls you don't need then.

For myself, I patched the charts to be 300px in height max. Ditched the s11_control_box and s21_control_box (and the setText statements); as I can read that with markers. Font size set to 7; and removed the about box. Now it fits snug inside my (small) display.

Just for the record, 1366 x 768 is the resolution of a really
high number of laptops including a majority of the under $500
laptops available. I appreciate your response to Steve, but thought
I would pass this along so you can decide just how hard you work
at this as it isn't just one person. I just throw it up on my external
monitor, but that would be really inconvenient at the tower site.

Dan Thompson
dan@...

Hi Reg,
The instructions were listed by forum member DMR.
Do a search for 'dmr' and 'linux' and I think you'll find it otherwise, I grabbed a copy but it's on my work PC so if I don't see it in the firmware section tomorrow, I'll stick a copy there. (You're 5 hours ahead of me)
Look here:
/g/nanovna-users/message/1508

Cheers
Larry

Rod

Have a look at

and start reading on page 24 of

--
=============================================
Thomas R. Berger Emeritus Professor
53 Kendal Drive Mathematics Department
Oberlin, OH 44074 Colby College
K1TRB Waterville, ME 04901
=============================================

Thanks for the great responses, all.

I don't care to stand up any instance of Ubuntu, no machines, Dockers, whatever. I don't want to build source.

When I download the latest release .zip file (0.1.1) I see a ch.bin, ch.elf and ch.hex. Are any of those usable with Windows DfuSe?

Thanks!

Any problems making your own calibration loads? 50 ohm non inductive resistor and a shorted connector or am I missing something?
KD0XX (Rod)

Greetings All,

Many thanks for your interest and info! This thread has been very helpful for me and I hope also found useful by others.

The return loss of my low cost Asian SMA/BNC adapter with my 50 Ohm DIY BNC load seems surprising good at 53dB/VSWR 1.005:1 up to 450+ MHz. As long as the same connector stack is used during calibration the resulting calibration data has proven to compensate well for the minor Z discontinuities caused by the connectors. To maintain accuracy it is important that no changes are made to the connection between the NanoVNA port and the DUT after the calibration procedure has been completed. It would also be important not to change any settings that would invalidate the calibration data.

There seems to be concern about the use of the BNC connector series with the NanoVNA. The BNC connector series specification states a maximum VSWR of 1.3:1 to 4GHz. In my case the return loss of 53dB at 450 MHz equates to less than 1.005:1 VSWR. But even if my SMA/BNC adapter presented a somewhat higher mismatch the resulting Z discontinuity would be compensated for by the calibration process. The TDR measurement of 53 Ohms is not surprising as it represents a 1.06:1 VSWR which is well within spec. This slight variation in Z would not result in a noticeable impedance bump for operation at lower frequencies that have significantly longer wavelengths than the connector length. The impedance bump seems to be well compensated for by the VNA calibration procedure considering the accuracy of the measurements I was able to make.

Without question the SMA connector series has much better impedance characteristics than the BNC series and can be used at much higher frequencies but I wonder if there is much practical difference for VHF and lower frequency measurements. The practical use reality is that for most common amateur radio applications the NanoVNA SMA connection will need to be adapted to some other more commonly used connector series for doing most measurements.

The bottom line for myself is that after doing this batch of measurements and discussing them here I now have a much better understanding of the the NanoVNA capabilities. I think it will serve me well for my applications. Many thanks again for the help!

Enjoy!
Tom
VA7TA

Dear Techo,

Thanks for the hint. I will try it and see what I see.
73 Dave

Hugen

My NanoVNA is using the STM32F072 processor and I've successfully installed the V0.1.1 release.That firmware version has issues when running standalone. Is there a compatibility issue between the F303 and F072 that would cause the errors in the cals and display data? See posts #2623 and #2644. I have seen no responses from anybody testing this code, so I'm wondering if the intent is that it only be used in PC mode and bundled with Rune's NanoVNA Saver GUI.

--
73

Gary, N3GO

I just downloaded V 0.1.1 and verified that I'm getting identical invalid results. Since nobody else seems to have any issues with this, firmware; am I remiss in my thinking that this version of NanoVNA firmware is backward compatible with previous versions? Is this firmware only intended for desktop use of the NanoVNA, and more specifically as a bundled package with NanoVNA Saver?

--
73

Gary, N3GO

I am discussing with the AA6KL9 to build a new firmware using the STM32F303CCT6. If all goes well, it can be provided later. To replace the mcu directly on the current hardware, you need to add a 1.5K resistor to the VCC on the USBDP Pin. The DFU mode of the STM32F303 requires an external 8M crystal to use USB, but STM32F072 does not need it, so you need to use SWD to update the firmware. You need to prepare an ST-Link or DAP-Link.
BTW: The new STM32F072-based NanoVNA firmware already supports TDR.

Thank you!

Dave,

That's the best way to confirm the "quality" of OSL test loads/terminations.

A few years ago I did a test by calibrating with a known "defective" 50 ohm termination. After calibration I measured the same defective termination. It looked great, but now my known Anrtisu OSL looked terrible.

My point is that almost any calibration made, and then a measurement of the load set used for that calibration will look great, but is it really a true reading? Hardly.

Burt, K6OQK


Dr. David Kirkby wrote:
I don't know if all the NanoVNAs are being shipped with the same open, but
I tested the open shipped with my NanoVNA using an HP 8753ES VNA after
first calibrating with an HP 85052B cal kit. The open did make a *small*
difference - a bit under 1 degree of phase difference at 900 MHz.

It did however cross my mind later that I had a 3.5 mm test port, rather
than SMA, so it would be worth my while repeating with SMA. My own
experience with both 3.5 mm and *SMA* connectors indicates adding *any*
sort of open ended device on the end, does make a measurable difference to
the phase, but I would have thought it pretty insignificant at 900 MHz.

Dave.
--
Dr. David Kirkby,
Kirkby Microwave Ltd,
drkirkby@...

-=-=-=-=-=-=-=-=-=-

Burt I. Weiner Associates
Broadcast Technical Services
Glendale, California U.S.A.
biwa@...
K6OQK



--
Burt I. Weiner Associates
Broadcast Technical Services
Glendale, CA? U.S.A.
K6OQK

Hi Rune,
new version is working fine here. Thank you very much for spending so many hours to create this excellent software. Changing font size one step higher made my screen much more easy to read.
Besides averaging as discussed above, one thing I am missing is a delta marker function.
Ernst

I've been trying to keep up with this firehose, but it's challenging as I can't recall where I read various things.

Would those familiar with various FW versions write a short summary describing them and where the repositories are? Rather than try to describe all of them, just describe the ones you know about and the build procedures you know about. I've created a "Firmware" folder for this in the "Files" section.

I've soldered a connector for an ST-Link to my nanoVNA and am ready to get serious about working on the FW. I'd like to work on Linux as I'm a Unix guy Someone commented they'd written a summary of building the FW on Ubuntu, but it's not in the Files section. If you wrote that, please put it in the folder I created.

My initial focus is going to be to implement an SWR & TDR only FW version that will allow using them as a fully portable unit for testing feedlines and tuning antennas. I have both an HP 8753B and a Tek 11801 & SD-24, so I'm well equipped for this. In addition I have 30+ years of professional experience in seismic DSP and R&D working on scientific software, most of which centered on solutions of the wave equation. So *very* familiar territory except for the jargon and some minor changes to the equations.

Hugen offered a couple of times to provide a unit with an STM32F303CCT6, but I've gotten no response asking to buy one and I saw mention he had cancelled orders. So for now I'm going to try to do this on the existing HW using the STM32F072CBT6 by ripping out other features.

I expect that OEMs will migrate over time towards the '303, but if I can make an '072 unit do just SWR and TDR, the field day box will be a great place for your old unit when you upgrade.

Have Fun!
Reg

BTW It's all Dave Kirkby's fault ;-) He talked me into buying one.

Most of the RF equipment I own have BNC connectors, so one of the first things I did was install SMA-BNC adapters on channels 0 and 1 of my nanoVNA. After recalibrating using a 50 ohm BNC OSL kit, the Smith chart display looked as expected when BNC OSL standards were sequentially connected to CH0. BNC mismatches of 33, 75, 100 and 150 ohms all looked good with expected return losses. I saved the BNC calibration data in "SAVE 1" and retained the original SMA calibration in "SAVE 0" in case I need to remove the SMA-BNC adapters.

qrp.ddc's discussion in group regarding the electrical delay menu option reminded me of how the port extension feature of the HP8753C was used to correct for an adapter attached to the native "N" connector. The HP8753C has a menu option allowing you to enter an electrical delay value, extending the measurement plane out to the end of the adapter and correcting for its additional length. I wondered if this would work with the nanoVNA and so tried the following:

1.Turn on nanoVNA. With nothing connected to the CH0 BNC adapter, the Smith chart displays an open with a tail corresponding to the reactance of the SMA-BNC adapter.

2. On the nanoVNA select DISPLAY_SCALE_ELECTRICAL DELAY.

3. I didn't have a clue as to the electrical delay value for the SMA-BNC adapter, so starting at 100 (ps?) I tried successive values until the nanoVNA displayed a single dot with no tail to the far right of the Smith Chart display. The value needed to achieve this for my SMA-BNC adapter was 180 x 1 as entered on the nanovna screen keypad.

4. With BNC OSL standards sequentially connected to CH0, the results looked almost as good as the original SMA calibration data.

5. BNC mismatches of 33, 75, 100 and 150 ohms looked as good or better than the values obtained during the earlier calibration using my BNC OSL kit.

6. I saved the port extension corrected data in "SAVE 2" .


Thanks qrp.ddc for pointing out the electrical delay menu option and how it could be used for correcting for port extensions. For those users that want to add different adapters to channels 0 and 1 but don't have a suitable OSL kit to correct for the adapters, give the electrical delay menu option a try.

On Wed, 18 Sep 2019 at 22:35, Kurt Poulsen <kurt@...> wrote:

Qrp.dd (whoever you are)
It seem like the distance from center conductor to flat part is as long as
to the top of the female SMA so probable without any influence.
You can test it yourself ....

I don’t know if all the NanoVNAs are being shipped with the same open, but
I tested the open shipped with my NanoVNA using an HP 8753ES VNA after
first calibrating with an HP 85052B cal kit. The open did make a *small*
difference - a bit under 1 degree of phase difference at 900 MHz.

It did however cross my mind later that I had a 3.5 mm test port, rather
than SMA, so it would be worth my while repeating with SMA. My own
experience with both 3.5 mm and *SMA* connectors indicates adding *any*
sort of open ended device on the end, does make a measurable difference to
the phase, but I would have thought it pretty insignificant at 900 MHz.

Dave.
--
Dr. David Kirkby,
Kirkby Microwave Ltd,
drkirkby@...

Telephone 01621-680100./ +44 1621 680100

Registered in England & Wales.
Company number 08914892.
Registered office:
Stokes Hall Lodge,
Burnham Rd,
Althorne,
Chelmsford,
Essex,
CM3 6DT,
United Kingdom

I use this.... It's handy for people like me who understand radio, but find computers a bit of a mystery....

Just wondering if vnaJ software can be used on the Nano ?

Anyone tried it ?

73 de Andy

I thought Windows users just pressed Alt + Print screen key to
grab a screenshot ?

Then open up any graphics editor or Paintbrush thingy and Control V
to paste it into the graphics editor.

No need for any extra software for grabbing the screen.

On Linux it's usually just Print Screen key in its own, then paste to graphics editor, save or edit as desired.

Hope this helps.

73 de Andy