开云体育

Bo,? HOw thick is that FR4 board?? Thinner material would improve the isolation, right? Mike WY6K

There is no such option. You can modify firmware but the logic for frequency boundaries is not easy, needs to deal with this. By the way, edy555 firmware uses different frequency segments boundaries.

Hi John, if you experience crashes, please try: - Running the program for a command prompt, which preserved the crash message, - Running using "-D logfile.txt" as a parameter, which saves debug data

qrp.ddc, I purchase cables of unknown quality at hamfests and the nanoVNA has paid for itself in helping me avoid selecting cables that physically looked fine, but from both cable ends looked like

did you tried original edy555 firmware? Firmware from hugen79 and from edy555 have different frequency modes. So they have different behavior at different frequency boundaries.

In my previous post, I was referring to coax from my hamshack to the antenna - not a piece of transmission line a foot or 2 long. Please remember that from a practical viewpoint, LOW resolution in a

Hi From a market volume point of view it might be an idea to divide the RF boards into: 1) Si5351A, as now. This is more than fine for the vast majority of radio amateurs 2) Si5351A + ADF4351, lower

on this list. that he has nothing to learn from a genuine ham of long and diverse experience. Not all of us are simply warmed over chicken banders. Some of us have ended up embarrassing engineers. On

Tried it on two different Windows 10 machines - it seems some combinations of sweep settings cause the program to close suddenly. This occurred on both PC's. Calibration was done (400kHz - 5MHz),

Hi Mike, I've heard a number of users mention antivirus problems. I have tried submitting it to VirusTotal, and it seems the "only" things it reports is a set of a few antivirus programs worried about

If I'm looking for discontinuities in the circuit, which total length is 1 foot total and TDR can show it one or two foot away from real point, I think it will be useless. To be more clear what I'm

This is why hugen came out with his 800MHz version of the firmware.

Hi Kurt, thanks for all your help with the calibration! I'm still working on it, and as you say, I need some better functions for saving the resulting calibration, that it may be used later. You are

OK, no problem then. However, please remember - considering the cost of the NanoVNA - it puts more capability in your shirt pocket than most of its predecessors used by Amateurs. As I mentioned, it

Hej Bo, I'll address the port numbering first: Port 0 and Port 1 should probably be "Ch0" and "Ch1", and are taken from the port numbering on the physical device:

LOn Fri, 27 Sep 2019 at 19:34, Bo, OZ2M <groups.io@...> wrote: One more thing. I agree 100% with you. Dave -- Dr. David Kirkby, Kirkby Microwave Ltd, drkirkby@...

Hi group I have measured a low pass filter, but experience some, for me expected, oddities around the maximum usable fundamental frequency of the Si5351A. Please see the attached picture that clearly

19 : "true value" - also : @Dr. David Kirkby : /g/nanovna-users/message/3207 Hello, We both thank you very much for the time you spent to compose such a lengthy reply, by which you

I'm already doing that. Unfortunately I'm not familiar with calibration math, so I have no idea how to improve it. If you can help with the math details for better calibration, it will be nice.

One more thing. It might be an idea to change the name of Port 0 to Port 1 and Port 1 to Port 2 in the S/W GUI so it matches S1x and S2x etc. instead of e.g. S10 ... I acknowledge that in programming