开云体育

Yes, I think we need to use payment methods that offer protection for
unscrupulous sellers.
And PayPal is a good example.

?n joi, 24 nov. 2022 la 00:33, John<ve3kkqve3kkq@...> a scris:

I realize that this bit of advice is too late, but always buy from the
OFFICIAL vendor.

I had a similar experience with a "really good deal" on a Chinese VHF
mobile radio.
I was very excited to receive my new rig on the projected delivery date...
disappointment soon ensued.
Investigation soon revealed that my rig was indeed delivered... to an
address in Montreal, Quebec, Canada. I lived in Fort Erie, Ontario, Canada
at that time.
I did not have the presence of mind to cancel the card transaction, so I
was out $50, that should have set off alarm bells at the get-go, does now.

I hope you get the card charg cancelled in time.

John
VE7KKQ

On Wed, Nov 23, 2022 at 2:12 PM Stuart Landau via groups.io <stuartl73=
[email protected]> wrote:

I purchased a model SV4401A 8-inch VNA from eBay seller Hui3165 on Oct

24

because their price was much lower than any other supplier. I followed

the

tracking on SpeedPAK Standard from China to my home. It was supposed to
have been given to the United States Postal Service for final delivery on
the afternoon of November 4, but never arrived; I was there. I checked

with

the postal service and letter carrier the next day and was told that they
never had it.

I contacted the seller immediately but was told that it had been
delivered. On November 6 I opened a case with eBay. On November 11, eBay
said because the tracking said that it had been delivered, they closed

the

case. Not only that, but eBay dropped my transaction on my purchase list

so

that I could not give negative feedback. I told my bank what had happened
and they stopped payment on my credit card. Hopefully, that will not be
challenged by eBay. The seller no longer lists the VNA.

In the meantime, the seller also showed two other negative feedbacks
describing a similar story to mine. The buyers did not receive their
packages and were left "hanging in the wind" during the same time

period. I

believe that the seller had hacked the SpeedPAK tracking. Their tracking
showed an error with the USPS chain of custody. The seller, who currently
has 136 listings has only 48 sales in six months. Their feedback

percentage

now is only 71.4% positive and I am unable to leave my negative

feedback. I

blame both the seller and eBay for how I have been treated.

Please be aware of this seller, or any other who has a very low price on

a

new item, compared to others.

Stuart K6YAZ
Los Angeles, California

I realize that this bit of advice is too late, but always buy from the
OFFICIAL vendor.

I had a similar experience with a "really good deal" on a Chinese VHF
mobile radio.
I was very excited to receive my new rig on the projected delivery date...
disappointment soon ensued.
Investigation soon revealed that my rig was indeed delivered... to an
address in Montreal, Quebec, Canada. I lived in Fort Erie, Ontario, Canada
at that time.
I did not have the presence of mind to cancel the card transaction, so I
was out $50, that should have set off alarm bells at the get-go, does now.

I hope you get the card charg cancelled in time.

John
VE7KKQ

On Wed, Nov 23, 2022 at 2:12 PM Stuart Landau via groups.io <stuartl73=
[email protected]> wrote:

I purchased a model SV4401A 8-inch VNA from eBay seller Hui3165 on Oct

24

because their price was much lower than any other supplier. I followed

the

tracking on SpeedPAK Standard from China to my home. It was supposed to
have been given to the United States Postal Service for final delivery on
the afternoon of November 4, but never arrived; I was there. I checked

with

the postal service and letter carrier the next day and was told that they
never had it.

I contacted the seller immediately but was told that it had been
delivered. On November 6 I opened a case with eBay. On November 11, eBay
said because the tracking said that it had been delivered, they closed

the

case. Not only that, but eBay dropped my transaction on my purchase list

so

that I could not give negative feedback. I told my bank what had happened
and they stopped payment on my credit card. Hopefully, that will not be
challenged by eBay. The seller no longer lists the VNA.

In the meantime, the seller also showed two other negative feedbacks
describing a similar story to mine. The buyers did not receive their
packages and were left "hanging in the wind" during the same time

period. I

believe that the seller had hacked the SpeedPAK tracking. Their tracking
showed an error with the USPS chain of custody. The seller, who currently
has 136 listings has only 48 sales in six months. Their feedback

percentage

now is only 71.4% positive and I am unable to leave my negative

feedback. I

blame both the seller and eBay for how I have been treated.

Please be aware of this seller, or any other who has a very low price on

a

new item, compared to others.

Stuart K6YAZ
Los Angeles, California

