Re: errors of "error" models
38 : our final report 2 : core uncertainty strips 37 : ann : the uncertainties of our nanovna will be estimated tomorrow /g/nanovna-users/message/4218Hello, Allow us, please, to inform you that we just uploaded the Core Uncertainty Strips for our NanoVNA: r ~ f : x ~ f : info Kernel: 4.0.0 Compiler: GCC 5.4.1 20160919 Architecture: ARMv6-M Core Variant: Cortex-M0 Port Info: Preemption through NMI Platform: STM32F072xB Entry Level Medium Density devices Board: NanoVNA Build time: Aug 2 2019 - 16:40:01 Sincerely, gin&pez@arg 38
|
Hi Larry and in3elx.
Larry he is not repeating himself he is editing his post. But he is
doing it with the web interface of the group.
You on the other side are using the email fonction of the group and
every time in3elx edit his post you receive a new email of his edited
post.
That is why you see [Edited Message Follows] into his messages.
hope this helps.
toggle quoted message
Show quoted text
Le lun. 7 oct. 2019 ¨¤ 15:09, <in3elx@...> a ¨¦crit :
On Mon, Oct 7, 2019 at 07:24 PM, Larry Rothman wrote:
Please stop repeating yourself in the forum - it is very poor etiquette.
You also appear to be the only one with this issue.
Please verify you are following all the various guides that are available
here.
Read, then read some more, then google for nanovna on other websites where
users have created pages about the device.
On Monday, October 7, 2019, 2:16:39 p.m. GMT-4, <in3elx@...> wrote:
[Edited Message Follows]
I can't communicate with the developers.
I don't repeating anything.
What problem I do you create? Is this your etiquette/ham spirit?
This is a forum, those who want to help help me maybe they will, those who don't want to help me can read other things.
Good night. Thanks again.
|
Re: Another modified nanoVNA software
Hi neb40gsm,
me too I would like to try your software.
Thank you in advance.
N.V.
|
Re: Annotated nanoVNA menu diagram
Hi Stan - I think the latest one looks pretty nice. It is more compact, which may help on smaller screens. I think you're doing terrific for not being too familiar with the programming you're using. Anyone with time and Internet search can do it. And remember, there's no way to make everybody happy... My goal is minimizing unhappiness. VNA is conceptually pretty simple, IMO, but acronyms and esoteric naming provoke difficulties. Traditional menus obscure too much. Ideally, one could mouse with menu map: * hover briefly for hints * right-click for more help * left click to execute. .. but * CSS hover does not work for mobile devices - tested mouse with new iOS 13.. * right-click also seems doomed without JavaScript Another possibility is radio buttons to switch action for all map entry links between help and execute.
|
Locked
Re: Inflation of this forum
I would be helpful if the Nano VNA group owner enabled the Hashtag option as others have previously suggested.
This needs to be set from the group owners admin page before it can be used.
I'd suggest a few to get things started
#Nano VNA Hardware
#Nano VNA Firmware
#Nano VNA Bug report
#Nano VNA New feature
#Nano VNA Saver Software
#Nano VNA Saver Bug report
#Nano VNA Saver New feature
#Nano VNA Documentation
I'm sure others would get added by users once it became normal to tag posts.
Regards,
Martin - G8JNJ
|
On Mon, Oct 7, 2019 at 07:24 PM, Larry Rothman wrote:
Please stop repeating yourself in the forum - it is very poor etiquette.
You also appear to be the only one with this issue.
Please verify you are following all the various guides that are available
here.
Read, then read some more, then google for nanovna on other websites where
users have created pages about the device.
On Monday, October 7, 2019, 2:16:39 p.m. GMT-4, <in3elx@...> wrote:
[Edited Message Follows]
I can't communicate with the developers.
I don't repeating anything. What problem I do you create? Is this your etiquette/ham spirit? This is a forum, those who want to help help me maybe they will, those who don't want to help me can read other things. Good night. Thanks again.
|
Re: Annotated nanoVNA menu diagram
I think the latest one looks pretty nice. I was just trying to help a little bit with making it narrower.
I think you're doing terrific for not being too familiar with the programming you're using.
And remember, there's no way to make everybody happy...
|
Re: Annotated nanoVNA menu diagram
Nah - way too crowded. I liked your previous layout That is still the default link.. Retweaked:
|
Please stop repeating yourself in the forum - it is very poor etiquette.
You also appear to be the only one with this issue.
Please verify you are following all the various guides that are available here.
Read, then read some more, then google for nanovna on other websites where users have created pages about the device.
toggle quoted message
Show quoted text
On Monday, October 7, 2019, 2:16:39 p.m. GMT-4, <in3elx@...> wrote:
[Edited Message Follows]
I can't communicate with the developers.
|
Re: Latest edy555 firmware release with dfu file
OK, thank you for adding the updated file.
Unfortunately, the Windoze DefuSe app doesn't care about the USB IDs and I forgot to check when I converted.
toggle quoted message
Show quoted text
On Monday, October 7, 2019, 2:07:41 p.m. GMT-4, reuterr@... <reuterr@...> wrote:
Hello Larry,
I tried to flash your provided file edy-0.2.3-oct-7-19.dfu
under MacOS with the program dfu-util (Ver. 0.9), which I have used before.
I have learned from the manual, that the USB product ID should be "df11".
Unfortunately in your provided file the USB Product ID was 0,
so it coud not be programmed. See error:
dfu-util: Error: File ID 0483:0000 does not match device (0483:df11 or 0483:df11)
Next I have taken the .hex file under Windows 10 and program DfuFileMgr.exe
to add the Provider ID "df11".
Then I could flash in the Terminal:
$ dfu-util -v -d 0483:df11 --alt 0 -D nanoVNA_0.2.3-ch.dfu
I have appended to file nanoVNA_0.2.3-ch.dfu
73, Rudi
|
Re: Annotated nanoVNA menu diagram
Nah - way too crowded. I liked your previous layout. On Monday, October 7, 2019, 2:00:13 p.m. GMT-4, Oristo <ormpoa@...> wrote: > I lost sleep last night, pondering Stan's suggestion for CSS changes which may result in overall cleaner (if not smaller) diagrams.
|
Hello Pierre,
thank you for the suggestion! It is indeed on my list ;-) For now, the
NanoVNA-F folks have changed their prompt in order to support the other
software versions available. I am working on a more general approach to
supporting different versions, including the differences between edy555's
latest firmwares and earlier versions.
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Mon, 7 Oct 2019 at 19:59, Pierre Martel <petem001@...> wrote: Rune, a little idea to make the software compatible to the new and
old prompt (as some still use older firmware) would be to make a
"check" when first connecting to the device and read the prompt and
use that one in the reste of the software..
But I am sure it was already what you wanted to do. ;-)
Le lun. 7 oct. 2019 ¨¤ 12:55, hwalker <herbwalker2476@...> a ¨¦crit :
[Edited Message Follows]
On Sun, Oct 6, 2019 at 02:26 PM, Rune Broberg wrote regarding NanoVNA-F:
The only discrepancy - which is fatal to the software working - that I
have
seen thus far, is that the developers have changed the prompt line,
which I
use to detect when output from the device has finished. Being able to
detect either prompt might make it work, or there might be other
differences. ¡¡.
--------------------------------------------------------------------------------------------------------------------
Rune,
The NanoVNA-F v0.0.3 2019-10-07 firmware was updated per your "prompt
line" observation. From the developer, to quote:
"I think the most suitable command prompt for NanoVNA products should be
"nanovna> ", not "ch> "(which means ChibiOS).
However, in order to be compatible with the existing PC software, we temporarily choose to compromise."
The GitHub page now lists supported software as: NanoVNASharp v1.0.3(by
Hugen), nanoVNA_mod_v2(by alex_m), and nanovna-saver(by Rune B. Broberg).
Herb
|
I can't communicate with the developers.
|
Re: Latest edy555 firmware release with dfu file
Hello Larry,
I tried to flash your provided file edy-0.2.3-oct-7-19.dfu
under MacOS with the program dfu-util (Ver. 0.9), which I have used before.
I have learned from the manual, that the USB product ID should be "df11".
Unfortunately in your provided file the USB Product ID was 0,
so it coud not be programmed. See error:
dfu-util: Error: File ID 0483:0000 does not match device (0483:df11 or 0483:df11)
Next I have taken the .hex file under Windows 10 and program DfuFileMgr.exe
to add the Provider ID "df11".
Then I could flash in the Terminal:
$ dfu-util -v -d 0483:df11 --alt 0 -D nanoVNA_0.2.3-ch.dfu
I have appended to file nanoVNA_0.2.3-ch.dfu
73, Rudi
|
Locked
Inflation of this forum
The forum was highly informative at the beginning. Thanks to the initiators.
But there are no moderators to separate the wheat from the chaff.
Meaningless comments and constant repetitions are the order of the day. It is extremely difficult to find an important message under this flood. It is simply no longer fun to read along here. The abuse in the form of exaggerated, bloated advertising lines has not been prevented.
I appeal to you, the users, to consider whether your contribution is really necessary and important.
73, Wolfgang, DH1AKF
|
Re: Annotated nanoVNA menu diagram
I lost sleep last night, pondering Stan's suggestion for CSS changes
which may result in overall cleaner (if not smaller) diagrams.
|
Rune, a little idea to make the software compatible to the new and
old prompt (as some still use older firmware) would be to make a
"check" when first connecting to the device and read the prompt and
use that one in the reste of the software..
But I am sure it was already what you wanted to do. ;-)
toggle quoted message
Show quoted text
Le lun. 7 oct. 2019 ¨¤ 12:55, hwalker <herbwalker2476@...> a ¨¦crit :
[Edited Message Follows]
On Sun, Oct 6, 2019 at 02:26 PM, Rune Broberg wrote regarding NanoVNA-F:
The only discrepancy - which is fatal to the software working - that I have
seen thus far, is that the developers have changed the prompt line, which I
use to detect when output from the device has finished. Being able to
detect either prompt might make it work, or there might be other
differences. ¡¡. --------------------------------------------------------------------------------------------------------------------
Rune,
The NanoVNA-F v0.0.3 2019-10-07 firmware was updated per your "prompt line" observation. From the developer, to quote:
"I think the most suitable command prompt for NanoVNA products should be "nanovna> ", not "ch> "(which means ChibiOS).
However, in order to be compatible with the existing PC software, we temporarily choose to compromise."
The GitHub page now lists supported software as: NanoVNASharp v1.0.3(by Hugen), nanoVNA_mod_v2(by alex_m), and nanovna-saver(by Rune B. Broberg).
Herb
|
On Sun, Oct 6, 2019 at 02:26 PM, Rune Broberg wrote regarding NanoVNA-F: The only discrepancy - which is fatal to the software working - that I have
seen thus far, is that the developers have changed the prompt line, which I
use to detect when output from the device has finished. Being able to
detect either prompt might make it work, or there might be other
differences. ¡¡. -------------------------------------------------------------------------------------------------------------------- Rune, The NanoVNA-F v0.0.3 2019-10-07 firmware was updated per your "prompt line" observation. From the developer, to quote: "I think the most suitable command prompt for NanoVNA products should be "nanovna> ", not "ch> "(which means ChibiOS). However, in order to be compatible with the existing PC software, we temporarily choose to compromise." The GitHub page now lists supported software as: NanoVNASharp v1.0.3(by Hugen), nanoVNA_mod_v2(by alex_m), and nanovna-saver(by Rune B. Broberg). Herb
|
Re: Command to set maximum fundamental SI5351 frequency implemented
I used edy555's in between release gihub repository, sorry to see it was not stable
Will rebuild with the officiel 2.3 release
Only delta in my version of 2.3 will be the scan command.
|
Re: errors of "error" models
Hello again nikolitsa oe3zgn|sv7dmc & petros oe3zzp|sv7bax @ arg iaoi nfi;
In your expanded definition, you state:
¡° g) does not provide its user with the means to complete his
measurements because it ignores the uncertainty of these
three 3 "standards" and the inaccuracy of these 8 = 4 x 2
¾±²Ô»å¾±³¦²¹³Ù¾±´Ç²Ô²õ.¡±
To be clear on this, and thus my concern for an unambiguous understanding of your approach; this comment raises my concern that you may be contaminating your conclusions due to a potential oversight on your part.
There is a conditional but important (firmware/software) difference that distinguishes the NanoVNA. This difference is my motivation to discuss hardware and firmware/software independently as an assurance that we are playing the same instrument, and hearing the same music. I am curious how that metaphor translates. :-)
The NanoVNA, as with any VNA, outputs results that have been normalized to the measuring equipment environment (offsets and ranges) and then calibrated to a set of fixed standards. The NanoVNA however does not attempt to correct for the characterized uncertainties of the standards, but rather assumes them to be ideal as measured. The key and very important difference is the characterization, and this is what traditionally is employed to offset and thereby minimize and bound the measurement uncertainties to a high tolerance in any (critically used) VNA. While purists will argue (with valid rationale) that the task requires precisely constructed standards devices; short of the normal high quality associated with stability and repeat ability, the task is principally computational.
I will need further clarification if I am remiss in my understanding of the role of the calibration standard uncertainties as a prerequisite requirement beyond their measured values taken as nominal. FACUPOV, where the Common User is a hobbyist that possesses a $50 instrument and perceives it as a fun new toy; most NanoVNAs will never be graced with such fine jewelry.
We are in total agreements on all of your remaining points.
--
73
Gary, N3GO
|
gin&pez@arg
Oristo
Wolfgang Kiefer