if I open WSJT-X, transmit on several (two? three? or more) different bands
in succession, eventually this will happen:
Just over two seconds into the transmission on the latest band, the
frequency display in the main WSJT-X window changes from the correct
transmit frequency on the latest band
Glenn,A mode that differs from FST4?Ed N4II.
Original message From: Glenn Williams via wsjt-devel
Date: 12/7/23 1:26 PM (GMT-06:00) To:
wsjt-devel@lists.sourceforge.net Cc: Glenn Williams
Subject: [wsjt-devel] 160m S/N needs advanced mode Hello,FT8 on 160m
pales.WSJT-X op
I had a 6m FT8 JA run using WSJT-X 2.5.0-rc3 today. After the event, I
copied the wsjt_log.adi file and uploaded the copy to my logging program,
where I noticed a curious, deterministic pattern in the RST_RCVD column
[Capture.PNG attached].
These incorrect RST_RCVD values were also in the wsjt
t&c=Global_Internal_YGrowth_AndroidEmailSig__AndroidUsers&af_wl=ym&af_sub1=Internal&af_sub2=Global_YGrowth&af_sub3=EmailSignature>
On Sat, 17 Jul 2021 at 3:49, jan0--- via wsjt-devel
mailto:wsjt-devel@lists.sourceforge.net> >
wrote:
I had a 6m FT8 JA run using WSJT-X 2.5.0-rc3 today.
ct during the JA run, but correct both before and after it.
Ed N4II.
-Original Message-
From: Jim Brown via wsjt-devel
Sent: Saturday, July 17, 2021 6:29 AM
To: jan0--- via wsjt-devel
Cc: Jim Brown
Subject: Re: [wsjt-devel] WSJT-X 2.5.0-rc3 RST_RCVD logging issue
On 7/17/2021 2:59
This sounds like it is related to the "WSJT-X 2.5.0-rc3 RST_RCVD logging
issue" that I reported on this reflector on Fri 7/16/2021 10:45 PM. In the
brief JA-to-NA 6m FT8 openings, it is typical for the JA station to start
with the Tx2 message.
Ed N4II.
-Original Message-
From: Martin Dav
Reino is correct – in the example I experienced (reported in the archives at
https://sourceforge.net/p/wsjt/mailman/message/37321504/ ) the JAs were not
calling in NA contest mode, either.
Since the received signal reports were displayed correctly in the WSJT-X Rx
Frequency window (and repor
If a channelized scheme is introduced to avoid recurrent channel collisions,
care should be taken not to reduce the network throughput. As anyone who
has visited 14.074 lately can attest, for much of the day there is more
channel demand than channel availability -- and other bands are frequently
s
om: Gordon Weast via wsjt-devel
Date: 8/29/21 2:34 PM (GMT-06:00) To:
jan0--- via wsjt-devel Cc: Gordon Weast
Subject: Re: [wsjt-devel] Idea for "frequency
hopping" FT8 to reduce
collisions Ed,When I look at decodes on 20m today, I've seen multiple times
when signals offset by
Phil,
[…] but even then the transmitter would only have to move one or
two SSB channels, and then only on each transmission. I don't see this as a
problem for any modern radio.
+ Indeed, at present the transmission frequency programmed into the
transceiver often is offset
Joe,
FYI, this isn't an isolated incident. Several hams, from NA, SA, VK and ZL,
working to exploit the December-January openings between the Americas and VK/ZL
have tried moving from FT8 to Q65-30A, only to have the same non-decode problem
appear. (I am one of them. For the record, watching
I can confirm problem 1, as it happened to me less than an hour ago, including
the orphaned JT9 decoding application. Running Win 10 on a Lenovo X1 Carbon
laptop. I had been on FT8 for about an hour when it happened.
Ed N4II.
From: Frode Igland via wsjt-devel
Sent: Thursday, October 1
While (unsuccessfully) attempting a Superfox decode of S21DX on 1836 kHz
tonight, WSJT-X V2.7.0-rc7 threw the following error:
Subprocess Error
Subprocess failed with exit code 2
Details:
Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bin -a
C:\Users\N4II\AppDat
Marco,In my case, I changed the Rx frequency parameter from 750 to 1750
because:1. I had forgotten about the discussion on this reflector about this
issue (which was why I submitted a duplicate bug report), and decoded nothing
at 750 and thought
Original message From: Marco Cal
Marco,In my case, I changed the Rx frequency parameter from 750 to 1750 because
I had forgotten about the discussion on this reflector about this issue (which
was why I submitted a duplicate bug report), and decoded nothing at 750 and
thought that frequency I had been given had an off-by-one typ
15 matches
Mail list logo
