¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Batteries

 

On Thu, Nov 21, 2019 at 04:56 AM, Dr. David Kirkby, Kirkby Microwave Ltd wrote:

Thnx, dear 9 lined signature sales man.




On Mon, 18 Nov 2019 at 13:58, RFy <gpdxdveil@...> wrote:

450mAh is... Not suitable for NanoVNA
1. Stand-by draw
2. Charge circuit pushes over 1A( over 2C rate )

My battery already swelled( PCB/LCD curved slightly )


There are some high specification batteries for sale on eBay, at quite a
reasonable cost.




Dave.
--
Dr. David Kirkby,
Kirkby Microwave Ltd,
drkirkby@...

Telephone 01621-680100./ +44 1621 680100

Registered in England & Wales, company number 08914892.
Registered office:
Stokes Hall Lodge, Burnham Rd, Althorne, Chelmsford, Essex, CM3 6DT, United
Kingdom


Re: Still Looks For A good Unit

Greg Phillips
 

Hi all,

What is your opinion of this one?


thanks & 73's
Greg W4GAP


File updated in [email protected]

[email protected] Notification
 

Hello,

This email message is a notification to let you know that the following files have been updated in the Files area of the [email protected] group.

Uploaded By: Larry Rothman <nlroth@...>

Description:
This is a translated, reformatted and edited version of cho45's excellent NanoVNA User Guide. I have made the URL links live as well as added additional content in order to clarify some sections. The document is 33 pages and is formatted for printing. updated Nov-19-2019 - Added sections on Scaling and changed the touchscreen menu map to white. (Thanks Oristo)

Cheers,
The Groups.io Team


Re: Still Looks For A good Unit

 

The two small differences I can see are:

1. On mine, the upper SMA connector has a label 'CH0'
which is missing in the photo on the link.
2. The photo on the link shows what appears to be a S/N (or similar) at the
lower left. Mine has no such number in sight.
Those small differences (missing 'CHO' and lower left number) were on "worse" clones without shielding.


Re: File updated in [email protected]

 

Better still would be to get the originator to change the colors.


Re: F303 and 4" LCD for next generation NanoVNA #circuit #flash_size #improvement #enclosure #battery

 

Thanks for the update, Ken!

Hopefully, you are able to make the jog switch more responsive by using interrupts instead of polling.

As for the power circuits, it is nice to be able to use a single 3.7v Li cell with an inverter but in order to get noise levels down (you want a 3GHz top end), using two cells and running 7.2v through a low noise analogue regulator to 5V and then to 3.3V will remove most power supply noise.

The down side of 2 cells is requiring >8V for charging the batteries (and price) although with really good filtering, the unit can still be powered from the USB port.

Just some thoughts...
Larry


Re: Still Looks For A good Unit

 

Tom,

The unit at the link you provided looks identical to the Aursinc unit I bought a few weeks ago
(also from Amazon).

The two small differences I can see are:

1. On mine, the upper SMA connector has a label 'CH0' which is missing in the photo on the link.
2. The photo on the link shows what appears to be a S/N (or similar) at the lower left. Mine has
no such number in sight.

Other than those two items, this is the spitting image of mine, right down to the black Phillips-head
screws holding down the top cover. Mine does have shields covering several areas of the ECB,
and has so far been trouble free (knock on wood). I've probably done about half a dozen partial
discharge/recharge cycles, with no visible evidence of battery swelling etc.

Mine came with a handy carrying box with room for the VNA, three CAL standards, the SMA bullet,
and the two cables, all of which were included in the price.

Dana (K8YUM)


Re: USBDeview - Uninstall USB Drivers and inactive COM Ports

 

Hi Doug,

I'm glad you tried it and are happy with the little program.
I reinstalled the operating system in September, but I only see the 13 drivers I've used on this computer since it was installed.
In several forum discussions, it is noted that the driver problem is not known or difficult to handle. I hope more people can help you find a damaged or inappropriate driver and remove it. You will then need to install the recommended driver and then connect to the device. I wish everyone a successful use.

You can download the language files from here:

73, Gyula


Re: Batteries

Andy
 

On Thu, Nov 21, 2019 at 01:26 PM, Nick wrote:


Hi Andy

- How did you determine "charged"? LED not flashing?
LED stops flashing and USB current meter shows zero current being drawn (nanovna being switched off).


- What did you measure the current with?
In line USB tester. Ten for quid from China variety / Ebay ;-)

- What was the charge source? USB or something else? Need spec please.
2.1 amp USB cell phone charger, as supplied with my ancient Acer phone.

73 de Andy


Re: USBDeview - Uninstall USB Drivers and inactive COM Ports

 

