开云体育

I'm reporting my experience with the Web app in case it might be helpful to somebody. I opened the web page on two Android devices. They are versions 5.3 and 6.0, which I know are old, but both worked

We are very sorry for this situation, it seems that the touch screen was damaged during transportation, if you buy a model made by us, we can provide the accessories for free, please contact your

Yes I do. and there are some stuff left in it ls /tmp/ mozilla_pierre0 pulse-PKdhtXMmr18n ssh-IfE43VTJEnve systemd-private-fb8c2b57f05146519286706d79b30aeb-colord.service-ITCxnV

Pierre Martel wrote: Check for us, please. Does this file exist? If you search for it, can you find a file somewhere in the file system named "setup.py"? (Probably in a PyQt5 subdirectory somewhere

Do you actually have a tmp directory in the root? 73 -Jim NU0C "Pierre Martel" <petem001@...> wrote:

On Sun, Jan 12, 2020 at 12:51 PM, Gyula Molnar wrote: > > Hi Chuck, > i see you need to install a driver on windows 7 so that your computer can see > nanoVNA. To do this, download and install

I know it is not related on the NanoVNA directly, but I did not think it is a github type issue Fresh install off debian 10 with Xfce as the windows manager. All is updated and I am in the Sudo group.

Thanks for the ideas, guys. There was a tiny amount of plastic film under the bezel. But, removing it made no difference. Operating with the bezel off is no different, either. There does not seem to

I have this book and it useful. https://www.amazon.co.uk/guide-NanoVNA-Christoph-Schw%C3%A4rzler-ebook/dp/B083BB82G5/ But it's mostly about the NanoVNA history, features and functions and not much

Hi Jim I don't see where my program starts. But it does (is it compile?) Go thru the process of trying to get there. I was wondering if I loaded a Python IDE and tried to get the program to run from

Your plot should be a little tighter together. Did you calibrate the NanoVNA before attaching the cable? The plots below are 30 cm of RG316 with an open BNC connector on the end. One up to 299 MHz.

I'm getting a program crash when enabling Continuous Scan after loading a calibration file on 0.2.2, Win7 SP1. Anyone else seeing this? I've posted a new bug issue on Github. -agc

Bob Larkin wrote: Take the four screws holding the screen bezel down, and check to see if there aren't scraps of the plastic film still stuck under there. I had that problem for a few minutes when

That might be the same error message I got when I installed the latest Nanovna-saver yesterday.? The program still starts, but I haven't tried actually connecting to the NVNA.

I don't know where the picture at groups.io went. Try http://www.janbob.com/electron/touchscreen.jpg Bob

It sounds like you may have a bad touchscreen or, make sure that There is nothing pinching the touchscreen around the front bezel.?You can remove the 4 screws on the front bezel and do a visual chaek

Here is a picture when running a stylus all over the screen in a touch test

My nanoVNA arrived in Dec and functions just fine in RF terms. The touch screen has never been correct and the numerical input from the pad has not worked. It is: ch> info Kernel: 4.0.0 Compiler: GCC

Rune, Thanks for fixing the "Offset Delay" bug in Calibration. I checked it out with several coax cables and got good results. It also correlates with the "electrical delay" parameter in the NanoVNA

On Sat, Jan 11, 2020 at 03:47 PM, Leif M wrote: Is S11 or CH0 impedance also available in polar plot form? ======================================================== Leif, You may have already found