Re: [wsjt-devel] NA VHF Contest Mode

[Gary McDuffie]

> 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 most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] OS X Audio Device Issues

[Larry Gadallah]

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 the
point where the various levels are close to correct.

Now as long as the computer and the screen don't go to sleep, WSPR
decoding works fine. However, when I go to setup transmitting, things
get odd: First of all, if I hit the Tune button, the transmitter will
key, but there won't be any audio.

If I go into Preferences -> Audio and set the Output Device to
Built-in Output and then set it back to USB Audio Codec, then the
transmitter will key and there will be audio at the radio's input.
Now, once that is done, if I click on the Enable Tx button and then
the Tx Next button, I will get a frame sent out during the next
period.

If I wait for another period or two, and press the Tx Next button, the
transmitter will be keyed, but there won't be any audio again. I have
to go back to preferences and "flip" the output device back to USB
Audio Codec to get it to provide transmit audio again.

Everything seems very flaky on the transmit audio side. Has anyone
been able to get this kind of setup running reliably?

A friend of mine, also using MacOS Sierra Version 10.12.6 and WSJT-X
v1.8.0-rc2 r8069 but with an Icom IC-7410 reports the following:

"I too experience the same problems with WSJT-X. I am hooking my Mac
to my Icom 7410 with just a USB cable. The transmit audio is good for
about 3 key-ups then it just goes to the computer speaker and NOT
through the USB cable to the radio. I have no problem with either
receive or transmit when running fldigi."

"I’ve done some further troubleshooting and here’s what I have found.
The problem does not appear to be related to Icom radios. It appears
to be related to USB sound cards and the Mac version WSJT-X. To prove
this I got out my SignaLink USB and connected it to the accessory jack
on the back of my IC 7410. In WSJT-X configuration I selected NONE for
radio and I selected VOX for PTT. I manually set the radio to the 20
meter frequency for FT8. I set the 7410 up so that data audio went in
and out of the accessory jack for data. FT8 signals were received fine
and an audio signal from the Mac/WSJT-X program was sent back through
the USB cable to the radio and would key the transmitter with VOX for
3 or 4 times and then revert to the problem sending outbound
(transmitter bound) audio to the iMac’s speaker (built-in output) when
it was supposed to have sent it via USB to the SignaLink USB which
would key the transmitter. I conclude the problem has to be in the
software and not  related to Icom or any other radios.  The thing that
I have not yet tried but I don’t see why it would work any better is
to connect the radio or SignaLink USB to the Mac via a powered USB
hub."

"I happened to have a powered USB  hub from another project so I tried
it. The results are the same. The audio changes path after keying the
transmitter 3 or 4 times. It’s what I figured would be the result of
the experiment but I figured that I had to just give it a try anyway."

Are there any references about how to build a "debug version" of
WSJT-X to help figure out what's going on in cases like this?

Thanks es 73,
-- 
Larry Gadallah, VE6VQ/W7  lgadallah AT gmail DOT com
PGP Sig: B5F9 C4A8 8517 82AC 16B6  02B6 0645 69F0 1F29 A512

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Frequency setting

[Kyle McKenzie]

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's 10 seconds.

On Thu, Sep 21, 2017 at 5:27 PM, Bill Somerville 
wrote:

> 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 18 100 000. I have seen this on previous builds
>> also.  Icom IC-7300, Win10, usb cable interface.
>>
>
> Hi Bill.
>
> WSJT-X goes through a short series of steps to determine the rig's
> frequency resolution when it first connects to the rig. For most rigs, i.e.
> those with one Hertz or ten Hertz resolution, this consists of reading the
> current frequency, QSYing to the current kHz rounded down plus 55 Hz, then
> QSYing back to where the rig was when the connection was opened. The net
> result should be no change in frequency.
>
> If your rig is being left at X plus 55 Hz and was not at that frequency
> before starting WSJT-X then something is not working correctly with your
> CAT interface.
>
> What do you have the "Settings->Radio->Poll interval" option set to?
>
> 73
> Bill
> G4WJS.
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>



-- 
-Kyle McKenzie KJ4SPG
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Frequency setting

[Bill Somerville]

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 18 100 000. I have seen this 
on previous builds also.  Icom IC-7300, Win10, usb cable interface.


Hi Bill.