You can also go to
Start >Control Panel >Device Manager >Ports (COM & LPT)
Then at the upper left corner of the window, click "View" and select "Show hidden devices". Once you can see them, you can right-click on one you don't want and select "Delete" to remove it. I removed 9 or 10 com ports created by USB serial ports connecting to my digital control ham radio equipment.
It also lists "USB Human Interface Device" 48 times (on my Vista PC).
Unfortunately, when I right-click and select "Properties" for those ports, there is no information about the device, so no way to know whether that device is still needed. The USB Serial Port for the NanoVNA is listed as "STMicroelectronics Virtual Com Port (COM9). I have one other port listed, "USB Serial Port (COM3), which only shows up when "Show hidden devices" is selected.

My NirSoft "USBDeview" tool shows 312 USB Devices!
NirSoft makes some very handy, very good tools.

Doug


Re: F303 and 4" LCD for next generation NanoVNA #circuit #flash_size #improvement #enclosure #battery

 

Dimmable LCD back light.
Being able to completely shut off LCD backlight (and refresh, but that is only firmware)
if/when driving from BLE to save power.


Re: data outside expected valid range

 

On Thu, Nov 21, 2019 at 12:10 AM, Nels Nelsen wrote:


I get this error:
This is firmware error. Old firmware has such bug which happens very often more fresh firmware works better, but it still can happens.
This bug is fixed completely in NanoVNA-Q firmware.

Just update firmware with NanoVNA-Q, it will solve this issue:


Re: running nanoVNA-saver under Linux Mint XFCE

 

Hi,
The "pip" command tries to install the dependencies from the "pypi"
repository - and PyQt5 is not available from there for 32bit Linux for some
reason. If you already have PyQt5 (not just Qt5) installed in the right
version, nanovna-saver should run fine, despite it not installing via pip.

--
Rune / 5Q5R

On Thu, 21 Nov 2019, 16:01 DL8AAP, <dl8aap@...> wrote:

I have a Win7 laptop running nanovna-saver but I don't want to use it any
longer caus of the license strategies of microsoft.
So I tried to meet all the requirements in my old Linux Mint 18.3 cinnamon
(= Ubuntu 16.04 Xenial) I know the prerequisites are Ubuntu 18 or 19,
anyway...
but if it comes to the "python3.7 -m pip install ." it makes the following
error:
Processing /home/user/nanovna-saver
Collecting pyserial (from NanoVNASaver===0.2.0)
Using cached
Collecting PyQt5>=5.11.2 (from NanoVNASaver===0.2.0)
Could not find a version that satisfied requirement PyQt5>=5.11.2 .....
No matching distribution found for PyQT5>=5.11.2 .....

I have Python 2.7.12, 3.5.2 and 3.7.5 installed, Qt5.11.2 was update via
repository (from 5.5)





Re: F303 and 4" LCD for next generation NanoVNA #circuit #flash_size #improvement #enclosure #battery

 

On Thu, 21 Nov 2019 at 15:12, Ken Liao, AA6KL <kuohsing@...> wrote:

I have been working with Hugen for the past two months to port the
STM32F303CCT6 and 4" LCD for new NanoVNA-H. The original author, edy555,
also provided valuable suggestions.
Good.


Software porting is about 90% finished. Some display and jog switch
related UI still needs to be fine tuned. Please check my porting at



Hugen keeps improving the hardware design. Here are some features that we
have discussed.
- STM32F303CCT6, which has 128KB flash memory, 40KB SRAM, and 8KB CCM,
running at 72MHz. Thanks to F3's FPU, the compiled code size can be even
smaller than the original F072's.
- 4" LCD 320x480, driven by ST7796S through SPI interface. Even with
twice the pixel numbers than ili9341, the sweep refresh rate remains the
same as original one, becasue of F303's higher clock rate.
Why not use a larger display? The nanoVNA-F uses 4.3", and I know it's only
0.3", but it is nearly 10% at this size.

Also, make it possible to change the display if it gets damaged, without
needing to desolder, as this is a weak point. Use a connector.

The option of N connectors sounds good. But female N's need will need
proper support for calibration kits, which current firmware lacks. The
centre pin of the female N sits more than 5 mm higher than the reference
plane, (5 mm nearer the front of the connector, so this should be
compensated for).

- UART pins, which can be used for Bluetooth and firmware update. Any
volunteer for the UART porting and mobile app?

- Larger battery to support larger LCD.
- The option of plastic and metal cases.
- The option of SMA and N connectors.
N connectors are most welcome.

- Miscellaneous circuit improvements
* Improved analog front-end. See

* New power management chip and circuit.
* Enter DFU by pressing jog switch at power on. Jumping into DFU by
software doesn't work for F303 yet.
* Option of hardware reset codec chip by MCU. This will help fix the
power on issue.
* Dimmable LCD back light.
It would be good if there could be headers to use in place of the toggle
swtich, and USB connectors, so people can put in their own case and use
decent quality switches, so things don't break.


Hugen hasn't finalized his design yet. Your voice will help him converge
the feature list faster. I hope that Hugen will freeze and release his
design soon so that we can have new gadgets to play with.

73
Ken, AA6KL
Dave, G8WRB


Re: running nanoVNA-saver under Linux Mint XFCE

 

