开云体育

where the hell do i find these?,there is no drivers section on the wiki files section,seems a pisspoorly organised site!!

On Sat, 30 Nov 2019 at 09:51, DJ7BA <dj7ba@...> wrote:

By googeling for some term, without being registered, you will get
groups.io messages without any problem.

So even as groups.io is thought to be group-private: It isn't.

If you don't like that, imho you have no choice except not writing
anything of any private nature.

Hans
DJ7BA

But the group the group is configured as:

Visibility: Group listed in directory, publicly viewable.

But I don’t see any reason that the *content* messages should be hidden
from Google. Removing email addresses does have some merrit.

I suspect that individuals have a set of privacy settings that they can
configure for themselves.


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

By googeling for some term, without being registered, you will get groups.io messages without any problem.

So even as groups.io is thought to be group-private: It isn't.

If you don't like that, imho you have no choice except not writing anything of any private nature.

Hans
DJ7BA

-----Ursprüngliche Nachricht-----
Von: [email protected] <[email protected]> Im Auftrag von David Feldman via Groups.Io
Gesendet: Samstag, 30. November 2019 01:09
An: [email protected]
Betreff: Re: [nanovna-users] CAUTION: Phishing Attempt !! #phishing #malware

(from list co-owner) -

As the initiator and one of the two co-owners of this list, I have configured the list to maximize user privacy to the best of my ability and understanding. With about 2800 members since June, it isn't practical to screen each new e-mail address that arrives (many look plain weird, but then again as I've discovered, it's a way to be creative!)

That said, I share below the group's privacy configuration in force since day 1, and seek any practical input from any list member regarding security or privacy concerns going forward. Should you wish to contribute recommendations regarding privacy and security configuration, I urge you to reply in "private" mode (or send a message to [email protected]) unless you are certain your input is directly germane to the nanovna, as I seek to keep S/N here maximized - I don't want to launch into a long generic thread on privacy or security, and will stop threads that diverge from issues that are of immediate and direct concern to *this* group and the nanovna.

This group is and has been since inception (June 2019) configured as follows re privacy:

Visibility: Group listed in directory, publicly viewable messages

Member Directory: Moderators and Owners (who can view the member directory, there are exactly two people fitting that classification)

Members Visible: Owners only (who can view the list of members; the same two people)

Hide Email Addresses In Archives: Mask all e-mail addresses in archives

Thank you for your interest in and support of nanovna-users on groups.io.

Dave

On Sat, Nov 30, 2019 at 09:04 AM, Andy wrote:

On Sat, Nov 30, 2019 at 04:28 AM, Roger Need wrote:

I tried to hook it up to my Windows 8.1 PC and ran unto problems.

It's Windows, what else do you expect ?
Meanwhile in Linuxland...drivers..we don't need no stinkin' drivers ;-)

- Andy -

yeah Andy,
do you think everyone is a pc guru?
people come here to ask for help, not education.
Successful use of linux until the first downfall. :D :D

73, Gyula

Use Zadig 2.4 to get USB STM32 downloader driver and STM32CubeProgrammer
for downloading the nanovna firmware 0.5.2 into the device.

Op za 30 nov. 2019 om 09:04 schreef Andy via Groups.Io <punkbiscuit=
[email protected]>:

On Sat, Nov 30, 2019 at 04:28 AM, Roger Need wrote:

I tried to hook it up to my Windows 8.1 PC and ran unto problems.

It's Windows, what else do you expect ?
Meanwhile in Linuxland...drivers..we don't need no stinkin' drivers ;-)

- Andy -

Interesting...

Over the past week I have casually reviewed various Li-Ion data sources, and I've seen surprising variations.

Up until recently, I had assumed that it was typical to charge a Li-Ion cells at 0.5C.

It appears that depending upon individual manufacturers chemistry variations, that you could expect to be informed
that they will recommend anything from 0.5 to 2.5C !!

But the average is 0.8C.

I'm not convinced that I need to be in a rush to change my own supplied NanoVNA cell.

The specsheet on the VNA indicates anything from a 300-500ma cell, which when supplied may have been sitting
around for a year or two in partly of even fully discharged state before being fitted into a NanoVNA.

Given that expectation, and the current draw of the vna anyway, I'm seeing 2.5 hours of use from a single charge
and no apparent overheating or explosions (!).