WSJT-X goes through a short series of steps to determine the rig's 
frequency resolution when it first connects to the rig. For most rigs, 
i.e. those with one Hertz or ten Hertz resolution, this consists of 
reading the current frequency, QSYing to the current kHz rounded down 
plus 55 Hz, then QSYing back to where the rig was when the connection 
was opened. The net result should be no change in frequency.


If your rig is being left at X plus 55 Hz and was not at that frequency 
before starting WSJT-X then something is not working correctly with your 
CAT interface.


What do you have the "Settings->Radio->Poll interval" option set to?

73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] NA VHF Contest Mode

[George J Molnar]

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 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 
>> contest mode?
>> 
>> -- Joe
>> 
 On Sep 21, 2017, at 12:42 PM, Joe Taylor  wrote:
 
 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 could distill down to just “Contest.” With 
> appropriate tooltips, think it should be okay.
 
 Thanks for the feedback.  A little GUI cleanup is indeed desirable.
 
 Why would you remove "Sh"?  In mSK144 mode it's widely used at 144 MHz and 
 higher.
 
 What would be *really* helpful is for you to work with someone else and 
 thoroughly exercise the new capabilities.  Both MSK144 and FT8. The idea 
 is that one of you would be trying to make contest QSOs; the QSO partnet 
 might or might not be in the contest, or know anything about what "Contest 
 Mode" means.  Test all possibilities, and report back.
 
 -- Joe, K1JT
>> 
>> --
>>  
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> -- 
> 73,
> 
> Jim S.
> N2ADV
> www.qrz.com/db/N2ADV
> https://www.facebook.com/groups/FT8.Digital.Mode/
> 
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] NA VHF Contest Mode

[James Shaver]

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 as a full word (e.g. 
“Shorthand”), not deleted.


RR, understood.  Can you find someone with whom to do stress tests of 
contest mode?


-- Joe


On Sep 21, 2017, at 12:42 PM, Joe Taylor  wrote:

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 could distill down to just “Contest.” With 
appropriate tooltips, think it should be okay.


Thanks for the feedback.  A little GUI cleanup is indeed desirable.

Why would you remove "Sh"?  In mSK144 mode it's widely used at 144 
MHz and higher.


What would be *really* helpful is for you to work with someone else 
and thoroughly exercise the new capabilities.  Both MSK144 and FT8. 
The idea is that one of you would be trying to make contest QSOs; 
the QSO partnet might or might not be in the contest, or know 
anything about what "Contest Mode" means.  Test all possibilities, 
and report back.


    -- Joe, K1JT


-- 


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
73,

Jim S.
N2ADV
www.qrz.com/db/N2ADV
https://www.facebook.com/groups/FT8.Digital.Mode/


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] NA VHF Contest Mode

[Joe Taylor]

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 
contest mode?


-- Joe


On Sep 21, 2017, at 12:42 PM, Joe Taylor  wrote:

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 
could distill down to just “Contest.” With appropriate tooltips, think it 
should be okay.


Thanks for the feedback.  A little GUI cleanup is indeed desirable.

Why would you remove "Sh"?  In mSK144 mode it's widely used at 144 MHz and 
higher.

What would be *really* helpful is for you to work with someone else and thoroughly 
exercise the new capabilities.  Both MSK144 and FT8. The idea is that one of you would be 
trying to make contest QSOs; the QSO partnet might or might not be in the contest, or 
know anything about what "Contest Mode" means.  Test all possibilities, and 
report back.

-- Joe, K1JT


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] NA VHF Contest Mode

[George J Molnar]

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: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 could distill down to just “Contest.” With appropriate tooltips, 
>> think it should be okay.
> 
> Thanks for the feedback.  A little GUI cleanup is indeed desirable.
> 
> Why would you remove "Sh"?  In mSK144 mode it's widely used at 144 MHz and 
> higher.
> 
> What would be *really* helpful is for you to work with someone else and 
> thoroughly exercise the new capabilities.  Both MSK144 and FT8. The idea is 
> that one of you would be trying to make contest QSOs; the QSO partnet might 
> or might not be in the contest, or know anything about what "Contest Mode" 
> means.  Test all possibilities, and report back.
> 
>-- Joe, K1JT
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] NA VHF Contest Mode

[Joe Taylor]

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 
could distill down to just “Contest.” With appropriate tooltips, think it 
should be okay.


