I would agree to that. I saw one with a P7 call yesterday that looked quite
legitimate. My finger wanted badly to click on it but I said "no, wait...".
Never saw it again. Despite what the nay-sayers claim, FT modes do require some
human thought to get the best out of them. :)
73
-Jim
NU0C
Yes, that improves decoding sensitivity quite a lot and
is useful once you have started a QSO. You may study the
a priori principle in the user guide 12.1. AP Decoding
and in more details in the reference 33,
https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf, especially
Figure 7, Table 6 and Figure 8.
So,
Do you mean that a priori information is used to help decode? That's a
bias. Shouldn't decodes stand on their own?
-73, Glenn, AF8C
On 1/26/2024 12:32 PM, Reino Talarmo via wsjt-devel wrote:
Hi Glenn, congrats about a nice false decode. The 'a3'
tells that the decoder tried as the known
"I have noticed the same thing at times while running as Hound in F/H where
the report from the Fox will appear in the Band Activity column but not in
the Rx Frequency column. I am presently running the "WSJT-X V2.7.1 devel
231031 Improved PLUS" version."
I think I have seen this once with ver
Please place this file as described below
https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
C:\Users\[username]\AppData\Local\WSJT-X
The WSJT-X_Rigcontrol.log file will be in the same location
Here's a youtube video showing Windows users howto --
Check RTS is not set high in program comport settings ?
73
vk4tux
On 27/1/24 01:59, kgross jensalt.com via wsjt-devel wrote:
I’m very confused. I have 2 different XGGcoms digimode 4’s for two
different models of Kenwoods. They work fine with the GA version but
with 2.7.0RC as soon as
I'm very confused. I have 2 different XGGcoms digimode 4's for two different
models of Kenwoods. They work fine with the GA version but with 2.7.0RC as
soon as the wsjt-x software is loaded and accessing the radio viat CAT control,
the radios go into TX, (ts-2000 and tx-480). I knew I had
I saw a call from North Korea from the same locator tonight. Someone
playing silly games perhaps with MW DXCC.
73
vk4tux
On 27/1/24 03:32, Reino Talarmo via wsjt-devel wrote:
Hi Glenn, congrats about a nice false decode. The 'a3'
tells that the decoder tried as the known information
your
Okay, then let's continue to observe whether we can find a pattern under
which exact conditions the unwanted effect occurs. As said, the
F/H-related part of the code in v2.7.0-rc3 (regular version) is
identical to the i+ version. This should therefore make no difference.
73 de DG2YCB,
Uwe
Hi Glenn, congrats about a nice false decode. The 'a3'
tells that the decoder tried as the known information
your call, DX call, and rest is decoded. The '?'
indicates that the probability of correct message is not
too high.
Also the contents of the decoded part is suspicious as
the report is
I saw the same behavior over the past few days while working TX5S.
I am running 2.7.0-rc3 (regular version) not the improved version.
My first thoughts were that it was due to the Rx green goalpost in the
waterfall being over a different stream than the one sending the response.
I have no means
#1 That's a false decode (detectable as a funky message)
#2 Not on the Fox offsets. Fox never transmitted at 474
Mike W9MDB
On Friday, January 26, 2024 at 11:19:40 AM CST, Glenn Williams via wsjt-devel
wrote:
I am reporting here another issue with my TX5S QSO and the FT8 windows
No...it just appends the file. Size doesn't matter as the saying goes...
Mike W9MDB
On Friday, January 26, 2024 at 11:10:08 AM CST, Glenn Williams via wsjt-devel
wrote:
So,
Once upon a time I asked a question and the gurus had an answer (V2.2.2
I think).
My question was about
I am reporting here another issue with my TX5S QSO and the FT8 windows
that happened last night. (Previous report is under "Subject:
[wsjt-devel] skips RX frequency window (bug?) wsjtx-2.7.0-rc3".) I am
also NOT confirmed in ClubLog!
My screenshots with iPhone are in
So,
Once upon a time I asked a question and the gurus had an answer (V2.2.2
I think).
My question was about "how does FT8 keep huge files open and still keep
up with the band activity while updating huge files". Today's question
is about that. ALL.TXT has grown really large. Is there a
I had the same thing happen as with Fred. Improved rc3 for Mac M1Sent from my iPhoneOn Jan 26, 2024, at 11:00 AM, Fred Price via wsjt-devel wrote:
Screenshot of it happening to me with TX5S.
On Jan 26, 2024, at 10:51 AM, Uwe, DG2YCB via wsjt-devel wrote:
But it worked also when I
But it worked also when I set my Rx QRG manually 275 Hz next to the Fox
offset.
73 de DG2YCB,
Uwe
German Amateur Radio Station DG2YCB
Dr. Uwe Risse
eMail: dg2...@gmx.de
Info: www.qrz.com/db/DG2YCB
Am 26.01.2024 um 16:44 schrieb Black Michael:
Perhaps
Perhaps when the fox offset for your callsign changes?
I think I've seen that.
On Friday, January 26, 2024 at 09:15:37 AM CST, Uwe, DG2YCB via wsjt-devel
wrote:
Hi Rich,
Last night I ran some tests with our good old standard WSJT-X (latest code)
using three instances all
Rick,
Just completed the same test with the i+ 2.7.1-devel "240202" code.
Identical results as with our standard WSJT-X v2.7.0-rc3 (not
surprising, since this part of the code is identical). Not a single
issue, all messages to the own callsign were displayed correctly in the
right window. So, I
Hi Rich,
Last night I ran some tests with our good old standard WSJT-X (latest
code) using three instances all connected via virtual audio. One in FT8
Fox mode and the other two in FT8 Hound mode. Then I simulated just such
QSO situations, but each time the reports appeared in the right-hand
I have noticed the same thing at times while running as Hound in F/H where
the report from the Fox will appear in the Band Activity column but not in
the Rx Frequency column.I am presently running the "WSJT-X V2.7.1 devel
231031 Improved PLUS" version.
Also, when the "Start new period decodes at
21 matches
Mail list logo
