开云体育

If you want to use NanoVNA app you have to be using a recent version of the firmware (last year or so). The reason is that NanoVNA app uses the binary (not ASII) transfer protocol to transfer data.

If you try to use old firmware it will connect but the app will not do sweeps.

Roger

On Mon, May 16, 2022 at 11:40 AM, k6whp wrote:

How does one specify COM10 -- which is what my NanoVNA uses?

You select the COM port from the drop down list. Then press button below to Connect.
You need to select where calibration is done from the drop down list.
You can transfer Stimulus range settings from NanoVNA to app by pressing button on left.

Attached screenshot shows where to click...

Roger

Yes indeed, thank you. Stunning app.

How does one specify COM10 -- which is what my NanoVNA uses?

--
William, k6whp
--------------------
"Cheer up, things could get worse. So I cheered up and things got worse."

..well, figured out how to flash the firmware with the app and, thanks to help here, I was able to do a cal first in order to make the new firmware retain the config I set up. My original goal is to brighten up the faint grid lines and am given to understand that this can be done via console commands in lieu of the missing "BRIGHTNESS" option on previous firmware.

I am using PuTTY to connect and having no success. It has been set up as a serial connection to COM10 (checked with my Windows 7 device manager) and the parameters are the same the as the app parms (shown in the attachments below). Each time I attempt to open the connection I get the missing file error message per the error message attached

Appreciate any help.
--
William, k6whp
--------------------
"Cheer up, things could get worse. So I cheered up and things got worse."

Thanks, Roger!

?n lun., 16 mai 2022 la 19:29, Roger Need via groups.io <sailtamarack=
[email protected]> a scris:

A very useful PC application for the NanoVNA was developed by One Of Eleven as an alternative to NanoVNA Saver and other earlier programs. It was originally done for personal use but was kindly offered to the community. After development was stopped by the author the source code was released so that improvements could be done by others.

The program is easy to use and has many nice features...
- Multiple graphing options and flexible scaling options.
- Calibration works reliably and includes averaging and smoothing options
- Built in firmware uploading tool that is easy to use
- Continuous run mode which is useful for tuning filters and antennas
- Four memories that can be used to compare results in the graphs
- Export and Import of Touchstone files (s1p and s2p)
- Multiple marker capability with various display options.

DiSlord and Owen Duffy have made several recent improvements and bug fixes. The updated program can be downloaded here >>

The program is mouse driven and by right clicking on any graph you can change the tiling options (# of graphs on screen) and the type of graph (SWR, RL, Reactance, Smith etc.).

Please post any questions about how to use the program in this topic.

Roger

William,
I will answer your second question:
You can find a lot of information about the upgrade in the forum wiki and you can also visit my website where I try to gather current information.

--
Gyula HA3HZ ( )

Rich,

BINGO! Thank you!

..I'm off on my journey -- beginning with RTFM. Wish me luck!

--
William, k6whp
--------------------
"Cheer up, things could get worse. So I cheered up and things got worse."

Your unit is a NanoVNA-F model. Try sending your query to this Groups IO

[email protected]

*Clyde K. Spencer*



On Mon, May 16, 2022 at 10:14 AM Team-SIM SIM-Mode via groups.io
<sim31_team@...> wrote:

Here is My attached Photo

Here is My attached Photo

It may be that a calibration is not stored in memory 0, so when the unit starts, it starts uncalibrated, and that could cause a display with a lot of unusual activity.
Could also be that the device is using the wrong clock chip mode. There are 2 versions, and if you have an earlier hardware platform (sounds as if you do), then you should be running the Si MODE. (look on the back of the nVNA. if it has _MS in the model, you have an MS device; else you have an Si device) Go to EXPERT SETTINGS, and confirm that the button says Si----. If it says MS----, tap it and change it. Then do a cal over some range...I usually do 50k-900M, and store that in location zero. that way when the device start, it will use a calibration.
--
~R~
72/73 de Rich NE1EE
The Dusty Key
On the banks of the Piscataqua

On 2022-05-15 18:12:-0700, you wrote:

I replied to your post on this issue a few days ago but you did not reply. Did you see my post?
/g/nanovna-users/topic/91082901#28066

Yep. Del the ini file.
"In order to get faster sweeps the display was frozen on the NanoVNA"
I guess I have a second or two here and there... ;-) I am not bothered by sweep speed. I appreciate faster anything (almost ;-), but the H4 on bandwidth 100 is not too slow for me. 'Course I guess if I were spending hours with it, I'd appreciate any speedup....

Jim Lux mentioned editing the ini file, which had not occurred to me...I'll look into that.

On 2022-05-15 18:06:-0700, you wrote:

Saver defaults to 101 points to maintain compatibility with older NanoVNA devices. I just go into Manage and set it to 401 points.

Didn't work for me, per email

Seems to work fine for me. What version of H4 firmware are you using? Which version of Saver?

nVNA-H4 v4.3_MS, firmware 1.1 , Saver 0.4.0, and your mod

I think that is the best way to use Saver. Just power up the NanoVNA and use slot 0 so the same cal data is loaded every time. I keep slot 0 at 50 kHz. to 900 MHz. Then connect to Saver. That way when Saver calibrates it has the same NanoVNA configuration and you can reload the Saver calibrations at a later date. When I disconnect from Saver I power down/power up the NanoVNA because Saver leaves the NanoVNA in an unknown state. Saver supports multiple hardware versions of the NanoVNA and the software developers decided not to try and restore the NanoVNA to the state when it was initially connected.

