@lists.sourceforge.net]
Sent: Monday, August 02, 2021 4:01 PM
To: wsjt-devel@lists.sourceforge.net
Cc: k8...@roadrunner.com
Subject: [wsjt-devel] MAP65 Decode issue
Hello,
I have a strange issue with MAP65/Q65 decodes.
I can see very strong traces but no decoding.
This is an intermittent issue.
I
Hello,
I have a strange issue with MAP65/Q65 decodes.
I can see very strong traces but no decoding.
This is an intermittent issue.
I close the program and restart it. This does not
cure the issue. I then reboot the PC and the problem
is resolved. Later on, the issue pops up again.
Has anyone
On 2/21/2021 4:50 PM, Black Michael W9MDB via wsjt-devel wrote:
Playing with Q65 decoding and anything over "Fast" mode takes a long
time to decode.
Example at Deep decode taking 24 seconds to decode.
Is this expected?
Yes.
As advised in "Quick-Start Guide to Q65", Use Decode | Fast with
Playing with Q65 decoding and anything over "Fast" mode takes a long time to
decode.Example at Deep decode taking 24 seconds to decode.
Is this expected?
Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Calling on FST4 160m tonight, I saw this transmission with no decode ;
It doesn't seem to fit the 60 second vertical span.
Is there any vision of wsjtx being able to identify other modes besides the
one selected ?
___
wsjt-devel
Thanks.
Jim
On 2/3/2021 4:54 AM, Steven Franke via wsjt-devel wrote:
Next thought. I called CQ for quite a while set for FST4-60. No responses, but
a guy near Phoenix (I'm near SF) posted me to PSKReporter, probably unattended.
My question is with respect to decoding, if I set up for
Would 1838 not be a better choice, there's not much JT65 or JT9 these days
and FST4 replaces them.
Jim Brown wrote:
> Makes sense. More questions, which came up first time I tried to use FST4
> on 160M, set up at 1839 kHz dial, 1050 Hz offset (I have a trash intermod
> carrier at 1840). If I
>
> Next thought. I called CQ for quite a while set for FST4-60. No responses,
> but a guy near Phoenix (I'm near SF) posted me to PSKReporter, probably
> unattended. My question is with respect to decoding, if I set up for FST4-60,
> would I also decode shorter period FST (and vice versa)?
On 2/2/2021 3:48 PM, Steven Franke via wsjt-devel wrote:
Increasing or decreasing the width of the search window will increase/decrease
the number of spurious candidates, so a larger search window means longer total
decoding time and higher false decode rate. That’s why we advise users to
> On Feb 2, 2021, at 4:56 PM, Jim Brown wrote:
>
> With FST4, is there an advantage to using narrower decode bandwidth and/or
> narrower frequency tolerance?
>
> Jim K9YC
Jim,
The GUI controls (FTol for FST4W and FLow/FHigh for FST4) determine the upper
and lower limits of the candidate
On 2/2/2021 3:18 PM, Bill Somerville wrote:
if you mean a narrower waterfall/spectrum bandwidth for the former, then
that doesn't make much difference. As always it is best to match your
receiver's bandwidth.
I was thinking of when the single decode is not checked.
The frequency tolerance
On 02/02/2021 22:56, Jim Brown wrote:
With FST4, is there an advantage to using narrower decode bandwidth
and/or narrower frequency tolerance?
Jim K9YC
Hi Jim,
if you mean a narrower waterfall/spectrum bandwidth for the former, then
that doesn't make much difference. As always it is best
With FST4, is there an advantage to using narrower decode bandwidth
and/or narrower frequency tolerance?
Jim K9YC
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Hi,
I am attempting a WSPR decoder on a single board computer using its
analog to digital converter for sampling. It won't be able to do 12,000
samples per second. Looking a /wsprd/ I see it reduces the /wav/ file by
a large factor. It also looks like the /C2/ processing only use 375
complex
Bill,
As stated in my post, replaying .wav files that where saved during
when the original failure occurred does NOT cause the failure to recur.
Also note that while WSJT-X is in the fault mode, ALT-Z only clears
the indicator until the next time the decoder is supposed to run (~ 12
sec ).
Hi Bill –
Already tried using Option+letter instead of Alt+letter …. No luck. The
Ctrl+letter and Shift+letter keyboard shortcuts work on the Mac keyboard with a
Mac Mini … none of the Option+letter (aka Alt+letter) work in 2.2.1 as far as I
can see.
-Tony
On 22/06/2020 11:16, Tony wrote:
On 22/06/2020 11:16, Tony wrote:
Hi Bill –
I was interested in keeping the Alt-Z shortcut in mind that you
mentioned to Al. I have found on WSJT-X 2.2.1 that most shortcuts
work on my MacMini (with a Mac keyboard), but no matter what I try I
can not get any of the “Alt” shortcuts to work.
2020 10:10:30 -0500
From: Al
To: WSJT software development
Subject: [wsjt-devel] FT8 Decode lockup observations
Message-ID:
Content-Type: text/plain; charset="utf-8"; Format="flowed"
( WSJT-X 2.2.1, Win 10 )
From time to? time, usually while monitoring 6m over night, I ge
On 21/06/2020 16:10, Al wrote:
( WSJT-X 2.2.1, Win 10 )
From time to time, usually while monitoring 6m over night, I get a a
Decode lockup. The Decode button is ON continuously, wide graph is
still running, wav files still being saved and no decodes are
displayed in the band activity
( WSJT-X 2.2.1, Win 10 )
From time to time, usually while monitoring 6m over night, I get a a
Decode lockup. The Decode button is ON continuously, wide graph is
still running, wav files still being saved and no decodes are displayed
in the band activity window. Seems more frequent with
On 18/12/2018 14:05, Joe Taylor wrote:
Next I suggest exploring the "References" page on the WSJT web site:
https://physics.princeton.edu/pulsar/k1jt/refs.html
73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Hi Brian,
On 12/17/2018 7:28 PM, bagel W9BGL wrote:
Now that FT8 version 2 is released and the uptake on the new version is
very successful, I hope this is an appropriate time to ask questions of
the development team. I want to learn the details on the FT8 decoding
algorithms. I am reading
Now that FT8 version 2 is released and the uptake on the new version is
very successful, I hope this is an appropriate time to ask questions of
the development team. I want to learn the details on the FT8 decoding
algorithms. I am reading the Fortran code, but there isn't a great
deal of
Sorry. Trying to give it a good test. I got fooled because I worked several
others FH with that version ok.
On Tue, Oct 23, 2018 at 9:16 AM WB5JJJ wrote:
> As stated by Joe Taylor, RC3 is NOT designed for DXP until the full
> release. It uses 77 bit and none of the DXP are using that mode
As stated by Joe Taylor, RC3 is NOT designed for DXP until the full
release. It uses 77 bit and none of the DXP are using that mode since it
is still in beta. VP6D specifically stated NOT to use RC3 and use v1.9.1
for this exact reason.
On Tue, Oct 23, 2018 at 4:39 AM David Spoelstra
wrote:
>
On 23/10/2018 10:04, David Spoelstra wrote:
Ubuntu 18.10
WSJT-X V2.0.0-rc3
In normal mode everything decodes ok. Switch to FH mode and there is
no decode even though waterfall shows strong signals. Switch back to
normal mode and everything decodes.
Switch back to 1.9.1 and both modes decode
Ubuntu 18.10
WSJT-X V2.0.0-rc3
In normal mode everything decodes ok. Switch to FH mode and there is no
decode even though waterfall shows strong signals. Switch back to normal
mode and everything decodes.
Switch back to 1.9.1 and both modes decode ok.
Switch back to rc3 and same decode problem
Tom,
some stations are using clone programs that have bastardized the
DXPedition mode, or early 1.9.1-RC versions that did not have the
standard FT8 frequency lock out.
Nothing you can do about that, and it does not appear that you did not
receive any type of signal report.
Its up to you
I was calling JY5IB, when this occured:
It does look likee dxpedition mode, but I was definitely not in Fox/Hound mode.
Unfortunately I had forgotten to set Save All, If it Occurs more, I have more
substantial stuff to bring...
73 de Tom OH6VDA
___
hris - N3PLM
>
>
>
> *From:* Black Michael via wsjt-devel [mailto:wsjt-devel@lists.
> sourceforge.net ]
> *Sent:* Tuesday, August 7, 2018 9:38 AM
> *To:* wsjt-devel@lists.sourceforge.net
> *Cc:* Black Michael
> *Subject:* Re: [wsjt-devel] no decode
>
>
>
>
your issue also.
Chris - N3PLM
*From:*Black Michael via wsjt-devel
[mailto:wsjt-devel@lists.sourceforge.net]
*Sent:* Tuesday, August 7, 2018 9:38 AM
*To:* wsjt-devel@lists.sourceforge.net
*Cc:* Black Michael
*Subject:* Re: [wsjt-devel] no decode
Hmmm hamspots.net doesn't show any transm
-devel
[mailto:wsjt-devel@lists.sourceforge.net]
*Sent:* Tuesday, August 7, 2018 9:38 AM
*To:* wsjt-devel@lists.sourceforge.net
*Cc:* Black Michael
*Subject:* Re: [wsjt-devel] no decode
Hmmm hamspots.net doesn't show any transmissions from you for the last
16 hours so you may not be transmitting as you think.
Chris - N3PLM
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Tuesday, August 7, 2018 9:38 AM
To: wsjt-devel@lists.sourceforge.net
Cc: Black Michael
Subject: Re: [wsjt-devel] no decode
Hmmm hamspots.net doesn't show any transmissions from you for t
sue
since.
It’s worth a try and might fix your issue also.
Chris - N3PLM
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Tuesday, August 7, 2018 9:38 AM
To: wsjt-devel@lists.sourceforge.net
Cc: Black Michael
Subject: Re: [wsjt-devel] no decode
Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Tuesday, August 7, 2018 9:38 AM
To: wsjt-devel@lists.sourceforge.net
Cc: Black Michael
Subject: Re: [wsjt-devel] no decode
Hmmm hamspots.net doesn't show any transmissions from you for the last 16 hours
so you may
Hmmm hamspots.net doesn't show any transmissions from you for the last 16 hours
so you may not be transmitting as you think.
You say your time is good but what does http://time.is tell you?
de Mike W9MDB
On Tuesday, August 7, 2018, 8:21:08 AM CDT, seaka...@juno.com
wrote:
I've
I've been using this software flawlessly for a while. I'm using it on a Mac
machine with Signalink and ICOM 735. This morning when I turned on the
computer and ran the program it was not decoding. The waterfall shows lots of
very strong signals. Time is exact between software and computer.
Chris,
With D4.exe turned off, have you checked your PC clock to see if it is gaining
or loosing time? Do a manual sync them wait 10 minutes and do another manual
sync. Then hover your mouse pointer over the Dx.exe icon in the lower right
toolbar. It should indicate the delta time from the last
Hello Chris, Hello Tim
ntp time sync goes like this:
---
your PC sends local time t1 to ntp
time t2 arrived at ntp:
local time t1 + delay client to ntp ( = upload delay) - offset
ntp sends correct time t3
time t4 arrived at PC:
ntp-time t3 + delay ntp to client ( = download delay) + offset
I believe that was fixed in r8646
de Mike W9MDB
On Wednesday, May 9, 2018, 4:28:26 PM CDT, Jeff Pyle
wrote:
Hello,
If a transmissions starts on an interval, and I immediately interrupt it,
(what's left of) that interval does not decode. If I click the decode
Hello,
If a transmissions starts on an interval, and I immediately interrupt it,
(what's left of) that interval does not decode. If I click the decode
button, I get the following error:
Running: /usr/bin/jt9 -s WSJT-X -w 1 -m 3 -e /usr/bin -a
> /home/jpyle/.local/share/WSJT-X -t /tmp/WSJT-X
>
One reason as to why using a narrow pass-band is less relevant today
than in past versions of WSJT-X is the addition of multi-pass decoding
where the software itself eliminates ( subtracts out ) a large number of
signals before a second pass is run on the same sample. Second pass
decoding
On 10-Sep-16 0833, Black Michael wrote:
> But...looks like you have a 1.2kHz filter turned on. Your waterfall
> shows it. You usually want the widest bandwidth you can do but at least
> 2.2kHz for JT65.
well, i guess i could be talked out of this practice.
As I think I see it, I am on JT9 and
sjt-devel@lists.sourceforge.net>
Sent: Saturday, September 10, 2016 4:45 AM
Subject: [wsjt-devel] Funny decode: LDE not . (r7034)
was calling CQ JT9 on 40m. Thought I had a bite but discovered it was me
calling CQ, hi hi.
see jpg for possibly helpful details.
--
73,
Bob KD7YZ
www.qrz.com/db/kd
On 10/09/2016 10:45, Bob KD7YZ wrote:
> was calling CQ JT9 on 40m. Thought I had a bite but discovered it was me
> calling CQ, hi hi.
Hi Bob,
as you can see from the waterfall the WSJT-X receive was not disabled
for your 0940 transmission, I assume you have your rig Tx monitor on but
very low
code anything here.
>
> de Mike W9MDB
>
>
> From: George J Molnar <geo...@molnar.com>
> To: WSJT software development <wsjt-devel@lists.sourceforge.net>
> Sent: Friday, September 2, 2016 1:57 PM
> Subject: [wsjt-devel] Noise Decode in MSK144
>
> WAV file
The wav file you send was 18:46:45 -- did you mean to send that one?It doesn't
decode anything here.
de Mike W9MDB
From: George J Molnar <geo...@molnar.com>
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Sent: Friday, September 2, 2016 1:57 PM
Subject:
On 05/05/2016 05:28, George J Molnar wrote:
> 6972 adds new issue - bilingual decodes (JT65/9) fail - JT9 is
> decoded, but not JT65. When switching to JT65 only mode, just a few
> decodes make it out of many visible in waterfall.
Hi George & all,
this defect should be repaired by r6673.
73
Thanks for looking, Joe.
The only steps I can take to reproduce the problem are reverting to an earlier
version (decodes work great), then updating to the latest (decodes work only
occasionally, if at all).
I’m going to look closer into possible cockpit errors. Will advise if I come up
with
Hi George,
On 5/5/2016 12:28 AM, George J Molnar (KF2T) wrote:
> Resolved in 6669. 6972 adds new issue - bilingual decodes (JT65/9)
> fail - JT9 is decoded, but not JT65. When switching to JT65 only
> mode, just a few decodes make it out of many visible in waterfall.
> Switched to single decode
Resolved in 6669. 6972 adds new issue - bilingual decodes (JT65/9) fail - JT9
is decoded, but not JT65. When switching to JT65 only mode, just a few decodes
make it out of many visible in waterfall. Switched to single decode mode and
got "error starting or running (path)/jt9 -s" error at decode
On 04/05/2016 03:28, George J Molnar wrote:
> Built 6665 for OS X tonight - after the first decode cycle, the Decode
> button lights and stays lit. No further decodes.
Hi George,
the most likely reason for this is a crash of the decoder component of
WSJT-X. If this is readily reproducible,
Just to add...on Windows 10 no such problem.
RRR
Mike W9MDB
On Tue, May 3, 2016 at 9:28 PM, George J Molnar wrote:
> Built 6665 for OS X tonight - after the first decode cycle, the Decode
> button lights and stays lit. No further decodes.
>
>
>
> *George J Molnar*KF2T |
Built 6665 for OS X tonight - after the first decode cycle, the Decode button
lights and stays lit. No further decodes.
George J Molnar
KF2T | AFA9GM
Twitter: @GJMolnar
SUPPORT HR-1301 & S-1685
http://www.arrl.org/amateur-radio-parity-act
Strange... after restarting the app, decodes seem to be coming in
faster. Will run a while and see...
73 Eric NO3M
On 11/27/2015 03:34 PM, Eric NO3M wrote:
> Running WSJT-X 1.7.0-devel r6133
>
> In most cases, initial decodes are not displayed until :57, the majority
> between :58-:59, and
Running WSJT-X 1.7.0-devel r6133
In most cases, initial decodes are not displayed until :57, the majority
between :58-:59, and even some as late as :12 into what should be my
transmit cycle. This is really wreaking havoc on the ability to have an
actual QSO.
Settings
Mode: JT9 only
Decode:
Hi All,
today try to compile sfrsd but seems that "sfrsd2.h" need by sfrsd.c is
not in svn
So I do a crazy test.
I configure 3 version of wsjtx to use the some audio board on input on
windows 10.
Only the first have CAT, the other are defined as radio "none" and run
with different profile
50MHz; 1.6.1 r5885 Linux 32-bit (Only seen once):
083200 0 3.3 1500 & 7D5FRM NU6INK FB53
--
Vy 73 de OZ1PIF/5Q2M, Peter
**
** If it sounds
As Joe, W1JT suggested earlier the message is protected by a 15(?) bit
CRC so there is a chance of 1/32768 of decoding a strange message.
We could give a "virtual prize" for the funniest message decoded by the
end of 2015:-D
73 Paolo
Il 10/10/15 10:37 AM, Peter Frenning [OZ1PIF] ha scritto:
Hi Mike,
Thanks for posting those troublesome wav files. As it happens, I have
been busy looking at a number of similar examples of problematic files.
More or less from the beginning, the JT9 decoder has failed without
obvious good reason something like 1% of the time... and I'd like to
Hello,
Running Xubuntu 14.04 64bit using wsjtx_1.4.0-rc2_amd64.deb. Trying to
use CAT net rigctl to QtRadio (localhost:19090). Get a consistent error
of Hamlib Error: communication timed out while getting split TX vfo.
Buttons for split operation seem to have no effect. Get same error for
61 matches
Mail list logo