I tried to meet all the requirements in my old Linux Mint 18.3 cinnamon
(= Ubuntu 16.04 Xenial) I know the prerequisites are Ubuntu 18 or 19, anyway...
but if it comes to the "python3.7 -m pip install ."
it makes the following error:
"because Mint is written partially in Python,
it's not good to modify the global version of python too much"


I have Python 2.7.12, 3.5.2 and 3.7.5 installed,
Qt5.11.2 was update via repository (from 5.5)
"leave the system-default version alone"



Re: F303 and 4" LCD for next generation NanoVNA #circuit #flash_size #improvement #enclosure #battery

 

I vote for the larger display. I have one of each and can say
the larger display is much better.

73, Dick, W1KSZ
________________________________
From: [email protected] <[email protected]> on behalf of hwalker <herbwalker2476@...>
Sent: Thursday, November 21, 2019 8:44 AM
To: [email protected] <[email protected]>
Subject: Re: [nanovna-users] F303 and 4" LCD for next generation NanoVNA #circuit #flash_size #improvement #enclosure #battery

In his past posts hugen said he believed a larger display unit would not market well. I'm glad to see that he is now considering not only a unit with a larger display but better processor also. I think the sales of the NanoVNA-F shows that a larger display is definitely the way to go. Hope design changes can also be made to the front end to achieve a lower noise floor.

- Herb


Re: F303 and 4" LCD for next generation NanoVNA #circuit #flash_size #improvement #enclosure #battery

 

In his past posts hugen said he believed a larger display unit would not market well. I'm glad to see that he is now considering not only a unit with a larger display but better processor also. I think the sales of the NanoVNA-F shows that a larger display is definitely the way to go. Hope design changes can also be made to the front end to achieve a lower noise floor.

- Herb


Re: File updated in [email protected]

 

Hello Larry,
I don't think item 16 addresses my issue. The original FW did not have a keypad icon at all. You just had to know to click in the white area to the right, hence my calling it an Easter egg. Attached is a photo of a recent unit from nooelec showing the numeric entry bar with no keypad icon.. FW in new units is the same as the older devices. I would address this with a photo that highlights the magic area like the second photo. Text like : "Note that earlier level firmware defaults to a one line numeric entry bar as shown here. Click in the white area to the right of the numbers (red circle here) to bring up the full keyboard." or some such verbiage.

Another thing I noticed is that the menu map on the last page while very useful is down right hostile to a printer because of the dark background. I took a quick hack at it with GIMP to make it more printer friendly. I'll attach what I got but it might need more work if you want something like this. Better still would be to get the originator to change the colors.
Thanks for the interest, Joe


F303 and 4" LCD for next generation NanoVNA #circuit #flash_size #improvement #enclosure #battery

 

I have been working with Hugen for the past two months to port the STM32F303CCT6 and 4" LCD for new NanoVNA-H. The original author, edy555, also provided valuable suggestions.

Software porting is about 90% finished. Some display and jog switch related UI still needs to be fine tuned. Please check my porting at



Hugen keeps improving the hardware design. Here are some features that we have discussed.
- STM32F303CCT6, which has 128KB flash memory, 40KB SRAM, and 8KB CCM, running at 72MHz. Thanks to F3's FPU, the compiled code size can be even smaller than the original F072's.
- 4" LCD 320x480, driven by ST7796S through SPI interface. Even with twice the pixel numbers than ili9341, the sweep refresh rate remains the same as original one, becasue of F303's higher clock rate.
- UART pins, which can be used for Bluetooth and firmware update. Any volunteer for the UART porting and mobile app?
- Larger battery to support larger LCD.
- The option of plastic and metal cases.
- The option of SMA and N connectors.
- Miscellaneous circuit improvements
* Improved analog front-end. See
* New power management chip and circuit.
* Enter DFU by pressing jog switch at power on. Jumping into DFU by software doesn't work for F303 yet.
* Option of hardware reset codec chip by MCU. This will help fix the power on issue.
* Dimmable LCD back light.

Hugen hasn't finalized his design yet. Your voice will help him converge the feature list faster. I hope that Hugen will freeze and release his design soon so that we can have new gadgets to play with.

73
Ken, AA6KL


Re: running nanoVNA-saver under Linux Mint XFCE

 

I have a Win7 laptop running nanovna-saver but I don't want to use it any longer caus of the license strategies of microsoft.
So I tried to meet all the requirements in my old Linux Mint 18.3 cinnamon (= Ubuntu 16.04 Xenial) I know the prerequisites are Ubuntu 18 or 19, anyway...
but if it comes to the "python3.7 -m pip install ." it makes the following error:
Processing /home/user/nanovna-saver
Collecting pyserial (from NanoVNASaver===0.2.0)
Using cached
Collecting PyQt5>=5.11.2 (from NanoVNASaver===0.2.0)
Could not find a version that satisfied requirement PyQt5>=5.11.2 .....
No matching distribution found for PyQT5>=5.11.2 .....

I have Python 2.7.12, 3.5.2 and 3.7.5 installed, Qt5.11.2 was update via repository (from 5.5)