开云体育

Hugen told me the g8ac9166 part is the build number (version?) and I assume you can peruse the changes in his git repo that relate to that specific number.
Also, this is his build release notes from 3 days ago:
1. not synchronized to save flash, this may use the last version of inline optimization, and the screen speed will be significantly
slower after disabling the function inline;
2. Fixed the problem that the AA version clear_flash is not properly emptied;
3. After recompiling, you can connect to the cho45 web interface normally, but I don't

On Monday, October 21, 2019, 2:57:15 p.m. GMT-4, Oristo <ormpoa@...> wrote:

> Where can one find the FW change log?

I find this tricky..
Recent Hugen releases have CONFIG -> VERSION
that now shows v0.2.3-2-g8ac9166

Going to ,
this suggests that Hugen pulled from edy555 on or after #111
.. but it is unclear to me which of those (if any)
e.g. reduced configuration storage from from five to four (SAVE 0-3)

It may be after #115? added negative value support for SCALE->ELECTRICAL DELAY

* does v0.2.3-2-g8ac9166 implement 12kHz IF?
* will shell 'offset' command still work?
* will disabling inline function promote even more touch screen bugs?
? (e.g. testing ELECTRICAL DELAY)
* will disabled items (e.g. 'dump') remain in shell 'help' output, like 'test'?

I see no battery symbol on the display.

Adding diode only connects sensor

Is it a case of reinstall the firmware, to enable this??

Yes.

Just popped a SMT 1n4148 in D2, but with my 0.2.3 firmware I see no battery symbol on the display.
Is it a case of reinstall the firmware, to enable this??

Where can one find the FW change log?

I find this tricky..
Recent Hugen releases have CONFIG -> VERSION
that now shows v0.2.3-2-g8ac9166

Going to ,
this suggests that Hugen pulled from edy555 on or after #111
.. but it is unclear to me which of those (if any)
e.g. reduced configuration storage from from five to four (SAVE 0-3)

It may be after #115 added negative value support for SCALE->ELECTRICAL DELAY

* does v0.2.3-2-g8ac9166 implement 12kHz IF?
* will shell 'offset' command still work?
* will disabling inline function promote even more touch screen bugs?
(e.g. testing ELECTRICAL DELAY)
* will disabled items (e.g. 'dump') remain in shell 'help' output, like 'test'?

On Mon, Oct 21, 2019 at 12:48 PM, <bryburns@...> wrote:

4 scans from 50 kHz to 900 MHz.

This should read "4 segments from 50 kHz to 900 MHz."
--
Bryan, WA5VAH

Dear all,
I have been blessed with a group of people who have helped test the last
few releases of NanoVNA-Saver. I'm getting ready to send them another alpha
version, but I thought I would offer inclusion into the little group to
some more of you.

If you want to help out, and particularly if you have reported a bug that I
have promised to fix "in the next release" - ;-) - do send me an email
direct (mihtjel at gmail.com, I hope this doesn't get eaten by groups.io)
and I will add you to my mailing list.

I'm looking for quite fast turnaround on these alpha releases. It's not
going to be testing for weeks on end - but on the other hand, I don't
require that you always take part and report back. Please only ask to be on
the list if you intend to actually test, and report the bugs and errors you
find :-)

I look forward to hearing from you,
--
Rune / 5Q5R

On Mon, Oct 21, 2019 at 12:32 PM, Oristo wrote:

This smells like you should reduce threshold

Interesting thought, but I already have done that as a test. I set threshold to 295 MHz. Of course, you have to fully recalibrate (nanoVNA and nanoVNA-Saver) once you make such a change and use saveconfig.

I also notice that the first sample in a particular segment is sometimes bad when doing 4 scans from 50 kHz to 900 MHz. Often both the second and fourth scans will have an error in the same scan;however, it also happens that only one of them has an error. I don't see the first sample bad in the first and third scans. It must be some kind of timing issue somewhere.

--
Bryan, WA5VAH

Kurt, thanks again for your explanations and pictures.

Now I have to experiment for a while and build a suitable fixture and see what the resuts are. I don't want to overdo it too much, primarily I need a good and reasonabe accuracy to compare ferrits for EMC applications of various manufactureres.

Once more thanks, and I'm sure at some point of time I will have more questions.... or even results.
Always great help to have someone experienced here.

The frequency in the s2p file is 602003132 Hz

This smells like you should reduce threshold
/g/nanovna-users/message/4155

