开云体育

@Dislord: could you update your github with the sources for the v1.0.14 beta binary .dfu you have already distributed? Thanks.

Ok. I stop public binaries.

Thus you write you will distribute your binaries derived from sources licensed under GPL without providing the source code?

I not want answer on every try, then users begin compile from git. I not want provide not stable code on release. I have already answered this question, and I will not change my attitude about when

When you distribute the 1.0.XX binaries (like here on this forum or on cqham.ru or vrtp.ru) you shall provide the source code on your github too. It does NOT matter whether those binaries are called

One thing you need to make sure of is that the velocity factor is set correctly on both the VNA and any PC software Larry (0.72 in my case). Just made a measurement on a short patch lead I use here,

Hi, then go for it. It might me a seller that bougth from Hugen in bulk. I am sure its an original H4 as only Hugen is supplying it. And since its Amazon you can always return it if not.

That could be done Piero if you have an SD card socket fitted on your NanoVNA. Does your VNA have the SD card socket fitted ? Could add a firmware option to record the measurement onto an SD card

Thank you to everyone who suggested solutions.? Indeed, I am now planning to use a RPi connected to nanoVNA (there is enough space inside the mokup) and measure&store without any human interaction.

You could set the software to scan a narrower range to get a higher frequency detail, and/or increase the number of segments, though can't yet zoom on the graph (will do eventually). For now show us

Thank you to everyone who proposed solutions.? Indeed, I was planning to use a RPi connected to nanoVNA (There is enough room inside the mokup) and make&store measurements.?? Anyway the idea to

As per Alezis says Larry, try using a much larger frequency span when it comes to measuring coax lengths in that range. 50kHz to 900MHz is good yes, or even 50kHz to 1.5GHz. The larger the span the

I like that ! Have changed the icon to yours Igor :) I hadn't got around to making an icon for it, it was just the standard borland icon till now.

It's located here Jos .. https://github.com/OneOfEleven/NanoVNA/tree/master/Release

I sell VNA calibration kits on Amazon, although I have sold very few on Amazon. Most sales are eBay, website or bank transfer from companies. However, I have never sold internationally on Amazon, as

Hello. The final price is on Amazon, with all taxes included. While I would buy on Alibaba probably I would have to pay separate custom taxes for product made in China. So, my assumption is: no other

Yes, page 2 5.357 is the frequency I am allowed to transmit on, those are fixed frequencies on the band plan, and 5.375 was the closest step I could chose on the VNA... unless there is another way to

Page 2 5.357 != 5.375 Page 3 Red marker is in wrong place, it is not at 7.25 MHz. SWR is 2.28 at 7.25 MHz. Gary AG7TH

Hi Gary, for 60m I know I am a little bit off because I could not get the same frequency on the VNA 201 measuring point and the frenquency you see on the 7300 is the frequency I am allowed to transmit

Larry, you should set the nanovna software to a way higher frenquency stop, the picture I see display 494m (which is a low frequency stop), if you set the stop frequency at 900MHz, you should have a