开云体育

I have recently been getting a lot of Epoch Times (a political slant I loathe) ads in my web browser, but not by email. I suspect ET is just running a major advertising blitz in the run-up to the

There was a period when I also received similar unsolicited letters from a different address. Ever since I started using MailWasher and set up spam addresses, I haven't had a case like this. -- Gyula

Is anyone besides myself receiving periodic spam from theepochtimes.com? I'm trying to figure out if this is a group spam problem or a personal spam problem. DaveD, co-owner -- This email has been

Hi i have a H4 V4.3MS , had it just over a month and very happy with it so far. Im not new to VNA's as have used professional HP/Agilent ones for years. I purchased mine from a seller in the UK

Unsure if this thread is still open.... But here we are, 10 months later, and I think the same exact questions still remain. To be specific: 1) For NanoVNA-H4, which hardware version is the best -

W1RS, yes I remember the slotted line from Lowry AFB PMEL school late '60s. The HP 715 klystron power supply, and modulator. the HP 430C power meter with bolometer mount, you had to bias it, make sure

You're better off doing the cals on the PC and sending a reset cal command to the NanoVNA - Take a look at the python code in NanoVNA-Saver for an example. It uses scikit-rf. I'm sure there's

Question how many times need write in this script. Most good - use calibration on CPU side and get raw data from NanoVNA Here is good guide how made calibration (H/H4 use 1-PORT + NORMALIZATION)

I checked the VNA before and after the modification and I saw no problems with it. Believe me if those diodes had an effect it would have really had a problem with the tinySA. The diodes were only a

Storing in slots also writes to flash. And honestly speaking, how often do you calibrate different setups. But it simplifies the change if you have e.g. some special fixtures. I will also check the

Lot of STM32 flash rewrite not so good (limit by datasheed ?10000 count) this can damage it. Better do calibration on CPU side. Or use stored slots

You can use this simple shell script from my toolbox to save the configuration and calibration on the PC and restore it later on the NanoVNA. Works for -H and -H4. I read out the binary block with

No NanoVNA precalculate calibration data for more faster apply to: ETERM_ED 2 /* error term directivity */ ETERM_ES 3 /* error term source match */ ETERM_ER 4 /* error term refrection tracking */

You can get the cal data out, but I don't think you can load the data back in. If you're using a computer with the NanoVNA, why not do the cals in the computer, and keep the NanoVNA simple. >

With the NanoVNA-H with DiSlord's FW, the calibration data of the 5 config slots is stored in the flash at address 0x08018800. The NanoVNA-H4 has a different memory layout, but with this unit you can

Use recall command recall 0 Now device use 0 slot, and data command load from it

My understanding is I can get the calibration[LOAD, OPEN, SHORT, THRU, ISOLN]. But how should I know which slot is being read? That is to say, we have 6 slots for saving calibration data on the device

Only get calibration data command: data 2 data 3 data 4 data 5 data 6 You can load and apply calicration from slot: recall {id}

Interestingly, in this application low C is nice, but not necessary. The calibration process would take out the shunt C, just as if you had a foot of coax or twisted pair. The potential "bad" effects

I am trying to automate my project. For this, I would need to read the stored calibration data from the device and save it to my pc, and then load it back when necessary. Preferable to automate this