I purchased a model SV4401A 8-inch VNA from eBay seller Hui3165 on Oct 24
because their price was much lower than any other supplier. I followed the
tracking on SpeedPAK Standard from China to my home. It was supposed to
have been given to the United States Postal Service for final delivery on
the afternoon of November 4, but never arrived; I was there. I checked with
the postal service and letter carrier the next day and was told that they
never had it.

I contacted the seller immediately but was told that it had been
delivered. On November 6 I opened a case with eBay. On November 11, eBay
said because the tracking said that it had been delivered, they closed the
case. Not only that, but eBay dropped my transaction on my purchase list so
that I could not give negative feedback. I told my bank what had happened
and they stopped payment on my credit card. Hopefully, that will not be
challenged by eBay. The seller no longer lists the VNA.

In the meantime, the seller also showed two other negative feedbacks
describing a similar story to mine. The buyers did not receive their
packages and were left "hanging in the wind" during the same time period. I
believe that the seller had hacked the SpeedPAK tracking. Their tracking
showed an error with the USPS chain of custody. The seller, who currently
has 136 listings has only 48 sales in six months. Their feedback percentage
now is only 71.4% positive and I am unable to leave my negative feedback. I
blame both the seller and eBay for how I have been treated.

Please be aware of this seller, or any other who has a very low price on a
new item, compared to others.

Stuart K6YAZ
Los Angeles, California

Just to check ——
The resonant frequency of any dipole (center fed, OCF, or end-fed) is
determined only but the TOTAL length of the wire, and not be WHERE you feed
it.
(And maybe how high above ground or other nearby conductors).

Altering the feed point location only changes the input IMPEDANCE.
Center feds are typically 30-80 ohms (depending on height above ground).
OCF I’ve seen at 200 to 600 ohms.
End-feds can be thousands of ohms.

Typically you see 1/3, 2/3 split (45 ft, 90 ft) for a 135 ft long wire,
which puts the impedance around 400 ohms.
I think some argue that for a 120-140 ft overall length, based on the
harmonics but you can try different locations depending on the BALUN ratio.

Barry k3eui

Bitte nichts mehr Schicken
mein Mann ist Tod

Am 19. November 2022 15:19:17 MEZ schrieb N4RFC<Bob@...>:

Found the problem. From a post on github () I found that the settings for antialiasing had been depreciated.

By editing /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.xsettings.gschema.xml and removing:

</schema>
<schema id="org.gnome.settings-daemon.plugins.xsettings.deprecated">

Then sudo glib-compile-schemas /usr/share/glib-2.0/schemas. This fixed the problem starting NanoVNA-Saver on Ubuntu 22.04.

Bitte nichts mehr Schicken
mein Mann ist Tod

Am 19. November 2022 15:19:17 MEZ schrieb N4RFC <Bob@...>:

Found the problem.? From a post on github

() I found that the settings
for antialiasing had been depreciated.

By editing

/usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.xsettings.gschema.xml
and removing:

? </schema>
? <schema id="org.gnome.settings-daemon.plugins.xsettings.deprecated">

Then sudo glib-compile-schemas /usr/share/glib-2.0/schemas.? This fixed

the problem starting NanoVNA-Saver on Ubuntu 22.04.

--
Diese Nachricht wurde von meinem Android-Ger?t mit K-9 Mail gesendet.

On 11/23/22 4:28 AM, Barry K3EUI wrote:

Just to check ——
The resonant frequency of any dipole (center fed, OCF, or end-fed) is

determined only but the TOTAL length of the wire, and not be WHERE you
feed it.

(And maybe how high above ground or other nearby conductors).

Altering the feed point location only changes the input IMPEDANCE.
Center feds are typically 30-80 ohms (depending on height above ground).

OCF I’ve seen at 200 to 600 ohms.
End-feds can be thousands of ohms.

Typically you see 1/3, 2/3 split (45 ft, 90 ft) for a 135 ft long wire,

which puts the impedance around 400 ohms.

I think some argue that for a 120-140 ft overall length, based on the

harmonics but you can try different locations depending on the BALUN
ratio.

Barry k3eui

Getting back to the original question - can you use the NanoVNA to
determine where the feed point is in an offcenter dipole:

NanoVNA can easily determine resonant frequency (where X=0).
Once you've got that, you'll know R at the resonance.
The question is whether there is a consistent relationship between R and
"split point"?? If R = 72, then you know it's in the middle of the
dipole.? But If there's droop in the dipole, that changes the R (e.g.
120 degrees gives you about 50 ohms; and diameter of the wires changes
the resistance as you move out.

