I have all of that checked as in clearing the cq field after each call
already. The only issue I see is when I just cut the software on and/or
change bands sometimes that's when a lot of these false codes come up even
before I transmit anything. Sometimes the software is just sitting there
and thes
Hi Mike,
as others have suggested, AP decoding will raise the probability of
false decodes a little. One thing you can do to reduce the false decode
probability is to ensure the DX Call filed is cleared when you are not
working or attempting to work another station. You can check the option
i
FT8 and all bands. It just pops up.
On Fri, Apr 26, 2019 at 11:28 AM Bill Somerville
wrote:
> On 26/04/2019 16:04, Mike Oakley wrote:
> > I continue to get false decodes everyday even when I am not
> > transmitting, for example today I cut my rig on and loaded the
> > software and then I got a f
And thanks for the reply as well.
On Fri, Apr 26, 2019, 11:24 AM Mike Oakley wrote:
> From what I gather the false decodes always end with the ?a2 so far but
> some from what I am getting do not have that. I just didn't know if it was
> something I was doing wrong that's all. No I don't want to
>From what I gather the false decodes always end with the ?a2 so far but
some from what I am getting do not have that. I just didn't know if it was
something I was doing wrong that's all. No I don't want to cut those out so
I guess I can ignore them as long as I know what they are.
On Fri, Apr 26,
On 26/04/2019 16:04, Mike Oakley wrote:
I continue to get false decodes everyday even when I am not
transmitting, for example today I cut my rig on and loaded the
software and then I got a false decode before anything even popped on
my screen. Can someone tell me why I am getting these and how
You can turn off AP decoding but, of course, you no longer have the advantage
of AP decoding (whether that’s a loss is up to you).
Or, you could ignore them since you’re aware they’re false decodes random
patterns in the static can make the program spit out a false decode and it is
just s
I continue to get false decodes everyday even when I am not transmitting,
for example today I cut my rig on and loaded the software and then I got a
false decode before anything even popped on my screen. Can someone tell me
why I am getting these and how do I stop them?
I note that most false decodes result in a 4 char. grid. I wonder if it
makes sense to not create a hashtable.txt entry for those type of decodes.
Jim
WA2ZKD
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge
Correct me if I'm wrong but any false decodes are not relevant unless
your running only in 77 bit mode. In other words the "Decode only 77 bit
messages" box must be checked.
73,
Connie/k5cm
On 9/23/2018 9:04 AM, Joe Taylor wrote:
Paul --
On 9/22/2018 3:32 PM, w3...@verizon.net wrote:
Just
Paul --
On 9/22/2018 3:32 PM, w3...@verizon.net wrote:
Just installed 2.0 RC1 yesterday, and so far so good with a couple of
exceptions,
I was under the impression that the false decodes would be
"significantly less than
previous versions", not the case here, if anything the rate is higher
!!!
FWIW
Just installed 2.0 RC1 yesterday, and so far so good with a couple of
exceptions, I was under the impression that the false decodes would be
"significantly less than previous versions", not the case here, if anything the
rate is higher !!! Another strange phenomenon is that the rcvr S meter
Hi Guys,
Personally I would rather have the occasional false spot rather than needing 2
spots before uploading.
I often get only a single spot which is valid.
Keep up the great work
73
Victor
--
__
13 matches
Mail list logo
