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
