开云体育

Hi, despite many "battery" related posts here with interesting info on batteries I opened my new H4 (1950mAh battery there, no sd socket) and measured the voltages at the battery connector. H4 freshly charged over night.

My HP34401A meater reads (aprox. 1min between measurements)

1. H4 turned off, no usb cable: 4.212V
2. H4 turned on, no usb cable: 4.153V +/- 2mV
3. H4 turned on, with active usb cable connected: 4.223V

During step 3 with vbat_offset set to 0 the vbat command returned values from 3682-3823.

My current understanding is as follows:
1. the battery gets a little bit overcharged
2. the "vbat" ADC reading is pretty noisy (see the graph below), provided it is done via stm32's 12b ADC, with a 2layer pcb and some decoupling the readings should stay within +/- 10mV, imho.

Hi AF7XT,
Please try 0.3.6 - possible version error, although I couldn't start only 0.3.6 on a 32-bit system.
73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

Thank you all for your help on this. Bought the NanoVNA-H last year and now could not resist the temptation to buy the H4 version with more features added!

BR
Nan

See this post for more information
/g/nanovna-users/message/14447

Hi Nan, here you can see the DiSlord firmware and links to the descriptions:
/g/nanovna-users/message/14450
Successful use

73, Gyula HA3HZ
--
*** If you are not part of the solution, then you are the problem. ( ) ***

Hi Hugen

Many thanks for the confirmation and I am relieved to note that I have bought an original version! The 32.768KHz X'tal is missing on this board although the MicroSD card is installed. Can you please point me to the need for the X'tal? I am away from home and might take several weeks before I can get back to my shack due to the pandemic.

BR
Nan

This version is produced by me. Thanks to DiSlord for completing the transplantation of microSD. For the newly produced PCB, we have installed a MicroSD card slot and replaced the 2000mAh battery. You can refresh DiSlord's latest firmware and use the microSD card after making holes in the case. I will modify the case and add a 32.768kHz crystal when the next larger version is updated.

Wow, you already have the SD-Card reader populated! The black box and that
SD card reader strongly suggests an authentic one, of the latest batch.
--
Sent from my mobile device, apologies for typos

PGP key:

Hi All

I just purchased a NanoVNA-H4 from a China seller via Lazada.sg in Singapore.
Can I get help to confirm if this is the original made by Hugen or a clone? It came pre-loaded with Hugen's latest firmware version of 21 Feb 2020.

BR
Nan

The iphone and android phones here in the house show both a battery icon level and the percentage at the same time, which we really like. I guess they know what their customers like (or not). But it's easy enough to comment out the bit of code I added to not show the battery percentage for those that don't want it, I'll add a #define in the nanovna.h file to make it easy to choose what one would like Larry.

But anyway, I need to move on soon, hopefully I've shown a tiny bit of what could be done to niciefy things up a teeny bit and add a little extra functionality. Lots more wonderful things could be done, a VNA is a tool that can do big things, but I really need to concentrate on other stuff. I may publish other changes/additions I need for my own use, but most likely at a later date.

Don't forget though, the user interface/experience is all important, as is functionality, they both go hand in hand, one without the other gets noticed very quickly on, any good user will/should thank you if at the end of the day they've had a nice and easy and fascinating time playing with what you've given 'em.

Tiz a wonderful and useful project !

Hi Larry,

My programming and compilation knowledge is not the best ones to do it but I totally agree with you.

Holger and Gyula told me how to do it with the Python and I was able to run it (yours help is very best) , ….
but it would be nice if someone compiled the latest versions for win 10 / 32-64....

Vy 73
Enrique LU8EFF



-----Mensaje original-----
De: [email protected] [mailto:[email protected]] En nombre de Larry Rothman
Enviado el: martes, 14 de julio de 2020 20:14
Para: [email protected]
Asunto: Re: [nanovna-users] NanoVNA Saver 0.3.3 or 0.3.4

Holger,

One of the newsletters I receive had an article on malware written in Python.
Part of the discussion revolved around how to get the size of the windows package down and there were 3 different Python to EXE utilities presented that are used for non-malware Python to Windows uses.

