开云体育

Hi,

That's for you :

@edy555 edy555 released this 2 hours ago
in-device TDR support (contributed by @cho45)
add scan command for multisegment scan excess 101 points
fixed invalid sweep at the narrow span (<5kHz)
fixed failures caused by a race condition between USB and measuring loop
find device automatically in python script




Regards,
David F4HTQ

digit255,

Larry addressed this topic a couple of days ago:

" Larry Rothman
Sep 26 #3138

As hugen mentioned yesterday, he is thinking of re-integrating (merging?) the larger fonts with his current source code.
The larger fonts were created in order to display Chinese characters.
Hopefully, that will offer more options to all us older, more mature folk."

Basically the larger font size cannot be used with the most recent firmware until memory is freed up by first dumpling the space used to create Chinese characters.


Herb

Hi Rune,
I tested a BP-filter and I am wondering why the VSWR plot is interrupted. If you take a look at the attached screenshot, there is no VSWR line from about 268MHz till 846MHz. A tested LP-filter shows a similar symptom.
Would you please take a look at it?
Did anybody of the group see similar VSWR plots?

Kind regards
Norbert, DG1KPN

Not yet but forum member hugen is looking into something to help with this.
Stay tuned...may take a week or two.

Bo

I am the owner of RFzero (THANK YOU!) and of three, soon to be four, Nanovnas. While it does not fundamentally alter the discussion here, The Nanovna only has two frequency ranges: 55kHz to 300 MHz is accomplished using the fundamental. 300.01 MHz to 900 MHz is accomplished using the third harmonic of the Si5351 with the fundamental level boosted about 9 dB for this range.

Nanovna uses a second 5351 oscillator as a "tracking" source that operates 5 kHz above the measurement frequency and is used as a heterodyne source to the mixer which generates the 5 kHz audio signal for measurement. I believe (I have measured it but cannot find the data) that Nanovna uses the third harmonic for this "tracking" source from 300 - 600 MHz and then switches to the 5th harmonic for 600-900 MHz.

So it goes like this:

55kHz - 300 MHz: Measurement = Fundamental; "Tracking" = Fundamental

300MHz - 600 MHz: Measurement = 3rd Harmonic; "Tracking" = 3rd Harmonic

600MHz - 900 MHz: Measurement = 3rd Harmonic; "Tracking" = 5th Harmonic

BTW..... I have a HUGE problem trying to decide between RFzero and Nanovna as which is my favorite instrument!

WA8TOD

Rune wrote:

" I'd have wished they'd contact me about it instead, but as it's open
source, they are of course free to use the code.

I may need to make sure they don't reuse the name, though, so there isn't
confusion about which version is which "
---------------------------------------------------------------------------------------------------------------------------------

I remember edy555 having similar thoughts after Hugen started selling the NanoVNA based on his original open source design. For a brief history lesson, see posted comments from edy555 to Hugen below:


" Hi hugen,

I'm an original developer of NanoVNA.

When I knew that you made the clone of my project, I very surprised that
you made PCB from schematics, and as an enthusiast, I felt pleased with
your challenges such as frequency range expansion and your original pc
software.

However, I was annoyed that you sell your clone without any prior notice
to me. Though I had a plan to forge and sell my product, it becomes
difficult.

Furthermore, your act cause that your design material was stolen by other
clone makers, and quite many units were sold in aliex, ebay and also amazon.
Those include worse clone as you say. This is a worrying state of affairs I think,
and you might agree.

To distinguish any unexpected clones, I propose that you should change your
product name by adding a suffix such as NanoVNA-H from your name, and it
should be shown in the market and printed on your product.

And also I'd like to publish the name of qualified products, so customers
become able to avoid worse clone.

I hope you think about this issue seriously.

Regards,

edy555
Aug 13, 2019 "


Herb

Is there build firmware with battery indicator, 1500 MHz and big font ?
I only found with small font.

