开云体育

@ Peter I0YLI hello peter, the merit is all who wrote the program, who designed the nanoVNA, the developers .. We, as users, try to give the most correct feedback possible. @All I confirm that the

OH I did not see you asked me a question, Sorry, no it did no work for me, I tried that and it did not start, ha, you woke me up. Thanks Nels wrote: -- n_n

It does not work on a fresh install of Mint 19.3 Cinnamon I did notice that the WIKI no longer claims to be multi platform but it states it will work with Linux SuSE , and you know I will go find out.

No problem, Leif. Have a look at my translated user guide in addition to the slides in the Presentation folder and also search the Wili and forum messages for Gunther's (spelling?) And Rudi's user

I didn't even look at the transform menu. I just updated from 0.0.0, so this is all new to me. I have been wondering how a signal generator inside Nano generates short pulses for TDR, but it looks now

I just signed on to report the same thing.. I had set my start and stop 144.0000Mhz to 148.000 and 2 sweeps... it exited and I couldn't read what was in the DOS BOX Treid to do a calibrate ---same

I often do a fresh install in VirtualBox for things like that.

Oops - wrong menu in prev mesg. From the NnoVNA User manual I edit (in the files section): Time domain operation The NanoVNA can simulate time domain measurements by signal processing frequency domain

Why do you have a 1000ps delay? It appears you're not in the TDR mode as I see frequency values at the bottom of the display. If you get good results from NanovnaSaver, it's not the device. Remember

I can confirm, I cannot get a good TDR result from NanoVna now.

This seemed to work for me... $ sudo python3.7 -m pip --no-cache-dir install . Processing /home/nick/nanovna-saver-0.2.2 Requirement already satisfied: PyQt5 in

There are now several new features. One seems to be scale for the delay. I have check this, so this may be no problem at all.

I have some 32cm teflon coax with an open end. I see no TDR from NanoVNA but I see a proper TDR from NanoVna_saver 0.22. Frequency settings seem to matter with TDR too. My frequency range was 50k-500M

On Tue, Jan 14, 2020 at 09:16 AM, Larry Rothman wrote: I would definitely look the "next" time, and thanks, Larry. > Please remember folks - This info is all in the NanoVNA WIKI - link is at the >

in your case try $ sudo python3.7 -m pip install . /Martin -- QrssPiG, a QRSS grabber for your Pi: https://gitlab.com/hb9fxx/qrsspig “The best surfer out there is the one having the most fun” --

I second Larry's advice. There is a lot of invaluable information in the Wiki and Files sections that can save our members a lot of time and effort. This group members always seem to be willing to

Using Linux Mint 19.3 amd64 here. Built 0.2.2alpha successfully on 15.12.19 using the instructions here... https://github.com/mihtjel/nanovna-saver Upgraded LM19.2 to LM19.3 on 19.12.19. Now all

Hi Rune, I still find some strange things in the marker handling? : 1) I did a 2 port calibration? from 10kHz to? 1400MHz (and pressed "apply") 2) I filled all 9 marker-bars with different

Please remember folks - This info is all in the NanoVNA WIKI - link is at the bottom of every email post... Please refer to the Wiki and Files areas as they have a pile of very good reference

Attached is the one I could convert to PDF. The other is standard jpg. Dave - W?LEV