Hi Bryan,
I know it's the easy way out to claim that it's the other guy's fault, but
I really don't treat 0.3.0 any differently than I did 0.2.3. The fact that
it's at a specific frequency might point towards it being related to your
calibration at that particular frequency. I assume, though, that you have
tried re-calibrating your device, and that it remained in place at the same
frequency? Do you get any errors in the console log? Have you tried
running it with '-d' command line option to see the debugging output, and
whether that gives you something? (though it probably won't.)

If you save a Touchstone S1P or S2P file, you can cut out the frequencies
around where the fault occurs, and maybe put those in this thread - it
would be interesting to see the numerical values of the fault, at least for
me. :-)

--
Rune / 5Q5R

On Mon, 21 Oct 2019 at 20:19, bryburns via Groups.Io <bryburns=
[email protected]> wrote:

On Sun, Oct 20, 2019 at 11:03 PM, <bryburns@...> wrote:

I am seeing a lot more data errors with this version of firmware than I

saw

with 0.2.3 from edy555

Rune,

I have a little more information on the data error issues when
nanoVNA-Saver 0.1.3 interfaces to the edy555 - 0.3.0 firmware.

I get a consistent error when running 3 scans from 50 kHz to 900 MHz. The
device connected to the nanoVNA was the "through" I used for calibration of
both the nanoVNA and nanoVNA-Saver 0.1.3. The first sample of the 3rd scan
is often, but not always, in error in the S11 data. The frequency in the
s2p file is 602003132 Hz. It seems to happen 2 or 3 times in 5 scans. I
setup nanoVNA-Saver to run continuously and put a marker on that frequency
and can see the errors are exactly the same frequency. Sometimes 2
consecutive scans will have errors. Often, the S11 data will show a 5-10
dB error. When the S11 data is in error at this frequency, S21 in (dB and
degrees) will also show a relatively small error compared to adjacent
samples. With these settings, I don't see any other obvious errors in the
S11 data or the S21 data. So, this particular issues seems tightly
correlated to scanning in nanoVNA-Saver and the 0.3.0 firmware. Again,
this doesn't happen with 0.2.3 firmware.

I hope this helps with figuring out the cause of some of the data errors.
--
Bryan, WA5VAH

The other menu change will be 2 less traces to enable/disable.One of the storage locations was cut due to the size of the larger fonts.Hugen found there was some overlap and corruption of the data area, which he fixed in his latest release.

On Monday, October 21, 2019, 2:12:27 p.m. GMT-4, Oristo <ormpoa@...> wrote:

> > I found the menu structure for firmware 0.2.3 -

but could not find one for the NanoVNA-H which was slightly different.

Thanks for heads up;

The main difference that I found in Google Drive Oct 18 AA firmware
is now only four (0-3) SAVE and RESTORE configurations, sigh...

Other that maybe order of some items, are there other menu changes?

On Sun, Oct 20, 2019 at 11:03 PM, <bryburns@...> wrote:

I am seeing a lot more data errors with this version of firmware than I saw
with 0.2.3 from edy555

Rune,

I have a little more information on the data error issues when nanoVNA-Saver 0.1.3 interfaces to the edy555 - 0.3.0 firmware.

I get a consistent error when running 3 scans from 50 kHz to 900 MHz. The device connected to the nanoVNA was the "through" I used for calibration of both the nanoVNA and nanoVNA-Saver 0.1.3. The first sample of the 3rd scan is often, but not always, in error in the S11 data. The frequency in the s2p file is 602003132 Hz. It seems to happen 2 or 3 times in 5 scans. I setup nanoVNA-Saver to run continuously and put a marker on that frequency and can see the errors are exactly the same frequency. Sometimes 2 consecutive scans will have errors. Often, the S11 data will show a 5-10 dB error. When the S11 data is in error at this frequency, S21 in (dB and degrees) will also show a relatively small error compared to adjacent samples. With these settings, I don't see any other obvious errors in the S11 data or the S21 data. So, this particular issues seems tightly correlated to scanning in nanoVNA-Saver and the 0.3.0 firmware. Again, this doesn't happen with 0.2.3 firmware.

I hope this helps with figuring out the cause of some of the data errors.
--
Bryan, WA5VAH

I found the menu structure for firmware 0.2.3 -

but could not find one for the NanoVNA-H which was slightly different.

Thanks for heads up;

The main difference that I found in Google Drive Oct 18 AA firmware
is now only four (0-3) SAVE and RESTORE configurations, sigh...

Other that maybe order of some items, are there other menu changes?

Thanks for your very quick reply. That sorted it.

Paul, G0VKT.

And to complete the comparison two more measurements.
The directivity of the bridge (red line) and the dynamic range of port 2 (CH1) (green line) of the nanoVNA and the home build VNA
Measured by connecting 50 ohm to both ports.
The bridge performances are fairly comparable but the dynamic range measurement requires further study

