Hi Steve,
Thanks! What's your antenna on 6m, and where was it pointed?
Coincidentally, your decodes illustrate another undesired behavior that
I'm aware of, in the WSJT-X running JTMSK mode. Sometimes the decoder
produces a pair of identical results. Supposedly, "dupes" are being
suppressed
Hi Joe -
I went back outside to finish mowing the lawn, so I missed this:
162015 4 6.1 1500 & CQ K1JT FN20
162015 4 6.1 1500 & CQ K1JT FN20
Thanks!
Steve k9an
> On Aug 30, 2015, at 4:10 PM, Joe Taylor wrote:
>
> Steve --
>
> I'll CQ with JTMSK, 50.280 in your direction for the next 1
Steve --
I'll CQ with JTMSK, 50.280 in your direction for the next 10-15 minutes.
(This is not a good time of day for meteors, though.)
-- Joe
On 8/30/2015 12:02 PM, Steven Franke wrote:
> That seems to have fixed it Joe. Neither file causes it to crash now. I have
> not yet decoded
That seems to have fixed it Joe. Neither file causes it to crash now. I have
not yet decoded any pings though. I will let it run on 50.280 for awhile to see
if I can decode anything.
Thanks!
Steve k9an
> On Aug 30, 2015, at 2:47 PM, Joe Taylor wrote:
>
> Hi Steve,
>
> I was about to write to
Hi All,
I received the follow message, on linux 64 bits.
On a single machine ran two instance of 1.6.1 r5830 compiled by JTSDK
2.0.14 in debug mode (only SEPARATE is No)
The two instance are running on separate audio board interconnected by
physical cross cable to understand some new modes functi
Hi Steve,
I was about to write to you along the same lines. The copies of nhash.h
and nhash.c in .../wsjtx_exp/lib have been used only for building the
executable testmsk, not for wsprx. I was clearly on the wrong track
yesterday.
It turns out, I believe, that the problem is entirely elsewhe