Of course, in due course I may see a variation in performance and change my mind ?

Not sure if I'm one of the luck ones, but I've had good fortune with my VNA (Black non Gecko)..

I bought it, it worked, seems as accurate as can be, was dead easy to re-box and just sits there ready for use
when I need it. Perfect !

- Andy -

Hi Roger,

The device manager shows the driver when it is working properly. There are more ways to see what's hidden. What I recommend is a utility called USBDeview, which shows you what driver programs have been installed on your computer since your operating system is running.
You can read the usage at the download site.

Green candidates at the beginning of the line are in use. Once selected, the right mouse button will bring up a menu and select what you want to do. It is advisable to remove any unknown drivers and then reinstall en.stsw-link004 (ST-Link Utility) or stsw-stm32080 (DfuSe), which will install the drivers as well. You may need these programs during firmware upgrade.
Successful use.

73, Gyula HA3HZ

Yes,I have done the same.

1st test was my Tecsun PL660. The input was about 500 ohms through the external antenna socket.
Spec sheet for the SDR chip said about 600 ohms, so that seems in order, since it's a typical broadband result.

NOTE - The RX needs to be powered ON, or else the active device impedance will change.

Just for fun I measured a few of my HT's.

A very cheap and nasty Baofeng UV3R had a typical input impedance of only 11 ohms.
A Baofeng UV5R varied between about 33 ohms to 100 ohms. Oh well, a nominal 50 ohms then ;-)
A Yeasu VX7R was pretty close to 50 ohms, but still had quite a bit of variation.

It's what I expect really, for price, "widebandness" considerations and what is really expected from this class of radio.
Most RX inputs are rarely 50 ohms anyway, unless you are purchasing monitoring equipment and you're a govt agency.
So don't expect 50 ohms dead on for a consumer rig.

- Andy -

Roger,
Checkout the "Drivers" section of this group's "Wiki" page, /g/nanovna-users/wiki/home .

-Herb

ajparent1/kb1gmx wrote:

For now its in a sloggy laptop running MINT-19.3.

So go to the local electronics recycler, junk store, or pawn shop, friend's junk pile, or whatever, expend maybe $20 or $30 for something the pawn shyster can't sell because it won't play the newest P.o.S. Winsucks game, and install a current version of Linux on it with a current version of Python.

Nano-Saver install, and you're copacetic.

Being an Illinois State retiree (University retirement for me, Teacher retirement for my wife), I am all too aware that $30 may be a lot of money some months. But a couple of pay-checques holding back ten or so clams each, and you're golden. That's how I do it.

