Keyboard Shortcuts
Likes
- Nanovna-Users
- Messages
Search
Re: File updated in [email protected]
Hi Herb,
toggle quoted message
Show quoted text
I think Erik or QRP (and maybe Rune) will have to answer that more accurately than me, as what I wrote was my interpretation of their explanation in a forum post waaaay back in October some time.? ... Larry On Thu, 12 Dec 2019 at 6:15 PM, hwalker<herbwalker2476@...> wrote: On Wed, Dec 11, 2019 at 12:46 PM, "[email protected] Notification" <[email protected]> wrote:
* /NanoVNA_Console_Commands_Dec 9-19.pdf ( /g/nanovna-users/files/NanoVNA_Console_Commands_Dec 9-19.pdf ) *Uploaded By:* Larry Rothman <nlroth@...> *Description:*This is the latest update of the Console Commands for the NanoVNA as of Dec 9th. It replaces the previous version. updated some command descriptions (per QRP's new v0.4.3 F/W) Please let me know of any errors or omissions. ========================================================================= I have a question regarding the "sweep" command: sweep - usage: sweep {start(Hz)} [stop] [points] ? ? if no inputs: then prints current setup eg:300000000 500000000 101 ? ? otherwise, can force new sweep settings using the following commands: ? ? start ? ? stop ? ? center ? ? span ? ? cw ? ? set ¨C sets sweep points Can "sweep"? "center"? "span" be entered on the same console command line? <sweep center 30000000> and; <sweep span 1000000> work for me. But not; <sweep center 30000000 span 1000000> TKs - Herb |
Re: File updated in [email protected]
On Wed, Dec 11, 2019 at 12:46 PM, "[email protected] Notification" <[email protected]> wrote:
* /NanoVNA_Console_Commands_Dec 9-19.pdf ( /g/nanovna-users/files/NanoVNA_Console_Commands_Dec 9-19.pdf ) *Uploaded By:* Larry Rothman <nlroth@...> *Description:*This is the latest update of the Console Commands for the NanoVNA as of Dec 9th. It replaces the previous version. updated some command descriptions (per QRP's new v0.4.3 F/W) Please let me know of any errors or omissions. ========================================================================= I have a question regarding the "sweep" command: sweep - usage: sweep {start(Hz)} [stop] [points] if no inputs: then prints current setup eg:300000000 500000000 101 otherwise, can force new sweep settings using the following commands: start stop center span cw set ¨C sets sweep points Can "sweep" "center" "span" be entered on the same console command line? <sweep center 30000000> and; <sweep span 1000000> work for me. But not; <sweep center 30000000 span 1000000> TKs - Herb |
Re: ordering a bigger screen from aliexpress
On Thu, Dec 12, 2019 at 12:55 PM, <nanovnauser@...> wrote:
,,, i enter my post code,it just says its in the wrong format,ive tried every which way with no luck,im tearing my hair out,anyone any idea whats going wrong? ¡ ==================================================================================== I had an order delayed for a couple of weeks on Aliexpress due to using an extended ZIP+4 code (five digits of the ZIP Code + a hyphen and four digits). As long as the extended zip code has been in use in the U.S. you would think it wouldn't cause any problems, but I had to change to a five digit zip code to complete my order. - Herb |
Re: QUESTION
Hi David,
toggle quoted message
Show quoted text
the NanoVNA-F is designed by a Chinese ham, so what you want to avoid is a clone - not a Chinese one ;-) The original NanoVNA-F is available at - and only there, as I understand. They link to the following seller on AliExpress as the official shop: -- Rune / 5Q5R On Thu, 12 Dec 2019 at 22:10, David Eckhardt <davearea51a@...> wrote:
After using the original with the 2.8" screen, I'm looking to order the |
Re: ordering a bigger screen from aliexpress
My FCU refuses to honor charges on my card to Aliexpress. I no longer
toggle quoted message
Show quoted text
tempt ordering from them. Three times. Same results. Likely due to Chinese vender? Dave - W?LEV On Thu, Dec 12, 2019 at 8:55 PM <nanovnauser@...> wrote:
ive found a screen the same as hermans 3.2 inch on aliexpress(thanks for --
*Dave - W?LEV* *Just Let Darwin Work* *Just Think* |
QUESTION
After using the original with the 2.8" screen, I'm looking to order the
4.3" unit. As best I can gather, there are three units available all with different external presentations. These are: 1) NANOVNA-F along the bottom right with the Gecko to the right of the screen on the vertical member. 2) NANOVNA-F along the bottom right with no Gecko. 3) NANOVNA-F along the side to the right of the screen - no Gecko.. I don't want a Chinese clone. Which of these three are legitimate and worth spending my $$ on? I do NOT want to support the cloners! *Dave - W?LEV* *Just Let Darwin Work* *Just Think* |
ordering a bigger screen from aliexpress
ive found a screen the same as hermans 3.2 inch on aliexpress(thanks for the link herman),however it goes ok trying to buy it untill i enter my post code,it just says its in the wrong format,ive tried every which way with no luck,im tearing my hair out,anyone any idea whats going wrong?,cheers .
|
Re: running nanoVNA-saver under Linux Mint XFCE
Hi,
Like others, I am having problems with Python PyQt5 etc. I am trying to get NanoVNA to run with a Raspberry Pi 4 with very little success. Works perfect on the Mac Pro. Do you or others know of a work around for this excellent program to work on this platform? Any advice would be much appreciated. 73 G8ORE |
Re: errors of "error" models
Garry,
Thanks, I may have formulated unclear but what you state is what I meant. Uncertainties in M act as "error bars" making it uncertain where you are in the graph, Uncertainties in the calibration standards cause left/right shifts/compression/decompression in the positioning of the graph -- NanoVNA Wiki: /g/nanovna-users/wiki/home NanoVNA Files: /g/nanovna-users/files Erik, PD0EK |
Re: errors of "error" models
Hello again Erik;
I think you may be confusing the uncertainty in M with the uncertainty in the calibration standard. For example; if the calibration standard is 45 ohms (a substantial 10 percent error), Only the value of Z0 changes in your equation. However; calibration of the VNA with this standard (uncorrected) equates the value of Z0 to 45 ohms, but declares it to be 50 ohms. "IF" there are "NO" other sources of uncertainty in our measurement, this would force a 5 ohms real uncertainty in our measurement results. The mathematical (and graphical) consequence of this (now hidden) error is that it shortens (compresses) the length of the perfectly linear distance to the right from 50 to infinity by 5 units, the entire length which then gets normalized to the length of 1, such that all values remain inside the boundary of the Smith Chart. Conversely; it also lengthens (stretches) the the line representing the perfectly linear distance to the left from 50 to 1/infinity (zero). Because we have decided that there are no other uncertainties in the measurement, we get a clear picture of the consequence of the 5 ohms of uncertainty as we move away from the center of the chart, and reveal that the uncertainty asymptotically approaches zero as we move toward the outside edge. Hence; it is my assertion that the consequence of errors in the load standard are most relevant and arguably critical for measurements of an impedance at or near Z0. In an analogous manner, I might even argue that reactance uncertainties may have even less influence on measurements of DUTs exhibiting a real part less of less than Z0; since Zero reactance is established at all three calibration points. In a practical sense, and given that even DIY calibration standards of high quality are not difficult to manufacture; it would appear that frequency accuracy and the precise definition of the reference plane are perhaps the most sensitive, and thus the most critical calibration parameters to be controlled. Ironically; uncertainties in those parameters diminish as impedance approaches Z0. What also becomes evident from these assertions is that the quality of the standards with respect to establishing the measurement reference plane increases as frequency increases. -- 73 Gary, N3GO |
Re: errors of "error" models
Forgive me to add something trying to create a simple mental picture of what you are saying.
As the nanoVNA has a almost perfect bridge below 300MHz (apart from a phase shift due to transmission line lengths) the relation between a measured R and the output of the bridge (M) is mathematically M=(R-Z0)/(R+Z0) and graphically (for Z0 is 50) and when only varying the real impedance of R Am I correct to assume your conclusion can be linked to the shape of this transform? Around Z0 the dominant factor is the placement of Z0 and the uncertainty in the measurement of M leads to a linear relation to an uncertainty in log(R) but as the first derivative of relation between R and M is at a global maximum the impact of measurement uncertainties of M is at its minimum. For high and low values of R the opposite is true. Even the smallest uncertainty of M around +1 and -1 leads to a substantial uncertainty in R. I assume the same is true for the imaginary component where instead of R=50 (real component of Z0) the center of the graph is around iR = i0 (imaginary component of Z0) This then would explain why during calibration the value of the real resistance of the load and its electrical length or its reactance are important to determine the center of the graph and the uncertainty in the center and the open and short for determining the extremes and the related uncertainties there. -- NanoVNA Wiki: /g/nanovna-users/wiki/home NanoVNA Files: /g/nanovna-users/files Erik, PD0EK |
Re: errors of "error" models
GIN&PEZ;
I have only advanced in my understanding to the extent that I have been able to confirm that the results of complex load measurements using the G-mini equations map virtually 1:1 to those obtained from and computed by the stand-alone NanoVNA. I have not looked at, nor have I attempted to identify and compare differences between the computational processes used to arrive at their respective results. To obtain the confirmation, required that I perform a single calibration of my NanoVNA using my imperfect set of calibration standards, immediately followed by a single sweep of my DUT*. This exercise yielded a calibrated NanoVNA measurement of my DUT and the set of the 4 raw data files (S, O, L , and DUT) that the NanoVNA used to compute its results, plus the NanoVNA's internally computed results that resulted from those same raw data measurements. All of the above were exported into a spreadsheet where using the G-mini equations I computed a new set of results which I could then compare with those produced by the NanoVNA. I have done a limited amount of "what-if" experiments to emulate a crude but viable simulated differential analysis, but only to the extent that I was able to confirm that such testing can be performed in a quantifiable manner. For example; I made the observation that the load value is a single interpolated data point along a logarithmic line that extends from 0 to infinity, and concluded that the accuracy of all measurements made with respect to this single fixed data point are highly dependent on the accuracy of the data point itself. It also appeared obvious (perhaps only to me) that the severity of the inaccuracy in the placement of this single calibrated data point is most critical, and possibly only critical in the immediate vicinity of the data point itself; observing that the extrapolated influence of the absolute error in the load standard compresses in significance as distance from the center of the chart increases. It seems intuitive that the ability to resolve any load standard error contribution erodes rapidly with distance from Z0, and the contribution of other uncertainties (linearity, noise, resolution in the vicinity of the measurement, etc.) would rapidly dominate elsewhere. I have however only confirmed that the measurements near the value of the load standard being used (Z0) are highly sensitive to differential values (alternative loads) in close proximity to Z0, and the errors do not appear to propagate sufficiently to degrade the DUT measurement results noticeably. More exhaustive testing is required to perform this test in a satisfactorily convincing manner to yield quantifiable results, but I am severely limited in my ability to do so with the instrumentation I have on hand. My hope is that those with capabilities such as near perfect standards, calibrated reference impedance standards, and/or a very well balanced HW bridge are eavesdropping and gaining in their own understanding of what you are doing; and that they will eventually become motivated to chime in and contribute to this exercise. Whatever the outcome; my ability to contribute is going to be limited to reproducing results that become useful and meaningful FACUPOV. :-) * The DUT used in my measurements is a 7 foot length of foam RG8X coaxial cable terminated in a 1/10 Watt 3.3 ohms metal film resistor, and yields an approximately 15:1 VSWR collapsing spiral vs. frequency. -- 73 Gary, N3GO |
Re: Free version of LabVIEW coming
Probably should add Python to the mix as candidate for your own application development..
Matlab is gold standard for college academics but it is more targeted at nuts and bolts simulations. It is expensive and has significant learning curve. Octave is a great open source Matlab look alike. Most Matlab programs can be run with Octave. Octave has extension libraries for signal processing similar to Matlab. With relatively minor syntax items, a Matlab programmer can ensure their program will run in Octave. Python was originally used often for test systems, the same group using Labview. It is very well supported open source and is one of the fastest growing programming application. If you plan on playing with Raspberry Pie you will likely be using Python. |
Re: errors of "error" models
#82' : On The Two-Port Sine Qua Non Practical Application - Source and Load
- REF : 11 December 2019 - /g/nanovna-users/message/8136 Hello, Allow us, please, to announce that we just uploaded an updated version at: with slight modifications and added * e x p l a n a t i o n s * on the text. Sincerely, gin&pez@arg :82' |
Re: History
Which had portions derived from a Project STM32-SDR which was developed by
Charlee Hill W5BAA, John Fisher K5JHF, Milt Cram W8NUE and Dave Miller VE7PKE/VE7HR. The software was released as open source. The STM32/SDR project has morphed to the IQ32 which is still in production. Charlie and Milt over the years have created some wonderful things. Dave VE7HR On Wed, Dec 11, 2019 at 12:53 PM Joe St. Clair AF5MH <saintc@...> wrote: I think the Texas hams Larry is referring to are Milt Cram (W8NUE) and-- 72 de Dave VE7HR |
File updated in [email protected]
[email protected] Notification
Hello, This email message is a notification to let you know that the following files have been updated in the Files area of the [email protected] group. Uploaded By: Larry Rothman <nlroth@...> Description: Cheers, |
File updated in [email protected]
[email protected] Notification
Hello, This email message is a notification to let you know that the following files have been updated in the Files area of the [email protected] group. Uploaded By: Larry Rothman <nlroth@...> Description: Cheers, |