Re: nanoVNASaver version 0.1.2 - Is it working properly for you?
Hi Bryan, could you try running a multi-segment scan, but after starting the program with the command-line option "-D logfile.txt" - and sending me the resulting log file? I would like to see if it's getting your firmware mixed up with one that supports the scan function edy555 implemented in the newer firmwares. -- Rune / 5Q5R On Sat, 12 Oct 2019 at 23:35, bryburns via Groups.Io <bryburns= [email protected]> wrote: I recently downloaded the latest nanoVNA-Saver version 0.1.2 from
.
I am using firmware which gives the following information from a terminal
window:
ch> version
0.1.1.1-5-gd609fb2
ch> info
Kernel: 4.0.0
Compiler: GCC 8.2.1 20181213 (release) [gcc-8-branch revision 267074]
Architecture: ARMv6-M
Core Variant: Cortex-M0
Port Info: Preemption through NMI
Platform: STM32F072xB Entry Level Medium Density devices
Board: NanoVNA-H
Build time: Sep 20 2019 - 17:31:03
The file I loaded this firmware from was nanoVNA_900_ch_20190920.dfu which
I think is the same as NanoVNA-H__900_ch_20190924.dfu found on the Wiki.
This firmware has worked fine with other versions of nanoVNA-Saver
including 0.0.10, 0.0.11, 0.0.12, 0.1.0, and 0.1.1; however, it doesn't
seem to work well with the latest version of nanoVNA-Saver (0.1.2).
Here are some of the issues I am having:
1) Frequency sampling is no longer the correct sample spacing when using
multiple scans. When using 5 scans from 50 kHz to 900 MHz, the sample
spacing is 9 MHz not ~1.785 MHz as it used to be.
2) All scans go from the starting frequency to the stop frequency. When
collecting 5 "Segments" all 5 appear to be on exactly the same frequencies
based on the plots on the computer screen.
3) It looks like all data is plotted and an average of the data collected
in averaging mode is not shown.
Are other people having similar issues with version 0.1.2 working with
their firmware? If you are having good success with the latest version;
what firmware are you using?
I don't seem to be able to get a good cal from the latest firmware version
which is the reason I have been sticking to a version from September 20
2019. Yes, I did clear the memory using DMR-CLEAR_MEMORY_DFU.dfu before
loading the latest firmware into my nanoVNA; however, I still can't get a
reliable calibration which shows a nice tight dot for all 3 calibration
standards.
--
Bryan, WA5VAH
|
nanoVNASaver version 0.1.2 - Is it working properly for you?
I recently downloaded the latest nanoVNA-Saver version 0.1.2 from
.
I am using firmware which gives the following information from a terminal window:
ch> version
0.1.1.1-5-gd609fb2
ch> info
Kernel: 4.0.0
Compiler: GCC 8.2.1 20181213 (release) [gcc-8-branch revision 267074]
Architecture: ARMv6-M
Core Variant: Cortex-M0
Port Info: Preemption through NMI
Platform: STM32F072xB Entry Level Medium Density devices
Board: NanoVNA-H
Build time: Sep 20 2019 - 17:31:03
The file I loaded this firmware from was nanoVNA_900_ch_20190920.dfu which I think is the same as NanoVNA-H__900_ch_20190924.dfu found on the Wiki.
This firmware has worked fine with other versions of nanoVNA-Saver including 0.0.10, 0.0.11, 0.0.12, 0.1.0, and 0.1.1; however, it doesn't seem to work well with the latest version of nanoVNA-Saver (0.1.2).
Here are some of the issues I am having:
1) Frequency sampling is no longer the correct sample spacing when using multiple scans. When using 5 scans from 50 kHz to 900 MHz, the sample spacing is 9 MHz not ~1.785 MHz as it used to be.
2) All scans go from the starting frequency to the stop frequency. When collecting 5 "Segments" all 5 appear to be on exactly the same frequencies based on the plots on the computer screen.
3) It looks like all data is plotted and an average of the data collected in averaging mode is not shown.
Are other people having similar issues with version 0.1.2 working with their firmware? If you are having good success with the latest version; what firmware are you using?
I don't seem to be able to get a good cal from the latest firmware version which is the reason I have been sticking to a version from September 20 2019. Yes, I did clear the memory using DMR-CLEAR_MEMORY_DFU.dfu before loading the latest firmware into my nanoVNA; however, I still can't get a reliable calibration which shows a nice tight dot for all 3 calibration standards.
--
Bryan, WA5VAH
|
Simple Vector Voltmeter option on FieldFox
Dr. David Kirkby from Kirkby Microwave Ltd
I bought a FieldFox at some point and paid for the ¡°vector voltmeter¡±
option. I was expecting a high impedance input, but it was not and I felt
it was a bit of a waste of money.
All this expensive option did was display something in a different way to
the usual way. But thinking about it, this feature does have use to the non
technical ham.
All this does is display the loss and phase of S11 at a single frequency in
big numbers. It¡¯s designed for cutting things like coax for antennas.
Since links often break, I took a screenshot from my mobile phone.
It certainly would not be on my wishlist, but it might interest others.
--
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
|
Re: This seller looks iffy selling nanoVNA's
When did non-gekko white nanoVNA first appear?
|
Re: Firmware upgrade - Touchscreen not working
Don't have a serial interface. PuTTY
|
Re: Firmware upgrade - Touchscreen not working
Yes, before the firmware upgrade.
|
Re: Firmware upgrade - Touchscreen not working
Hmm, the calibration within the firmware should be the same as if it's activated from serial - it puts a couple of marks on the screen and asks you to press them? If you have a screen that's for some reason "flipped", it might be impossible to calibrate. Has it worked at any point? -- Rune / 5Q5R On Sat, 12 Oct 2019 at 21:59, Andy Yates <andyfranyates@...> wrote: Rune,
Thanks.
Don't have a serial interface. BTW I've tried dfu-util with linux and
DfuSe with Windows. Same result. I've done the stand-alone
touchscreen cal within the firmware which appears to work, It's
almost like the screen is upside down and backwards. i've tried
different corner combinations within the calibration. No success.
Any other ideas besides the serial interface ?
Andy -W4KIL
|
Re: Firmware upgrade - Touchscreen not working
Rune,
Thanks.
Don't have a serial interface. BTW I've tried dfu-util with linux and
DfuSe with Windows. Same result. I've done the stand-alone
touchscreen cal within the firmware which appears to work, It's
almost like the screen is upside down and backwards. i've tried
different corner combinations within the calibration. No success.
Any other ideas besides the serial interface ?
Andy -W4KIL
|
Re: Please change project name: NanoVNA V2
Anything sold for under $30 is 99% fraudulent.?
On Sat, 12 Oct 2019 at 12:49 PM, W5DXP<w5dxp@...> wrote: Tomohiro, you have given me the most performance for the least cost of any electronic device that I can remember and I can't thank you enough. I wonder how many total NanoVNAs, have been manufactured and how anyone could be selling them for $17?
|
Re: Firmware upgrade - Touchscreen not working
Hi Andy, sounds like exactly what you would experience if the firmware thought you were pressing somewhere other than the menu itself. Try a touchscreen cal? (command "touchcal" when connected via serial interface). -- Rune / 5Q5R On Sat, 12 Oct 2019 at 21:23, Andy Yates <andyfranyates@...> wrote: Yes and it works fine except NO touchscreen sub-menus.
I touch the screen and the main menu pops up fine, but
selecting any item and it just goes away.
|
Re: This seller looks iffy selling nanoVNA's
This seller is currently away. Hmmmmm
|
Re: Firmware upgrade - Touchscreen not working
Yes and it works fine except NO touchscreen sub-menus.
I touch the screen and the main menu pops up fine, but
selecting any item and it just goes away.
|
Re: Can the NanoVNA be used on 75-ohm antennas/cables?
Somehow, I don't see a good reason to CARE about matching
receiver input impedance. Maybe it lowers the antenna bandwidth or Q? Certainly Q, which is good or bad, depending on application. Mismatch also plays with imbalance, so that e.g. coax from antenna to receiver can effectively become part of antenna, picking up noise between outdoor antennas and indoor receivers.
|
Re: Can the NanoVNA be used on 75-ohm antennas/cables?
Does not a mismatch create problems with loss and noise?
|
Re: Firmware upgrade - Touchscreen not working
I've tried several different firmwares Did you try Hugen's latest?
|
Re: Firmware upgrade - Touchscreen not working
|
Re: Firmware upgrade - Touchscreen not working
On 2019-10-12 13:18, Andy Yates wrote: Touchscreen works for main menu, but I can't go to any sub-menus.
Menus all work with toggle/PB.
I've tried several different firmwares and they all load correctly,
but no touchscreen sub-menus.
Any ideas for a fix ?
Thanks,
Andy -W4KIL
did you try calibrating it
|
Re: Can the NanoVNA be used on 75-ohm antennas/cables?
Does not a mismatch create problems with loss and noise?
If I connect a 50 ohm coax to a 300 ohm TV antenna, without a
transformer, should I not anticipate a poor quality received signal?
Or am I misunderstanding?
David, KD4E
toggle quoted message
Show quoted text
You know, after all the talk about matching impedances, I'm really
wondering .... we talk about POWER in watts but that's pretty much for
transmitters. But we talk about receivers in? VOLTS. Well, okay, microvolts,
usually. Somehow, I don't see a good reason to CARE about matching
receiver input impedance. Maybe it lowers the antenna bandwidth or Q?
Impedances have PHASE, but voltages do not. Care to comment?
Bill
|
Re: Finally I found out how to order a NanoVNA-H
Were there photos to show if the back was shielded ?
-Kevin (KK4YEL)
|
Re: errors of "error" models
#42 : The compact SLO formula for [AnyVNA] Hello, Allow us, please, to inform you that our two final reports: 1 : #30 : 5 October 2019 : /g/nanovna-users/message/41792 : #38 : /g/nanovna-users/message/4293are resulted after we used the formulas given at: #16 : 27 September 2019 : /g/nanovna-users/message/3161with the clarifications provided at: #17 : 27 September 2019 : /g/nanovna-users/message/3192for the following Nominal Values of SLO "standards": Short : A := S = Polar : ( 1 , 180 ) = Cartesian : ( -1 , 0 ) = Complex : -1 + j0 = Real : -1 Load : B : = L = Polar : ( 0, undefined) = Cartesian : ( 0, 0 ) = Complex : 0 + j0 = Real : 0 Open : C := O : Polar : (1 , 0) = Cartesian : ( 1 , 0) = Complex : 1 + j0 = Real : +1 and the following Indicated values of our [NanoVNA] and [VNA] Short Indication : a := s Load Indication : b := l Open Indication : c := o Unknown load Indication : gamma substituted to: to got the following minimal mathematical expression for the Unknown Gamma measured by [AnyVNA] - all complex: at each defined frequency. Sincerely, gin&pez@arg #42
|
Oristo
George K4LAZ
z_ kevino
gin&pez@arg