On 7/16/2021 11:33 PM, Derek Turner via wsjt-devel wrote:
Is it just coincidental that of the 33 log records only two contain
Maidenhead locators.
Nope. I've probably worked close a hundred JAs, and I count count the
ones who call with their grid without taking my shoes off. But JA hams
are n
On 7/17/2021 2:59 AM, jan0--- via wsjt-devel wrote:
It is characteristic of this propagation phenomenon between NA and AS on
6m that the opening between any given pair of stations is brief: One or
two minutes is not uncommon.
That depends a LOT on which part of the US and which DX country. He
On 8/1/2021 9:34 AM, Bill Somerville via wsjt-devel wrote:
A grid square does not meet that criteria. OTOH the grid square is not
required by that definition of a QSO.
Horsepucky. A name is a piece of information. So is a State. And a grid
square a IS a piece of information, accepted as such b
On 8/1/2021 1:30 PM, Bill Somerville via wsjt-devel wrote:
read my post again, and also the Region 1 VHF handbook! The term is "QSO
specific" information, a grid is not QSO specific it is general
information about a station. I
YES, a grid IS QSO-specific -- operators move around. Just because
On 8/1/2021 9:13 PM, MIKE LAVELLE via wsjt-devel wrote:
What's wrong with signal reports... lots of us like to know how well we
are getting out.
But signal reports only tell us signal to noise ratio in the other
station's receiver, NOT signal strength. I use WSJT modes on 6M and 160M
to make
On 8/2/2021 5:04 AM, Bill Somerville via wsjt-devel wrote:
If reports were dropped in favour of grid squares the protocols would
need fundamental changes, including a loss of sensitivity, unless all
those non-standard calls were to be excluded from normal QSOs.
RE-READ KF2T's posts. He is not
On 8/2/2021 5:04 AM, Bill Somerville via wsjt-devel wrote:
If reports were dropped in favour of grid squares the protocols would
need fundamental changes, including a loss of sensitivity, unless all
those non-standard calls were to be excluded from normal QSOs.
Does this mean that Contest Mode
On 9/1/2021 11:32 PM, Phil Karn via wsjt-devel wrote:
I don't see that that necessarily follows.
At this point, I think it is appropriate to note that the developers of
this software are VERY bright, have carefully observed how it works in
the real world, test extensively themselves, get lots
On 9/14/2021 10:55 AM, Rich - K1HTV via wsjt-devel wrote:
*"When operating on FT8, I ran WSJT-X and JTDX in parallel. The JTDX
decode capability on weak signals is significantly better - but JTDX
doesn't recognize contest mode. I had several contacts that decoded only
on JTDX so I had to manual
On 9/14/2021 11:43 PM, Laurie, VK3AMA via wsjt-devel wrote:
That has been my experience as well. On the surface JTDX offers a
greater number of decodes, but many were false decodes.
If I made the QSO and it shows up on LOTW, it wasn't a false decode!
And, BTW, WSJT-X is not without false decod
On 9/18/2021 10:08 AM, Joe Taylor via wsjt-devel wrote:
It turns out that Mike, W3IP, was using WSJT-X for FT8 with the
"Decode | Fast" setting.
With nearly any modern computer one should use "Decode | Deep" for
maximum FT8 sensitivity.
Was in the shack today, and checked WSJT-X setting and i
I'm seeing news stories saying aurora visibility is predicted farther
south than usual. I worked AU on CW from Chicago and WV, but have never
heard it here, 70 miles S of San Francisco. Would any WSJT modes be useful?
73, Jim K9YC
___
wsjt-devel mai
On 10/3/2021 7:50 PM, Alex via wsjt-devel wrote:
No 73, no QSO. I really don't care if that means my log will be a few
Q's short. The world is already rude enough as it is. We can take a few
moments to be courteous.
Not when there's short band opening for DX, and not in a contest. :)
When the
Well said, Grant. From where I sit, very active on 6M, and both DX
chasing and contesting on HF and MF, the only poor decisions made by by
the design team are based on their lack of broad experience below VHF.
That's the only possible explanation for how 40M FT4 ended up where it did.
Your com
On 10/10/2021 7:12 PM, Neil Zampella via wsjt-devel wrote:
as F/H specifically requires you to reply to a Fox CQ above 1000 hz, and
since the decoder decodes the entire passband based on the base
frequency set, you would not need any 'waterfall history' to determine
where to Tx your reply.
Su
On 10/10/2021 11:02 PM, Peter Sumner via wsjt-devel wrote:
Rather than extra buttons / tick boxes on the existing busy screen
I hardly see the FT8/FT4 main screen as "busy" -- indeed, I see plenty
of empty real estate for these two tick boxes with labels (or buttons
with labels within the but
On 10/11/2021 2:22 AM, Bill Somerville via wsjt-devel wrote:
that space is basically an illusion. The reason is that the main window
layout is largely shared by all modes and variants, the exceptions to
that are WSPR, FST4W, Frequency calibration, and EME Echo mode. What
appears to be empty spa
On 10/18/2021 12:10 PM, Conrad PA5Y via wsjt-devel wrote:
Well typically Lance asks that if you decode him you start with TX2.
To conserve battery/generator fuel, Lance does not call CQ on
expeditions, directing callers to call blind, and answering those he
copies. In that situation, callers
On 11/12/2021 9:14 AM, Chris Elmquist via wsjt-devel wrote:
I apologize for resurrecting an old thread but I came back to the list
because I continue to have a problem in this very same space.
See the post I just made responding to another ham 2 minutes ago about
grounding and bonding in your
As a very active CW operator, I view this as a VERY BAD move. The
presence of FT4 in that region is a most unwelcome intrusion. I view it
as the only major bad judgement call by the WSJT team.
73, Jim K9YC
On 12/26/2021 7:44 PM, Tsutsumi Takehiko via wsjt-devel wrote:
Hi,
ARRL Letter on 09/2
http://www.arrl.org/news/view/arrl-announces-new-world-wide-digital-contest
73, Jim K9YC
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
On 2/19/2022 4:45 AM, Marco Calistri via wsjt-devel wrote:
Very interesting! I was not aware of the MSHV software, IMHO it's not a
good behavior to use "not standard" software expecting same results as
it should work as per the "standard way".
Fox/Hound mode is NOT a "standard way," it is a v
On 2/19/2022 2:23 PM, Marco Calistri via wsjt-devel wrote:
Amazing explanation of an "historical" and already well identified issue
Grant!
Many of the answers to questions asked here are in the manual for
WSJT-X. To reduce the load on the guys who provide support here,
everyone should STUDY t
On 3/19/2022 9:39 AM, DX Jami via wsjt-devel wrote:
My call is AH6FX and I am in Virginia now. For WSJT-X purposes I
configure or set-up WSJT-X for W4/AH6FX.
Totally unnecessary -- calling CQ or answering with your grid tells
others all they need to know.
73, Jim K9YC (in California since 2
Please provide an option to start a new ALL.TXT for each calendar month,
keeping each month's file and naming it by the month. Without that
option, the file grows so large that it cannot be opened by any software
on my computer.
73, Jim K9YC
___
ws
if the file is larger than a 1GB.
It does not load the file into memory. It can be active while WSJT-X is
active and can display a selected number of
records from the All.txt file while WSJT-X is appending to it.
73,
Sam W2JDB
-Original Message-
From: Jim Brown via wsjt-devel
To
Thanks Stan.
73, Jim
On 7/28/2022 5:12 PM, Stan Gammons via wsjt-devel wrote:
On 7/28/22 18:38, Jim Brown via wsjt-devel wrote:
Please provide an option to start a new ALL.TXT for each calendar month,
keeping each month's file and naming it by the month. Without that
option, the file gro
Thanks Dave. For those reading the mail, DXKeeper is part of his
FREEWARE DXLab Suite.
To the development team -- it seems to me that the time sent to logging
software as the starting time ought to be either 1) the completion time
or 2) 2 minutes prior to the completion time. This solves the "
On 8/24/2022 12:57 PM, Dwayne Sinclair via wsjt-devel wrote:
Sure… All the LOTW awards come with rules.
LOTW does not issue awards. It is ONLY a worldwide log book that the
issuers of awards can consult to document QSOs. Some issuers of awards
are ARRL, CQ Magazine, the County Hunters, the RS
On 9/19/2022 10:25 PM, on4ckt--- via wsjt-devel wrote:
There is an alternative site namelywww.pskreporter.info. This can also be used
in the meantime.
I don't know about www.pskreporter.info as an "alternative" site, but
I've been using it for years for the functions that Adrian is looking
f
On 9/30/2022 1:35 PM, Dave wrote:
JTDX has 2 features I really like. Since I work a lot of DX, the ability to
filter out regions particularly North America is very helpful. The second one
is the transmitting station's country is always listed not just for stations
calling CQ. Any chance th
Hi Saku,
There are logging programs that keep track of contests. I log contests
with N1MM+ (Freeware), export the log to DXKeeper (FREEware), choose
from a dropdown menu in the DXKeeper Import screen what contest it's
from and choose the log file. That's all it takes! And when you're ready
to
On 10/15/2022 2:13 AM, Saku via wsjt-devel wrote:
Linux has Wine, but I do not have any need to run Windoze programs via it.
It seems that you might need it. You're asking for features to be added
to WSJT-X that are in Windows software. An operating system is a tool,
not a religion. Or perhap
On 11/8/2022 1:07 AM, Erik Icket via wsjt-devel wrote:
I observed that confusion as well last weekend when F/H was used on the
regular FT8 frequencies.
Someone failed to study the F/H doc -- WSJT is programmed to NOT use F/H
on standard FT8 frequencies. If it's on regular frequencies, it's NOT
On 1/1/2023 12:59 PM, alawler mudhawk.com via wsjt-devel wrote:
I had an odd situation just now where operating as PP1/WB1BQE, I
attempted to work KB1EFS/2 on FT8. He heard me and appeared to answer
by calling me. I attempted to send back a signal report, but it was
truncated as well.
I kn
On 1/7/2023 2:06 PM, Joe Taylor via wsjt-devel wrote:
You can click on a decode that appears after the next sequence starts.
The program will know which sequence to transmit in.
Yes, and I've found that I'm often decoded starting 3-5 seconds late!
73, Jim K9YC
___
On 2/15/2023 9:05 AM, Fred Carvalho via wsjt-devel wrote:
However I would like to stick on why and how things happened that caused
so much confusion:
I suspect the fundamental problem with FT8 was like the problem with the
trip as a whole -- poor planning. I I couldn't see radials in relative
On 4/23/2023 11:20 AM, Daniel Uppström via wsjt-devel wrote:
Isn't that obvious why he wants more than 16 bits? With a receiver using
more than that it could be possible to eliminate AGC all together and
just feed something with 100 dB of dynamics into WSJT.
If I'm not mistaken, what the origi
On 4/25/2023 7:27 AM, Uwe, DG2YCB via wsjt-devel wrote:
Dear WSJT-X Users,
(WSJTXY.groups.io), where you can discuss technical issues and help each
other with problems.
Thanks Uwe. I think that most of us who were banished were there simply
trying to help out, both with technical issues an
On 4/27/2023 12:28 PM, Glenn Williams via wsjt-devel wrote:
Yes exactly. After hundreds of QSOs and two+ years that's getting old.
But I do really understand the issues with revising good code.
Except for contesting, it has ALWAYS been good operating practice to do
a LOT more listening than t
On 4/28/2023 4:35 AM, Saku via wsjt-devel wrote:
How do you know that?
Of course, thanks to skip zones, we do not, but we know more than if we
hadn't paused to listen. But you chose not to quote this part of my
response, which acknowledged that. :)
> and then to choose a TX frequency that w
On 4/28/2023 7:04 AM, Sam W2JDB via wsjt-devel wrote:
Yes I know exactly what split is in WSJT-X.
And it is confusing to long time hams because it was a very poor choice
of words, contrary to what "split" operation has meant on the HF bands
for at least 70 years. "Split" in the context of ham
On 4/30/2023 4:30 PM, Adrian via wsjt-devel wrote:
Reino, this is where we disagree, as my point is if the vfo frequency
changes, then the 'radio frequency' which I consider the same also changes.
Adrian,
Reino is right, and you are wrong. Nothing personal, just scientific
fact. The frequency
On 5/1/2023 8:31 PM, Black Michael via wsjt-devel wrote:
Nobody owns the definition of split
Mike,
For as long as I've been a ham (68 years) "split" operation has meant
transmitting on a frequency DIFFERENT from the station you're working.
The most common application is for a DX station in a
On 5/1/2023 10:13 PM, Reino Talarmo via wsjt-devel wrote:
2# Limiting the usage of the split word to that most probably was a logical
decision to prevent mixing it to the 'split working', hi! Well, in reality
WSJT was designed for various weak signal modes especially EME and there is
(was) no nee
On 5/6/2023 10:41 PM, Reino Talarmo via wsjt-devel wrote:
This start to be really funny!
There's a saying in the States that "you can't argue with a drunk." A
corollary is that it's a waste of time to one who only wants the world
to tell him he's right.
The story related in your post is per
I strongly disagree, Mike. Bjorn's suggestion to call it Transmit
Harmonic Prevention is a VERY good one, because it describes what the
choice does. It is NOT "split" in the sense it has been used in ham
radio for at least 70 years.
People learn from things being called what they are. Bjorn's
#1 is hardly a benefit, #3 is bogus. #2 is a side benefit, but VERY
secondary, and not the fundamental purpose of the practice.
73, Jim K9YC
On 5/8/2023 7:26 AM, Black Michael via wsjt-devel wrote:
#1 It allows you to transmit outside your passband.
#2 It avoids roll off of power at band edges
On 5/8/2023 10:06 AM, Adrian wrote:
How would you know ? You lack the technical ability..
I'm a Fellow of the Audio Engineering Society, on the basis of a wide
range of technical achievements. Also a member of the Standards
Committee of the AES, Vice-Chair of the WG on EMC, a principle author
On 7/14/2023 10:30 PM, Björn Ekelund via wsjt-devel wrote:
1.30. I cannot believe why anyone would run an outdated firmware on a radio.
Björn,
You vastly overestimate the knowledge of the average ham (at least those
in the US), or their willingness to study more than it took to memorize
the
Team,
I've several times observed in the more public forum that "split" was a
VERY bad word choice to describe the TX shift devised to prevent
transmission of audio harmonic distortion. The practice is great, the
word choice is terrible, because it is in conflict with what has been
standard u
51 matches
Mail list logo
