|
The other thread was getting long, and seemed to have branched a lot, so as
a new one: I just released NanoVNASaver 0.0.8. It now saves settings, and has continuous from the NanoVNA, both as single spans of 101 points, or across multiple spans if you want both high resolution and continuous updates. There's a few other improvements as well - I started work on a quality factor graph, as someone had requested that. There's a .exe for Windows, and for other platforms (Mac OS, Linux, BSD(?)), run it using pip/python, described in the README. I welcome all feedback, bug reports and suggestions! -- Rune / 5Q5R |
|
Great job Rune and thank you for this excellent software!
I am running on Mac OSX and the QLineEdit boxes are white on white text. I can highlight the contents and see the text. I set the text color to black in NanoVNASaver.py and that seems to work but I'm not sure if it's only happening to me or why it's happening. It may have something to do with Mojave Dark Mode. Anyone else seeing this? Thanks again, Gene KJ4M |
|
I've certainly not seen it before - I think it might well be a "Dark Mode"
toggle quoted message
Show quoted text
thing changing default font look. I haven't done anything in particular to force the backgrounds to be white, but it is the default when not running any theme, I believe. If anyone who has a Mac, access to these themes, and knows how to code Python & PyQT5, comes across a fix - do let me know ;-) Otherwise, I'll try to see what I can find out on my own. I may write to you later, Gene, if I think I find a fix - I hope you will be up for testing it. -- Rune / 5Q5R On Tue, 10 Sep 2019 at 23:44, Gene Eighmy <kj4m@...> wrote:
Great job Rune and thank you for this excellent software! |
|
Hi Gene,
toggle quoted message
Show quoted text
I'm always open to suggestions for improvements, including code - either by email (mihtjel@gmailcom) or as "pull requests" to the GitHub repository. :-) Thanks! -- Rune / 5Q5R On Wed, 11 Sep 2019 at 02:55, Gene Eighmy <kj4m@...> wrote:
Hi Rune, |
|
It's Friday, and that apparently means NanoVNA-Saver 0.0.9:
This edition has focused a lot on the markers: You can now pick which marker to control using the mouse by radio buttons; and if you hold shift, you can drag around the nearest marker on the charts. The markers have their own data readout panel, which can be hidden, if you want more room to marvel at the charts. They also now have more data display options, including Q and parallel equivalent R and C/L. Additionally, when you enter a marker frequency manually, the markers are updated immediately, without needing to press enter. Sweep controls now include a center/span option, and both start/end and center/span update the other fields as you update them. Some of the TDR functionality has been moved to a separate window (selecting cable types), and now also shows a graph of response vs distance. An icon was added, and in the true tradition of VNA software, it features a Smith chart. Of course. Lastly, support for high-resolution monitors was improved. Feedback, suggestions and bug reports welcome as always! This list has provided a lot of good suggestions already, and while I know I'm probably disappointing some of you by not having gotten your changes in yet, I promise I'm still working on the app, and you should definitely feel free to send me an email if you want to help out. We have a Discord server for anyone who's so into this app, they want to hang out on Discord with us (?). Send me an email if you want the invite. -- Rune / 5Q5R On Tue, 10 Sep 2019 at 20:56, Rune Broberg via Groups.Io <mihtjel= [email protected]> wrote: The other thread was getting long, and seemed to have branched a lot, so as |
|
Hello Rune,
thank you for your work. I had trouble with the calibration Routine. Doing the calibration procedure for open, short, match, isolation and trough and save the results. i can recall them but in the command window i get following message: "Division error - did you use the same measurement for two of short, open and load?". any idea? 73 Holger, DF6DBF |
|
Hi Holger,
toggle quoted message
Show quoted text
For each of the standards, you first need to sweep them in the main window, then press the corresponding button in the calibration window. This allows some more control over what area you are doing the calibration for. (though I should really integrate that better) If you already did that, then you may have found a bug! Please let me know if my suggestion doesn't work :-) -- Rune / 5Q5R On Fri, 13 Sep 2019 at 17:48, <df6dbf@...> wrote:
Hello Rune, |
|
Herb, I blush. Thank you very much for your appreciation :-)
toggle quoted message
Show quoted text
-- Rune / 5Q5R On Fri, 13 Sep 2019 at 17:45, hwalker <herbwalker2476@...> wrote:
Rune, |
|
Hello Rune,
Thank you very much for the lot of useful extensions in version 0.0.9. I have tried the Calibration and have a problem with it: 1. When I start the program nanoVNA-saver.py which calibration is used, or none? 2. If I load my saved calibration file and start a sweep I get a divide by 0 error: Settings: /Volumes/DAT/Users/rudi/.config/NanoVNASaver/NanoVNASaver.ini Traceback (most recent call last): File "/Volumes/DAT/HDA8/INSTALL/Develop/Afu/NanoVNA/nanovna-saver-009/NanoVNASaver/SweepWorker.py", line 87, in run self.saveData(frequencies, values, values12) File "/Volumes/DAT/HDA8/INSTALL/Develop/Afu/NanoVNA/nanovna-saver-009/NanoVNASaver/SweepWorker.py", line 150, in saveData re21, im21 = self.app.calibration.correct21(re21, im21, freq) File "/Volumes/DAT/HDA8/INSTALL/Develop/Afu/NanoVNA/nanovna-saver-009/NanoVNASaver/Calibration.py", line 375, in correct21 s21 = (s21m - self.e30[index]) / self.e10e32[index] ZeroDivisionError: complex division by zero Abort trap: 6 How can I avoid it? 73, Rudi |
|
Rune,
Thanks for the update it makes the VNA more useful every day. Would it be possible to enter the start and stop frequencies as Megahertz instead of Hz. Its a lot of zeros to enter. Perhaps we could have a drop down box or radio button so as to enter MHz, KHz or Hz. It would save the chance of entering too many or not enough 0's David |
|
Hi David,
toggle quoted message
Show quoted text
If you suffix a number entered with k or M, it will be interpreted as kHz or MHz. :-) The other set of fields automatically updated will be in Hz, though. -- Rune / 5Q5R On Sat, 14 Sep 2019, 07:07 David Hopkins, <davhop@...> wrote:
Rune, |
|
Hello Rudi,
toggle quoted message
Show quoted text
when you start the program, it initially uses only the device calibration - that is, from the application point of view, it displays uncalibrated readings. I am sorry to see the crash you experienced - if you would send me the calibration file you have saved (either on the list, or direct to mihtjel@... ) I will try to reproduce and fix the problem as quickly as possible. Thank you for trying out the software, and for taking the time to report the problems you find! -- Rune / 5Q5R On Sat, 14 Sep 2019 at 06:17, <reuterr@...> wrote:
Hello Rune, |
|
From: Rune Broberg
It's Friday, and that apparently means NanoVNA-Saver 0.0.9: ======================= Rune, Trying with the new 10k-1500M firmware. If the start frequency is set to lower than 50000 (I tried 10000 and 40000) the program shows an hourglass timer and then simply aborts, taking the command script with it. Difficult to keep up, I appreciate! Cheers, David -- SatSignal Software - Quality software for you Web: Email: david-taylor@... Twitter: @gm8arv |
|
Yes, I've heard someone else mention that. I can't quite think what causes
it, *assuming* the firmware didn't change the format of the commands used. I currently just have the one NanoVNA, and as I need to use it for development, I have been a bit reluctant to flash experimental firmware on it. I may have to try :-) -- Rune / 5Q5R On Sat, 14 Sep 2019, 11:13 David J Taylor via Groups.Io, <gm8arv= [email protected]> wrote: From: Rune Broberg |
|
Yes, I've heard someone else mention that. I can't quite think what causes
it, *assuming* the firmware didn't change the format of the commands used. I currently just have the one NanoVNA, and as I need to use it for development, I have been a bit reluctant to flash experimental firmware on it. I may have to try :-) Rune / 5Q5R ===================================== Yes, I also have just the one, and that was the first time I'd flashed new firmware. I was hoping that getting back to a known working version wouldn't be too difficult if I did need to do that! The flashing is very quick. 73, David GM8ARV -- SatSignal Software - Quality software for you Web: Email: david-taylor@... Twitter: @gm8arv |
|
For those who have previously had problems with using newer 10k-1500M
firmwares with NanoVNA-Saver (or other crash issues): On GitHub, the latest version of the master branch now has a debug function: Use the command line option '-d' to see debug info, and '-D filename.log' to save debug info to a file, which you can send to me if you see crashes. This should help me be able to find out what's going wrong when you see these crashes. It will also be included in the next release, including in the Windows .exe, which will be out this week, maybe tomorrow. Thanks, -- Rune / 5Q5R On Sat, 14 Sep 2019 at 11:45, David J Taylor via Groups.Io <gm8arv= [email protected]> wrote: Yes, I've heard someone else mention that. I can't quite think what causes |
|
Rune where can I find the 1500 mhz code?
toggle quoted message
Show quoted text
Thx 73 Dana VE3DS On Sep 17, 2019, at 06:15, Rune Broberg <mihtjel@...> wrote:
For those who have previously had problems with using newer 10k-1500M firmwares with NanoVNA-Saver (or other crash issues): On GitHub, the latest version of the master branch now has a debug function: Use the command line option '-d' to see debug info, and '-D filename.log' to save debug info to a file, which you can send to me if you see crashes. This should help me be able to find out what's going wrong when you see these crashes. It will also be included in the next release, including in the Windows .exe, which will be out this week, maybe tomorrow. Thanks, -- Rune / 5Q5R On Sat, 14 Sep 2019 at 11:45, David J Taylor via Groups.Io <gm8arv= [email protected]> wrote: Yes, I've heard someone else mention that. I can't quite think what causes |
Gene Eighmy
David J Taylor