Re: SMITH CHART REACTANCE LINES.
On Tue, Jan 21, 2020 at 05:00 AM, hwalker wrote:
The NanoVNA was designed for hobbyist use and the majority prefer the pF and
nH format so they don't have to do the additional component conversion math.
- Herb
Herb, please explain the advantage of using the pF and nF format. When I am trying to calculate LC-match, for instance in MMANA-GAL, I need to use R+/-jX format. See screenshot. That's why I prefer NanoVHA-Q firmware. The way to read jX value, is to set one of the CH0 traces to "REACTANCE".
|
Re: A Capsule Summary of Nonfictional VNA Measurements
Dear gin&pez,
Thank you -- I'm glad to learn that the article inspired you to repair your HP 8505A.
Best regards,
- Jeff, k6jca
|
Re: A Capsule Summary of Nonfictional VNA Measurements
Dear Jeff,
Thank you, very much indeed, for this; we much appreciate it!
Well, we will try sometime to reproduce your MatLab code in Maxima.
By the way, allow us, please, to publicly express our admiration for
your Dedicated Work, with which we acquainted after we discovered
your Prototype Article about:
"Modifying a 75 ohm HP 85046B S-Parameter Test Set to be 50 ohms":
which encouraged us to attempt a successful repair of HP-IB in our
HP 8505A - hence, we would also like to thank you for this valuable
contribution by you.
Kind regards,
gin&pez@arg
|
Re: SMITH CHART REACTANCE LINES.
I play with RF as a hobby, but seeing something like 50ohms +22uF looks quite odd, whatever the frequency is. It is like there is large capacitor somewhere, when there isn't of course..
|
Re: A Capsule Summary of Nonfictional VNA Measurements - ERRATUM
Instead of the wrong:
G = S(L-O)(gs+lo) + L(O-S)(gl+os) + O(S-L)(go+sl) /
/ [ (L-O)(gs+lo) + (O-S)(gl+os) + (S-L)(go+sl) ]
the correct one:
G = [ S(L-O)(gs+lo) + L(O-S)(gl+os) + O(S-L)(go+sl) ] /
/ [ (L-O)(gs+lo) + (O-S)(gl+os) + (S-L)(go+sl) ]
|
On Wed, Jan 22, 2020 at 05:33 AM, Merle W wrote:
" I also have the c connector issue. Had to remove some plastic."
"Tried your firmware issue and my unit hangs as well. The center freq did show up correctly though."
==============================================================
Merle,
Thanks for confirming both the usb case opening and center frequency hang up issues. Also glad you found the review useful. If no one else makes a report, then I will submit both of these issues to hugen at his GitHub page. I'm happy to have my hands on the 4" NanoVNA-H4 and can deal with a few warts knowing hugen will address them in a timely matter. First soldiers into battle catch the most flack.
- Herb
|
Re: A Capsule Summary of Nonfictional VNA Measurements
On Tue, Jan 21, 2020 at 03:46 PM, gin&pez@arg wrote:
G = (g - l)(o - s) / [ (g - o)(s - l) - (g - s)(l - o) ]
And it is in this -and-only-in-this- way, that these 7 values,
(the 3 assumed plus the 4 measured), result in terms of frequency
in some calculated values of the -still unknown, of course- loads,
that is to those which are widely known as "VNA measurements"
- the Nonfictional ones, of course.
For clarification, I will note that the standard VNA error-correction equations reduce down to this same equation (that I've quoted, above) if we assume the reflection coefficients of the Short, Load, and Open standards are exactly -1, 0, 1. MATLAB can easily demonstrate this: % One-port VNA Calibration, k6jca % % Find the equations for the three error terms: e00, e11, and delta_e % Derived from the equations in: % Network Analyzer Error Models and Calibration Methods, % by Doug Rytting, Agilent Technologies % % And then find the equation for an Unknown load's actual % Gamma, based upon these three error terms and the measured % Gamma of the unknown. % Definitions: % ------------ % G1 = -1 = Actual Gamma of Standard 1 (short) % G2 = 0 = Actual Gamma of Standard 2 (load) % G3 = 1 = Actual Gamma of Standard 3 (open) % G = Actual Gamma of Unknown % % s = Measured Gamma of Standard 1 % l = Measured Gamma of Standard 2 % o = Measured Gamma of Standard 3 % g = Measured Gamma of Unknown syms G g s l o e00 e11 d_e [e00,e11,d_e] = solve(e00+e11*(-1)*s-d_e*(-1) == s,... e00+e11*(0)*s-d_e*(0) == l,... e00+e11*(1)*o-d_e*(1) == o,[e00,e11,d_e]) [G] = solve((g-e00)/(g*e11 - d_e) == G,[G]) The results of this MATLAB script are:: e00 = l e11 = (o - 2*l + s)/(o - s) d_e = -(l*o + l*s - 2*o*s)/(o - s) G = (g*o - g*s - l*o + l*s)/(g*o - 2*g*l + g*s + l*o + l*s - 2*o*s) Note that this last equation is the same as your equation that I've quoted, above, expanded. Best regards, - Jeff, k6jca P.S. The MATLAB code, above, is based upon the MATLAB code in this post:
|
Modify Original Nanovna for easy DFU mode like the H4
#dfu
#mods
BTW, for those who are into modding their NanoVNA - you can also make your original unit go into DFU mode the same way as the new H4 model:
- Add a jumper wire from the BOOT0 pin on the CPU over to the centre pin on the jog switch (refer to attached H4 schematic)
- Change R5 to 1K ohm (same as H4)
- DONE - I changed my unit - no need for a separate jumper now to go into DFU.
Now you can go into DFU mode as mentioned below.
toggle quoted message
Show quoted text
On Wednesday, January 22, 2020, 8:26:54 a.m. GMT-5, Larry Rothman <nlroth@...> wrote: The DFU mode is entered by turning OFF the unit, pressing in and holding the selector switch and then turning the unit ON. Then, release the switch. ? ? On Wednesday, January 22, 2020, 8:22:32 a.m. GMT-5, Jos Stevens <jrs@...> wrote: Why ofcourse Herb ? DFU mode is replaced by "Brightness" and I remember to have seen DFU mode passing by, but can't find it back now, please how to entyer DFU mode, I tried a long press? af the swith, but no luck. Jos Op 22-1-2020 om 10:58 schreef hwalker: On Wed, Jan 22, 2020 at 12:17 AM, Oristo wrote:
" You may be able to capture screens by modifying Specifically, replace 320 and 240 at lines 46 and 73 with pixel dimensions of NanoVNA-H4 display, and COM3 at line 11."
Hi Oristo,
? ? I fell back on your script after Rune's module stopped working.? Changing the script to:
? ? ? ? ? b = ser.read(320 * 480 * 2)
? ? ? ? ? x = struct.unpack(">153600H", b)
Resulted in a correctly colored,? but double overlayed image.? I wanted to get a review out and so did not work on the script further.? Note: other parts of the script were changed as appropriate (or at least to my understanding) for 320x480 resolution.? The resolution comes from hugen's product specification and I'm assuming is correct.
? " If someone can describe menu changes or point to an image for printed NanoVNA-H4 Menu Structure Map, I will create and updated map for /g/nanovna-users/wiki/User-Guides ."
The? included Menu Structure Map (see attachment) was the same as for the NanoVNA-H v3.4 and was not updated for the NanoVNA-H4.? For example, it shows ">DFU" option under CONFIG and of course the NanoVNA_H4 does not use this method to enter DFU mode.
- Herb
|
Herb,
Thanks for the reply, then? it starts up with a black screen then, but when you connect it to the PC? you hear the wellknown sound and DFUse recognises it correctly. I had no need to use DFU, because the device was loaded with the latest firmware when it arrived by DHL yesterday, it came 10 days after ordering at Alibaba. Not bad .? Now I am going to see what it does via NanaVNA-Saver I had some problems at first start of this program yesterday.
Jos
Op 22-1-2020 om 14:22 schreef Jos Stevens:
toggle quoted message
Show quoted text
Why ofcourse Herb ? DFU mode is replaced by "Brightness" and I remember to have seen DFU mode passing by, but can't find it back now, please how to entyer DFU mode, I tried a long press? af the swith, but no luck.
Jos
|
Herb,
Very nice report. I also have the c connector issue. Had to remove some
plastic.
Tried your firmware issue and my unit hangs as well. The center freq did
show up correctly though.
Merle
toggle quoted message
Show quoted text
On Wed, Jan 22, 2020 at 1:26 AM hwalker <herbwalker2476@...> wrote: A number of members have annouced the arrival of their 4" NanoVNA-H4. Mine
came in today. I ordered the NanoVNA-H4 ($60usd) from hugen's Alibaba store
plus $15 DHL express shipping. It arrived in a little over a week (shipped
out just before the Chinese new year). I had previously ordered the 2.8"
NanoVNA-H v3.4 with free shipping via parcel post; it arrived in a little
over two weeks. If you are ordering from hugen's store and not in a hurry,
save yourself the extra $15 and use parcel post. Maggie King, at hugen's
Alibaba store, was my point of contact.
I previously reviewed the NanoVNA-H v3.4 (see message #9883) and wanted to
see how the NanoVNA-H4 stacked up.
What's in the box.
The 4" NanoVNA-H4 came in a similiar, but larger, storage box than the
NanoVNA-H v3.4, with molded compartments and accessories. The storage box
was packed in a shipping container with sufficient padding to survive the
slow boat from China parcel post route.
The contents of the storage box included:
NanoVNA-H (with 1950mAh battery) Note: 3x more capacity than the
NanoVNA-H v3.4
USB Type-C data cable x1
20cm SMA male to male RG316 RF cable x2 Note: Better quality than the
NanoVNA-H v3.4 RG-174 cables.
SMA male calibration kit - OPEN x1
SMA male calibration kit - SHORT x1
SMA male calibration kit - LOAD x1
SMA female to female connector x1 Note: Supposedly better quality than
NanoVNA-H < ver3.4.
Type-c to Type-c cable x1
Guitar pick type stylus with lanyard
Visual improvements over original NanoVNA.
1. The NanoVNA-H4 comes in a well fitted ABS case and provides guards for
the side mounted port connectors. The top mounted power and multi-function
switches are larger (see attached photo) and feel more substantial than the
NanoVNA-H. A couple of members have reported that the case opening for the
usb port was mis-aligned and they had to shave away a part of the opening
in order to insert the usb cable properly. My unit did not have that
problem, as was also the case for a few other members that reported
receiving their units. Hopefully this is not a wide scale manufacturing
problem.
2. The 4" display is the most requested feature by users of the smaller
2.8" NanoVNA-H. It is a tft display and the brightness is controllable in
the CONFIG->BRIGHTNESS menu. I use the hugen -AA large font firmware on my
NanoVNA-H v3.4 and in a side by side comparison, the font size looks the
same as the NanoVNA-H4. The biggest advantage of the 4" display is the
graphics are not as compressed and the larger fonts can be laid out
normally so that the screen is more legible (See the attached photos for
comparison). Even with the larger size screen, a stylus is still preferable
to using your finger for navigation. The resolution of the screen is about
twice that of the NanoVNA-H but does not come close to matching the
resolution of the NanoVNA-F. Because of the increased screen resolution,
Rune's screen capture module in NanoVNA-saver 2.2-1 did not work, hugen
warned this would be the case until developers catch up. Due to this no
screen captures are attached.
3. While on the subject of software, it looks like the NanoVNA-H4
maintains excellent backwards software command compatibility with the
NanoVNA-H. So far the capture command is the only failure I've run into.
On the other hand, the firmware is not backwards compatible with the
NanoVNA-H. Too many changes had to be made to accommodate the new Cortex-M4
MCU (F303) and the 4" display to maintain compatibility. hugen now
maintains a NanoVNA-H4 firmware branch and a NanoVNA-H firmware branch.
NanoVNA-H4 users who prefer features in QRP's or edy555's firmware updates
are out of luck unless hugen merges those changes into his NanoVNA-H4
firmware branch. He has done just that in his initial release of the
NanoVNA-H4. It has some of the marker enhancements from edy555's firmware
incorporated.
4. The NanoVNA-H4 comes with a 1950mAh battery. The off-line operating
life should be all day. The battery voltage indicator option is installed.
The larger battery and a new power chip decrease noise that was limiting
measurement range during usb connection. The larger display and faster
processor will eat some portion of the increased battery capacity.
5. A Type-c to Type-c cable was not part of hugen's original NanoVNA
accessories, primarily because the termination resistors that allow Type-c
to Type-c data communications were not installed on the board. The
termination resistors are properly installed on the NanoVNA-H4 so direct
Type-c to Type-c cable connection is possible.
6. A label on the rear of the NanoVNA-H4 uniquely identifies the
NanoVNA-H4 with a QR-code, serial number and version number (4.2).
7. Turning on the NanoVNA-H4 presented a version screen of 0.4.5-7 Jan 1
2020. hugen has just released firmware January 18th, 2020 which I have not
updated to. Updating the firmware for the NanoVNA-H4 is different than in
the NanoVNA-H v3.4. There is no DFU menu option. Instead you have to push
down on the top multi-function switch while turning on the NanoVNA-H4 to
enter the DFU mode. From there updating is the same as in the past.
6. The specified NanoVNA-H4 frequency range is 50k-1.5GHz. The 0.4.5-7
firmware allows setting a lower frequency of 10kz and a high frequency of
1.5GHz. The lower bound frequency is limited by the IF frequency. It needs
twice or more of IF frequency. The other limitation is the mixer coupling
capacitor. The high frequency limit is locked in the firmware to 1.5GHz but
can be increased with accompanying loss of directivity and increase in
noise.
7. The NanoVNA-H4 removes the two accessory RG174 cables and replaces
them with higher quality RG-316 cables. A printed Menu Structure Map is
included in the package but is basically the same menu map that is
available on this group's wiki page.
8. The slightly annoying "feature", where the power LED stays on for a few
moments after switching the NanoVNA-H off, seems to be gone forever on the
NanoVNA-H4 and NanoVNA-H v3.4.
So what's under the hood? ¡
1. All the following under the hood comparisons were made using NanoVNA-H
v3.4 and NanoVNA-H4 devices.
2. The NanoVNA-H4 is powered by a new and more powerful STM32F303CCT6
processor. The benefits are larger SRAM 40KB from 16KB, larger flash 256KB
from 128KB, faster CPU clock 72MHz from 48MHz, and floating point
accelerator. A separate charge pump to power the mixer and tantalum
capacitors were added to reduce the power supply noise. The 1950mAh battery
can independently power the NanoVNA-H4 for more than 8 hours. Access to
UART1, PC14, and PC15 are user available on the v4.2 PCB. Certain members
were clamoring for this UART access in order to add Bluetooth capability.
3. hugen's published specifications are:
Measurement frequency:10 kHz-1.5 GHz
RF output: 0 dBm (2 dBm)
Measurement range: 70 dB (50 kHz-300 MHz), 60 dB (300 m-900 MHz), 40 dB
(0.9 g-1.5 GHz).
Number of scan points: 101 (fixed)
Display traces: 4, markers: 4, Settings Saving: 5
Frequency tolerance: zlt;2.5ppm
Frequency stability: 0.5ppm
Even with the almost 3x the SRAM and 2x the flash memory it looks like
the 101 scan point limitation is going to stay imposed to maintain
backwards software compatibility, bummer.
4. The attached noise floor measurements were made with CH1 of both
devices terminated with a 50 ohm load. The test ranges were 10 kHz - 1 GHz
and 1-1.5 GHz. My NanoVNA-H4 was >70 dB (10 kHz-700 MHz), >=60 dB
(700-1000 MHz), >=50 dB (1-1.5 GHz) meeting or exceeding hugen's
specifications.
5. After the noise floor measurements, I measured some real world
components. First was a 1300 MHz BPF which I used in my previous message
#9883 comparison. The filter skirts and lobes were more defined for the
NanoVNA-H4.
6. Using my Agilent 70dB step attenuator (dc-4GHz) the NanoVNA-H4 hit its
measure limit at -50dB in the 1 - 1.5 GHz range. If erik convinces hugen
to open the NanoVNA v3.4 top frequency to 2.1 GHz, I hope hugen does the
same with the NanoVNA-H4.
7. The last photo is of a vswr antenna measurement on CH0. Its a well
crafted Japanese antenna marked for 1450 MHz operation. The NanoVNA-H4
measured about the same as my NanoVNA-H 3.4 showing a VSWR of 1.1 and that
the antenna is well matched to 50 ohms.
At only $10 usd above the price of the NanoVNA-H v3.4 the NanoVNA-H4 has a
lot to offer. The 4" display is a major improvement over the 2.8"
display. The NanoVNA-F owners are probably wondering what all the fuss is
about as they have enjoyed a large display from the get go.
The faster processor and larger SRAM and Flash memory are eventually going
to remove the bottle neck that is a limiting feature of the NanoVNA-H (v3.4
and below). Currently the desire to maintain backwards software
compatibility is throttling back those advantages. Looking into the future
I can see more measurement points, averaging and a fft bandwidth
implementation. Extended marker functionality has already been added which
otherwise would not fit in the NanoVNA-H -AA memory space.
hugen definitely needs to look into the misaligned usb port opening QA
issue that some members have reported.
I came across one firmware issue while writing this review:
1. I calibrated range 1 - 1.5G saved to memory 1.
2. I recalled memory 1 during later testing and tried the change the
center frequency.
3. STIMULUS->CENTER shows a strange default value (-89748364).
4. I entered a new value (i.e. 1300 M).
5. Screen changes to CENTER 1300 MHz, SPAN 400 MHz but is locked up (No
sweep, no touchscreen or switch response).
6. Cycling power restores function.
7. Above repeats
Before I submit this as an issue to hugen I'm going to investigate this
further tomorrow. If anyone else that has received a NanoVNA-H4 would try
the above and let me know the results I'd appreciate it. I always assume
operator error before submitting a software issue.
- Herb
|
The DFU mode is entered by turning OFF the unit, pressing in and holding the selector switch and then turning the unit ON.Then release the switch.
toggle quoted message
Show quoted text
On Wednesday, January 22, 2020, 8:22:32 a.m. GMT-5, Jos Stevens <jrs@...> wrote: Why ofcourse Herb ? DFU mode is replaced by "Brightness" and I remember to have seen DFU mode passing by, but can't find it back now, please how to entyer DFU mode, I tried a long press? af the swith, but no luck. Jos Op 22-1-2020 om 10:58 schreef hwalker: On Wed, Jan 22, 2020 at 12:17 AM, Oristo wrote:
" You may be able to capture screens by modifying Specifically, replace 320 and 240 at lines 46 and 73 with pixel dimensions of NanoVNA-H4 display, and COM3 at line 11."
Hi Oristo,
? ? I fell back on your script after Rune's module stopped working.? Changing the script to:
? ? ? ? ? b = ser.read(320 * 480 * 2)
? ? ? ? ? x = struct.unpack(">153600H", b)
Resulted in a correctly colored,? but double overlayed image.? I wanted to get a review out and so did not work on the script further.? Note: other parts of the script were changed as appropriate (or at least to my understanding) for 320x480 resolution.? The resolution comes from hugen's product specification and I'm assuming is correct.
? " If someone can describe menu changes or point to an image for printed NanoVNA-H4 Menu Structure Map, I will create and updated map for /g/nanovna-users/wiki/User-Guides ."
The? included Menu Structure Map (see attachment) was the same as for the NanoVNA-H v3.4 and was not updated for the NanoVNA-H4.? For example, it shows ">DFU" option under CONFIG and of course the NanoVNA_H4 does not use this method to enter DFU mode.
- Herb
|
Why ofcourse Herb ? DFU mode is replaced by "Brightness" and I remember to have seen DFU mode passing by, but can't find it back now, please how to entyer DFU mode, I tried a long press? af the swith, but no luck.
Jos
Op 22-1-2020 om 10:58 schreef hwalker:
toggle quoted message
Show quoted text
On Wed, Jan 22, 2020 at 12:17 AM, Oristo wrote:
" You may be able to capture screens by modifying Specifically, replace 320 and 240 at lines 46 and 73 with pixel dimensions of NanoVNA-H4 display, and COM3 at line 11."
Hi Oristo,
I fell back on your script after Rune's module stopped working. Changing the script to:
b = ser.read(320 * 480 * 2)
x = struct.unpack(">153600H", b)
Resulted in a correctly colored, but double overlayed image. I wanted to get a review out and so did not work on the script further. Note: other parts of the script were changed as appropriate (or at least to my understanding) for 320x480 resolution. The resolution comes from hugen's product specification and I'm assuming is correct.
" If someone can describe menu changes or point to an image for printed NanoVNA-H4 Menu Structure Map, I will create and updated map for /g/nanovna-users/wiki/User-Guides ."
The included Menu Structure Map (see attachment) was the same as for the NanoVNA-H v3.4 and was not updated for the NanoVNA-H4. For example, it shows ">DFU" option under CONFIG and of course the NanoVNA_H4 does not use this method to enter DFU mode.
- Herb
|
Re: *** FIX FOR NANOVNA-SAVER PYQT5 INSTALLATION PROBLEMS ON LINUX MINT 19.3 ***
#nanovna-saver
On Tue, Jan 21, 2020 at 07:50 PM, Bob Larkin wrote: Not so on a 32-bit PC with 18.04. Hi Bob thanks for pointing this out. It's not a bug... "Wheels are the standard Python packaging format for pure Python or binary extension modules such as PyQt5. Only Python v3.5 and later are supported. Wheels are provide for 32- and 64-bit Windows, 64-bit macOS and 64-bit Linux." There is no wheel file for 32 bit PyQt5 that pip can use. So trying to install it using pip will fail. Read the instructions for building and bundling PyQt5 and decided life too short! Your workaround using PyQt5 v5.10.1 from the Ubuntu repo (post #10010) is probably best for 32-bit. Will update the .pdf and wiki to qualify fix is 64-bit only. 73 Nick G3VNC
|
On Wed, Jan 22, 2020 at 12:17 AM, Oristo wrote: " You may be able to capture screens by modifying Specifically, replace 320 and 240 at lines 46 and 73 with pixel dimensions of NanoVNA-H4 display, and COM3 at line 11." Hi Oristo, I fell back on your script after Rune's module stopped working. Changing the script to: b = ser.read(320 * 480 * 2) x = struct.unpack(">153600H", b) Resulted in a correctly colored, but double overlayed image. I wanted to get a review out and so did not work on the script further. Note: other parts of the script were changed as appropriate (or at least to my understanding) for 320x480 resolution. The resolution comes from hugen's product specification and I'm assuming is correct. " If someone can describe menu changes or point to an image for printed NanoVNA-H4 Menu Structure Map, I will create and updated map for /g/nanovna-users/wiki/User-Guides ." The included Menu Structure Map (see attachment) was the same as for the NanoVNA-H v3.4 and was not updated for the NanoVNA-H4. For example, it shows ">DFU" option under CONFIG and of course the NanoVNA_H4 does not use this method to enter DFU mode. - Herb
|
Re: Improving the performance of a pre-V3.4 original Hugen nanoVNA
On Wed, Jan 22, 2020 at 11:37 AM, Jim Allyn - N7JA wrote: , "You know how you can tell who the pioneers are?? They're the ones with the arrows in their backs."
I agree that the best is the enemy of the good! :-) But if you can 't, but you really want to, you can! :-) Hi Hi Thanks!
|
Re: Improving the performance of a pre-V3.4 original Hugen nanoVNA
On 1/21/20 10:15 PM, Andy UA3RAW wrote: Hello, dear friends!
I have a dilemma, which one of the CH1 modifications to apply?:) The original, as on rev.3.4.1 schematic.
R22, R23=51Ohm, R24=91 Ohm, R25=11 Ohm.
Or suggested by Erik PD0EK. R22, R23=240 Ohm, R24=56 Ohm, R25=75 Ohm. ???? I'm in no rush to mod mine.? It seems to work fairly well, so I'm going to wait until others have tried the various mods and figured out what works and what doesn't.? Years ago, an employer of mine used to say, "You know how you can tell who the pioneers are?? They're the ones with the arrows in their backs."
|
Hi Herb - Because of the increased screen resolution, Rune's screen capture module in
NanoVNA-saver 2.2-1 did not work, hugen warned this would be the case until
developers catch up. Due to this no screen captures are attached. You may be able to capture screens by modifying Specifically, replace 320 and 240 at lines 46 and 73 with pixel dimensions of NanoVNA-H4 display, and COM3 at line 11. A printed Menu Structure Map is included in the package but is basically the same menu map that is available on this group's wiki page. If someone can describe menu changes or point to an image for printed NanoVNA-H4 Menu Structure Map, I will create and updated map for /g/nanovna-users/wiki/User-Guides
|
" I always assume operator error before submitting a software issue."
More importantly, just one measurement is not a measurement.
My ePacket has already moved on, I hope to get here next week.
73, Gyula HA3HZ
|
Herb,
Excellent report. Thanks for taking the time to write this up...
Roger
|
Re: Improving the performance of a pre-V3.4 original Hugen nanoVNA
On Wed, Jan 22, 2020 at 09:37 AM, <erik@...> wrote:
Use the original. I only used other values because I did not have the original
Erik, PD0EK
Thank you Erik. I have ordered the original and yours 1% resistors. Now waiting... :-) 73!
|
Andy UA3RAW
gin&pez@arg
Merle W
Jim Allyn - N7JA
Oristo
Gyula Molnar
Roger Need