To send this email, I am using a salvaged Panasonic CF-30 Toughbook (scavenged fro the Springfield, IL police department when they dumped them all for new models) for my main day-to-day communications and Nano device. It cost me some clean-up and rehab time (cops aren't exactly tidy in my experience, and my little brother retired from the IL State Police, so I know of what I speak here), and it does everything I need (including Nano), for a grand total of about $45. That includes a memory upgrade, for completeness' sake.

Money doesn't need to be an obstacle. If there are other road-blocks, I suspect they can be gone around with sufficient gumption and a little thought.

--
wwill
n9kdy

I just received delivery of a NanoVNA-H and it works well stand-alone.

I tried to hook it up to my Windows 8.1 PC and ran unto problems. The driver is not able to install so I can't connect to NanoSaver.

Under device manger I find it under Other Devices as ChibiOS/RT Virtual COM port. When I right click under properties I get the following:

"The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver."

I tried updating the driver but no luck.

Anyone have an idea how to fix this or where to get the driver?

I bought one at a very low price from Walmart.? It was shipped promptly and works perfectly.? It did not come with the usual two coaxial cables but otherwise I am happy with it.? The 50 Ohm load is very close in value.
So price isn't necessarily the clue of quality.
Bob

I have received feedback from multiple resellers, and a new clone manufacturer is selling them low-quality NanoVNA clones at a lower price. They have not tested before leaving the factory, and they do n’t know the role of the calibration parts, or even provide Wrong calibration, you may need to contact your reseller to confirm that the device is correct.

hugen

If your trying to test an antenna against a small ground plane anything attached to the
test setup extends the ground plane side of the antenna. The ground plane for a
monopole is effectively the other half of the antenna.

So at 170 mhz that small piece of copper clad is anything but an effective ground plane.
I'm surprised even if you are running on battery that moving hte VNA around does not
change things. Also that vise is likely part of the system as well.

Likely you have read about it but never associated it with how antennas interact with
the environment. Simple case is height of dipole above ground will impact the feed
point impedance. Or vertical antennas over variable ground (earth with many or few
radials) will reflect different impedance.

So you must apply choking to the coax feeding the antenna to keep the shield of the
coax and even the metallic parts of the VNA from becoming part of the measurement
circuit (antenna under test). Of course if the antenna will have a radio with coax
attached then you need a dummy radio with typical coax attached and in the typical
use environment. FYI a dummy radio would be a cardboard box covered with copper foil
of the approximate size and shape of the typical radio. From there a very heavily
choked cable to the VNA.

Allison
-----------------------------
I don not accept private email due to forum scraping groups.io

ajparent1/kb1gmx wrote: As an old programmer that ran unix-V6 current keeping old software alive especially when well debugged is sometime a very valuable thing.

I wrote a lot of useful DOS-based Quick BASIC programs many years ago but nowadays needed DOSBox to run them under Windows. Today I discovered that QB64 running on my Windows 10 PC will take those BASIC source files and turn them into .exe files that will run on Windows 10. It's like discovering a long, lost friend. :-) www.qb64.net

Hello Ulrich
I look s like you load is not 50 ohm. In the calibration you tell the NanoVNA is at center position whatever value it has
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af UlrichKraft
Sendt: 29. november 2019 18:05
Til: [email protected]
Emne: [nanovna-users] Calibration artifact at OPEN #calibration

Hello user group,
I just realized having a problem with calibration OPEN

Going through the device calibration process and everything goes well and I save data at Cal-x

However when I check S0 on SmithChrt it doesn't show OPEN correctly.
The marker should be far right at infinite. However it circles somewhere between 50@ and infinite.

It does not matter if I clibrate directly on the SMA connectors or having a cable in between, effect is the same.
It also doesn't matter whether I leave S0 completely open or having an OPEN-standard connected.

Is something wrong with that device, or does someone know that effect?

Hi Betex
This is quite simple to understand why as the cable from you feeding point of the antenna incl. the NanoVNA with or without the USB cable is constituting a sort of dipole where the whip under test is one half of the dipole and the test cable ++ is the other half. The measurement is for the "feeding point of the "dipole" and remember the current for the VNWA TX signal is running only in the center conductor and the inside of the cable screen. The outside of the screen of the testcable an the outside of the UCB cable wires and coupled to the whip antenna.
So mount the NanoVNWA on the underside of the "ground plane directly to the "feeding point" raise the vertical whip to 90 degree to the ground plane lay yourself flat on the floor hold the ground plane with both hands and let the whip point vertical up and have fun seeing a real measurements. Raise and lower you arms and see if you corps has an impact on the resonance.
Have fun
Kind regards
Kurt

-----Oprindelig meddelelse-----
Fra: [email protected] <[email protected]> P? vegne af betex
Sendt: 29. november 2019 14:58
Til: [email protected]
Emne: [nanovna-users] USB connection affecting measuring vertical ground-plane antenna #usb #calibration #measurement

Hi,
I try to use NanaoVNA for measuring a vertical ground-plane antenna at 170MHz for later impedance matching.
A picture of the test setup is attached.
Connecting NanaoVNA to USB affects the measurement quite much, as you can see on the pics (max scale for VSWR here is 10).
Does anybody made the same experiences, as I never read about this being a problem?

The NanaoVNA has been calibrated with the same wire, as attached to the antenna and all calibration points (open, close, load) show the same values on the display, no matter if USB is connected or not. But attached to the antenna, the measurement shows quite different results.
And I'm not really sure if the results are reliable, even with unconnected USB.
The antenna should physically (length of the whip) have an VSWR minimum at 170MHz and not a peak (USB not connected).
Connected to USB, the result makes more sense to me, but I don't know which result to trust.
Any ideas what I'm missing or what I can do?

I have two NanoVNA devices from different suppliers, which both show the same results.

Many thanks!

if calibration is ok, then also possible defect in OPEN load. Try to calibrate with open connector instead of OPEN load.

did you performed CAL => RESET before calibration?