Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Nanovna-Users
- Messages
Search
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: NanoVNA-Saver 0.0.12
Pierre Martel
Rune, a little idea to make the software compatible to the new and
toggle quoted message
Show quoted text
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 :
|
Re: NanoVNA-Saver 0.0.12
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-------------------------------------------------------------------------------------------------------------------- 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: 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 |
Re: Are there any firmware releases supporting calibration kits?
Dr. David Kirkby from Kirkby Microwave Ltd
On Mon, 7 Oct 2019 at 16:36, <erik@...> wrote:
Adding setting the three parametersThat would be useful. Note for many of the kits, the male and female components have different parameters. Could there be a few user-defined kits? In an ideal world, a few of the common calibration kits owned by several members on this list (85032B, 85033D/E), as well as a few user-defined ones. I have * 85050B APC7 * 85032B 3.5 mm * 85054B N * 85038A 7-16 * 85039B (75 ohm, type F) *None of those are popular,* so I would not suggest they need to be in the firmware. Depending on memory/space on the screen, the 85052B / 85052D would be nice to have on the menu, but those use exactly the same coefficients as the 85033D and 85033E. As strange as it may seem, the 85039A and 85039B type F 75 ohm kits seem quite popular on eBay. The whole idea of a VNA calibration kit for the F connector strokes me as a bit odd, but there does seem to be a lot of them sold. But being 75 ohm, supporting them would no doubt need changes in several places, and I can't imagine many NanoVNA users wanting to test devices with F connectors on them. A few user-defined kits, ideally which one can name, but if not CALKIT 0, CALKIT 1 etc would be fine. Dave -- Dr David Kirkby Ph.D C.Eng MIET Kirkby Microwave Ltd Registered office: Stokes Hall Lodge, Burnham Rd, Althorne, CHELMSFORD, Essex, CM3 6DT, United Kingdom. Registered in England and Wales as company number 08914892 Tel 01621-680100 / +44 1621-680100 |
Re: Command to set maximum fundamental SI5351 frequency implemented
edy555's 0.2.3 release does NOT lock-up with the capture command.
toggle quoted message
Show quoted text
When I run capture from the command prompt, I get a 2 page dump of non-printing output to the terminal, then I get the ch> prompt back I assume it's a binary display buffer dump. The attached file is my teraterm terminal.tty dump:? in console, I hit return twice, then version, then info, then capture, then exit On Monday, October 7, 2019, 11:37:49 a.m. GMT-4, <erik@...> wrote:
@Larry Can you try the edy555 0.2.3 release and see if that also locks up on capture? |
Re: Are there any firmware releases supporting calibration kits?
Can someone specify how these should be added to the calibration correction calculation?
This is the current code where "measured" is the raw data that gets corrected void apply_error_term_at(int i) { // S11m' = S11m - Ed // S11a = S11m' / (Er + Es S11m') float s11mr = measured[0][i][0] - cal_data[ETERM_ED][i][0]; float s11mi = measured[0][i][1] - cal_data[ETERM_ED][i][1]; float err = cal_data[ETERM_ER][i][0] + s11mr * cal_data[ETERM_ES][i][0] - s11mi * cal_data[ETERM_ES][i][1]; float eri = cal_data[ETERM_ER][i][1] + s11mr * cal_data[ETERM_ES][i][1] + s11mi * cal_data[ETERM_ES][i][0]; float sq = err*err + eri*eri; float s11ar = (s11mr * err + s11mi * eri) / sq; float s11ai = (s11mi * err - s11mr * eri) / sq; measured[0][i][0] = s11ar; measured[0][i][1] = s11ai; // CAUTION: Et is inverted for efficiency // S21m' = S21m - Ex // S21a = S21m' (1-EsS11a)Et float s21mr = measured[1][i][0] - cal_data[ETERM_EX][i][0]; float s21mi = measured[1][i][1] - cal_data[ETERM_EX][i][1]; float esr = 1 - (cal_data[ETERM_ES][i][0] * s11ar - cal_data[ETERM_ES][i][1] * s11ai); float esi = - (cal_data[ETERM_ES][i][1] * s11ar + cal_data[ETERM_ES][i][0] * s11ai); float etr = esr * cal_data[ETERM_ET][i][0] - esi * cal_data[ETERM_ET][i][1]; float eti = esr * cal_data[ETERM_ET][i][1] + esi * cal_data[ETERM_ET][i][0]; float s21ar = s21mr * etr - s21mi * eti; float s21ai = s21mi * etr + s21mr * eti; measured[1][i][0] = s21ar; measured[1][i][1] = s21ai; } Adding setting the three parameters * offset delay of the open * offset delay of the short. * C0 of the open and saving them as part of a config or calibration dataset I know how to do |
Re: Latest edy555 firmware release with dfu file
Seems to work well.
One small request - Could the velocity factor that has been used please be added to the TDR marker text, or displayed in some other way, so that it's more obvious if you have used the wrong value for the type of cable being measured. Regards, Martin - G8JNJ |
Latest edy555 firmware release with dfu file
Hot off the presses, folks:
Version 0.2.3 edy555 released this 1 hour ago -change toggle behavior of trace menu and marker menu -add transform command to change mode of TDR - add threadshold command -remove cal glitch between different harmonic modes -NanoVNA-saver in multisegment mode shall work well ** Needs touch calibration and save it after flashing firmware. Regards, Larry |
File updated in [email protected]
[email protected] Notification
Hello, This email message is a notification to let you know that the following files have been updated in the Files area of the [email protected] group. Uploaded By: Larry Rothman <nlroth@...> Description: Cheers, |
Are there any firmware releases supporting calibration kits?
Dr. David Kirkby from Kirkby Microwave Ltd
Are there any *firmware* releases that have support for *proper*
calibration kits? By that I minimum of * offset delay of the open * offset delay of the short. * C0 of the open More parameters would be useful, especially of lower quality kits, but the above would be a start Dave -- 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: Inductor S21 measurement using nanoVNA
On Mon, Oct 7, 2019 at 04:03 AM, Kurt Poulsen wrote:
Kurt, Thanks for your more detailed explanation. I think I understand the "trick" you are suggesting more thoroughly. It certainly makes a difference if you want to more precisely characterize the 13 micro-Henry inductor at higher frequencies like 30 MHz to 100 MHz. -- Bryan, WA5VAH
|
Re: Command to set maximum fundamental SI5351 frequency implemented
Erik,
toggle quoted message
Show quoted text
Your release 0.2.2_1 may have a bug with the 'capture' console command - device locks-up when I try to use capture. Regards, Larry On Saturday, October 5, 2019, 4:01:44 p.m. GMT-4, <erik@...> wrote:
Edy555 has implemented in his GitHub nanoVNA repository a command to set the threshold for switching to harmonics mode Command threshold {Frequency in Hz} The default is 300MHz. After changing you can use the save configuration command to permanently store the new value This greatly simplifies testing if your SI5351 has difficult reaching 300MHz and if so, provides a easy workaround I can not test now. Maybe tomorrow |
Re: errors of "error" models
Good afternoon nikolitsa oe3zgn|sv7dmc & petros oe3zzp|sv7bax @ arg iaoi nfi;
As I stated in an earlier post, our communications get somewhat contaminated in translation. Please understand that you have my unreserved agreement on your definition. My use of quotation marks encompassing any... i.e. ¡°any¡± VNA was intended to communicate that I am not all knowing with respect to the architectural differences employed by various equipment manufacturers. In the context of our discussions, I also believe that the hardware choice is not relevant, and that it is your desire to focus on the software independent of the hardware choice in the evaluation of the derived measurement uncertainties. My overtly verbose description was an attempt to separate the hardware from the software, to ensure my understanding of the point that the hardware employed for the measurements is irrelevant. I have not yet read your response in its entirety. I sensed a priority to put your mind at ease, and respond immediately in that regard. I will comment on anything I feel unclear about your response after giving it my undivided attention. 73 Gary, N3GO agreement -- 73 Gary, N3GO |
to navigate to use esc to dismiss