¿ªÔÆÌåÓý

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

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)


Re-using Mobile Phone Batteries - Instructables article #batteries #battery

 

Folks,
There have been a number of concerns raised regarding the charging circuit used in the Nanovna.

A number of forum members also wanted to know what other batteries might work in the unit.

I've commented previously on how to re-use existing mobile/cellphone/tablet/radio batteries and I have done so on many of my projects.

As an avid follower of the various projects on the Instructables.com website, today's Instructable's newsletter came with yet another person's take on re-using these cells.


As always, due to the unique properties of lithium batteries, care must always be observed.
**Please address any questions to the author of the article on the Instructables website.


Re: Still Looks For A good Unit

 

hamrad45,
Instead of the old model, I would purchase hugen's latest NanoVNA-H, such as this one at Amazon, .

For about the same price as the older model you will be reviewing a unit that:
1. Has more recent firmware installed that allows operation to over 1000 MHz.
2. Has the TDR option installed.
3. Allows DFU mode to be accessed in firmware which makes upgrading easier.
4. Has the diode already installed that allows battery level display.
5. Has a more finished appearance with a molded case which provides an extra level of protection.
6. Has the USB-C termination resistors installed for more reliable operation with USB-C to USB-C.
7. Comes with an extra USB-C to USB-C cable and better through standard.

Again, this is pretty much at a cost that is comparable in in some case lower than the older version.

- Herb


Re: Batteries

 

On Wed, Nov 20, 2019 at 06:37 PM, Andy wrote:

Typically 650ma on an empty 400ma supplied cell, oh dear !!!

Before I did the test, I also measure the current on a supposedly charged
cell, and it wasn't actually any different.
Hi Andy

- How did you determine "charged"? LED not flashing?

- What did you measure the current with?

- What was the charge source? USB or something else? Need spec please.


Re: Still Looks For A good Unit

Jeff Davis
 

Yes¡­ that¡¯s the one to buy¡­ I got the kit with the attenuators. Sometimes they are necessary when the results are too large to fit on the screen. Jeff ve3ak

On Nov 21, 2019, at 7:32 AM, hamrad45 <hamrad@...> wrote:

I would really like to get one of these units to review on my YouTube channel but their are many to choose from and so many dealers. Here is one I found today. Can any one tell me if this is a good one or not. I prefer getting one on Amazon as they have easy returns.



If the link does not work, it is sold by onebird for $59.99.

Thanks for your time and help,

Tom Stiles, YouTube ID - hamrad88


=================== Jeff - VE3AK =====================

"It is not the class of license that the Amateur holds but the class
of the Amateur that holds the license"


Still Looks For A good Unit

 

I would really like to get one of these units to review on my YouTube channel but their are many to choose from and so many dealers. Here is one I found today. Can any one tell me if this is a good one or not. I prefer getting one on Amazon as they have easy returns.



If the link does not work, it is sold by onebird for $59.99.

Thanks for your time and help,

Tom Stiles, YouTube ID - hamrad88


Re: data outside expected valid range

 

Thank you very much,
That got rid of my port ERROR - Tried to open /dev/ttyACM0 and failed

I still have gibberish being swept up
more work to do,
Nels

On Wed, Nov 20, 2019 at 8:32 PM k9wkj <k9wkjham@...> wrote:

sudo usermod -a -G dialout $USER

replacing $USER with your user name



--




n_n


Re: Batteries

Brian Ray
 

Larry, thanks for the translated sheet for the FM9688. This sheet refers to there being 4 programmable charging currents. The two lowest might be appropriate for the NanoVNA with original battery. BUT nowhere does the spec sheet say how it is programmed. The assumption is that one needs to specify this to their factory at the time of purchase. Very little chance of sorting this out when buying one or ten through Ebay!

Brian. 5B4AHW

On 19 Nov 2019, at 18:57, Larry Rothman <nlroth@...> wrote:

I'm wondering if hugen is able to verify that the replacement battery control chip he is thinking of using will prevent over charging any cells.
I've translated and attached a copy of the FM9688 Mobile Power Management IC spec sheet.

On Tuesday, November 19, 2019, 11:17:19 a.m. GMT-5, Nick <g3vnc@...> wrote:

On Mon, Nov 18, 2019 at 01:58 PM, RFy wrote:

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

My battery already swelled( PCB/LCD curved slightly )
Yes. This issue has been reported before (posts #3096, #4533, #6288 etc.)

Supplied nvna battery spec is here...


Maximum Charging Current specified as 450mA.

IP5303 Charging current specified as 1.2A typ and 1.4A max. There does not appear to be any way to reduce this without additional circuitry.

So worst case the 450mAh battery might be charged at 1.4/0.45 = 3.1C !

Qualifies as ultra fast charging...



Charge rate might depend on the source. If the nvna is being charged from a standard downstream USB2 port, such as those fitted to this computer, then the charge current could be limited to 500mA which is ~1.1C.

Might explain why my battery was fine until I subjected it to an iPad charger!

Looking longways on the nvna I can see that the pcb and rear panel are deflected by the battery swelling. Easily verified by removing one screw in the rear panel where a gap opens up between the panel and the brass spacer.

I have now removed the 450mAh battery and temporarily fitted a 1100mAh ex call phone battery stuck on the rear panel.

I will fit a "quality" protected 18650 cell when I assemble the repackaged nvna.





<FM9688 Mobile Power Management IC.pdf>