Hi Herman,
That is really strange. However, your Nano is not lost -just buy a cheap power bank that puts out 5v and use that to power the Nano, which really runs from 5v, not 3.7v.
In fact, you can always buy a very inexpensive and small charger-inverter board from the likes of banggood for around $2.
Yes, I know it's a pain in the butt but at least you can keep using your unit.

These boards use the 54xx chip..




Note both boards use a 4R7 coil but the cheaper board uses a 33ohm in series with USB 5v but the more expensive board uses 2 - 1ohm in parallel for current limiting.
I wonder if these chips are sensitive to input current from USB and are being damaged somehow.
Try placing a 33ohm at the 5v input to the chip and see if that helps.

You might be able to transplant parts from one of these modules to the Nano.

Regards
Larry

Its time to give Rune a cup of coffee!
Where is the paypal button?? :-)

Peter
Op 28-9-2019 om 15:06 schreef Rune Broberg:

On Fri, Sep 27, 2019 at 05:38 PM, yza wrote:

where, the sine qua non Core Uncertainty is due both to:

(a) the 5 = 2 + 1 + 2 uncertainties of the S, L, and O standards,
which are known from their manufacturers' data, as well as

(b) the 8 = 2 x 4 inaccuracies of the four VNA readings,

that is the Core Uncertainty is due to a combination of
26 = 13 x 2 error bounds, in total.

Hello yin&pez,

Thank you for introducing the topic of errors of error-models. This discussion is very interesting.

To help me understand, I would like to ask a few questions.

First, you mention that the S and O standards have 2 uncertainties each (while the load has 1 uncertainty). How are you defining these uncertainties? Are they defined as uncertainties in a Standard's Reflection Coefficient (that is, uncertainties in rho and theta), or are they defined to be something else? And why does the load only have 1 uncertainty?

Second, you mention the inaccuracies of the four VNA readings (two inaccuracies for each of the four readings, which I assume are the three readings for the SOL standards plus a fourth reading for the device-under-test). Could you please explain what these inaccuracies are and how one determines them?

Finally, how did you arrive at a Core Uncertainty of 26 error bounds? I can see how you calculate 13 (by adding 5 plus 8), but I do not understand why this value is then multiplied by 2.

Thank you very much for your time.

Best regards,

- Jeff, k6jca

22 : We Learn Our Lessons - NanoVNA Calibration
Considerations and Procedure_v1.1

@Gary O'Neil : /g/nanovna-users/message/3259

Hello,

Thank you very much for your time that you spent to
subjectively but kindly advice us lengthy about the
existed perfect climate that rein among the honorable
members of this forum !

We much appreciate that; indeed. Therefore, allow us,
please, to inform you that, as we already assured at:

18 : @Dr. David Kirkby : /g/nanovna-users/message/3192

and we can also gladly repeat here:

"
we always try to be good listeners, we shall also attempt
to follow your valuable subjective suggestions on this very
subject and to learn our lessons : Thank you once more !
"
On the occasion, allow us, please, to ask you to accept
our respects for your Excellent Work you have done into
the proven so valuable to us:

"NanoVNA Calibration Considerations and Procedure_v1.1"

where we read that :

"This document is mostly the work of Alan Victor, W4AMV
and his colleague Gary O’Neil, N3GO":
/g/nanovna-users/files/NanoVNA%20Calibration%20Considerations%20and%20Procedure_v1.1.pdf

Thanking you again,

Sincerely,

gin&pez@arg

I'd have wished they'd contact me about it instead, but as it's open
source, they are of course free to use the code.

I may need to make sure they don't reuse the name, though, so there isn't
confusion about which version is which.

Thanks for letting me know :-)
--
Rune / 5Q5R

Rune,
The popularity of NanoVNA Saver continues to grow. I just saw this over on the NanoVNA-F user group.

"We are currently modifying nanovna-saver (a good NanoVNA PC software) to fit NanoVNA-F, so stay tuned"