#67 : On [TheLeastVNA] : 18 Questions and 15 Answers

@Gary O'Neil - 17 October 2019 :
/g/nanovna-users/message/5081

Dear Gary,

It is our pleasant duty to reply your specific Questions regarding our work !

However, allow us, please, to not make any comment or to comment any
of your conclusions, regarding the comparison of the Qualities of our
instruments, simply because we do not consider appropriate to do so.

Well, after all that said, let's proceed as follows:


Q1 : "What were the Putty commands you used to extract data from the NanoVNA?"
-
A1 : The commands to [NanoVNA] through PuTTy are [info], [frequencies] and [data],
as these are shown as "headers" inside the following data files:

[info]

[frequencies]:


[data]:





but take into account, please, that you have to edit all data files in order
to remove any such "headers" and leave just 101 lines of data, if you
intend to use them with the current version of [TheLeastVNA]:



=

Q2 : "Can you confirm the data as raw (uncorrected) or post calibration
corrected measurements?"
-
A2 : Yes. Right after you finish with each measurement s, l, o, g of S, L, O, G
you command with the PuTTy : [data], so the measurements are shown in
PuTTy's console window and then you have to select, copy, and paste them
to the corresponding file.

=

Q3 : "Your VNA data (blue) appears to have been taken at a significant offset
from the reference plane. If this is uncorrected raw data it makes sense in an
automated VNA environment."
-
A3 : Not at all - Our VNA data were taken exactly on the same reference plane.
Otherwise a comparison would not be possible at all - Please, be careful at this
very point - You have been warned

=

Q4-7 : "I am interpreting your full final report 1 as follows:" "1. ..." "2. ..." "3. ..." "4. ..."
-
A4-7 : Yes - Yes -Yes - Yes

=

Q8 : "The variables used in the gamma equation shown are assumed to be the
complex values..."
-
A8 : Yes

=

Q9 : "There are no numerical values or constants in the equation..."
-
A9 : Yes

=

Q10 : "There are no calibration correction coefficients used in producing
any of this data, nor in any of the computed results plotted in this report."
-
A10 : No - The so called "calibration" procedure is hidden in our compact
computation of Reflection Coefficient of the Unknown load.

Q11 : "To that point, the calibration standards used are considered ideal and
perfect."
-
A11 : Not at all - The manufacturers of these 'standards' declare their NOMINAL
VALUES and thus we are obliged to take these NOMINAL VALUES exactly
- Please, be careful at this very point - You have been warned

=

Q12 : "The upper case gamma is the computed complex result of this equation
representing the corrected measured value of the DUT, and is interpreted as
the reflection coefficient of the DUT at the measurement frequency."
-
A12 : Yes

=

Q13: "This then enables one to graphically visualize the nominal result differences
between..."
-
A13 : Yes

=

Q14 : "The inference that one can observe..."
Q15 : "The NanoVNA is clearly shown, not surprisingly, to be inferior in performance..."
Q16 : "As to whether or not the..."
-
A14-16 : We don't want to comment to the slightest on these - These are exclusively
your conclusions

=

Q17 : "Part 3 of 3 (III / III) is simply the computed complex impedance..."
-
A17 : Yes

=

Q18 : "This is all quite encouraging. I believe that I am now following your process up
to this point. If any of my interpretation to this point is in error, I trust you will correct
me where needed."
-
A18 : Thank you very much, indeed - The trustfulness is always mutual.

Best regards,

gin&pez@arg

67#

something didnt work properly under Catalina…still trying to trace the issue,
something to do with the serial ports

I cannot even use High Sierra because of driver (and Java) issues.
macOS has become more restrictive about 3d party kernel extensions or kexts.
"They act as drivers — if you like a Windows analogy — and give access to your Mac’s hardware."

Something done on previous macOS that was inherited by Catalina update
could be at issue. Check 'Security & Privacy' under 'System Preferences'

"If a user space driver quits unexpectedly or you restart your Mac,
you might need to unplug and reattach the accessory cable to enumerate the driver. (50042397)"
"Driver extensions might not launch on-demand after installation. (51229724)
Workaround: Disable System Integrity Protection"


CH340 driver

Thanks Larry - good summary

This all worked fine on my iMac under High Sierra, however something
didnt work properly under Catalina…still trying to trace the issue, something
to do with the serial ports… I’ll report back if I can figure it out.

Cheers
Dana VE3DS

Signature test 21 Oct 2019 1030AM MDT

Interestingly the .io sites have the embedded Wiki, the Yahoo groups did
not.

Mel, K6KBE