开云体育

Hi Marcel, If I understand it, searching for "NanoVNA doesn't want to start" in forum discussions may be a solution. It's a good idea to read these and it might help. As far as I remember, there was

btw we just merged in all recent changes from edy555's firmware branch, so we have all the new features like TDR, marker search, marker delta, group delay, etc. ;)

If you can see the images I posted you'll see it runs the same UI as the Nano ;) And it's compatible with the most widely used Nano software, nanovna-saver. The STM32 we are using is of the same specs

I have been pursuing other interests and muted several topics and hashtags here. You, Larry, Erik, Alan and others do fine; I should add more "like"s. The USB shell `sweep` command already supports

If compatible with neither nanoVNA (nor, sadly, VWNA) software and lacking STM32 support, then substantially as unrelated to this group as any other low cost VNA.

It's 201 points per save location, 5 save locations total. The command interface is *not* compatible with the original Nano, but I already have a working patch for nanovna-saver which I will upstream

On Sat, Dec 28, 2019 at 09:11 PM, Gabriel Tenma White wrote: "... Finally got 201 point sweep working. You can now configure arbitrary number of sweep points between 2 and 201 (on-screen)…."

Finally got 201 point sweep working. You can now configure arbitrary number of sweep points between 2 and 201 (on-screen). The max sweep points over USB is still 1024. Memory and flash usage: Memory

I was just looking over the image hugen uploaded a few days ago for the new rev 3.4 board at https://github.com/hugen79/NanoVNA-H/blob/master/doc/NanoVNA_Rev3.4_PCB.jpg . Looks like he delivered on

On Sat, Dec 28, 2019 at 05:50 PM, Oristo wrote: It would require some additional code for a single firmware to dynamically detect whether installed with more flash, then conditionally increase that

On our Comparison of our [NanoVNA] with our [HP 8505A] Using the Ultimate Criterion of Cross-Ratios Dear all, It is our great pleasure and honor to present to you our results - which we just got for

Hi Herb - It would require some additional code for a single firmware to dynamically detect whether installed with more flash, then conditionally increase that 101 limit. Of course, that additional

[#97] On our Comparison of our [NanoVNA] with our [HP 8505A] Using the Ultimate Criterion of Cross-Ratios Dear all, It is our great pleasure and honor to present to you our results - which we just got

I too have power problems, perhaps not quite the same as yours. I also have two units, a black and a white.? The black one behaves normally most of the time but occasionally will switch off.? I

hugen, per your GitHub info: "This is my attemp to port the STM32F303CCT6 to this popular NanoVNA project. The benefits are larger SRAM 40KB from 16KB, larger flash 256KB from 128KB, faster CPU clock

Establishing a "measurement plane" makes the impedance or admittance displayed on the VNA valid at that specific point. For example, you want to know what the impedance is at the input of some device.

The easiest one to explain is using a simple random length of RG316 (PTFE) cable terminated in sma (instrument end) at one end and bare wires the other (DUT end). If we want to normalize the cable

I have two NanoVNAs here that both seem to have the same problem in that they very often don't power on. The first NanoVNA is a white/gecko model (2 traces firmware, micro-USB, official ttrftech

VNA works by measuring signals, then calculating based on differences from known references namely open, short and 50 Ohms. So long as there are measurable differences among those references, then

I've been looking through posts here, and other internet references, to try to understand the meaning of the term "measurement reference plane." My general understanding is that this refers to the