1. I used this ancient v.0.1.0 sw. version because on github this release was offered. I used it as it was. I didn't modify anything, no coefficients or other settings (except dot/comma in default.set). I suggest that the data format and protocol should work, as without cal the sw. works.
When I posted "You never show a screen shot of the calibration terms. " I thought you would take the hint. Without providing details of what you're seeing, I have no way of helping you. Something is certainly causing a divide by zero. I can tell you it's nothing I have ever ran into.
Without my having the same hardware with the same firmware installed, I have no idea if your VNA would actually work or not. I tell people what hardware and firmware I test with. If you choose to deviate from that, you're setting yourself up for failure.
2. The default.set file is the v.0.1.0 version, as all my problems aroused originally there. Having the problem, I tried to find a new version and found the new v0.2.8 exe in your zip file and believed that it is enough to replace it. I didn't realize that for other versions I should replace the default.set, too. I will search for all the components (default.set and sound.dll as you mentioned). If I got a complete package, I would install it from scratch. Perhaps a remark on the github page can orient other people, also.
You had posted about reading the manual so you already know, it's up to you to create the defaults file based on your setup. This isn't something I would supply you and if I did, it's most likely not going to be correct.
The current released software is 3.13. If you followed the link in my signature, you would see where the new releases are for the LiteVNA and V2Plus4. If your VNA is compatible with that protocol, this is the software you should be using. It will require new defaults and calibrations and of course, that troublesome Sound file. Moving forward with these low cost VNAs, this is the only version of the software I plan to support as it's the only one a still actively use.
3. I am only a curious software engineer extending my home automation system and trying to solve the 433 MHz communication problems of sensors with terrible antennas. Your YouTube videos with full of details and knowledge impressed me so, that I thought that using this necessity I would learn a bit about the interesting RF world that is a terra incognita for me. Your sw. has much more potential compared to vna_qt I had tried.
I suspect it will be a steep learning curve for you which is why I suggest using one of the more generic open sourced programs. You could waste a lot of time and not reach what ever your goals are. Because I received so many basic questions covered in the manual, I stopped wasting time updating it. For people like yourself who are actually trying to make us of the documentation, this doesn't help matters. You would need to watch the videos where I cover the changes or like many, trial and error your way along. Things seldom work out for the random button pushers.
4. Sorry, if I caused some annoyance, I understand that it is a challenge to solve the (repetitive) problems of noobs, like me.
As long as you understand that there isn't an Act in the USA called "No VNA User Left Behind". If you read this long thread you will find people who feel that just because there are several other who post about their woes, I should lower my expectations and change what I provide to help them. I've been clear my software isn't a good choice for the beginner. Think of it as being a few decades of experiments (not antenna tuning) that I have conducted at home and compiled into one program. Just because a user can afford a sub $200 VNA isn't going to make them any more knowledgeable on how to use it and my goal isn't to educate those unwilling to do their own research.
Of course, the flip side to that is I have made some pretty major changes to the software for the few people that have taken the time to learn how to use it and putting it to use.
***
poor grammar
Home
Help
Search
Login
Register