Thanks for the feedback.  A little GUI cleanup is indeed desirable.

Why would you remove "Sh"?  In mSK144 mode it's widely used at 144 MHz 
and higher.


What would be *really* helpful is for you to work with someone else and 
thoroughly exercise the new capabilities.  Both MSK144 and FT8. The idea 
is that one of you would be trying to make contest QSOs; the QSO partnet 
might or might not be in the contest, or know anything about what 
"Contest Mode" means.  Test all possibilities, and report back.


-- Joe, K1JT

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] NA VHF Contest Mode

[George J Molnar]

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 tooltips, think it 
should be okay.


George J Molnar
Nevada, USA




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Frequency setting

[Bill Turner via wsjt-devel]

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.  Icom IC-7300, 
Win10, usb cable interface.
In r8101, the NA VHF contest box is on the main page.  Maybe the 
UHF/VHF/Microwave Enhancements box should be under it.  Not every VHF effort is 
a contest but placing the enhancement box on the main page might be useful.
Thanks to everyone on the development team, you all do amazing work!
Bill Turner, W4WNT


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] NA VHF Contest Mode

[Jay Hainline]

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 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 just condense the standard message to send a single 
> call of the station you are working with R Grid? Wouldn’t this save the 
> effort of having to use extra coding in the software for converting an odd 
> ball grid to something that makes sense? Then no matter if you are in contest 
> mode or not, everyone would see the same message.
> 
> Example:
> 
> Current TX3 message in contest mode:  K1JT KA9CFD R EN40
> 
> Replace TX3 message transmitted by KA9CFD:  K1JT R EN40
> 
> Rational: A CQ with one call has already been sent, and response has been 
> received with both calls and a grid by the time TX3 is ready to be sent.

Yes, we could co it that way.  But...

1. The message "K1JT R EN40" is not a standard JT-style structured 
message.  It will be transmitted as free text, but the MSK144/FT8 
auto-sequencer will not process it correctly.  To avoid other potential 
problems, it insists on finding both calls in a valid auto-sequenced 
message.

2. MSK144 QSOs often take place on a time-shared channel with pings from 
several different stations being decoded in the same 15 s interval.  As 
many as several dozen FT8 transmissions are often decoded in a single 
interval.  When both callsigns appear in nearly every transmission it's 
easy to keep track of what's going on, and who's working whom.  With 
just one callsign in a message this is much harder -- both for those 
listening in and for the auto-sequencer.

-- Joe, K1JT

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] power equivalence of FT8 / JT65 = > SSB / CW

[Wolfgang]

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 power entries are either for SSB or CW. Remember that I saw a table of
power relations between SSB and JT65 (or FT8) for an acceptable contact.

Anyone has a link or info for me please ?

73's de OE1MWW
Wolfgang

--


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] NA VHF Contest Mode

[Joe Taylor]

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 just condense the standard message to send a single call of the station you 
are working with R Grid? Wouldn’t this save the effort of having to use extra 
coding in the software for converting an odd ball grid to something that makes 
sense? Then no matter if you are in contest mode or not, everyone would see the 
same message.

Example:

Current TX3 message in contest mode:  K1JT KA9CFD R EN40

Replace TX3 message transmitted by KA9CFD:  K1JT R EN40

Rational: A CQ with one call has already been sent, and response has been 
received with both calls and a grid by the time TX3 is ready to be sent.


Yes, we could co it that way.  But...

1. The message "K1JT R EN40" is not a standard JT-style structured 
message.  It will be transmitted as free text, but the MSK144/FT8 
auto-sequencer will not process it correctly.  To avoid other potential 
problems, it insists on finding both calls in a valid auto-sequenced 
message.


2. MSK144 QSOs often take place on a time-shared channel with pings from 
several different stations being decoded in the same 15 s interval.  As 
many as several dozen FT8 transmissions are often decoded in a single 
interval.  When both callsigns appear in nearly every transmission it's 
easy to keep track of what's going on, and who's working whom.  With 
just one callsign in a message this is much harder -- both for those 
listening in and for the auto-sequencer.


-- Joe, K1JT

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost logging times

[Dan Malcolm]

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 asked.  I have seen many times on this forum where the same
question is asked over and over.  

-73
___
Dan - K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Thursday, September 21, 2017 11:09 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] Lost logging times

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 did read it).
> 
> 'Nuff said.  It's on my head now.

