> On Sep 21, 2017, at 2:14 PM, James Shaver wrote:
>
> Drop me a note, George, we can find a semi-empty corner of a band :)
Same here, George.
Gary - AG0N
--
Check out the vibrant tech community on one of the world's
Hi all:
I have found a few more interesting problems with the Mac version of
WSJT-X 1.80-rc2 r8069:
I am running a Mac laptop with OS X 10.12.6, and I installed the
SiLabs USB serial port drivers. I am using an Icom IC-7300 via the USB
cable, and after considerable tinkering, I think I have it to
I too have experienced the X+55hz CAT control phenomenon for some time
now. I use WSJT-X with SDR-Console v2&3. It's a non-issue for me, nothing
more than a curiosity, but I thought I'd mention it since another is also
seeing it. I will verify my polling interval when I get home, but I think
it
On 21/09/2017 19:48, Bill Turner via wsjt-devel wrote:
I was operating r8094 on 17m, 18.100.000. I then compiled r8101 and
clicked on the shortcut to bring it up. The frequency showed as 18
100 055. Clicking on the frequency box to get back to the 17m
default, the box and the radio now show
You bet, Joe.
George J Molnar, CEM, CHPP
KF2T - Nevada, USA
> On Sep 21, 2017, at 1:14 PM, James Shaver wrote:
>
> Drop me a note, George, we can find a semi-empty corner of a band :)
>
> Jim S.
>
> N2ADV
>
>
>> On 9/21/2017 4:05 PM, Joe Taylor wrote:
>> Hi George,
>>
>>> On 9/21/2017 3:56
Drop me a note, George, we can find a semi-empty corner of a band :)
Jim S.
N2ADV
On 9/21/2017 4:05 PM, Joe Taylor wrote:
Hi George,
On 9/21/2017 3:56 PM, George J Molnar wrote:
Joe, would absolutely not remove sh - it’s incredibly useful. My
intention was to say the term should be written
Hi George,
On 9/21/2017 3:56 PM, George J Molnar wrote:
Joe, would absolutely not remove sh - it’s incredibly useful. My intention was
to say the term should be written as a full word (e.g. “Shorthand”), not
deleted.
RR, understood. Can you find someone with whom to do stress tests of
cont
Joe, would absolutely not remove sh - it’s incredibly useful. My intention was
to say the term should be written as a full word (e.g. “Shorthand”), not
deleted.
George J Molnar, CEM, CHPP
KF2T - Nevada, USA
> On Sep 21, 2017, at 12:42 PM, Joe Taylor wrote:
>
> Hi George,
>
>> On 9/21/2017 3:
Hi George,
On 9/21/2017 3:31 PM, George J Molnar wrote:
Quick feedback on the repositioned contest mode checkbox. Bravo! Good idea.
Before GA release, it might be helpful to clean up the labels and alignment, so
everything flows smoothly. ”Sh” could be written out, and maybe NA VHF Contest
co
Quick feedback on the repositioned contest mode checkbox. Bravo! Good idea.
Before GA release, it might be helpful to clean up the labels and alignment, so
everything flows smoothly. ”Sh” could be written out, and maybe NA VHF Contest
could distill down to just “Contest.” With appropriate toolt
I was operating r8094 on 17m, 18.100.000. I then compiled r8101 and clicked on
the shortcut to bring it up. The frequency showed as 18 100 055. Clicking on
the frequency box to get back to the 17m default, the box and the radio now
show 18 100 000. I have seen this on previous builds also. I
Ok Joe. Thanks for the explanation.
73 Jay KA9CFD
Sent from my U.S. Cellular® Smartphone
Original message From: Joe Taylor Date:
9/21/17 12:39 (GMT-06:00) To: WSJT software development
Subject: Re: [wsjt-devel] NA VHF Contest
Mode
Hi Jay,
On 9/20/2017 5:08 PM, Jay Hainli
Hi all,
Will be next year in march QRV as 8Q7WK on the Maldives as I have been
2 years ago. KX3 + vertical plus laptop with JT65 & FT8 - what else ;-)
The software voacap can calculate the estimated signal level for a
radio link between two stations on the globe. Was curious to check that.
The p
Hi Jay,
On 9/20/2017 5:08 PM, Jay Hainline wrote:
Joe and all. Curious because I am not a big contester. My understanding is the
reason for the extra coding is for producing the message sent for TX3 with both
calls plus R Grid. If it’s a problem with extra characters involved, why can't
you j
Agree Joe, but hence the questions on this forum. Given that we users are
not paying for this, I am appreciative of you and the rest of the
development teams efforts. But sometimes I don't know why something works
the way it does. I do think we users need to some research before a
question is as
On 09/21/2017 05:34 PM, Joe Taylor wrote:
Hi Joe & all,
> WSJT-X does not attempt to replace the cognizant human being using it.
> All logging information is presented to you for review, before you click
> "OK".
>
> As station operator it's your responsibility to maintain your log as you
> want
Hi Dan,
On 9/21/2017 11:54 AM, Dan Malcolm wrote:
Joe, Michael,
I don't disagree. I do have a problem being the cognizant human being at
times, and yes it is my responsibility. I just didn't realize how things
worked until now. The online guide says nothing about this behavior however
(yes I
Joe, Michael,
I don't disagree. I do have a problem being the cognizant human being at
times, and yes it is my responsibility. I just didn't realize how things
worked until now. The online guide says nothing about this behavior however
(yes I did read it).
'Nuff said. It's on my head now.
Dan
Dan --
On 9/21/2017 11:21 AM, Dan Malcolm wrote:
Yes I did log it twice because the first attempt failed. But since the QSO is
reflected in the log entry, the times should still be correct.
WSJT-X does not attempt to replace the cognizant human being using it.
All logging information is pre
Not the way it works. If you log a 2nd time you are reponsible for setting
times.Why do you think it failed the first time? An error message from your
logger?
de Mike W9MDB
On Thursday, September 21, 2017, 10:21:58 AM CDT, Dan Malcolm
wrote:
Yes I did log it twice because the f
Yes I did log it twice because the first attempt failed. But since the QSO is
reflected in the log entry, the times should still be correct.
Dan – K4SHQ
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Thursday, September 21, 2017 10:09 AM
To: WSJT Software Dev
Looks to me like you logged it twice.The times reset after you log it so
logging it a 2nd time without a QSO will use the current time in both.
de Mike W9MDB
On Thursday, September 21, 2017, 10:00:17 AM CDT, Dan Malcolm
wrote:
I just noticed that QSO start/stop times are getting l
I just noticed that QSO start/stop times are getting logged more as logging
times rather than the times encompassing the QSO. The QSO shown in the screen
capture wasn’t logged until a few minutes later. Checking the Log4OM entry,
both start & stop times were 14:44:00. The WSJT-X log shows tw
23 matches
Mail list logo