Yep. That long explanation is what I don't want to bother with.

I use the forked version by Owen Duffy because he fixed some bugs.

I don't because it does not work standalone as the other programs do. Personal preference.

On 2022-05-15 16:19:-0700, you wrote:

noted some inconsistencies when trying to set it for 401 pts on the H4 (it works better if I let it use 201 or 101 pts and then let Saver control additional segments for more points).

Not fond of "inconsistencies" here...but I see the point you make...

But please note that many of us who use it want Saver to be in control, <snip> And we do any required setup through Saver.

Problem for me is what I described in my email...the out-of-sync nature of the Manage dialog and its unpredictable (to me) behavior. If it works well for others, that's fine...it doesn't have to meet my expectations...but I was irritated when I wrote the email. Not using Saver should help w that :-)

If you haven't tried nanovna-app, you may find you like it better.

I have. I do. I don't expect perfect software at this level, but I like to be able to predict how it will behave, and not remember a bunch of steps. I documented that its behaviour is inconsistent. Being in control is one thing, and I appreciate that. And of course, the usual guessing game for newbies, because there is no good user manual that I have seen.

~R~

On 2022-05-15 07:20:-0700, you wrote:

Electrical tape as a 'condom'. Put them in separate places could control mating.
--
KT0TT
Allen Kiddoo

As long as there are no unwanted SMA connectors, I don't want to stick my nose in their personal affairs. ;-)

~R~
72/73 de Rich NE1EE
The Dusty Key
On the banks of the Piscataqua

..and looking to orient myself. Have a NanoVNA H as well as a NanoVNA H4 but this query is about the "H" only. I flashed the firmware with a DiSlord clone (v1.1.01 (Build Dec 30 2021) after having done the same with the DiSlord v1.0.38 version.

After getting everything set the way I want it, I power down the "H" unit and power it back up and it reverts to the original psychedelic flashing phantasmagora that frankly looks like the unit is going ape-****. How does one retain the preferred config versus the firmware original default?

Second question: I upgraded the firmware from a v0.4.0-something version and am wondering is there a similar version to the v0.5.0 version? If so, where might that dfu reside.

Thanks.
--
William, k6whp
--------------------
"Cheer up, things could get worse. So I cheered up and things got worse."

On Sun, May 15, 2022 at 03:01 PM, Rich NE1EE wrote:

That's just wrong.
Every time it connects, it reset the H4 to what someone else thinks it should
be. The user should be the one to determine that. I even changed the Manage
settings to agree with my device.
1. I could not change them until I had connected. Not good.
2. Even after connecting, changing settings, disconnecting....changed them
back to some default.

I don't think I'll be using Saver much. Too many problems and bugs.

I replied to your post on this issue a few days ago but you did not reply. Did you see my post?
/g/nanovna-users/topic/91082901#28066

Roger

On Sun, May 15, 2022 at 04:20 PM, Stan Dye wrote:

Yes, saver has some bugs. In particular I have noted some inconsistencies
when trying to set it for 401 pts on the H4 (it works better if I let it
use 201 or 101 pts and then let Saver control additional segments for more
points).

Saver defaults to 101 points to maintain compatibility with older NanoVNA devices. I just go into Manage and set it to 401 points. Seems to work fine for me. What version of H4 firmware are you using? Which version of Saver?

But please note that many of us who use it want Saver to be in control, and
do not want to worry about what state their device was left in before they
attach it. And we do any required setup through Saver.

I think that is the best way to use Saver. Just power up the NanoVNA and use slot 0 so the same cal data is loaded every time. I keep slot 0 at 50 kHz. to 900 MHz. Then connect to Saver. That way when Saver calibrates it has the same NanoVNA configuration and you can reload the Saver calibrations at a later date. When I disconnect from Saver I power down/power up the NanoVNA because Saver leaves the NanoVNA in an unknown state. Saver supports multiple hardware versions of the NanoVNA and the software developers decided not to try and restore the NanoVNA to the state when it was initially connected.

You obviously have a different idea/use case. If you haven't tried
nanovna-app, you may find you like it better. In that app, you need to
understand that the many graphing and charting options are only seen after
right-clicking on a graph pane.

NanoVNA App by One-Of-Eleven is my preferred PC program for the NanoVNA. Better graph scaling and more features. I use the forked version by Owen Duffy because he fixed some bugs.


Roger

Yes, saver has some bugs. In particular I have noted some inconsistencies
when trying to set it for 401 pts on the H4 (it works better if I let it
use 201 or 101 pts and then let Saver control additional segments for more
points).

But please note that many of us who use it want Saver to be in control, and
do not want to worry about what state their device was left in before they
attach it. And we do any required setup through Saver.

You obviously have a different idea/use case. If you haven't tried
nanovna-app, you may find you like it better. In that app, you need to
understand that the many graphing and charting options are only seen after
right-clicking on a graph pane.

Stan

Hi
I have this hardware on this attached photo.

All seems running as expected except for the touchescreen , it's arratic .
i tryed to calibrate it , test function still showing erratic behavior and the menu is hard to handle.

Any help will be appreciated .
73's Nizar