开云体育

Hi Alessandro, Generally, this means your firmware is so old, there is no way to read the firmware version. -- Rune / 5Q5R

Hi all, I noticed that moving to NanoVNASaver 0.2.0 > About, the NanoVNA Firmware version displayed is: NanoVNA Version ? Has anyone noticed the same thing or I have something wrong? NanoVNAe works

Many have measured and tested it but found no noticeable difference between the variants. Probably the raw material comes from the same source, pcb is the same. So why would it differ unless the

Looking again at your pic from Amazon, I notice it is sold by KKMoon. I brought two NanoVNAs from this same seller there. When they arrived one was a clone and the other appears to be a hugen

I thought it was 1.2 amps max pass current, not actual current ? English data sheet mentions intelligent charge levels. https://datasheetspdf.com/pdf/1139134/Injoinic/IP5305/1 Not sure if this helps,

What is pictured there is missing the "CH0" on the bezel. I think hugen would tag that as a clone That said, I have not seen where the clones have been shown to perform any worse. All NanoVNAs can be

The unit can operate as a stand-alone, unlike the many SDRs out there. However, it can also operate with a PC, laptop, Android, and a number of other platforms. With PC support, you get a MUCH larger

Hello June I have joined the group and I will discuss the situation on that group. I am very keen to buy the right product and support the right people. Regards Conrad ________________________________

First of all, I am a total newbie. I ordered in the blind, only looking for the "NanoVNA" word or label: https://www.amazon.com/gp/product/B07WNVXHL6/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

I'm wondering if hugen is able to verify that the replacement battery control chip he is thinking of using will prevent over charging any cells. I've translated and attached a copy of the FM9688

It's Python that's a mess, as bad as java. It promises app portability, and its anything but. We need something like good old QBASIC, where we can load source into an interpreter and run it. Python

Hi Kurt, Sorry for taking long to reply to your email. The issue in your earlier tests seem to be with C0=0: the calibration corrections divide by a value that is dependant on C0, and for that reason,

Hello David. I have a very specific use for the NanoVNA-F, basically the VNA-H is too small to be useful with my poor eyesight. I have a VNA-H and it compares very favourably with my HP-8712B. The

Very interesting! I had essentially the same problem trying to run nanovnasaver on Windows Vista and was assured that i I installed Linux, I'd be golden! But I have already installed Linux and tried

Yes. This issue has been reported before (posts #3096, #4533, #6288 etc.) Supplied nvna battery spec is here...

I think it's 3.1 based on the "V3.1" that appears under the battery. This one was purchased directly from nooelec on 10/12/2019. I don't know what the differences are between versions, nor am I aware

Darn, I just tried it, and failed. Everything appears to be installed if I follow the messages. Same old story, NVNA-S complains about pyqt5 or pip. Install the required. Console tells me they are

Hi All In the NanoVNA-saver the calibration settings, when doing a female calibration with the supplied NanoVNA calibration kit, where the male SOL parts are fitted to the FF adaptor, need some

Runs OK for me with Debian 9 and XFCE, but I did follow the installation instructions and carefully installed all the recommended support. [email protected]> wrote:

A few months ago I managed to get nanoVNA-saver running using the instructions on Rune's Github page. This was on a Linux Mint 18.3 machine and Cinnamon. Then I had a catasrophic PC failure, known as