开云体育

You recalibrate device after?

Linux was released in 1991, RH came a few years later.

Thanks for the info. Never been one to go with the latest and the greatest. Been running RedHat Linux since about 1991. I always go with 'stable'.

What I'm wanting to do is to check a dupexler I have coming in the next week or so to make sure its tuned close the frequencies I requested. I know this is not the ideal way to do it but I don't have

hmm ... as far as i know the version from dislord is more actual (12 days old) and displord also is making new fw fro nanovna v2 (and some other clones,brothers,sisters, cousins) version from oen

What are you measuring? Try the 50 ohm load and post a screenshot Then connect the two ports with a cable and post a screenshot. Roger

Hello, Yes, I did both calibrations. I just now updated the fw and the app. Its still doing the same. Do you think my nanovna may be bad? I have expanded the frequency range to 460Mhz to 470Mhz and

I prefer the latest NanoVNA app fork by Owen Duffy. He incorporates some of DiSlord's changes and fixed the "info" parameters so they now work correctly when you hover over the data.

Awesome!! I did not know they were outdated. I did see the NanoVNA App, but only saw the 1.0.69 version in the files section. Are the fw files in a new location? Thank you!!

Your screenshot shows that you are using calibration in the App and not on the NanoVNA itself. Did you calibrate in the NanoVNA app? If not then you have to calibrate in the app or change the

1.0.69 for your H4 is outdated as is nano vna app (displord version 210 is most actual) you find it here https://github.com/DiSlord/NanoVNA-App/blob/main/Win32/Release/NanoVNA-App.exe and new fw?? i

Hello, Just got my NanoVNA H4, have upgraded the firmware to DiSlord's v1.0.69 and using the NanoVNA App v1.1.208 by OneOfEleven. Reason for doing so was to be able to get more than 101p. After going

A comparable tool to S11.exe is now in my NanoVNA toolbox: https://github.com/Ho-Ro/nanovna-tools The tools are easy to modify because most of them are written in python.

The problem with that is that on a lot of Linux distros, devices are created by udev at boot, so this will typically revert on restart of the system. The proper solution is to add the user to the

Hi Tim, I tried connecting to the NanoVNA using a USB cable, and it seems to work OK. I can do a scan and get the Smith chart to populate. Both NanoVNA-QT / NanoVNA seems to work fine. I am pretty

For me : Ubuntu 22.04 nanovna saver 0.2.2 1)plug nanovna 2)in a term sudo chmod o+rw /dev/ttyACM0

In PJ the variations according to the frequency of the values of the six columns of data. 4 faults are clearly identified visually. We note that the fault is generally concomitant on two columns. In

Whether you do the calibration on a single port or on both, there are errors in the .cal file. To put it simply, we will say that these are parasites that generate false measurements. The real cause

You might see if you can see it via USB, and if you can get it into DFU mode and reload it. Bad software can cause that as well. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

It appears I may have killed my 2nd NanoVNA. Last time, I let the battery voltage drop too low, and in my effort to repair, I managed to snap some of the connectors off. This time, I had a display