5 Apr
2020
5 Apr
'20
12:30 p.m.
After using WSJT V9 for a few years I recently started using WSJT-X as a
second decoder. Sometimes it is better, sometimes not. It has the advantage
that it decodes when one station is calling another (V9 only does this for
strong stations).
One issue I am having is that the Average window in X sometimes shows
stations that I decoded way earlier...sometimes an hour or more earlier and
on a different frequency.
If I click Clear Avg or double-click Erase, the window clears. But a while
later, old decodes once again start to show up in the Average window.
V9 does not have this problem.
I have been using V2.0...today I moved to V2.1.2 and maybe that will be
better. Waiting for MR here.
Has anyone else experienced this behavior?
Does anyone know if that was a bug in the earlier version and fixed in
2.1.2 or can some one suggest what setting I may have set incorrectly?
Thanks & 73,
Doug K1DG
5 Apr
5 Apr
1:37 p.m.
Hi Doug,
You are correct that there are some peculiarities in JT65 decoding
behavior when "Enable averaging" is used.
Why have these problems been allowed to persist? The simple answer is
that we have been unable to gathered the required background information
to allow tracing them down. A longish sequence of recorded *.wav files
that can be opened from within WSJT-X to show examples of unwanted
behavior would be a good start. None of our development team currently
has EME capability, so it's not easy for us to produce usable data for
such tests.
If you can do so, please operate with "Save all" enabled for a while.
When you see the undesired behavior that you have described, isolate the
relevant *.wav files -- perhaps those for the previous half hour or so
-- and test them later to see if you can reproduce the problem off-line
by opening the files sequentially, clicking "Clr Avg" at any appropriate
times, etc. If you can reproduce the problem, send us the .wav files
and a recipe for reproducing the undesirable behavior.
-- 73, Joe, K1JT
On 4/5/2020 12:30, Doug Grant via Moon-net wrote:
After using WSJT V9 for a few years I recently started
using WSJT-X as a
second decoder. Sometimes it is better, sometimes not. It has the
advantage that it decodes when one station is calling another (V9 only
does this for strong stations).
One issue I am having is that the Average window in X sometimes shows
stations that I decoded way earlier...sometimes an hour or more earlier
and on a different frequency.
If I click Clear Avg or double-click Erase, the window clears. But a
while later, old decodes once again start to show up in the Average window.
V9 does not have this problem.
I have been using V2.0...today I moved to V2.1.2 and maybe that will be
better. Waiting for MR here.
Has anyone else experienced this behavior?
Does anyone know if that was a bug in the earlier version and fixed in
2.1.2 or can some one suggest what setting I may have set incorrectly?
Thanks & 73,
Doug K1DG
_______________________________________________
Moon-Net posting and subscription instructions are at
http://www.nlsa.com/nets/moon-net-help.html
6:53 p.m.
Hi, Joe -
Thanks for following up. Good to know it is not some setting that I messed
up.
I saved the .WAV files for an hour or sonhis afternoon and managed to see
the odd behavior a couple of times.
I’ll see if I can make it happen offline and send the files for your team
to examine. Give me a few days.
In the meantime, I’ll be working guys.
BTW, your old amp is purring away here. I have discovered that 1kW+
stresses things like cheap connectors and wattmeters way more than my 600W
Larcan did.
73,
Doug
On Sun, Apr 5, 2020 at 13:37 Joe Taylor <joe(a)princeton.edu> wrote:
Hi Doug,
You are correct that there are some peculiarities in JT65 decoding
behavior when "Enable averaging" is used.
Why have these problems been allowed to persist? The simple answer is
that we have been unable to gathered the required background information
to allow tracing them down. A longish sequence of recorded *.wav files
that can be opened from within WSJT-X to show examples of unwanted
behavior would be a good start. None of our development team currently
has EME capability, so it's not easy for us to produce usable data for
such tests.
If you can do so, please operate with "Save all" enabled for a while.
When you see the undesired behavior that you have described, isolate the
relevant *.wav files -- perhaps those for the previous half hour or so
-- and test them later to see if you can reproduce the problem off-line
by opening the files sequentially, clicking "Clr Avg" at any appropriate
times, etc. If you can reproduce the problem, send us the .wav files
and a recipe for reproducing the undesirable behavior.
-- 73, Joe, K1JT
On 4/5/2020 12:30, Doug Grant via Moon-net wrote:
After using WSJT V9 for a few years I recently
started using WSJT-X as a
second decoder. Sometimes it is better, sometimes not. It has the
advantage that it decodes when one station is calling another (V9 only
does this for strong stations).
One issue I am having is that the Average window in X sometimes shows
stations that I decoded way earlier...sometimes an hour or more earlier
and on a different frequency.
If I click Clear Avg or double-click Erase, the window clears. But a
while later, old decodes once again start to show up in the Average
window.
V9 does not have this problem.
I have been using V2.0...today I moved to V2.1.2 and maybe that will be
better. Waiting for MR here.
Has anyone else experienced this behavior?
Does anyone know if that was a bug in the earlier version and fixed in
2.1.2 or can some one suggest what setting I may have set incorrectly?
Thanks & 73,
Doug K1DG
_______________________________________________
Moon-Net posting and subscription instructions are at
http://www.nlsa.com/nets/moon-net-help.html
3:05 p.m.
Hi Doug. Yes, averaging does not work very well in WSJT-X. I still use it when I am
trying with a very weak station, but I’ve learned how to detect when it has given me false
information, usually. The biggest clue is that the time delta is almost always shown as
1.5 on the bogus decodes. I have seen it show decodes on contacts made several days ago,
and even on contacts that I didn’t even decode anything real, again with the bad DT value.
I have seen those bad decodes show up in the middle of an ongoing contact, and sometimes
when I come back to the computer after letting it idle for long periods receiving nothing
(not even pointed at the moon).
To minimize the problem, I keep averaging turned off all the time except when I feel I
really need it. As soon as I am done with a contact where I do use averaging, I uncheck
the averaging box and click the ‘clear average’ button. Even that is not enough
sometimes. It seems like WSJT-X holds those bad decodes somewhere it it’s memory. I have
had to resort to shutting down WSJT-X and then restarting it. I think this will make it
totally forget, but I am not sure…
I’ve complained to the WSJT-X developers about this but was told that they are working on
‘other stuff’ now.
73, Russ K2TXB
From: Moon-net <moon-net-bounces(a)mailman.pe1itr.com> On Behalf Of Doug Grant via
Moon-net
Sent: Sunday, April 05, 2020 12:30 PM
To: moon-net(a)mailman.pe1itr.com
Subject: [Moon-Net] WSJT-X average window behavior
After using WSJT V9 for a few years I recently started using WSJT-X as a second decoder.
Sometimes it is better, sometimes not. It has the advantage that it decodes when one
station is calling another (V9 only does this for strong stations).
One issue I am having is that the Average window in X sometimes shows stations that I
decoded way earlier...sometimes an hour or more earlier and on a different frequency.
If I click Clear Avg or double-click Erase, the window clears. But a while later, old
decodes once again start to show up in the Average window.
V9 does not have this problem.
I have been using V2.0...today I moved to V2.1.2 and maybe that will be better. Waiting
for MR here.
Has anyone else experienced this behavior?
Does anyone know if that was a bug in the earlier version and fixed in 2.1.2 or can some
one suggest what setting I may have set incorrectly?
Thanks & 73,
Doug K1DG
3:52 p.m.
I think averaging works quite well, but you have to know how to spot the false decodes or
old decodes from the real ones. Not usually that hard if you check DT, the end of line
decode info and have some idea of what the decode should be. Leave averaging off unless
you need it, reboot the program from time to time (as needed). If you have things set for
maximum decode sensitivity then you will get quite a few false/spurious decodes. If I
leave things on overnight with averaging, DS and AP all on there are often a few
bogus/spurious decodes waiting for me. Some have my call in them, some have plausible DX
callsigns, some don't. You just have to learn what's real and what's not.
Neither WSJTx window is as clean and free from extraneous decodes as it could be, but
software is never perfect and if you're operating at the limits of detectability with
everything turned up to "11", a few spurious results are to be expected.
I'm still trying to figure out of there's any meaning to the extra spaces in this
decode:
1858 -30 2.6 1283 ## KA1GT OZ1CTZ JO46 OO O d32
Note it's "OO O", not "OOO". It's a low
confidence decode, but was confirmed with higher confidence (and higher signal strength)
and correct "OOO" on a subsequent transmission. If you look at the time stamp,
the DT, the sync indicator (#* and ##) and the end of line codes, you can almost always
figure out if a decode is valid. I've seen the oddly spaced "OO O"
more than once.
73
Bob, KA1GT
________________________________
From: Moon-net <moon-net-bounces(a)mailman.pe1itr.com> on behalf of Russ via Moon-net
<moon-net(a)mailman.pe1itr.com>
Sent: Sunday, April 5, 2020 3:05 PM
To: moon-net(a)mailman.pe1itr.com <moon-net(a)mailman.pe1itr.com>
Cc: 'Doug Grant' <dougk1dg(a)gmail.com>
Subject: Re: [Moon-Net] WSJT-X average window behavior
Hi Doug. Yes, averaging does not work very well in WSJT-X. I still use it when I am
trying with a very weak station, but I’ve learned how to detect when it has given me false
information, usually. The biggest clue is that the time delta is almost always shown as
1.5 on the bogus decodes. I have seen it show decodes on contacts made several days ago,
and even on contacts that I didn’t even decode anything real, again with the bad DT value.
I have seen those bad decodes show up in the middle of an ongoing contact, and sometimes
when I come back to the computer after letting it idle for long periods receiving nothing
(not even pointed at the moon).
To minimize the problem, I keep averaging turned off all the time except when I feel I
really need it. As soon as I am done with a contact where I do use averaging, I uncheck
the averaging box and click the ‘clear average’ button. Even that is not enough
sometimes. It seems like WSJT-X holds those bad decodes somewhere it it’s memory. I have
had to resort to shutting down WSJT-X and then restarting it. I think this will make it
totally forget, but I am not sure…
I’ve complained to the WSJT-X developers about this but was told that they are working on
‘other stuff’ now.
73, Russ K2TXB
From: Moon-net <moon-net-bounces(a)mailman.pe1itr.com> On Behalf Of Doug Grant via
Moon-net
Sent: Sunday, April 05, 2020 12:30 PM
To: moon-net(a)mailman.pe1itr.com
Subject: [Moon-Net] WSJT-X average window behavior
After using WSJT V9 for a few years I recently started using WSJT-X as a second decoder.
Sometimes it is better, sometimes not. It has the advantage that it decodes when one
station is calling another (V9 only does this for strong stations).
One issue I am having is that the Average window in X sometimes shows stations that I
decoded way earlier...sometimes an hour or more earlier and on a different frequency.
If I click Clear Avg or double-click Erase, the window clears. But a while later, old
decodes once again start to show up in the Average window.
V9 does not have this problem.
I have been using V2.0...today I moved to V2.1.2 and maybe that will be better. Waiting
for MR here.
Has anyone else experienced this behavior?
Does anyone know if that was a bug in the earlier version and fixed in 2.1.2 or can some
one suggest what setting I may have set incorrectly?
Thanks & 73,
Doug K1DG
4:16 p.m.
Hi Bob,
On your oddball decode from WSJT-X with everything turned up to 11 and
averaging on:
1858 -30 2.6 1283 ## KA1GT OZ1CTZ JO46 OO O d32
Here's a hypothesis, and a question. Does the "split OOO" always occur
when your QSO partner's callsign has six characters? I suspect it's
just a matter of an "off by one" error in the character index when the
"d32" tag gets moved out to its position at end of line.
As you guys are discovering, message averaging was added onto the JT65
portions of WSJT-X late in the game, and has never been thoroughly
tested. As I wrote to Doug, it would be a big help if someone provided
us with a set of *.wav files which, when read back into WSJT-X, would
reproduce the bad behavior you have described. Bob? Russ? Can you do
this?
This reflector is a bit of an oddity, itself. I sent a reply to Doug
and to moon-net about three hours ago. I haven't seen that reply yet,
posted on Moon-Net; but evidently others have seen it.
-- Joe, K1JT
On 4/5/2020 15:52, Bob Atkins via Moon-net wrote:
I think averaging works quite well, but you have to
know how to spot the
false decodes or old decodes from the real ones. Not usually that hard
if you check DT, the end of line decode info and have some idea of what
the decode should be. Leave averaging off unless you need it, reboot the
program from time to time (as needed). If you have things set for
maximum decode sensitivity then you will get quite a few false/spurious
decodes. If I leave things on overnight with averaging, DS and AP all on
there are often a few bogus/spurious decodes waiting for me. Some have
my call in them, some have plausible DX callsigns, some don't. You just
have to learn what's real and what's not.
Neither WSJTx window is as clean and free from extraneous decodes as it
could be, but software is never perfect and if you're operating at the
limits of detectability with everything turned up to "11", a few
spurious results are to be expected.
I'm still trying to figure out of there's any meaning to the extra
spaces in this decode:
1858 -30 2.6 1283 ## KA1GT OZ1CTZ JO46 OO O d32
Note it's "OO O", not "OOO". It's a low
confidence decode,
but was confirmed with higher confidence (and higher signal strength)
and correct "OOO" on a subsequent transmission. If you look at the time
stamp, the DT, the sync indicator (#* and ##) and the end of line codes,
you can almost always figure out if a decode is valid. I've seen the
oddly spaced "OO O" more than once.
73
Bob, KA1GT
------------------------------------------------------------------------
*From:* Moon-net <moon-net-bounces(a)mailman.pe1itr.com> on behalf of Russ
via Moon-net <moon-net(a)mailman.pe1itr.com>
*Sent:* Sunday, April 5, 2020 3:05 PM
*To:* moon-net(a)mailman.pe1itr.com <moon-net(a)mailman.pe1itr.com>
*Cc:* 'Doug Grant' <dougk1dg(a)gmail.com>
*Subject:* Re: [Moon-Net] WSJT-X average window behavior
Hi Doug.Yes, averaging does not work very well in WSJT-X.I still use it
when I am trying with a very weak station, but I’ve learned how to
detect when it has given me false information, usually.The biggest clue
is that the time delta is almost always shown as 1.5 on the bogus
decodes.I have seen it show decodes on contacts made several days ago,
and even on contacts that I didn’t even decode anything real, again with
the bad DT value.I have seen those bad decodes show up in the middle of
an ongoing contact, and sometimes when I come back to the computer after
letting it idle for long periods receiving nothing (not even pointed at
the moon).
To minimize the problem, I keep averaging turned off all the time except
when I feel I really need it.As soon as I am done with a contact where I
do use averaging, I uncheck the averaging box and click the ‘clear
average’ button.Even that is not enough sometimes.It seems like WSJT-X
holds those bad decodes somewhere it it’s memory.I have had to resort to
shutting down WSJT-X and then restarting it.I think this will make it
totally forget, but I am not sure…
I’ve complained to the WSJT-X developers about this but was told that
they are working on ‘other stuff’ now.
73, Russ K2TXB
*From:*Moon-net <moon-net-bounces(a)mailman.pe1itr.com> *On Behalf Of
*Doug Grant via Moon-net
*Sent:* Sunday, April 05, 2020 12:30 PM
*To:* moon-net(a)mailman.pe1itr.com
*Subject:* [Moon-Net] WSJT-X average window behavior
After using WSJT V9 for a few years I recently started using WSJT-X as a
second decoder. Sometimes it is better, sometimes not. It has the
advantage that it decodes when one station is calling another (V9 only
does this for strong stations).
One issue I am having is that the Average window in X sometimes shows
stations that I decoded way earlier...sometimes an hour or more earlier
and on a different frequency.
If I click Clear Avg or double-click Erase, the window clears. But a
while later, old decodes once again start to show up in the Average window.
V9 does not have this problem.
I have been using V2.0...today I moved to V2.1.2 and maybe that will be
better. Waiting for MR here.
Has anyone else experienced this behavior?
Does anyone know if that was a bug in the earlier version and fixed in
2.1.2 or can some one suggest what setting I may have set incorrectly?
Thanks & 73,
Doug K1DG
_______________________________________________
Moon-Net posting and subscription instructions are at
http://www.nlsa.com/nets/moon-net-help.html
7 Apr
7 Apr
12:51 p.m.
Thanks for the reply Joe
I had not made a note of the conditions under which the "OOO" turns into
"OO O", but I did see it again today while listening on 1296. I saw in
the felt window (not averaged):
2042 -6 5.0 1147 ## PA3FXB DK0ZAB JO61 OO O f
2034 -15 4.9 1177 ## PL9CHJ T86ABK NB09 OO O a2
Both do have 6 character calls. The first one is a good decode with correct identification
of the two stations in QSO. The second one is almost certainly spurious! The number of
characters sounds like a plausible explanation for the added spaces with some sort of
"tab" coming after a particular character count maybe?
Incidentally I also saw these:
2120 -23 4.5 1381 #* / E-NK901W-2H f
2126 -17 -3.4 1313 #* WAFH2PXLE85M4 f
Both quite clearly spurious decodes, so not really a problem. The human brain sometimes
comes in useful ...
Then I looked back though my all.txt file and found many examples, such as:
1016 -14 1.5 1264 ## KA1GT SM3RPQ JP74 OO O d12
1443 -9 1.5 802 ## KA1GT UP70A MO13 OO O d11
0825 -17 4.5 784 ## KA1GT W8MM EM79 OO O d12
0154 -20 2.6 1003 ## UA3TCF OK1DFC JN79 OO O f
0942 -30 2.1 1762 ## KA1GT F6KKR JN08 OO O d12
So it looks like all 6+6 call combinations split the "OOO". However 5+5
combinations and even 5+4 combinations also split the "OOO" when it's a Deep
Search decode. So it does indeed look like it's some sort of character count issue
that's inserting a tab or spaces. Looking at the text in a text editor that will show
tabs and whitespace, it appears that it's whitespace that is being inserted.
Not a problem now that I know it's a bug, not a feature!
Thanks and 73
Bob, KA1GT
________________________________
From: Joe Taylor <joe(a)princeton.edu>
Sent: Sunday, April 5, 2020 4:16 PM
To: Bob Atkins <ka1gt(a)hotmail.com>om>; moon-net(a)mailman.pe1itr.com
<moon-net(a)mailman.pe1itr.com>om>; Russ <k2txb(a)comcast.net>
Cc: 'Doug Grant' <dougk1dg(a)gmail.com>
Subject: Re: [Moon-Net] WSJT-X average window behavior
Hi Bob,
On your oddball decode from WSJT-X with everything turned up to 11 and
averaging on:
1858 -30 2.6 1283 ## KA1GT OZ1CTZ JO46 OO O d32
Here's a hypothesis, and a question. Does the "split OOO" always occur
when your QSO partner's callsign has six characters? I suspect it's
just a matter of an "off by one" error in the character index when the
"d32" tag gets moved out to its position at end of line.
As you guys are discovering, message averaging was added onto the JT65
portions of WSJT-X late in the game, and has never been thoroughly
tested. As I wrote to Doug, it would be a big help if someone provided
us with a set of *.wav files which, when read back into WSJT-X, would
reproduce the bad behavior you have described. Bob? Russ? Can you do
this?
This reflector is a bit of an oddity, itself. I sent a reply to Doug
and to moon-net about three hours ago. I haven't seen that reply yet,
posted on Moon-Net; but evidently others have seen it.
-- Joe, K1JT
On 4/5/2020 15:52, Bob Atkins via Moon-net wrote:
I think averaging works quite well, but you have to
know how to spot the
false decodes or old decodes from the real ones. Not usually that hard
if you check DT, the end of line decode info and have some idea of what
the decode should be. Leave averaging off unless you need it, reboot the
program from time to time (as needed). If you have things set for
maximum decode sensitivity then you will get quite a few false/spurious
decodes. If I leave things on overnight with averaging, DS and AP all on
there are often a few bogus/spurious decodes waiting for me. Some have
my call in them, some have plausible DX callsigns, some don't. You just
have to learn what's real and what's not.
Neither WSJTx window is as clean and free from extraneous decodes as it
could be, but software is never perfect and if you're operating at the
limits of detectability with everything turned up to "11", a few
spurious results are to be expected.
I'm still trying to figure out of there's any meaning to the extra
spaces in this decode:
1858 -30 2.6 1283 ## KA1GT OZ1CTZ JO46 OO O d32
Note it's "OO O", not "OOO". It's a low
confidence decode,
but was confirmed with higher confidence (and higher signal strength)
and correct "OOO" on a subsequent transmission. If you look at the time
stamp, the DT, the sync indicator (#* and ##) and the end of line codes,
you can almost always figure out if a decode is valid. I've seen the
oddly spaced "OO O" more than once.
73
Bob, KA1GT
------------------------------------------------------------------------
*From:* Moon-net <moon-net-bounces(a)mailman.pe1itr.com> on behalf of Russ
via Moon-net <moon-net(a)mailman.pe1itr.com>
*Sent:* Sunday, April 5, 2020 3:05 PM
*To:* moon-net(a)mailman.pe1itr.com <moon-net(a)mailman.pe1itr.com>
*Cc:* 'Doug Grant' <dougk1dg(a)gmail.com>
*Subject:* Re: [Moon-Net] WSJT-X average window behavior
Hi Doug.Yes, averaging does not work very well in WSJT-X.I still use it
when I am trying with a very weak station, but I’ve learned how to
detect when it has given me false information, usually.The biggest clue
is that the time delta is almost always shown as 1.5 on the bogus
decodes.I have seen it show decodes on contacts made several days ago,
and even on contacts that I didn’t even decode anything real, again with
the bad DT value.I have seen those bad decodes show up in the middle of
an ongoing contact, and sometimes when I come back to the computer after
letting it idle for long periods receiving nothing (not even pointed at
the moon).
To minimize the problem, I keep averaging turned off all the time except
when I feel I really need it.As soon as I am done with a contact where I
do use averaging, I uncheck the averaging box and click the ‘clear
average’ button.Even that is not enough sometimes.It seems like WSJT-X
holds those bad decodes somewhere it it’s memory.I have had to resort to
shutting down WSJT-X and then restarting it.I think this will make it
totally forget, but I am not sure…
I’ve complained to the WSJT-X developers about this but was told that
they are working on ‘other stuff’ now.
73, Russ K2TXB
*From:*Moon-net <moon-net-bounces(a)mailman.pe1itr.com> *On Behalf Of
*Doug Grant via Moon-net
*Sent:* Sunday, April 05, 2020 12:30 PM
*To:* moon-net(a)mailman.pe1itr.com
*Subject:* [Moon-Net] WSJT-X average window behavior
After using WSJT V9 for a few years I recently started using WSJT-X as a
second decoder. Sometimes it is better, sometimes not. It has the
advantage that it decodes when one station is calling another (V9 only
does this for strong stations).
One issue I am having is that the Average window in X sometimes shows
stations that I decoded way earlier...sometimes an hour or more earlier
and on a different frequency.
If I click Clear Avg or double-click Erase, the window clears. But a
while later, old decodes once again start to show up in the Average window.
V9 does not have this problem.
I have been using V2.0...today I moved to V2.1.2 and maybe that will be
better. Waiting for MR here.
Has anyone else experienced this behavior?
Does anyone know if that was a bug in the earlier version and fixed in
2.1.2 or can some one suggest what setting I may have set incorrectly?
Thanks & 73,
Doug K1DG
_______________________________________________
Moon-Net posting and subscription instructions are at
http://www.nlsa.com/nets/moon-net-help.html
6 Jan
6 Jan
1:16 p.m.
Hi Doug.
I know this is an old thread, but I believe I have recently seen this
behaviour on Map65, the most recent version.
I was monitoring SV6KRW calling K5QE repeatedly as K5QE was calling CQ. I
went off to eat supper and watch some
TV. I returned to that frequency a few hours later and I knew that a
russian station was calling CQ on the same frequency
and K5QE was long gone. With the same DFand DT as the Russian station, I
saw that SV6KRW was calling K5QE and
it happened repeatedly several times. I should have decoded the Russian
station but I got SV6KRW instead. Really odd.
A little later I noticed SV6KRW calling CQ on a new frequency and he was
-30db, 3 times in a row. I never get a -30db valid decode. I restarted
Map65 and all returned to normal. I would suspect a
memory management error in the program. It's not a big problem, but I
thought I would mention it especially since it showed
up on Map65 as well. Map65 seems to no longer crash since I put memory
priority to buffers rather than programs. I still
have 100% CPU load during decodes.
WB9UWA
On Sun, Apr 5, 2020 at 11:34 AM Doug Grant via Moon-net <
moon-net(a)mailman.pe1itr.com> wrote:
After using WSJT V9 for a few years I recently started
using WSJT-X as a
second decoder. Sometimes it is better, sometimes not. It has the advantage
that it decodes when one station is calling another (V9 only does this for
strong stations).
One issue I am having is that the Average window in X sometimes shows
stations that I decoded way earlier...sometimes an hour or more earlier and
on a different frequency.
If I click Clear Avg or double-click Erase, the window clears. But a while
later, old decodes once again start to show up in the Average window.
V9 does not have this problem.
I have been using V2.0...today I moved to V2.1.2 and maybe that will be
better. Waiting for MR here.
Has anyone else experienced this behavior?
Does anyone know if that was a bug in the earlier version and fixed in
2.1.2 or can some one suggest what setting I may have set incorrectly?
Thanks & 73,
Doug K1DG
_______________________________________________
Moon-Net posting and subscription instructions are at
http://www.nlsa.com/nets/moon-net-help.html
--
Earl Shaffer, WB9UWA
My EME array photos
https://www.dropbox.com/sh/bbn2ktonko8e3az/AACHBBOhf6Djk5Pf2c86Br5ja
Detailed array photos
http://www.gm4jjj.co.uk/WB9UWA/
Facebook
http://www.facebook.com/earl.shaffer
Linkedin
http://www.linkedin.com/pub/earl-shaffer/12/881/735
878
days inactive
1154
days old
7 comments
5 participants
participants (5)
-
Bob Atkins -
Doug Grant -
Earl Shaffer -
Joe Taylor -
Russ