Simple (dB/m) and advanced (k parameters) coaxial cable modell exist.
|
Does not fully understand this forum. Cable loss compensated? I see big errors from cable loss. Lossy coaxial line not circle on smith diagram. It s a spiral. I see electrical lenght compensated, but loss not.
|
Re: Looking for firmware with battery indicator, 1500 and big font
Thank you,
Just flashing using latest AA version from
2 traces is enaough for me.
|
Port 1 mismatch is already corrected for by the usual SOL 3 term calibration. The only things left that it *doesn't* correct for are linearity error (e.g. signal source's output power changing depending on DUT impedance in a nonlinear way) and side channels. In this case we have two nearly identical impedances (the open circuit standard vs the cable's impedance which crosses the open circuit point) that measure wildly differently, so the most likely explanation is side channels (other things that are different about the two DUTs other than the impedance at the measured frequency), which one of them is the DUT's impedance at f/3. The solution is, of course, don't use harmonic mode ;)
|
Re: Voltage sensing diode
No problem, we're all here to help each other.?
On Wed, 6 Nov 2019 at 7:05 PM, QRP RX<qrp.ddc@...> wrote: Larry Rothman, sorry. I opened groups.io, found question which I seen in email and wrote answer. Just didn't noticed that I replied on your answer :)
|
Re: NanoVNA software developers wanted
#hacking
Just FYI and to keep with the original post.
I have manged to extract multiple "projects" from simply cloning the original Github repository.
So part of the goal is done.
Now I have to figure out which of the multitude of C projects is the chief.
I can add a new file, using plain "project" perspective - which is a step up.
There seems to be some test / emulation code projects too.
As far as RFI from Bluetooth hardware - will cross that river when I get there,
Still looking for software partner(s).
|
Re: NanoVNASaver QT Platform problem (won't load)
I tried to create V 0.1.5 for my mac, OS version is Catalina.
I got an error message trying to install scipy¡
I think scipy was new for v0.1.5?
Has anyone else encountered this?
Dana VE3DS
toggle quoted message
Show quoted text
On Nov 6, 2019, at 16:59, Rune Broberg <mihtjel@...> wrote: Hi Doug, as others have indicated, I build NanoVNA-Saver executables using the very oldest build environment I can get from Microsoft - namely Windows 7 32 bit. Mainstream support for Windows Vista ended 7? years ago, and extended support 2? years ago. It might still be possible to run NanoVNA-Saver on Windows Vista by installing Python 3.7, and the modules PyQt5 5.11 or newer, pyserial, numpy and scipy. Then run it from the Python source available on GitHub. It might even be possible to build compatible executables - but I personally have no way to do that, nor to test on Windows Vista. I hope you find a good solution for your setup! -- Rune / 5Q5R On Wed, 6 Nov 2019 at 18:38, DougVL <K8RFTradio@...> wrote: I've tried NanoVNASaver v0.1.3 and v0.1.4 but they will not start. I get
a DOS window with the error message:
"Could not load the Qt platform plugin "Windows" in "" even though it was
found.
This application failed to start because no Qt platform plugin could be
initialized. Reinstalling the application may fix this problem.
Available platform plugins are: minimal, offscreen, webg1, windows."
Reinstalling NanoVNASaver (either version) did not fix the problem.
My PC runs Windows Vista with all available updates made. I suspect this
may be the problem, but no newer operating system is available for this
computer.
Is there any known solution to not loading the Qt platform?
NanoVNA Sharp works well, though.
Thanks,
Doug, K8RFT
|
Re: Voltage sensing diode
Larry Rothman, sorry. I opened groups.io, found question which I seen in email and wrote answer. Just didn't noticed that I replied on your answer :)
|
Re: Voltage sensing diode
QRP, that is not my quote, below - that is from the other member whom I already explained what you just did as well....? On Wed, 6 Nov 2019 at 6:54 PM, QRP RX<qrp.ddc@...> wrote: On Thu, Nov? 7, 2019 at 01:41 AM, Larry Rothman wrote:
I don't know where I can enter vbat_offset.
Can anyone "lead my hand"?
just connect to your NanoVNA with PuTTY and use command "vbat_offset" This command will change battery offset until power off. In order to save current battery offset permanently, use command "saveconfig"
|
Re: Voltage sensing diode
On Thu, Nov 7, 2019 at 01:41 AM, Larry Rothman wrote:
I don't know where I can enter vbat_offset.
Can anyone "lead my hand"?
just connect to your NanoVNA with PuTTY and use command "vbat_offset" This command will change battery offset until power off. In order to save current battery offset permanently, use command "saveconfig"
|
Re: Voltage sensing diode
You need to connect the Nano to a terminal session on a PC and use the console command vbat_offset [xxxx ] where xxxx is mV of offset.? On Wed, 6 Nov 2019 at 4:37 PM, Zbigniew Olszanowski<zbigniew.olszanowski@...> wrote: On Wed, Nov? 6, 2019 at 06:41 AM, Nick wrote:
With BAV99 2 diodes and a fully charged battery set vbat_offset to 1000
and
VBAT reads 4210mV on Version screen.
Just calibrated by setting vbat_offset so that the indicated voltage on the
Version screen = measured battery voltage.
Fully charged reading (LED1 not blinking) now 4140mV with vbat_offset set to
950.
Estimated error +/-1%.
The on screen charge indicator works well as the battery runs down.
VBAT now < 3.7V under all charge conditions. Within Absolute maximum rating
spec of 4.0V.
Looking at the Fairchild data sheet a pair of 1N4148 should give similar
results.
Hi, Now I have a VBAT: 4024mV, and measured after the diode: 3963mV. I don't know where I can enter vbat_offset. Can anyone "lead my hand"?
|
Hi Bryan, thanks for the Touchstone files - I'll have a look at them, and see if I can figure out what's going on. :-) -- Rune / 5Q5R On Wed, 6 Nov 2019 at 20:21, bryburns via Groups.Io <bryburns= [email protected]> wrote: On Wed, Nov 6, 2019 at 01:16 AM, Rune Broberg wrote:
Have you set the NanoVNA to normal (non-TDR) mode before making the
readings?
If you would be willing to send me a Touchstone file of the data, that
would be helpful for testing! :-)
Rune,
Yes, I did set the nanoVNA to non-TDR mode before making the readings.
This is essential to getting good data in nanoVNA-Saver from the nanoVNA.
I recalled cal0 which was created with my best SMA calibrators (from
another VNA) on short male-female connector savers attached directly to the
nanoVNA.
Attached is an S1P file from the ~0.5m long RG316. I also have attached
an S1P file from the ~1 m long 75 ohm cable that you can use for testing
with nanoVNA-Saver 0.1.5. Using the velocity factor for RG316 as 0.695
give a length of 0.56 m for that cable. Setting the velocity factor for the
75 ohm cable to 0.66 yields a cable length of 1.086 m. The cables are
showing a little longer than the measured length because of some 50 ohm
adapters that are about a total of 2" long on the nanoVNA end of the
cables. These are the same cables I used in the nanoVNA screen shots shown
above.
Both cable measurements were made using my best nanoVNA calibration and
the best tuned nanoVNA-Saver calibration.
I hope these help your efforts with the TDR software to show the impedance
vs time.
--
Bryan, WA5VAH
|
Re: NanoVNASaver QT Platform problem (won't load)
Hi Doug,
as others have indicated, I build NanoVNA-Saver executables using the very
oldest build environment I can get from Microsoft - namely Windows 7 32 bit.
Mainstream support for Windows Vista ended 7? years ago, and extended
support 2? years ago.
It might still be possible to run NanoVNA-Saver on Windows Vista by
installing Python 3.7, and the modules PyQt5 5.11 or newer, pyserial, numpy
and scipy. Then run it from the Python source available on GitHub. It
might even be possible to build compatible executables - but I personally
have no way to do that, nor to test on Windows Vista.
I hope you find a good solution for your setup!
--
Rune / 5Q5R
toggle quoted message
Show quoted text
On Wed, 6 Nov 2019 at 18:38, DougVL <K8RFTradio@...> wrote: I've tried NanoVNASaver v0.1.3 and v0.1.4 but they will not start. I get
a DOS window with the error message:
"Could not load the Qt platform plugin "Windows" in "" even though it was
found.
This application failed to start because no Qt platform plugin could be
initialized. Reinstalling the application may fix this problem.
Available platform plugins are: minimal, offscreen, webg1, windows."
Reinstalling NanoVNASaver (either version) did not fix the problem.
My PC runs Windows Vista with all available updates made. I suspect this
may be the problem, but no newer operating system is available for this
computer.
Is there any known solution to not loading the Qt platform?
NanoVNA Sharp works well, though.
Thanks,
Doug, K8RFT
|
Re: Voltage sensing diode
On Wed, Nov 6, 2019 at 06:41 AM, Nick wrote:
With BAV99 2 diodes and a fully charged battery set vbat_offset to 1000
and
VBAT reads 4210mV on Version screen.
Just calibrated by setting vbat_offset so that the indicated voltage on the
Version screen = measured battery voltage.
Fully charged reading (LED1 not blinking) now 4140mV with vbat_offset set to
950.
Estimated error +/-1%.
The on screen charge indicator works well as the battery runs down.
VBAT now < 3.7V under all charge conditions. Within Absolute maximum rating
spec of 4.0V.
Looking at the Fairchild data sheet a pair of 1N4148 should give similar
results.
Hi, Now I have a VBAT: 4024mV, and measured after the diode: 3963mV. I don't know where I can enter vbat_offset. Can anyone "lead my hand"?
|
The resistance is a bit of and there is some capacitance How would that error impact your other VNA?
|
I did.
The resistance is a bit of and there is some capacitance. Do you suggest to add that capacitance to the cable? But that capacitance is already there in the open calibration? I'm not quick in understanding this....
--
Erik, PD0EK
|
They must be specific for the design of the nanoVNA How about measuring CH0 impedance by another VNA?
|
I already did
The same cables measured in the same way at another vna do not show these oscillations. Even though the same calibration kit calibrated perfect on both vna's. They must be specific for the design of the nanoVNA
--
Erik, PD0EK
|
The oscillation seems to be faster then the rotation speed from the cable
length so there could be some capacitive factor involved. Using the open for calibration also at the end of cables could eliminate one variable.
|
Re: NanoVNASaver QT Platform problem (won't load)
on the other end of the "scale" ..someone gifted me a HP Stream (2018 model) ...running Linux Mint 19.1 ..has more than 10 g freespace left on solid-state fixed drive
(if you don't want to mess with your current device) ...approx $200 on amazon
Jim
toggle quoted message
Show quoted text
On Wednesday, November 6, 2019, 7:25:55 PM UTC, Jim Allyn - N7JA <jim@...> wrote: On 11/6/19 9:38 AM, DougVL wrote: My PC runs Windows Vista with all available updates made.? I suspect this may be the problem, but no newer operating system is available for this computer. ???? Yes, there is a newer operating system available for your computer:? Linux.? Windows Vista is out of support and no longer updated, so, if you continue to use it, at a minimum you should keep it off the internet.? I have updated many older computers running Vista, XP (and even earlier versions) to Linux.? A common comment from the owners of those computers is, "Wow, this is faster than it ever was, even when it was new!"? Linux is a great way to breathe new life into older computers.? Something to think about, anyway.? If you want more information on using Linux on our old computer, you can email me off-list. ????????????????????????????????????????????? Jim, N7JA
|
OwO
Oristo