I’m really hoping that the Dev Team chooses NOT to make a Field Day (or any HF
contest) variant for FT8. Too many variations in formats, exchanges, and such
will lead to bloatware and confusion.
Since FD, in particular, is a training event, maybe we shouldn’t encourage
semi-automated contacts.
I think Tim’s suggestion is a good answer to the problem we have identified.
Keeps it simple, too.
George J Molnar
Arlington, Virginia, USA
KF2T - FM18lv
> On Jun 13, 2018, at 12:15 PM, Tim Goeppinger via wsjt-devel
> wrote:
>
> I would estimate that the issues with people
Would a unique CQ message for contest mode work, or is that asking for
confusion?
Normal mode: CQ KF2T FM18
Contest mode: CX KF2T FM18
The contest community is smaller than the general population, so it might be an
easier “sell."
George J Molnar
Arlington, Virginia, USA
KF2T - FM18lv
Is it possible that the software could interpret receipt of a grid in place of
an expected signal report as an automatic switch to contest mode? That way the
receiving station doesn’t need to even know that the transmitter is using one
mode or the other.
Added benefit - if signals are such
>
> Bob Nobis
> n7...@nobis.net <mailto:n7...@nobis.net>
>
>
>> On May 1, 2018, at 08:57, George Molnar <geo...@molnar.com
>> <mailto:geo...@molnar.com>> wrote:
>>
>> I’ve had this reproducible error occur a few times now. 1.90rc4 (8642
Deselect “NA VHF Contest" Mode.
George J Molnar
Washington, DC, USA
KF2T - @GJMolnar
> On May 2, 2018, at 1:38 PM, Reinhard wrote:
>
>
--
Check out the vibrant tech community on one of
I’ve had this reproducible error occur a few times now. 1.90rc4 (8642)
downloaded from the WSJT-X homepage crashes when command-double clicking on the
FT8 wide graph to change DF only after at least one decode cycle has completed.
I had not seen this before 8642.
OSX 10.13.5 beta, quad core i7
Hi Claude.
I think Mike´s interpretation is correct. Third harmonics are often stronger
than the 2nd, and the variation in signal strength does seem to match the
fundamental (which, BTW, is not the TX/RX selected DF).
I see this quite frequently. A lot of hay is made on the Facebook group and
Have to agree with Jim, N2ADV. An expedition should NOT be using a
mode-in-development. It is a near-guarantee of confusion.
That said, DXpedition mode is something of a Pandora’s Box. Once opened, the
developers have no control over who uses it or when. It would be more than a
little naive
Using 1.9 (8603) under MacOS 10.13.4.
Upon launch, program operates smoothly. As Band Activity window fills, CPU
usage rises slowly, until the program becomes unresponsive. At that point, only
a forced quit recovers the app. It does keep receiving and decoding, however.
If I catch it early
t you should look carefully into why you are having this issue
> with your home-built executable. I do not think our builds show any problem
> of this kind.
>
> -- 73, Joe, K1JT
>
> On 4/9/2018 8:33 AM, George Molnar wrote:
>> Using 1.9 (8603) under MacOS 10.13.4.
Regarding comments suggesting that a band plan can be implemented and enforced
in software, I don’t think that will work. It would rely on properly engaged
and functional CAT control by the Fox. Given that several stations have already
“jumped the gun” and are using the mode in its incomplete
The digital mode watering holes are not (as far as I know in most cases) part
of any international agreement or national regulation. If a group of operators
want to agree amongst themselves to operate on a particular spot, it is
incumbent on them to avoid interference with existing operations
CONGRATULATIONS!
George J Molnar
Arlington, Virginia, USA
(702) 767-5420
KF2T - FM18lv
> On Jul 4, 2019, at 9:10 AM, Rich Zwirko - K1HTV wrote:
>
> On Monday, July 1, the Mid-Atlantic had a very long duration opening to
> Europe. While I was on the ON4KST IARU Region II
For the Mac users out there —
Version 2.1 has crashed on my Mac running 10.15 beta. Runs fine on the other
machine on 10.13.6.
Have corresponded a few times with Bill (G4WJS) off-list. He’s looking into it.
Take appropriate precautions if you try the new version.
George J Molnar
Arlington,
Thanks for the effort, Bill. Unfortunately, no change on MacOS Catalina beta.
Still crash on launch.
73
George J Molnar
Arlington, Virginia, USA
> On Jul 21, 2019, at 6:34 AM, Bill Somerville wrote:
>
> Hi all,
>
> some of you have reported a crash on startup, thanks to those who have
Hi Rich,
I’ve observed the same, exactly as you described. Had put it down to urban
reflections, perhaps more obvious when W3/W4 is beaming N/NE. Agree with you
they are not aircraft scatter.
George J Molnar
Arlington, Virginia, USA
(702) 767-5420
KF2T - FM18lv
> On Jul 6, 2019, at
Perhaps tuning your VFO 200 Hz lower will do the trick? I have adjusted the
frequency tables down 500 Hz and use a 5 kHz filter, and everyone is in the
passband without difficulty.
George J Molnar
College Park, Maryland
KF2TFM19ma
> On Jun 22, 2022, at 8:42 PM, Notko Mermerski via
Likely to be an RF ingress issue, vs a software problem.
George J Molnar
College Park, Maryland
KF2TFM19ma
> On Jul 21, 2022, at 1:28 PM, Marty Wayne via wsjt-devel
> wrote:
>
> I tried operating with WSJTx 2.5.2 and 2.5.4 with same issue.
>
> 73,
>
> Marty, W6NEV
> _ . . . . _ _
I’m a Mac user so will work around the issue with the Kenwood settings for now.
Thanks for the info, Mike.
George J Molnar
College Park, Maryland
KF2TFM19ma
> On Nov 29, 2022, at 1:52 PM, Jay via wsjt-devel
> wrote:
>
> This has solved the problem for me. Thanks Mike and the team.
>
>
Confirmed here. Control works when selecting Ts2000, but not Flex6000.
George J Molnar
College Park, Maryland
KF2TFM19ma
> On Nov 29, 2022, at 1:03 PM, Jay via wsjt-devel
> wrote:
>
> I just installed the new RC5 into my Windows 10 64 bit computer and am
> getting a Hamlib error when
21 matches
Mail list logo