So the short answer might be "maybe" -
You could build a model in NEC, and then iterate it until R matches what
you measured. Somewhere around, I have a plot of R vs split for a dipole
from a series of modeled scenarios. I'll look for it.

Or you could use 4nec2 or one of the other tools

Found the problem. From a post on github () I found that the settings for antialiasing had been depreciated.

By editing /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.xsettings.gschema.xml and removing:

</schema>
<schema id="org.gnome.settings-daemon.plugins.xsettings.deprecated">

Then sudo glib-compile-schemas /usr/share/glib-2.0/schemas. This fixed the problem starting NanoVNA-Saver on Ubuntu 22.04.

READ BELOW about VAR AC

I would like to suggest that tonight’s *Five County Digital Training net*
(7 pm Nov 21) finishes up our discussion of the *Nano VNA* apparatus. We
have covered the basics over the last few nets: calibration over a
frequency range, measuring reflection coefficient and return loss (dB)
leading to SWR. We covered Smith Charts and dealt with questions about
antenna resistance, reactance, impedance and resonance. I’ve shown some
graphs from my own antennas on HF. We briefly touched on PHASE and what it
shows about resonance.

I always use Nano VNA SAVER to create CAL files and save antenna files.
My Nano VNA is now three years old, and has never failed.

Let’s finish this topic Nano VNA tonight on our net.
Come prepared with questions YOU have about your Nano VNA.
Share your graphs of your own antennas with SCREEN SHARE.

My Zoom link: Monday Nov 21 at 7 pm (will be on by 6:45 pm)



The next topic I would like to explore is VAR AC.
This is a new and rapidly evolving application that offers some tremendous
possibilities, including the new “broadcast” (non ARQ) mode for VARA.

There are TWO VARA modems: VARA for HF SSB and VARA FM for fm (VHF/UHF)

In the next week, please download the latest VARA modem (EA5HVK web page)
and download and install and configure VAR AC for your radio and sound card.
Be careful with the CAT (rig control) and with PTT (send mechanism).
You have a few options depending on your radio and sound card.

If using a SignaLink, your PTT choice is VOX.
Set the DLY know to nearly minimum to shorten the “hang-time” (Tx back to
Rx)

We can continue to use Zoom to talk about this topic, and for those within
a few hundred miles of Phila PA we can use 80m SSB (around 3584 kHz) to
communicate with each other, as well as use 2m FM via the 147.270 and
147.060 repeaters if you live in the Phila area and can hear/hit those
machines.

We may have to adjust the 80m digi frequency based on QRM at the time.
There are a few Winlink stations now operating in the 3580 to 3585 kHz
region, including W1AW Winlink VARA on 3582.5 kHz (VFO dial frequency in
upper sideband mode) and W1AW CW bulletins on 3581.5 kHz. There also are
some NBEMS nets from Midwest as well in the 3582 to 3585 kHz region.

Looking forward to a new topic: VAR AC
Read the description below.

Maybe we can get the author (4Z1AC) to join us soon on a Zoom link (from
Israel) if we meet at a time more suitable for Israel.

73
Barry k3eui
West Chester PA (near Philly)
Nov 21

*Subject:* *VarAC V6.2.4 is here! With Broadcasts (Group chat), Linux/Pi
compatibility, SNR graphs, VarAC RIG profiles, Chat translate and more!*
*Reply-To:* iradirad@...

?

Hi VarACiers! I thought we would take some time off from developing after
the launch of V6 which was a true game changer. But I must admit i

? ? ? ?

? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? ?




































VarAC V6.2.4 is here



With Broadcasts (group chat), Linux/Pi compatibility, SNR graphs, VarAC
RIG profiles, Chat translate and more!














































Hi VarACiers!







I thought we would take some time off from developing after the launch of
V6 which was a true game changer. But I must admit it was hard to keep

our

hands off the keyboard ?







This is by far the richest VarAC release ever. Lots of new features,
enhancements and also huge infrastructure upgrade for future scale.







BUT one of the game changers in this version is the BROADCAST features
which allows you to send asynchronous (non ARQ) messages to one or to

ALL.

This allows for the first time a GROUP CHAT! Broadcasts are using the

same

good old protocol that is used by packet radio and APRS - the X25
protocol.







In addition, beyond the many other new features we developed (see list
below), we also implemented a SQL based database (Sqlite) for Vmails
(first), and soon for other features. Upon startup, VarAC will convert
your existing mailbox from the VarAC_mailbox.mbx file into the new
VarAC.db SqLite DB file.



This opens up huge opportunities, for software developers who want to
integrate their software with VarAC and extend the echo-system. More
features will soon utilize this SqLite DB.







PLEASE UPGRADE:



1. This version requires VARA 4.6.5!



2. Relay notifications only works between VarAC 6.2.4 version.







Now lets dig in:







New features in V6.2.4



*

VarAC Broadcasts - Sending an asynchronous message to a user or to ALL.

(Requires

VARA 4.6.5)


*

SNR Live graph - see SNR reports of you and your QSO partner on a live
graph.


*

Pi/Linux compatible mode - Full support of VarAC on Linux/Raspberry using
WINE. Read THIS (

) for more details.


*

Translation - "right click text -> Translate" in the data stream and it
will show a google translate result.


*

Edit VMails - that are waiting in your outbox


*

VarAC profiles - easily switch between different VarAC configurations for
different RIGs. (Settings -> Switch profile)


*

VarAC Cluster - run multiple VarACs with different ini & rigs while

sharing

resources. Great for VMail relays across different bands. Read THIS (

) tutorial for more details.


*

QSO Summary - showing summary data upon disconnection.


*

Clean VARA buffer - clear a message that is already in the VARA buffer

but

yet to be sent. Requires a VARA license (requires VARA 4.6.5)



















Highlights to some of the new features:







Broadcasts & Clear VARA Buffer





























SNR graphs





























Enabling Linux compatible mode & Block Vmail parking





























Profile switch





























But that's not all. There are many more things that we have changed /
improved in VarAC V6.2.4:







Enhancements/Changes



*

Block VMail parking - Prevent your VarAC from receiving 3rd party VMails
(under settings)


*

Removing personalized away messages to save traffic.


*

Closing com ports upon VARA modem disconnect.


*

Reported ADIF Mode is no longer controlled by the user. It's now hard
coded as DYNAMIC.


*

Showing a warning if trying to start a connection on a busy frequency.


*

Showing a warning if setting a callsign that is too long under "My
information" screen.


*

Small arrows above the frequency indicator are now tied to the slot

system

and will move you between slots.


*

Change in 17m Calling frequency. Moved from 18.106 to 18.107.


*

Allowing the use of <LOC> tags in welcome messages.


*

Reducing welcome message to 50 characters.


*

Reducing max Vmail message size to 300 characters.


*

Mailbox is now implemented using a SqLite DB (VarAC.db file). This opens
new opportunities for software integrations for developers.


*

Not showing non-500Hz CQ/Beacons if intercepted on a calling frequency.


*

Disable VarAC <-> VARA KISS connection with VarAC.ini parameter:
VarahfEnableKissInterface






?



Have fun!



73, Irad 4Z1AC and the VarAC team.




Important note: if you upgrade from an older VarAC version then:

*

YOU MUST Upgrade your VARA version to 4.6.5


*

Download the VarAC Zip file.


*

Unpack to a temporary directory.


*

Copy ONLY the VarAC.exe file to your existing VarAC installation
directory.

















*Download VarAC V6.2.4* (

)
















P.S: With great features, come great bugs... so we did a lot of cleanup

on

some very annoying bugs you've reported:







Bug fixes



*

Locking field on the call-history screen for read-only.


*

VARA-FM - closing the modem screen upon VarAC Closing.


*

VARA-FM - changing the VARA ports automatically based on port numbers
selected in the VarAC settings screen.


*

VARA-FM - Fixing the "WRONG" message on the VARA command log upon VarAC
Startup


*

Mailbox rows where too tight. Extended their height for better
viewability.


*

Added 500ms wait time before queueing up a new message to be sent to
overcome some VARA modem dead locks.


*

Not sending relay notification with callsigns that are longer than 6
characters (AX25 protocol limit)


*

Using the mouse wheel on the slot selector slider now moves one slot at a
time


*

When receiving a VMail with a full callsign (Like 4Z1AC/P) it ended up in
parking and not in inbox.


*

Free form QSY ("#") did not allow a sniffing or QSY to a manually

inserted

frequency.


*

Pausing beacon while sniffing another non-CF frequency.


*

When a corrupted packet is received, performing a clean disconnection.


*

While invited to QSY, and when not using frequency control through cat
(but manually) your VarAC kept showing you are on the CF and killed your
link when CF time limit exceeded.


*

When the CF is busy, and trying to connect on a slot, VarAC didn't let

you

continue with the connect sequence.


*

When disabling Vmail relay notifications, VarAC still changed the

VARA.ini

kiss port number.


















*VarAC website* (

)


























*You've received this email because you are a subscriber of this site (

).*
*If you feel you received it by mistake or wish to unsubscribe, please
click here (

).*