No problem...

On the User Guide:

We put a lot of effort into this document.  We want people to read it,
because WSJT-X is a complex program.  Many people don't read it, as you can
tell from some traffic here and on the wsjtgroup email list.  In part this
may be because the Guide is already some 90 pages long.  We don't have the
space (nor the inclination) to describe of every detail of every program
function.

-- Joe, K1JT


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost logging times

[Claude Frantz]

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 it maintained.

Because the log entry window is presented before the end of the QSO,
having the presentation time as end time, in the case of the option
requiring the opening of this window, I have suggested to include a new
button allowing to set the current time as the end time of the QSO. An
alternative option could be to insert a new button "save the log entry
with the current time as end time". This would be simpler as the
changing of the end time in every log window for every QSO.

Please allow me to point again to this suggestion.

Best wishes,
Claude (DJ0OT)

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost logging times

[Joe Taylor]

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 did read it).

'Nuff said.  It's on my head now.


No problem...

On the User Guide:

We put a lot of effort into this document.  We want people to read it, 
because WSJT-X is a complex program.  Many people don't read it, as you 
can tell from some traffic here and on the wsjtgroup email list.  In 
part this may be because the Guide is already some 90 pages long.  We 
don't have the space (nor the inclination) to describe of every detail 
of every program function.


-- Joe, K1JT

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost logging times

[Dan Malcolm]

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 - K4SHQ

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Thursday, September 21, 2017 10:34 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] Lost logging times

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 presented to you for review, before you click
"OK".

As station operator it's your responsibility to maintain your log as you
want it maintained.

-- Joe, K1JT


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost logging times

[Joe Taylor]

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 presented to you for review, before you click 
"OK".


As station operator it's your responsibility to maintain your log as you 
want it maintained.


-- Joe, K1JT

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost logging times

[Black Michael via wsjt-devel]

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 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 Development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Lost logging times
 
  
 
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 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 two lines, since I 
didn’t have Log4OM running the first logging attempt (my bad):
 
 
 
2017-09-21,14:30:15,2017-09-21,14:31:15,VE1JS,FN64,14.074968,FT8,+03,-02,,,
 
2017-09-21,14:44:13,2017-09-21,14:44:13,VE1JS,FN64,14.074968,FT8,+03,-02,,,
 
 
 
The first line has the correct start/stop times, but the second line is 
obviously wrong, and that’s what got sent to Log4OM. 
 
 
 
__
 
Dan – K4SHQ
 
 
 
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
   --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost logging times

[Dan Malcolm]

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 Development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Lost logging times

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 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 two lines, since I 
didn’t have Log4OM running the first logging attempt (my bad):



2017-09-21,14:30:15,2017-09-21,14:31:15,VE1JS,FN64,14.074968,FT8,+03,-02,,,

2017-09-21,14:44:13,2017-09-21,14:44:13,VE1JS,FN64,14.074968,FT8,+03,-02,,,



The first line has the correct start/stop times, but the second line is 
obviously wrong, and that’s what got sent to Log4OM.



__

Dan – K4SHQ


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lost logging times

[Black Michael via wsjt-devel]

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 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 two lines, since I 
didn’t have Log4OM running the first logging attempt (my bad):
 
  
 
2017-09-21,14:30:15,2017-09-21,14:31:15,VE1JS,FN64,14.074968,FT8,+03,-02,,,
 
2017-09-21,14:44:13,2017-09-21,14:44:13,VE1JS,FN64,14.074968,FT8,+03,-02,,,
 
  
 
The first line has the correct start/stop times, but the second line is 
obviously wrong, and that’s what got sent to Log4OM. 
 
  
 
__
 
Dan – K4SHQ
 
  
 --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Lost logging times

[Dan Malcolm]

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 two lines, since I 
didn’t have Log4OM running the first logging attempt (my bad):

2017-09-21,14:30:15,2017-09-21,14:31:15,VE1JS,FN64,14.074968,FT8,+03,-02,,,
2017-09-21,14:44:13,2017-09-21,14:44:13,VE1JS,FN64,14.074968,FT8,+03,-02,,,

The first line has the correct start/stop times, but the second line is 
obviously wrong, and that’s what got sent to Log4OM.

__
Dan – K4SHQ

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel