开云体育

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 direct, ie not via ebay.

My version has a ARM 7E-M CORTEX M4F , PLATFORM STM32F383Xc and the clone synth chIp MS5351 hence the MS Suffix in the model number.

It has been stable for me and i double checked a measurement on a 10MHZ BPF against an agilent analyser i have access to at work. The results were pretty much spot one. I should add i do have a HP calibration kit (SMA) and i havnt even used the supplied cal SOLT's.

I just wish i could get J.Smiths labview software to run with it.

Hope this helps Pete

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 - having proper MCU and included SD Card Slot?
- It appears version 4.2 is older and still sold by many authorized sellers, but is newer version 4.3 the better one to buy?
- After all this time, why are there still so many 4.2 versions for sale? Is it because no one wants the older 4.2 version??

2) Will the latest Firmware revision run correctly with same features on both hardware version 4.2 and 4.3? I think DisLord firmware V1.2.00 is the latest - correct??

3) Who is the best / trusted seller to purchase a proper functioning NanoVNA-H4, with all latest features / firmware?

4) Or is it better to buy a NanoVNA-F version 3.1 from www.deepelec.com by BH5HNU?
- That design seems to be well defined/stable and more clearly marketed.
- But maybe it is not equal in features to the latest -H4? This is all very confusing!!!

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 the bias was off, before you connected the mount (instant Fail). The HP vswr detector and the probe in the slotted line. Early measurements of measuring wavelength, plotting values on the smith chart to calculate impedance and vswr.. Oh, and don't forget to take off your wristwatch. (:-) or you Failed...

This is one of the best threads I've read on Groups.io. Thanks.

wb7ond

On 10/5/22 3:16 PM, hopkor@... wrote:

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 process using MATLAB/commands. I was wondering in which registry the calibration data stored are stored in nanovana and how can I read and write to it after connecting the device using matlab.

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 equivalents to the python Scikit-RF as a Matlab toolbox.

On Thu, Oct 6, 2022 at 11:03 AM, Ho-Ro wrote:

On Thu, Oct 6, 2022 at 06:26 PM, DiSlord wrote:

Or use stored slots

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 possibility to just update one slot.

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 couple of dollars and Mouser was great at getting them shipped out and I ordered eight of them because they were so tiny. If you have any questions read the thread I posted above.
Dave
NL7QY

On Thu, Oct 6, 2022 at 06:26 PM, DiSlord wrote:

Or use stored slots

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 possibility to just update one slot.

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

On Thu, Oct 6, 2022 at 03:46 PM, Jim Lux wrote:

You can get the cal data out, but I don't think you can load the data back in.

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 configuration and calibration from the flash via dfu-tool upload and restore it via dfu-tool download.
I don't care about the internal format, just stupid bytes :)



I'm working on a straightforward python tool to parse the bin file and save the individual calibration slots under "talking" filenames, e.g. "config_10000000_20000000_101.slot" for a 101-point calibration from 10MHz to 20MHz.
With a simple "cat FILE1.slot FILE2.slot ... >my_new_config.bin" you can rearrange the data and "flash" it back to suit your needs.

On Thu, Oct 6, 2022 at 06:46 AM, Jim Lux wrote:

On 10/5/22 9:54 PM, Ata wrote:

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 and each of them
includes SOLT calibration data.

- data [array]
Get complex data
0: S11, 1: S21,
2: CAL_LOAD, 3: CAL_OPEN, 4: CAL_SHORT, 5: CAL_THRU, 6: CAL_ISOLN

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.

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 */
ETERM_ET 5 /* error term transmission tracking */
ETERM_EX 6 /* error term isolation */

!!! All data complex
S11 = (refl - Ed) / (Es * (refl - Ed) + Er);
S21 = (thru - Ex) * Et

On 10/5/22 9:54 PM, Ata wrote:

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 and each of them includes SOLT calibration data.
- data [array]
Get complex data
0: S11, 1: S21,
2: CAL_LOAD, 3: CAL_OPEN, 4: CAL_SHORT, 5: CAL_THRU, 6: CAL_ISOLN

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 the SD card for storage.

Upload data from NanoVNA:

- switch into DFU mode, either from menu or with BOOT jumper.

dfu-util -d 0483:df11 -a 0 -s 0x08018800 -U CONFIG.bin

- switch NanoVNA off to leave DFU mode.

To download this calibration data to the NAnoVNA:

- switch into DFU mode, either from menu or with BOOT jumper.

dfu-util -d 0483:df11 -a 0 -s 0x08018800 -D CONFIG.bin

- switch NanoVNA off to leave DFU mode.

To make it easier to switch to DFU mode, you can use this small HW mod (with the NanoVNA-H, the resistor does not need to be replaced):

/g/nanovna-users/topic/69979852

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 and each of them includes SOLT calibration data.

- data [array]
Get complex data
0: S11, 1: S21,
2: CAL_LOAD, 3: CAL_OPEN, 4: CAL_SHORT, 5: CAL_THRU, 6: CAL_ISOLN

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}

On 10/5/22 11:45 AM, Costin R wrote:

Thanks for the reply, Dave!
I had not seen the exact model of the ESD diode in the link sent. I must
have been careless...
I asked the exact type because in NanoVNA the junction capacity is very
important in order not to influence the measurements. I see in the catalog
of this diode a capacity of 0.05pF, which is very good for this application.
As for soldering, I have all the necessary tools for Safe ESD operations,
good eyes (;-) with glasses) and a magnifying glass with light.
Regards,
Costin

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 are two fold:
1) the shunt C reduces the signal level, so the sensitivity of the receiver is less.

2) it is a semiconductor junction, so the possibility of IMD is there.

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 process using MATLAB/commands. I was wondering in which registry the calibration data stored are stored in nanovana and how can I read and write to it after connecting the device using matlab.

Thanks for the reply, Dave!
I had not seen the exact model of the ESD diode in the link sent. I must
have been careless...
I asked the exact type because in NanoVNA the junction capacity is very
important in order not to influence the measurements. I see in the catalog
of this diode a capacity of 0.05pF, which is very good for this application.
As for soldering, I have all the necessary tools for Safe ESD operations,
good eyes (;-) with glasses) and a magnifying glass with light.
Regards,
Costin


?n mie., 5 oct. 2022 la 20:58, Dave via groups.io <dvfuller=
[email protected]> a scris:

I used Mouser PN 652-CG0603MLU-05E. All the information was in the link that I gave above. They are tiny and you need a fine tip low wattage soldering iron. Good luck

That latest firmware from DisLord , V1.2.00 adds the following :-

additional 4 admittance marker format and Admittance background
G + jB
G + L/C
Rp + jXp
Rp + L/C

? Add text keyboards for input filenames (max 8 chars on H and 18 on H4)
? Progress bar on screenshots
? Remote Desktop (work in NanoVNA-App, translate screen to CPU)
? Add flip display option
? More stable work on harmonics
? Speedup and reduce code in math/fft operations