Good luck with them trying to keep up with your pace of development in a different branch :)

Herb

21 : The Mathematica Code and the Unpacked DERDEI Code

@Jose Luu : /g/nanovna-users/message/3278

Hello,

Thank you very much for your kind interest in our work !
We much appreciate that; indeed.

Especially, the fact that you spend your time to read our
documentation for our code. Therefore, allow us, please,
to inform you that, unfortunately enough, we are not in
place to fulfill your inquiry about our mathematica code,
which is already a more than ten 10 years old code ,
for an hierarchy of numerous reasons:

From the most generic first top one, which has to do with
the fact that meanwhile we radically changed our point of
view regarding proprietary software and thus we don't want
to support any one, in any way, even in our humble one,
anymore, down to the most specific last bottom one, which
has to do with the fact that this code is nothing more than
yet another example of the worst of programming style,
of a most personal character, that confused even us some
years ago, when we tried to find out what we had wrote
those days...

Well, after all that subjectively said, we conclude with our
definite decision : this mathematica code of ours is
definitely an unworthy, definitely a non-presentable,
definitely a not for publication code.

However, allow us, please, to also inform you that your inquiry
motivated us to decide that it is really now the time to unpack
the DERDEI code and distribute it, also under an MIT /F/L/O/S/S/
license, thus, we would like to please you to give us some time
to prepare the unpacked code in a form that will allow us to
decide that it is perhaps a somehow worthy, somehow
presentable, and thus a definitely publishable code.

Sincerely,

gin&pez@arg

21

Thanks for the info Warren,
73
de VU2PGB
VEEN

An update on dynamic range. In the photo the upper unit is the unshielded "worse" version and the bottom is the latest, best, shielded version. Both are calibrated for the 600 - 900 MHz range, Logmag, Ch1 with Through calibration. The reference level is the seventh level on both.

The diffenence in noise floor ranges from 3 - 10 dB across the range. Both units meet the dynamic range spec of 40 dB with the shielded unit showing better than 50 dB at the low end.

For my purposes the two units are substantially identical.

WA8TOD

is this modified software available to other users?

Gyula

All,

Thanks for the excellent information - so it does sound like step attenuator leakage is the culprit....which is not at all surprising given that it is a very cheap one ($40) that I purchased on Ebay earlier this year. I used it for some low power (-10 dBm to 10 dbM final RF output) WSPR mode experiments, typically at settings below 30 dB of attenuation, using an oscilloscope to verify the actual RF output power.

It's great to know that the dynamic range of the nanoVNA in the HF zone is as large as the S21 displayed values.


73,
Bruce

For those interested in the spectrum of the Si5351A here is a series of pictures, using my RFzero, at 267 MHz (i.e. 800 MHz "NanoVNA version"), 280 MHz, 298 MHz and 299 MHz. The pictures clearly show the behavior of the PLL and also the signal-to-noise performance.

More spectrum plots are here:

Bo

@Larry, Brian, DMR
In the meantime I have replaced the IP5303. Also the 10?F cap. But there is no improvement. The Nano still won't start on its battery.
The battery can be charged normally. I have placed the switch on pin 5 of the IP5303, so that I can start with the key-pin of the IP5303.
All proposals here do not improve. I also replaced the blue LED with a red one. A slightly increased load (+ 50 mA) with an additional LED or a resistor does not cause the IP5303 to start. All measured values ??appear normal.
But after 2 days there is a new phenomenon: after starting the Nano (via the IP5303 pin), it drops out after 7-8 seconds! I can repeat this endlessly, but it is always the same. Also with a full battery, also connected with the USB cable!
This way the Nano is no longer usable. I have no idea where this is coming from. There is no timer in the IP5303 that causes this? I have compared different schemes from IP53xx to IP5306, but they are all the same. The only difference I can find is that the coil (2.2?H) sometimes has a different value.
What could partly help me is that someone would post a detail photo of the components around the IP5303. Other experiences are also welcome.