Re: Determining OCFD total length and split points
#circuit
The OCF set of wires is NOT a balauced (differential mode) source/load!
Why use a balun? A balun is a circuit element intended to transform
differential mode (dipole) to common mode (coax). An RF choke consisting
of multiple turns of coax through an appropriate toroid or a number of
clamp-on ferrites on the coax at the feed point are appropriate, but not a
"balun" as such. The proposed "fixes" will choke common mode currents on
the external surface of the coax shield.
Dave - W?LEV
toggle quoted message
Show quoted text
On Wed, Nov 23, 2022 at 12:29 PM Barry K3EUI <k3euibarry@...> 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
-- *Dave - W?LEV* *Just Let Darwin Work*
--
Dave - W?LEV
|
Um sich abzumelden, klicken Sie auf den Link unten in dieser E-Mail, wo es hei?t: Unsubscribe
toggle quoted message
Show quoted text
On 11/23/22 02:12, Peter, DG4EK wrote: 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.
|
Re: Determining OCFD total length and split points
#circuit
On Tue, Nov 22, 2022 at 02:29 PM, Don - KM4UDX wrote:
How can we use the mighty nanoVNA to identify total length of a Off Center Fed
Dipole (OCFD)?
You MIGHT be able to do it with 2 measurements. Use the TDR function to measure one section (lelement) and then the other section. I assume that you would have to reverse the NanoVNA's connection to the co-ax (or other leadin) between measurements. Then compare the difference in lengths. If you have some spare wire and coax, it might be easiest to test the method with some wire and coax at ground level first. -- Doug, K8RFT
|
Mein herzlichstes Beileid... Sie m¨¹ssen die emailgruppe verlassen damit da keine Mails mehr ankommen.
Dg9bfc sigi
Am 23.11.2022 11:12 schrieb "Peter, DG4EK" <info@...>:
toggle quoted message
Show quoted text
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.
|
Re: Determining OCFD total length and split points
#circuit
... You have to feed ocf with a 1 to 4 and a good choke
Measure over a halfwave (or multiple of) cable (to see same resistance as on feedpoint).
Easy as baking cakes.
DJ0IP made several dozen ocfd versions and messured them (different lengths and split ratios).
And he 3xacrly explains that antenna.
Cwntre loaded ocfd adds a few more bands with low swr. So you also should think about that.
Dg9bfc sigi
Am 23.11.2022 15:07 schrieb Jim Lux <jimlux@...>:
toggle quoted message
Show quoted text
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
|
Re: Determining OCFD total length and split points
#circuit
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
|
Re: Determining OCFD total length and split points
#circuit
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@...>:
toggle quoted message
Show quoted text
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.
|
Re: Determining OCFD total length and split points
#circuit
this is a really good article on ocfd at various different places.
seems you can select from about 20% to over 33%.
All depends on your prefered frequencies.
There is no definative 'point' each of us has differing requirements.
My own is aout 1/3 - 2/3 ... but that is as much to fit it into the space(s) available.
Have fun...
|
Re: Determining OCFD total length and split points
#circuit
OCFD puts the feedpoint at 5/8lambda from one end. That would be about 81-82ft for a 80m antenna.
Stephen W9SK
toggle quoted message
Show quoted text
-----Original Message----- From: [email protected] < [email protected]> On Behalf Of Don - KM4UDX Sent: Tuesday, November 22, 2022 11:30 AM To: [email protected]Subject: [nanovna-users] Determining OCFD total length and split points #circuit Hello! How can we use the mighty nanoVNA to identify total length of a Off Center Fed Dipole (OCFD)? Or Normally a 80m dipole is about 130 feet the sides are 130/2. Can the nano measure the total length or the sides? An OCFD moves the split point from 50/50 to some other point. Can the NanoVNA determine or infer the split point? Thank you nanoVNA experts!
|
Determining OCFD total length and split points
#circuit
Hello! How can we use the mighty nanoVNA to identify total length of a Off Center Fed Dipole (OCFD)?
Or
Normally a 80m dipole is about 130 feet the sides are 130/2. Can the nano measure the total length or the sides? An OCFD moves the split point from 50/50 to some other point. Can the NanoVNA determine or infer the split point?
Thank you nanoVNA experts!
|
Re: New topic for the Five County Digi Training Net VarAC V6.2.4
Dear Mr.Berry,
Hiii. Am VU2BOA handle Sam from South India. Just purchased Nanovna - H.
Just wanted to know how the return loss of an antenna is done using Nanovna
-H. Will be highly thankful if you can kindly share.
Kind regards,
VU2BOA - Sam
toggle quoted message
Show quoted text
On Mon, Nov 21, 2022 at 5:52 PM Barry K3EUI <k3euibarry@...> wrote: 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 (
).*
|
Re: Use NANO VNA to make a 90deg phasing stub
Fabulous! Sir thankyou so much
|
Re: Use NANO VNA to make a 90deg phasing stub
This is a perfect application of the nanovna.
If your nanovna has a recent version of firmware, I think 1.1 or better, it
will have a "measure" item on the top menu. Select that, and choose the
'resonance' option.
This puts a resonance display on the screen. Connect the cable stub,
leaving it open at the far end. This enables the vna to see the resonance
of that cable. The first resonance is at 1/4 wavelength, so just trim the
cable until that reads your desired frequency. Make sure to consider the
length of a connector that you will install - but that's not much of a
concern at 7MHz.
If your nanovna doesn't have that measure/resonance function, it is almost
as easy. Just connect the cable in the same way, and set one of the traces
on the vna to display S11 phase. To start, set the frequency range to
something like 50kHz to 15MHz, just to get a feel for what you will see.
With an open-ended cable attached, you will see a sawtooth pattern on the
S11 phase trace. The position where the phase first does a 'zero crossing'
from -180 to +180 (or vice versa) is the quarter wavelength resonance.
Hopefully that is happening above 7.04MHz, and you can now set the top
frequency to something like 7.5MHz, put your cursor on the desired 7.04MHz,
and trim until the zero-crossing is at your cursor. The vna should be
calibrated, of course, as always - but you can calibrate once across the
desired range, say 6-8MHz, and then change the range as noted above to help
see the zero crossing pattern.
Good Luck.
Stan
toggle quoted message
Show quoted text
On Mon, Nov 21, 2022 at 6:22 AM <blake_mulder@...> wrote: If anyone can help with a guide or instructions, I need to cut a 90deg
phasing stub for 7.04mhz using my nanovna. Really didnt see much on
youtube? Can anybody help, please?
|
Use NANO VNA to make a 90deg phasing stub
If anyone can help with a guide or instructions, I need to cut a 90deg phasing stub for 7.04mhz using my nanovna. Really didnt see much on youtube? Can anybody help, please?
|
New topic for the Five County Digi Training Net VarAC V6.2.4
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
toggle quoted message
Show quoted text
*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 (
).*
|
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.
|
Downloaded NanoVNA Saver 5.3 and loaded it on Ubuntu 22.04. Get this error message upon running the app:
Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
Anyone got ideas where to start. My Python version is 3.10.6
Regards
|
OMG OMG OMG...
thank you so much i unbricked my NanoVNA-H4 using the section "FIRMWARE UPGRADE USING NanoVNA-App for Windows
by OneOfEleven" in the absolute begirners guide.
thank you so much again this totally made my day!!
|
Re: NanoVNA-App impedance phase
Hi,
DisLord made a great job again, and S11 works great in 1.2.14.
Uwe, DL4AC
|
Barry K3EUI
Peter, DG4EK
Jon-G0MYW
Stephen W9SK
Don - KM4UDX
N4RFC
Eric KO4ZEK