One of these is: Nuitka -

Right now, the NanoVNA-Saver EXE application is very large and takes time to execute.
What Nuitka does is to convert Python code to C and then compile.
The resultant application size is a fraction of what you get with py2exe or pyinstaller and runs much faster.

Could you try Nuitka on NanovnaSaver to see if it speeds up the application?
I did not look over the entire website but if Nuitka compiles C, it might be able to generate both 32 and 64 bit binaries.

Thanks,
Larry




--
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.

The following files have been uploaded to the Files area of the [email protected] group.

• /Nano VNA Saver/Instalar Python 3.8 para NanoVNA-Saver.pdf

By: Enrique A. Wembagher LU8EFF

Description:
Spanish doc for Python Installation on Windows 10 – 32-bit to work NanoVNA-Saver program in later versions to 0.2.2.exe -- Thanks to Holger Müller <dg5dbh@...> and Gyula Molnar <gyula.ha3hz@...>

Holger,

One of the newsletters I receive had an article on malware written in Python.
Part of the discussion revolved around how to get the size of the windows package down and there were 3 different Python to EXE utilities presented that are used for non-malware Python to Windows uses.

One of these is: Nuitka -

Right now, the NanoVNA-Saver EXE application is very large and takes time to execute.
What Nuitka does is to convert Python code to C and then compile.
The resultant application size is a fraction of what you get with py2exe or pyinstaller and runs much faster.

Could you try Nuitka on NanovnaSaver to see if it speeds up the application?
I did not look over the entire website but if Nuitka compiles C, it might be able to generate both 32 and 64 bit binaries.

Thanks,
Larry

OneofEleven & DiSlord,
Currently, the location of the display you need to touch and hold for a screen capture is very small and can take a few attempts with your fingernail along the bottom edge.
I'm wondering if the portion of the display you need to press could be moved over to the battery icon area which is currently not an active touch area of the screen. That would provide for an easy touch location for a stylus.

Also, why do we need both a battery icon and a charge percentage readout? - It's kind of redundant. How about a console switch - one or the other?

Thanks for the great UI & functional improvements folks!
Cheers,
Larry

Traceback (most recent call last):
File "NanoVNASaver/Charts/Polar.py", line 45, in paintEvent
File "NanoVNASaver/Charts/Polar.py", line 87, in drawValues
OverflowError: argument 2 overflowed: value must be in the range -2147483648 to 2147483647
Aborted (core dumped)

Still..............

Screenshots are excellent, and I see buttons that respond more quickly. Fine!

On Tue, Jul 14, 2020 at 01:22 PM, WB2UAQ wrote:

It is based on a paper from Agilent and agrees with G3TXQ's method.

Hi WB2UAQ,

Do you have a link or title for the Agilent paper? I'd very much like to take a look at it.

Many thanks, and 73,

- Jeff, k6jca

Hello Roy.

I believe these type numbers are pretty universal, although I was directly taking the numbers and graphs from my Fair-Rite catalog.

Stackpole, Ferronics, and quite a few other manufacturers use different model designations for the same material...too bad. But they generally state "like 43 material" which has a perm value of 850 nominal. For example Stackpole would designate 4C4 and so. Bottom line, you really need to find out what is the perm value. When I finally know what I have, I paint white out on the sample and use a black ink pen to label the perm value.

Just added two new SD card serial commands that can be used to list the files on your SD card and to also read a file from the card.

"sd_list"
"sd_readfile <filename>"

Typing "help" on the command line will list all the available serial commands.

I id cores by first measuring their physical dimensions. I then measure the inductance at low frequency (even as low as kHz) and calculate the inductance index, AsubL. With these two parameters I have been able to ID the cores against published specs for Fair-Rite Products. The test freq must be below where the real and imaginary permeability begin their rapid changes. Also the drive level must be kept low as well (<10 gauss). I have been doing this for years with good results.
Some where along the way I put a spreadsheet on this site using the S21 Series method of measuring CMC Z. It is based on a paper from Agilent and agrees with G3TXQ's method. In the Agilent paper there is also an S21 Shunt method for measuring low inductances at low freq. 73