开云体育

Erik, Did you take a look at what I did in the following post and the subsequent posts in that thread? This involved trying to fix a poor BNC short and open.

Hi Herb - ????? My script has NEITHER of those for several most recent versions, instead: x = struct.unpack("<76800H", b[prune:blen]) This allows easy 'prune' tuning and avoids a buffer copy.. Yours

I'll try to help, but mostly in order to understand: Why is it you need to put something into the calculator? Can you not use the impedance measurements which is shown in NanoVNA-Saver under

Hi Rich - The more, the merrier. No, I called that 'color fringing artifact' and occurs because blue was pick up from the next byte; there are 2 bytes for each nanoVNA display pixel, and get this

Forgot to include the attachments to the previous post.

Oristo, The color fringing wasn't readily apparent to me until I saw the photo attachment from Rich Messeder where his color fringing is easily distinguishable when zoomed in. You are correct that

Many thanks for the inputs. I am following G3TXQ method of measuring common mode impedance. I connected the shields of the input and outputs of the 1:1 Balun to CH0 and CH1 inputs of VNA. I am trying

Thank you for the addition. Bob Beltz

Well, the delays did not work as expected. So I'l formulate my tuning question a bit more to the point. The green line in attached picture shows the outcome of this formula "phase(S11open) -

I don't know who manufactured mine...I purchased from Amazon US from AURSINC. Attached images in detail, FWIW. Seems like nice work, and I have been able to use nanoSaver and do a firmware update.

Hi Eric, no problem - the calculations seem to be *correct* which is the major hurdle ;-) As I posted, scipy.signal.convole seems a lot faster, and is probably a good way to do it. The test also

I'm new to the discursion, but I see a blue "shadow" on everything...is that deliberate? The image posted is 320x240, but I understand that this may be different from the device itself somehow. Note

Oops, >>email attachment<< is correct 320x240 and very clearly has color fringing. Online images are evidently subsampled... Try changing 'prune' from 9 to 7 or 8 in the current version at:

It appears that the latest firmares still do not support a freq step less than 100 Hz. Are there any plans to support a smaller step size? 1 Hz would be great. 10 Hz would be good. Use cases would be

That image is 215x161, not 320 x 240, and has color fringing. In buffer, RGB565 should be: "RRRRRGGGGGGBBBBB" .. then 0xFF000000 + ((arr & 0xF800) << 8) + ((arr & 0x07E0) << 5) + ((arr & 0x001F) << 3)

Oristo wrote. " … which should make color fringe artifacts on vertical edges in the PNG" ------------------------------------------------------------------------------------------------ No fringing

Oristo wrote, "If QRP's NanoVNA-Sharp MOD works with your firmware while my script does not..." ---------------------------------------------------------------------------------------------------- I

Did not yet try to optimize the delay. Will try The low frequency phase wobble reduces substantially if I use loadR=50.7 Could that be the actual impedance of the coax? Or is that the value where the

drkirkby@...> wrote: I should have added, that there is possibly some point in including C0, C1, C2 and C3 on homemade cal kits, but not inductance coefficients.

Someone else (forget who), showed to my satisfaction at least, that there was no need for anything beyond C0 for cal kits. He checked 3 kits I own * 85054B 18 GHz N * 85052B 26.5 GHz 3.5 mm * 85050B