Re: [wsjt-devel] Announcing the World Wide Digi DX Contest

[Don Hill AA5AU]

Six meters wasn't considered. We wanted it to be similar to the other WW 
contests.

 

Don AA5AU

 

From: Edfel Rivera [mailto:edfelj...@gmail.com] 
Sent: Wednesday, July 3, 2019 1:25 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Announcing the World Wide Digi DX Contest

 

Hi Don:

 

Why not include the 6M band? Know it is mostly active in summer but even the 
ARRL Sept VHF (Sept 14-16) include the bad.  Just wondering why to exclude the 
6M.

 

73'

 

Edfel

KP4AJ

 

On Sat, Jun 29, 2019 at 4:50 PM Don Hill AA5AU  wrote:

For immediate release. June 29, 2019. 

 

The World Wide Radio Operators Foundation (“WWROF”), in collaboration with the 
Slovenia Contest Club (“SCC”), is pleased to announce the first annual World 
Wide Digi DX Contest (“WW Digi”). The new contest taps into the excitement 
being generated by the new digital modes pioneered by Joe Taylor K1JT and the 
WSJT-X development team. The contest will occur over 24 hours on August 31 and 
September 1, 2019 using the FT4 and FT8 modes on the 160, 80, 40, 20, 15, and 
10-meter bands. 

 

WW Digi will utilize a distance-based scoring system to measure operators’ 
abilities in making DX contacts across the 6 HF amateur radio bands. Contacts 
will earn points based on the distance between grid square centers of the two 
stations. This will encourage operators to seek out long distance weak signal 
contacts that highlight the technical advantages of the new digital modes. 

 

To encourage activity across all bands, a multiplier will be given for each new 
2-character grid field contacted on each band. The final score will the product 
of the total contact points times the number of grid fields contacted. There 
should be plenty of strategy required to balance distant QSOs and the need to 
work all available grid fields. Single and multi-operators are welcome to 
operate as much or as little of the 24-hour contest period as they wish. 

 

The contest has been designed to enable making contacts utilizing standard 
WSJT-X software behavior, making it easy for non-contesters to participate. At 
the same time, the contest supports some new techniques that will encourage 
operating innovation, such as permitting stations to work up to three “QSO 
streams” on a band at one time. Robotic operation is specifically prohibited in 
order to keep the human element as part of the game. The full rules and other 
information are available on the WW Digi DX contest web site at 
https://ww-digi.com

 

It is fitting that the World Wide DX contest series be expanded with a fourth 
mode, Digi, to support evolution into ham radio’s future. Accordingly, with 
WWROF’s sponsorship of the World Wide Digi DX Contest, there will now be 
similar worldwide DX contests at the end of four successive months, August 
through November.

 

Serious contesters and casual participants alike can make ham radio history and 
have fun as the hobby pioneers the exciting world of digital communication. 
WWROF hopes the WW Digi DX Contest will attract new digital operators into 
contesting.

 

Plaques will be awarded for top scorers. Please contact the WW Digi Contest 
Director Ed Muns, W0YK at plaq...@ww-digi.com to sponsor an award. Electronic 
certificates will also be available for download for anyone that submits a log. 
The goal is to have results available on the web site within 90 days after the 
end of the contest.

 

About WWROF

The World Wide Radio Operators Foundation is dedicated to improving the skills 
and fun of amateur radio operators around the world by utilizing education, 
competition, advancement of technology and scientific research, promoting 
international friendship and goodwill.

WWROF is a non-profit, donor-supported, organization which sponsors this 
contest and provides the infrastructure for log submission, log checking, and 
other services in support of many popular radio contests. Please visit  
 wwrof.org for more information.

 

About SCC

The Slovenia Contest Club has a long tradition of supporting digital contesting 
with its annual RTTY Championship contest held the last weekend of August. For 
more information about SCC please visit   
http://lea.hamradio.si/scc/

 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

We seem to be hearing problems with a few people on both 2.0.1 and 2.1.0-rc7.  
2.0.1 has been out for a long time and if this was common I'd think we would 
have heard a lot more reports of the problem.Upgrading to 2.1.0-rc7 and back to 
2.0.1 should (and I emphasize should) just revert completely back to 2.0.1 
thought there is a bug with FT4 in that case.
The common thread probably is Windows updatesor time is off.  Check 
http://time.is to ensure you're time is reported as "Exact".
If you see waterfall activity but no decodes on of three things is likely 
happening.
#1 Time is off#2 WAV files are not being recorded.  Ensure Save/All is checked 
and see if WAV files are showing up in the Save folder.  One user found using 
Remote Desktop that audio files weren't being saved.  TeamViewer worked 
though.#3 Audio corrupted.  If WAV files are showing up but not decoding and 
your time is correct then send in a few audio files so we can look at them.

de Mike W9MDB

 

On Wednesday, July 3, 2019, 10:27:56 PM CDT, Tod Farrell WE5TR 
 wrote:  
 
 Similar issue here on 2.0.1, win10, and flex6700 after a long operating 
session or even a long monitoring session. I.e. I’ll leave the shack powered up 
monitoring a band while I’m at work or elsewhere in the house. 
When I come back sometimes the waterfall is showing activity, dT is good, 
time.is is good, but no decodes.Other times it’s that clicking transit or tune 
causes no generated audio to the DAX  software which has a meter that shows me 
no incoming audio is present from WSJT-X.
Typically corrected with a WSJT-X restart 
--73
Tod    WE5TRWhile mobile
On Jul 3, 2019, at 16:52, Hasan al-Basri  wrote:


Hi Mike,No transmitting at all. RF Chokes all over the place. No issues running 
KW out on any band 6m through 80m. (if I have just rebooted the computer). Once 
it has run for several hours. it will stop decoding, whether I have transmitted 
or not, no matter qrp or qro. I monitor 24x7 , go days without tx'ing...it 
still goes deaf.
IOW, it's not a USB RFI problem. 
All power settings for USB have been set to never sleep. 
I"m baffled, like I said, it acts like a memory leak and I don't think it's a 
coincidence that it showed up the very first time after installing and running 
RC7 64 bit. 
The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change a 
thing in my setup or operating habits. Now I have to reboot every day or it 
just stops decoding, even having uninstalled RC7 64 bit and returned to 2.01 
Gen Release.
Audio level is perfect, waterfall shows signals...no decode. Reboot...decodes 
resume. No other program shows any symptoms like this at all on the same 
computer. WSJT-X is running on its own USB Sound Dongle for both RX and 
TXand has been for over a year. Any further ideas are most welcome 
(TS-590sg, running from headphone jack for rx audio) Audio sounds perfect to 
the ear. Levels are right...Most peculiar!
73, N0ANHasan

On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel 
 wrote:

Failing audio or rig connections are most always due to RFI or USB ports going 
to sleep.If RFI low power transmissions can be tested and if they work but high 
power does not then it's RFI.The USB ports going to sleep can be 
solved.https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices

de Mike W9MDB

 

On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
 wrote:  
 
 I’ve seen this with other radios. Definitely not a flex only issue.
RiaN2RJ
On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel 
 wrote:

 Peter,
Flex has its own set of unique problems and fixes.  Suggest you post your 
question on the Flex forum page.  Good luck.

    Danny    AH6FX/W4

On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam  
wrote:  
 
 Greetings,

I have been using WSJT-X quite successfully for several years during 
June VHF Contests. I experienced a failure of the WSJT program to accept 
received audio input after several hours of proper operation during the 
recent Field Day exercise.

I'll provide a brief outline and reply with more detail, should it be 
needed.

My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The 
WSJT-X software version is 2.0.1 7ddcb7.

My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX" 
program that interfaces various applications that wish to receive the 
audio stream. WSJT accepts the stream and displays results on the Wide 
Graph and a small audio signal-strength window. Activity proceeded 
normally for the first three hours of Field Day, until both the Wide 
Graph and the audio signal-strength stopped showing any incoming audio.

I can't offer any help on what might have caused the problem. It was 
abrupt and seemingly unrelated to any other system actions. I am unable 
to reproduce the problem.

Several operators spent several hours speculating about what a solution 
might be. Program restarts and computer re-boots (time-tested favorite 

Re: [wsjt-devel] WSJT Audio Input Loss

[Bill Richter]

You should be able to check the memory usage via Task Manager to determine 
whether or not it is a memory leak...



--
Thanks,
Bill

> On July 3, 2019 at 2:52 PM Hasan al-Basri  wrote:
> 
> 
> I"m baffled, like I said, it acts like a memory leak and I don't think 
> it's a coincidence that it showed up the very first time after installing and 
> running RC7 64 bit. 
> 
> 
> 73, N0AN
> Hasan
> 
> 
> On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel < 
> wsjt-devel@lists.sourceforge.net mailto:wsjt-devel@lists.sourceforge.net > 
> wrote:
> 
> > > Failing audio or rig connections are most always due to 
> RFI or USB ports going to sleep.
> > If RFI low power transmissions can be tested and if they work but 
> > high power does not then it's RFI.
> > The USB ports going to sleep can be solved.
> > 
> > https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices
> > 
> > de Mike W9MDB
> > 
> > 
> > 
> > 
> > On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
> > mailto:rjai...@gmail.com < rjai...@gmail.com mailto:rjai...@gmail.com > 
> > wrote:
> > 
> > 
> > I’ve seen this with other radios. Definitely not a flex only issue.
> > 
> > Ria
> > N2RJ
> > 
> > On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel < 
> > wsjt-devel@lists.sourceforge.net mailto:wsjt-devel@lists.sourceforge.net > 
> > wrote:
> > 
> > > > >  
> > > Peter,
> > > 
> > > Flex has its own set of unique problems and fixes.  Suggest 
> > > you post your question on the Flex forum page.  Good luck.
> > > 
> > > Danny
> > > AH6FX/W4
> > > 
> > > On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam < 
> > > pe...@ni6e.com mailto:pe...@ni6e.com > wrote:
> > > 
> > > 
> > > Greetings,
> > > 
> > > I have been using WSJT-X quite successfully for several years 
> > > during
> > > June VHF Contests. I experienced a failure of the WSJT 
> > > program to accept
> > > received audio input after several hours of proper operation 
> > > during the
> > > recent Field Day exercise.
> > > 
> > > I'll provide a brief outline and reply with more detail, 
> > > should it be
> > > needed.
> > > 
> > > My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 
> > > 64-bit. The
> > > WSJT-X software version is 2.0.1 7ddcb7.
> > > 
> > > My receiver is a Flex 6500. It passes data to a Flex-supplied 
> > > "DAX"
> > > program that interfaces various applications that wish to 
> > > receive the
> > > audio stream. WSJT accepts the stream and displays results on 
> > > the Wide
> > > Graph and a small audio signal-strength window. Activity 
> > > proceeded
> > > normally for the first three hours of Field Day, until both 
> > > the Wide
> > > Graph and the audio signal-strength stopped showing any 
> > > incoming audio.
> > > 
> > > I can't offer any help on what might have caused the problem. 
> > > It was
> > > abrupt and seemingly unrelated to any other system actions. I 
> > > am unable
> > > to reproduce the problem.
> > > 
> > > Several operators spent several hours speculating about what 
> > > a solution
> > > might be. Program restarts and computer re-boots (time-tested 
> > > favorite
> > > of generations) changed nothing. The only useful clue was 
> > > that the DAX
> > > audio output stream was present and could be re-directed to 
> > > Fldigi, but
> > > not to WSJT-X.
> > > 
> > > I was able to restore operation for a brief period by 
> > > stopping WSJT,
> > > renaming WSJT.ini and restarting WSJT. That fix lasted for a 
> > > half hour.
> > > Repeating the procedure provided operation for the rest of 
> > > Field Day.
> > > 
> > > The two .ini files that were renamed are available for your 
> > > inspection,
> > > along with the one that continued to function.
> > > 
> > > Any suggestions you can offer to prevent a recurrence would 
> > > be greatly
> > > appreciated.
> > > 
> > > Regards,
> > > Peter
> > > NI6E
> > > 
> > > 
> > > 
> > > 
> > > 
> > > 
> > > ___
> > > wsjt-devel mailing list
> > > wsjt-devel@lists.sourceforge.net 
> > > mailto:wsjt-devel@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> > > ___
> > > wsjt-devel mailing list
> > > wsjt-devel@lists.sourceforge.net 
> > > mailto:wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] WSJT Audio Input Loss

[Gary McDuffie]

> On Jul 3, 2019, at 15:52, Hasan al-Basri  wrote:
> 
> Any further ideas are most welcome (TS-590sg, running from headphone jack for 
> rx audio) Audio sounds perfect to the ear. Levels are right...
> Most peculiar!

Hasan - 

As you probably remember, when you uninstall and reinstall, the old user folder 
isn’t cleaned out.  If you haven’t done it, try uninstalling and then go rename 
the entire installation folder in your user folder.  Then reinstall in a new 
folder using the 32 bit version of rc7 and test it.  Hopefully, that will tell 
the story about whether it comes from the 64 bit rc7.

Of course, I didn’t have that problem, but I wasn’t all that impressed with rc7 
anyway, so I only had it up a few times to test JT4.  I haven’t brought it up 
again since shortly after it was put out there for testing.

Gary - AG0N

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

If a restart of WSJT-X does not recover than it sounds like your USB sound 
device is locking up.If that's true just unplugging it and plugging it back in 
would recover the audio (with a restart of WSJT-X too of course).
You may want to uninstall an reinstall your USB sound card.  WIndows updates 
for USB are know to mess things up.
Mike

P.S.According to my notes the transmit side of the 590SG needs this:
Menu 71 = 1Menu 72 = 2
Windows playback audio -20 to -25 dB with the ALC meter on the just bouncing a 
bit.
 

On Wednesday, July 3, 2019, 04:52:13 PM CDT, Hasan al-Basri 
 wrote:  
 
 Hi Mike,No transmitting at all. RF Chokes all over the place. No issues 
running KW out on any band 6m through 80m. (if I have just rebooted the 
computer). Once it has run for several hours. it will stop decoding, whether I 
have transmitted or not, no matter qrp or qro. I monitor 24x7 , go days without 
tx'ing...it still goes deaf.
IOW, it's not a USB RFI problem. 
All power settings for USB have been set to never sleep. 
I"m baffled, like I said, it acts like a memory leak and I don't think it's a 
coincidence that it showed up the very first time after installing and running 
RC7 64 bit. 
The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change a 
thing in my setup or operating habits. Now I have to reboot every day or it 
just stops decoding, even having uninstalled RC7 64 bit and returned to 2.01 
Gen Release.
Audio level is perfect, waterfall shows signals...no decode. Reboot...decodes 
resume. No other program shows any symptoms like this at all on the same 
computer. WSJT-X is running on its own USB Sound Dongle for both RX and 
TXand has been for over a year. Any further ideas are most welcome 
(TS-590sg, running from headphone jack for rx audio) Audio sounds perfect to 
the ear. Levels are right...Most peculiar!
73, N0ANHasan

On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel 
 wrote:

Failing audio or rig connections are most always due to RFI or USB ports going 
to sleep.If RFI low power transmissions can be tested and if they work but high 
power does not then it's RFI.The USB ports going to sleep can be 
solved.https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices

de Mike W9MDB

 

On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
 wrote:  
 
 I’ve seen this with other radios. Definitely not a flex only issue.
RiaN2RJ
On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel 
 wrote:

 Peter,
Flex has its own set of unique problems and fixes.  Suggest you post your 
question on the Flex forum page.  Good luck.

    Danny    AH6FX/W4

On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam  
wrote:  
 
 Greetings,

I have been using WSJT-X quite successfully for several years during 
June VHF Contests. I experienced a failure of the WSJT program to accept 
received audio input after several hours of proper operation during the 
recent Field Day exercise.

I'll provide a brief outline and reply with more detail, should it be 
needed.

My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The 
WSJT-X software version is 2.0.1 7ddcb7.

My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX" 
program that interfaces various applications that wish to receive the 
audio stream. WSJT accepts the stream and displays results on the Wide 
Graph and a small audio signal-strength window. Activity proceeded 
normally for the first three hours of Field Day, until both the Wide 
Graph and the audio signal-strength stopped showing any incoming audio.

I can't offer any help on what might have caused the problem. It was 
abrupt and seemingly unrelated to any other system actions. I am unable 
to reproduce the problem.

Several operators spent several hours speculating about what a solution 
might be. Program restarts and computer re-boots (time-tested favorite 
of generations) changed nothing. The only useful clue was that the DAX 
audio output stream was present and could be re-directed to Fldigi, but 
not to WSJT-X.

I was able to restore operation for a brief period by stopping WSJT, 
renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour. 
Repeating the procedure provided operation for the rest of Field Day.

The two .ini files that were renamed are available for your inspection, 
along with the one that continued to function.

Any suggestions you can offer to prevent a recurrence would be greatly 
appreciated.

Regards,
Peter
NI6E






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] WSJT Audio Input Loss

[Bill Frantz]

On 7/3/19 at 2:52 PM, hbasri.schie...@gmail.com (Hasan al-Basri) wrote:


I"m baffled, like I said, it acts like a memory leak and I don't think it's
a coincidence that it showed up the very first time after installing and
running RC7 64 bit.


I don't know if this is relevant, but a while ago I got a 
warning from MacOS 10.14.5 that I was almost out of application 
memory and should quit some applications. I closed a bunch of 
tabs in Firefox, quit everything that I wasn't using (including 
wsjt-x) and didn't get the warning again.


I will note that wsjt-x needs to have the shared memory 
increased as part of the Macintosh install.


73 Bill AE6JV

---
Bill Frantz| Truth and love must prevail  | Periwinkle
(408)356-8506  | over lies and hate.  | 16345 
Englewood Ave
www.pwpconsult.com |   - Vaclav Havel | Los Gatos, 
CA 95032




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Hasan al-Basri]

I also followed the link from Mike and verified that I had already done
what he recommended...months and months ago.
It's not an RFI problem.

I've thought about uninstalling X and then going into the registry and
searching for anything related to WSJT-X and deleting it, along with any
left-over files like *.ini, etc

...but, that's a pretty drastic step for something that might be cured by
the general release or finding and replacing a corrupt file. I just don't
know what to find and what to replace   :-)

73, N0AN

Hasan


On Wed, Jul 3, 2019 at 4:53 PM Peter Putnam  wrote:

> No USB ports are involved in a Flex -> DAX -> WSJT setup. Audio is passed
> from one program to another in memory.
>
> One would not suspect RFI to be the culprit after three hours of steady
> operation at full power without an issue.
>
>
>
> On 7/3/2019 2:36 PM, Black Michael via wsjt-devel wrote:
>
> Failing audio or rig connections are most always due to RFI or USB ports
> going to sleep.
> If RFI low power transmissions can be tested and if they work but high
> power does not then it's RFI.
> The USB ports going to sleep can be solved.
> https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com
>   wrote:
>
>
> I’ve seen this with other radios. Definitely not a flex only issue.
>
> Ria
> N2RJ
>
> On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Peter,
>
> Flex has its own set of unique problems and fixes.  Suggest you post your
> question on the Flex forum page.  Good luck.
>
> Danny
> AH6FX/W4
>
> On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam 
> wrote:
>
>
> Greetings,
>
> I have been using WSJT-X quite successfully for several years during
> June VHF Contests. I experienced a failure of the WSJT program to accept
> received audio input after several hours of proper operation during the
> recent Field Day exercise.
>
> I'll provide a brief outline and reply with more detail, should it be
> needed.
>
> My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The
> WSJT-X software version is 2.0.1 7ddcb7.
>
> My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX"
> program that interfaces various applications that wish to receive the
> audio stream. WSJT accepts the stream and displays results on the Wide
> Graph and a small audio signal-strength window. Activity proceeded
> normally for the first three hours of Field Day, until both the Wide
> Graph and the audio signal-strength stopped showing any incoming audio.
>
> I can't offer any help on what might have caused the problem. It was
> abrupt and seemingly unrelated to any other system actions. I am unable
> to reproduce the problem.
>
> Several operators spent several hours speculating about what a solution
> might be. Program restarts and computer re-boots (time-tested favorite
> of generations) changed nothing. The only useful clue was that the DAX
> audio output stream was present and could be re-directed to Fldigi, but
> not to WSJT-X.
>
> I was able to restore operation for a brief period by stopping WSJT,
> renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour.
> Repeating the procedure provided operation for the rest of Field Day.
>
> The two .ini files that were renamed are available for your inspection,
> along with the one that continued to function.
>
> Any suggestions you can offer to prevent a recurrence would be greatly
> appreciated.
>
> Regards,
> Peter
> NI6E
>
>
>
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

You're correct in that Flex is different in that respect.
I've heard of problems with the audio chain dropping out on Flex before.  Don't 
recall is there was a solution though.
I wonder if the ethernet might have gone to sleep and it burped on that?
de Mike W9MDB

 

On Wednesday, July 3, 2019, 04:50:27 PM CDT, Peter Putnam  
wrote:  
 
  No USB ports are involved in a Flex -> DAX -> WSJT setup. Audio is passed 
from one program to another in memory.
 
 One would not suspect RFI to be the culprit after three hours of steady 
operation at full power without an issue.
 
 
 
 On 7/3/2019 2:36 PM, Black Michael via wsjt-devel wrote:
  
 
  Failing audio or rig connections are most always due to RFI or USB ports 
going to sleep. If RFI low power transmissions can be tested and if they work 
but high power does not then it's RFI. The USB ports going to sleep can be 
solved. 
https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices
  
  de Mike W9MDB 
   

  
  On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
 wrote:  
  
  I’ve seen this with other radios. Definitely not a flex only issue.  
  Ria N2RJ 
   On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel 
 wrote:
  
   Peter, 
  Flex has its own set of unique problems and fixes.  Suggest you post your 
question on the Flex forum page.  Good luck.
  
      Danny     AH6FX/W4
  
On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam 
 wrote:  
  
   Greetings,
  
  I have been using WSJT-X quite successfully for several years during 
  June VHF Contests. I experienced a failure of the WSJT program to accept 
  received audio input after several hours of proper operation during the 
  recent Field Day exercise.
  
  I'll provide a brief outline and reply with more detail, should it be 
  needed.
  
  My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The 
  WSJT-X software version is 2.0.1 7ddcb7.
  
  My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX" 
  program that interfaces various applications that wish to receive the 
  audio stream. WSJT accepts the stream and displays results on the Wide 
  Graph and a small audio signal-strength window. Activity proceeded 
  normally for the first three hours of Field Day, until both the Wide 
  Graph and the audio signal-strength stopped showing any incoming audio.
  
  I can't offer any help on what might have caused the problem. It was 
  abrupt and seemingly unrelated to any other system actions. I am unable 
  to reproduce the problem.
  
  Several operators spent several hours speculating about what a solution 
  might be. Program restarts and computer re-boots (time-tested favorite 
  of generations) changed nothing. The only useful clue was that the DAX 
  audio output stream was present and could be re-directed to Fldigi, but 
  not to WSJT-X.
  
  I was able to restore operation for a brief period by stopping WSJT, 
  renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour. 
  Repeating the procedure provided operation for the rest of Field Day.
  
  The two .ini files that were renamed are available for your inspection, 
  along with the one that continued to function.
  
  Any suggestions you can offer to prevent a recurrence would be greatly 
  appreciated.
  
  Regards,
  Peter
  NI6E
  
  
  
  
  
  
  ___
  wsjt-devel mailing list
  wsjt-devel@lists.sourceforge.net
  https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel
 
  ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel
 
  
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
 
 ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Hasan al-Basri]

Hi Mike,
No transmitting at all. RF Chokes all over the place. No issues running KW
out on any band 6m through 80m. (if I have just rebooted the computer).
Once it has run for several hours. it will stop decoding, whether I have
transmitted or not, no matter qrp or qro. I monitor 24x7 , go days without
tx'ing...it still goes deaf.

IOW, it's not a USB RFI problem.

All power settings for USB have been set to never sleep.

I"m baffled, like I said, it acts like a memory leak and I don't think it's
a coincidence that it showed up the very first time after installing and
running RC7 64 bit.

The problem NEVER showed up b4 RC7 64 bit was installed. I didn't change a
thing in my setup or operating habits. Now I have to reboot every day or it
just stops decoding, even having uninstalled RC7 64 bit and returned to
2.01 Gen Release.

Audio level is perfect, waterfall shows signals...no decode.
Reboot...decodes resume. No other program shows any symptoms like this at
all on the same computer. WSJT-X is running on its own USB Sound Dongle for
both RX and TXand has been for over a year.

Any further ideas are most welcome (TS-590sg, running from headphone jack
for rx audio) Audio sounds perfect to the ear. Levels are right...
Most peculiar!

73, N0AN
Hasan


On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Failing audio or rig connections are most always due to RFI or USB ports
> going to sleep.
> If RFI low power transmissions can be tested and if they work but high
> power does not then it's RFI.
> The USB ports going to sleep can be solved.
> https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices
>
> de Mike W9MDB
>
>
>
>
> On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com <
> rjai...@gmail.com> wrote:
>
>
> I’ve seen this with other radios. Definitely not a flex only issue.
>
> Ria
> N2RJ
>
> On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel <
> wsjt-devel@lists.sourceforge.net> wrote:
>
> Peter,
>
> Flex has its own set of unique problems and fixes.  Suggest you post your
> question on the Flex forum page.  Good luck.
>
> Danny
> AH6FX/W4
>
> On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam 
> wrote:
>
>
> Greetings,
>
> I have been using WSJT-X quite successfully for several years during
> June VHF Contests. I experienced a failure of the WSJT program to accept
> received audio input after several hours of proper operation during the
> recent Field Day exercise.
>
> I'll provide a brief outline and reply with more detail, should it be
> needed.
>
> My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The
> WSJT-X software version is 2.0.1 7ddcb7.
>
> My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX"
> program that interfaces various applications that wish to receive the
> audio stream. WSJT accepts the stream and displays results on the Wide
> Graph and a small audio signal-strength window. Activity proceeded
> normally for the first three hours of Field Day, until both the Wide
> Graph and the audio signal-strength stopped showing any incoming audio.
>
> I can't offer any help on what might have caused the problem. It was
> abrupt and seemingly unrelated to any other system actions. I am unable
> to reproduce the problem.
>
> Several operators spent several hours speculating about what a solution
> might be. Program restarts and computer re-boots (time-tested favorite
> of generations) changed nothing. The only useful clue was that the DAX
> audio output stream was present and could be re-directed to Fldigi, but
> not to WSJT-X.
>
> I was able to restore operation for a brief period by stopping WSJT,
> renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour.
> Repeating the procedure provided operation for the rest of Field Day.
>
> The two .ini files that were renamed are available for your inspection,
> along with the one that continued to function.
>
> Any suggestions you can offer to prevent a recurrence would be greatly
> appreciated.
>
> Regards,
> Peter
> NI6E
>
>
>
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Peter Putnam]

No USB ports are involved in a Flex -> DAX -> WSJT setup. Audio is 
passed from one program to another in memory.


One would not suspect RFI to be the culprit after three hours of steady 
operation at full power without an issue.




On 7/3/2019 2:36 PM, Black Michael via wsjt-devel wrote:
Failing audio or rig connections are most always due to RFI or USB 
ports going to sleep.
If RFI low power transmissions can be tested and if they work but high 
power does not then it's RFI.

The USB ports going to sleep can be solved.
https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices

de Mike W9MDB




On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
 wrote:



I’ve seen this with other radios. Definitely not a flex only issue.

Ria
N2RJ

On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel 
> wrote:


Peter,

Flex has its own set of unique problems and fixes.  Suggest you
post your question on the Flex forum page.  Good luck.

    Danny
    AH6FX/W4

On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam
mailto:pe...@ni6e.com>> wrote:


Greetings,

I have been using WSJT-X quite successfully for several years during
June VHF Contests. I experienced a failure of the WSJT program to
accept
received audio input after several hours of proper operation
during the
recent Field Day exercise.

I'll provide a brief outline and reply with more detail, should it be
needed.

My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The
WSJT-X software version is 2.0.1 7ddcb7.

My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX"
program that interfaces various applications that wish to receive the
audio stream. WSJT accepts the stream and displays results on the
Wide
Graph and a small audio signal-strength window. Activity proceeded
normally for the first three hours of Field Day, until both the Wide
Graph and the audio signal-strength stopped showing any incoming
audio.

I can't offer any help on what might have caused the problem. It was
abrupt and seemingly unrelated to any other system actions. I am
unable
to reproduce the problem.

Several operators spent several hours speculating about what a
solution
might be. Program restarts and computer re-boots (time-tested
favorite
of generations) changed nothing. The only useful clue was that the
DAX
audio output stream was present and could be re-directed to
Fldigi, but
not to WSJT-X.

I was able to restore operation for a brief period by stopping WSJT,
renaming WSJT.ini and restarting WSJT. That fix lasted for a half
hour.
Repeating the procedure provided operation for the rest of Field Day.

The two .ini files that were renamed are available for your
inspection,
along with the one that continued to function.

Any suggestions you can offer to prevent a recurrence would be
greatly
appreciated.

Regards,
Peter
NI6E






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[Black Michael via wsjt-devel]

Failing audio or rig connections are most always due to RFI or USB ports going 
to sleep.If RFI low power transmissions can be tested and if they work but high 
power does not then it's RFI.The USB ports going to sleep can be 
solved.https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices

de Mike W9MDB

 

On Wednesday, July 3, 2019, 04:31:39 PM CDT, rjai...@gmail.com 
 wrote:  
 
 I’ve seen this with other radios. Definitely not a flex only issue.
RiaN2RJ
On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel 
 wrote:

 Peter,
Flex has its own set of unique problems and fixes.  Suggest you post your 
question on the Flex forum page.  Good luck.

    Danny    AH6FX/W4

On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam  
wrote:  
 
 Greetings,

I have been using WSJT-X quite successfully for several years during 
June VHF Contests. I experienced a failure of the WSJT program to accept 
received audio input after several hours of proper operation during the 
recent Field Day exercise.

I'll provide a brief outline and reply with more detail, should it be 
needed.

My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The 
WSJT-X software version is 2.0.1 7ddcb7.

My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX" 
program that interfaces various applications that wish to receive the 
audio stream. WSJT accepts the stream and displays results on the Wide 
Graph and a small audio signal-strength window. Activity proceeded 
normally for the first three hours of Field Day, until both the Wide 
Graph and the audio signal-strength stopped showing any incoming audio.

I can't offer any help on what might have caused the problem. It was 
abrupt and seemingly unrelated to any other system actions. I am unable 
to reproduce the problem.

Several operators spent several hours speculating about what a solution 
might be. Program restarts and computer re-boots (time-tested favorite 
of generations) changed nothing. The only useful clue was that the DAX 
audio output stream was present and could be re-directed to Fldigi, but 
not to WSJT-X.

I was able to restore operation for a brief period by stopping WSJT, 
renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour. 
Repeating the procedure provided operation for the rest of Field Day.

The two .ini files that were renamed are available for your inspection, 
along with the one that continued to function.

Any suggestions you can offer to prevent a recurrence would be greatly 
appreciated.

Regards,
Peter
NI6E






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[rjai...@gmail.com]

I’ve seen this with other radios. Definitely not a flex only issue.

Ria
N2RJ

On Wed, Jul 3, 2019 at 4:58 PM DX Jami via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

> Peter,
>
> Flex has its own set of unique problems and fixes.  Suggest you post your
> question on the Flex forum page.  Good luck.
>
> Danny
> AH6FX/W4
>
> On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam 
> wrote:
>
>
> Greetings,
>
> I have been using WSJT-X quite successfully for several years during
> June VHF Contests. I experienced a failure of the WSJT program to accept
> received audio input after several hours of proper operation during the
> recent Field Day exercise.
>
> I'll provide a brief outline and reply with more detail, should it be
> needed.
>
> My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The
> WSJT-X software version is 2.0.1 7ddcb7.
>
> My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX"
> program that interfaces various applications that wish to receive the
> audio stream. WSJT accepts the stream and displays results on the Wide
> Graph and a small audio signal-strength window. Activity proceeded
> normally for the first three hours of Field Day, until both the Wide
> Graph and the audio signal-strength stopped showing any incoming audio.
>
> I can't offer any help on what might have caused the problem. It was
> abrupt and seemingly unrelated to any other system actions. I am unable
> to reproduce the problem.
>
> Several operators spent several hours speculating about what a solution
> might be. Program restarts and computer re-boots (time-tested favorite
> of generations) changed nothing. The only useful clue was that the DAX
> audio output stream was present and could be re-directed to Fldigi, but
> not to WSJT-X.
>
> I was able to restore operation for a brief period by stopping WSJT,
> renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour.
> Repeating the procedure provided operation for the rest of Field Day.
>
> The two .ini files that were renamed are available for your inspection,
> along with the one that continued to function.
>
> Any suggestions you can offer to prevent a recurrence would be greatly
> appreciated.
>
> Regards,
> Peter
> NI6E
>
>
>
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Audio Input Loss

[DX Jami via wsjt-devel]

 Peter,
Flex has its own set of unique problems and fixes.  Suggest you post your 
question on the Flex forum page.  Good luck.

    Danny    AH6FX/W4

On Wednesday, July 3, 2019, 3:11:48 PM EDT, Peter Putnam  
wrote:  
 
 Greetings,

I have been using WSJT-X quite successfully for several years during 
June VHF Contests. I experienced a failure of the WSJT program to accept 
received audio input after several hours of proper operation during the 
recent Field Day exercise.

I'll provide a brief outline and reply with more detail, should it be 
needed.

My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The 
WSJT-X software version is 2.0.1 7ddcb7.

My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX" 
program that interfaces various applications that wish to receive the 
audio stream. WSJT accepts the stream and displays results on the Wide 
Graph and a small audio signal-strength window. Activity proceeded 
normally for the first three hours of Field Day, until both the Wide 
Graph and the audio signal-strength stopped showing any incoming audio.

I can't offer any help on what might have caused the problem. It was 
abrupt and seemingly unrelated to any other system actions. I am unable 
to reproduce the problem.

Several operators spent several hours speculating about what a solution 
might be. Program restarts and computer re-boots (time-tested favorite 
of generations) changed nothing. The only useful clue was that the DAX 
audio output stream was present and could be re-directed to Fldigi, but 
not to WSJT-X.

I was able to restore operation for a brief period by stopping WSJT, 
renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour. 
Repeating the procedure provided operation for the rest of Field Day.

The two .ini files that were renamed are available for your inspection, 
along with the one that continued to function.

Any suggestions you can offer to prevent a recurrence would be greatly 
appreciated.

Regards,
Peter
NI6E






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT Audio Input Loss

[Peter Putnam]

Greetings,

I have been using WSJT-X quite successfully for several years during 
June VHF Contests. I experienced a failure of the WSJT program to accept 
received audio input after several hours of proper operation during the 
recent Field Day exercise.


I'll provide a brief outline and reply with more detail, should it be 
needed.


My computer is a Dell Optiplex 780 running Win 7 Pro SP1, 64-bit. The 
WSJT-X software version is 2.0.1 7ddcb7.


My receiver is a Flex 6500. It passes data to a Flex-supplied "DAX" 
program that interfaces various applications that wish to receive the 
audio stream. WSJT accepts the stream and displays results on the Wide 
Graph and a small audio signal-strength window. Activity proceeded 
normally for the first three hours of Field Day, until both the Wide 
Graph and the audio signal-strength stopped showing any incoming audio.


I can't offer any help on what might have caused the problem. It was 
abrupt and seemingly unrelated to any other system actions. I am unable 
to reproduce the problem.


Several operators spent several hours speculating about what a solution 
might be. Program restarts and computer re-boots (time-tested favorite 
of generations) changed nothing. The only useful clue was that the DAX 
audio output stream was present and could be re-directed to Fldigi, but 
not to WSJT-X.


I was able to restore operation for a brief period by stopping WSJT, 
renaming WSJT.ini and restarting WSJT. That fix lasted for a half hour. 
Repeating the procedure provided operation for the rest of Field Day.


The two .ini files that were renamed are available for your inspection, 
along with the one that continued to function.


Any suggestions you can offer to prevent a recurrence would be greatly 
appreciated.


Regards,
Peter
NI6E






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Announcing the World Wide Digi DX Contest

[Ken Chandler]

WSJT-X set to log contacts in N1MM!

Ken.. G0ORH

Sent from my iPad


> On 3 Jul 2019, at 18:31, VE3FBZ  wrote:
> 
> I use N3FJP logging program interfaced through JTALERT 
> 
> 
>  Regards and 73s
> VE3FBZ
> London Amateur Radio Club
> www.larc.ca 
> 
> 
> 
> 
>> On Jul 3, 2019, at 11:56, Joe  wrote:
>> 
>> What Logger is anyone planning to use for this contest?
>> 
>> Joe WB9SBD
>> 
>> The Original Rolling Ball Clock
>> Idle Tyme
>> Idle-Tyme.com
>> http://www.idle-tyme.com
>>> On 6/29/2019 3:25 PM, Don Hill AA5AU wrote:
>>> For immediate release. June 29, 2019.
>>>  
>>> The World Wide Radio Operators Foundation (“WWROF”), in collaboration with 
>>> the Slovenia Contest Club (“SCC”), is pleased to announce the first annual 
>>> World Wide Digi DX Contest (“WW Digi”). The new contest taps into the 
>>> excitement being generated by the new digital modes pioneered by Joe Taylor 
>>> K1JT and the WSJT-X development team. The contest will occur over 24 hours 
>>> on August 31 and September 1, 2019 using the FT4 and FT8 modes on the 160, 
>>> 80, 40, 20, 15, and 10-meter bands.
>>>  
>>> WW Digi will utilize a distance-based scoring system to measure operators’ 
>>> abilities in making DX contacts across the 6 HF amateur radio bands. 
>>> Contacts will earn points based on the distance between grid square centers 
>>> of the two stations. This will encourage operators to seek out long 
>>> distance weak signal contacts that highlight the technical advantages of 
>>> the new digital modes.
>>>  
>>> To encourage activity across all bands, a multiplier will be given for each 
>>> new 2-character grid field contacted on each band. The final score will the 
>>> product of the total contact points times the number of grid fields 
>>> contacted. There should be plenty of strategy required to balance distant 
>>> QSOs and the need to work all available grid fields. Single and 
>>> multi-operators are welcome to operate as much or as little of the 24-hour 
>>> contest period as they wish.
>>>  
>>> The contest has been designed to enable making contacts utilizing standard 
>>> WSJT-X software behavior, making it easy for non-contesters to participate. 
>>> At the same time, the contest supports some new techniques that will 
>>> encourage operating innovation, such as permitting stations to work up to 
>>> three “QSO streams” on a band at one time. Robotic operation is 
>>> specifically prohibited in order to keep the human element as part of the 
>>> game. The full rules and other information are available on the WW Digi DX 
>>> contest web site at https://ww-digi.com
>>>  
>>> It is fitting that the World Wide DX contest series be expanded with a 
>>> fourth mode, Digi, to support evolution into ham radio’s future. 
>>> Accordingly, with WWROF’s sponsorship of the World Wide Digi DX Contest, 
>>> there will now be similar worldwide DX contests at the end of four 
>>> successive months, August through November.
>>>  
>>> Serious contesters and casual participants alike can make ham radio history 
>>> and have fun as the hobby pioneers the exciting world of digital 
>>> communication. WWROF hopes the WW Digi DX Contest will attract new digital 
>>> operators into contesting.
>>>  
>>> Plaques will be awarded for top scorers. Please contact the WW Digi Contest 
>>> Director Ed Muns, W0YK at plaq...@ww-digi.com to sponsor an award. 
>>> Electronic certificates will also be available for download for anyone that 
>>> submits a log. The goal is to have results available on the web site within 
>>> 90 days after the end of the contest.
>>>  
>>> About WWROF
>>> The World Wide Radio Operators Foundation is dedicated to improving the 
>>> skills and fun of amateur radio operators around the world by utilizing 
>>> education, competition, advancement of technology and scientific research, 
>>> promoting international friendship and goodwill.
>>> WWROF is a non-profit, donor-supported, organization which sponsors this 
>>> contest and provides the infrastructure for log submission, log checking, 
>>> and other services in support of many popular radio contests. Please visit 
>>> wwrof.org for more information.
>>>  
>>> About SCC
>>> The Slovenia Contest Club has a long tradition of supporting digital 
>>> contesting with its annual RTTY Championship contest held the last weekend 
>>> of August. For more information about SCC please visit 
>>> http://lea.hamradio.si/scc/
>>>  
>>> 
>>> 
>>> 
>>> ___
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> 
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Announcing the World Wide Digi DX Contest

[Edfel Rivera]

Hi Don:

Why not include the 6M band? Know it is mostly active in summer but even
the ARRL Sept VHF (Sept 14-16) include the bad.  Just wondering why to
exclude the 6M.

73'

Edfel
KP4AJ

On Sat, Jun 29, 2019 at 4:50 PM Don Hill AA5AU  wrote:

> For immediate release. June 29, 2019.
>
>
>
> The World Wide Radio Operators Foundation (“WWROF”), in collaboration with
> the Slovenia Contest Club (“SCC”), is pleased to announce the first
> annual World Wide Digi DX Contest (“WW Digi”). The new contest taps into
> the excitement being generated by the new digital modes pioneered by Joe
> Taylor K1JT and the WSJT-X development team. The contest will occur over 24
> hours on August 31 and September 1, 2019 using the FT4 and FT8 modes on the
> 160, 80, 40, 20, 15, and 10-meter bands.
>
>
>
> WW Digi will utilize a distance-based scoring system to measure operators’
> abilities in making DX contacts across the 6 HF amateur radio bands.
> Contacts will earn points based on the distance between grid square centers
> of the two stations. This will encourage operators to seek out long
> distance weak signal contacts that highlight the technical advantages of
> the new digital modes.
>
>
>
> To encourage activity across all bands, a multiplier will be given for
> each new 2-character grid field contacted on each band. The final score
> will the product of the total contact points times the number of grid
> fields contacted. There should be plenty of strategy required to balance
> distant QSOs and the need to work all available grid fields. Single and
> multi-operators are welcome to operate as much or as little of the 24-hour
> contest period as they wish.
>
>
>
> The contest has been designed to enable making contacts utilizing standard
> WSJT-X software behavior, making it easy for non-contesters to participate.
> At the same time, the contest supports some new techniques that will
> encourage operating innovation, such as permitting stations to work up to
> three “QSO streams” on a band at one time. Robotic operation is
> specifically prohibited in order to keep the human element as part of the
> game. The full rules and other information are available on the WW Digi DX
> contest web site at https://ww-digi.com
>
>
>
> It is fitting that the World Wide DX contest series be expanded with a
> fourth mode, Digi, to support evolution into ham radio’s future.
> Accordingly, with WWROF’s sponsorship of the World Wide Digi DX Contest,
> there will now be similar worldwide DX contests at the end of four
> successive months, August through November.
>
>
>
> Serious contesters and casual participants alike can make ham radio
> history and have fun as the hobby pioneers the exciting world of digital
> communication. WWROF hopes the WW Digi DX Contest will attract new digital
> operators into contesting.
>
>
>
> Plaques will be awarded for top scorers. Please contact the WW Digi
> Contest Director Ed Muns, W0YK at plaq...@ww-digi.com to sponsor an
> award. Electronic certificates will also be available for download for
> anyone that submits a log. The goal is to have results available on the web
> site within 90 days after the end of the contest.
>
>
>
> *About WWROF*
>
> The *World Wide Radio Operators Foundation* is dedicated to improving the
> skills and fun of amateur radio operators around the world by utilizing
> education, competition, advancement of technology and scientific research,
> promoting international friendship and goodwill.
>
> WWROF is a non-profit, donor-supported, organization which sponsors this
> contest and provides the infrastructure for log submission, log checking,
> and other services in support of many popular radio contests. Please visit
> wwrof.org for more information.
>
>
>
> *About SCC*
>
> The *Slovenia Contest Club* has a long tradition of supporting digital
> contesting with its annual RTTY Championship contest held the last weekend
> of August. For more information about SCC please visit
> http://lea.hamradio.si/scc/ 
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Announcing the World Wide Digi DX Contest

[VE3FBZ]

I use N3FJP logging program interfaced through JTALERT 


 Regards and 73s
VE3FBZ
London Amateur Radio Club
www.larc.ca 




> On Jul 3, 2019, at 11:56, Joe  wrote:
> 
> What Logger is anyone planning to use for this contest?
> 
> Joe WB9SBD
> 
> The Original Rolling Ball Clock
> Idle Tyme
> Idle-Tyme.com
> http://www.idle-tyme.com
>> On 6/29/2019 3:25 PM, Don Hill AA5AU wrote:
>> For immediate release. June 29, 2019.
>>  
>> The World Wide Radio Operators Foundation (“WWROF”), in collaboration with 
>> the Slovenia Contest Club (“SCC”), is pleased to announce the first annual 
>> World Wide Digi DX Contest (“WW Digi”). The new contest taps into the 
>> excitement being generated by the new digital modes pioneered by Joe Taylor 
>> K1JT and the WSJT-X development team. The contest will occur over 24 hours 
>> on August 31 and September 1, 2019 using the FT4 and FT8 modes on the 160, 
>> 80, 40, 20, 15, and 10-meter bands.
>>  
>> WW Digi will utilize a distance-based scoring system to measure operators’ 
>> abilities in making DX contacts across the 6 HF amateur radio bands. 
>> Contacts will earn points based on the distance between grid square centers 
>> of the two stations. This will encourage operators to seek out long distance 
>> weak signal contacts that highlight the technical advantages of the new 
>> digital modes.
>>  
>> To encourage activity across all bands, a multiplier will be given for each 
>> new 2-character grid field contacted on each band. The final score will the 
>> product of the total contact points times the number of grid fields 
>> contacted. There should be plenty of strategy required to balance distant 
>> QSOs and the need to work all available grid fields. Single and 
>> multi-operators are welcome to operate as much or as little of the 24-hour 
>> contest period as they wish.
>>  
>> The contest has been designed to enable making contacts utilizing standard 
>> WSJT-X software behavior, making it easy for non-contesters to participate. 
>> At the same time, the contest supports some new techniques that will 
>> encourage operating innovation, such as permitting stations to work up to 
>> three “QSO streams” on a band at one time. Robotic operation is specifically 
>> prohibited in order to keep the human element as part of the game. The full 
>> rules and other information are available on the WW Digi DX contest web site 
>> at https://ww-digi.com
>>  
>> It is fitting that the World Wide DX contest series be expanded with a 
>> fourth mode, Digi, to support evolution into ham radio’s future. 
>> Accordingly, with WWROF’s sponsorship of the World Wide Digi DX Contest, 
>> there will now be similar worldwide DX contests at the end of four 
>> successive months, August through November.
>>  
>> Serious contesters and casual participants alike can make ham radio history 
>> and have fun as the hobby pioneers the exciting world of digital 
>> communication. WWROF hopes the WW Digi DX Contest will attract new digital 
>> operators into contesting.
>>  
>> Plaques will be awarded for top scorers. Please contact the WW Digi Contest 
>> Director Ed Muns, W0YK at plaq...@ww-digi.com to sponsor an award. 
>> Electronic certificates will also be available for download for anyone that 
>> submits a log. The goal is to have results available on the web site within 
>> 90 days after the end of the contest.
>>  
>> About WWROF
>> The World Wide Radio Operators Foundation is dedicated to improving the 
>> skills and fun of amateur radio operators around the world by utilizing 
>> education, competition, advancement of technology and scientific research, 
>> promoting international friendship and goodwill.
>> WWROF is a non-profit, donor-supported, organization which sponsors this 
>> contest and provides the infrastructure for log submission, log checking, 
>> and other services in support of many popular radio contests. Please visit 
>> wwrof.org for more information.
>>  
>> About SCC
>> The Slovenia Contest Club has a long tradition of supporting digital 
>> contesting with its annual RTTY Championship contest held the last weekend 
>> of August. For more information about SCC please visit 
>> http://lea.hamradio.si/scc/
>>  
>> 
>> 
>> 
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Announcing the World Wide Digi DX Contest

[Joe]

What Logger is anyone planning to use for this contest?

Joe WB9SBD
Sig
The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com
On 6/29/2019 3:25 PM, Don Hill AA5AU wrote:


For immediate release. June 29, 2019.

The World Wide Radio Operators Foundation (“WWROF”), in collaboration 
with the Slovenia Contest Club (“SCC”), is pleased to announce the 
first annual World Wide Digi DX Contest (“WW Digi”). The new contest 
taps into the excitement being generated by the new digital modes 
pioneered by Joe Taylor K1JT and the WSJT-X development team. The 
contest will occur over 24 hours on August 31 and September 1, 2019 
using the FT4 and FT8 modes on the 160, 80, 40, 20, 15, and 10-meter 
bands.


WW Digi will utilize a distance-based scoring system to measure 
operators’ abilities in making DX contacts across the 6 HF amateur 
radio bands. Contacts will earn points based on the distance between 
grid square centers of the two stations. This will encourage operators 
to seek out long distance weak signal contacts that highlight the 
technical advantages of the new digital modes.


To encourage activity across all bands, a multiplier will be given for 
each new 2-character grid field contacted on each band. The final 
score will the product of the total contact points times the number of 
grid fields contacted. There should be plenty of strategy required to 
balance distant QSOs and the need to work all available grid fields. 
Single and multi-operators are welcome to operate as much or as little 
of the 24-hour contest period as they wish.


The contest has been designed to enable making contacts utilizing 
standard WSJT-X software behavior, making it easy for non-contesters 
to participate. At the same time, the contest supports some new 
techniques that will encourage operating innovation, such as 
permitting stations to work up to three “QSO streams” on a band at one 
time. Robotic operation is specifically prohibited in order to keep 
the human element as part of the game. The full rules and other 
information are available on the WW Digi DX contest web site at 
https://ww-digi.com


It is fitting that the World Wide DX contest series be expanded with a 
fourth mode, Digi, to support evolution into ham radio’s future. 
Accordingly, with WWROF’s sponsorship of the World Wide Digi DX 
Contest, there will now be similar worldwide DX contests at the end of 
four successive months, August through November.


Serious contesters and casual participants alike can make ham radio 
history and have fun as the hobby pioneers the exciting world of 
digital communication. WWROF hopes the WW Digi DX Contest will attract 
new digital operators into contesting.


Plaques will be awarded for top scorers. Please contact the WW Digi 
Contest Director Ed Muns, W0YK at plaq...@ww-digi.com 
 to sponsor an award. Electronic 
certificates will also be available for download for anyone that 
submits a log. The goal is to have results available on the web site 
within 90 days after the end of the contest.


*About WWROF*

The***World Wide Radio Operators Foundation*is dedicated to improving 
the skills and fun of amateur radio operators around the world by 
utilizing education, competition, advancement of technology and 
scientific research, promoting international friendship and goodwill.


WWROF is a non-profit, donor-supported, organization which sponsors 
this contest and provides the infrastructure for log submission, log 
checking, and other services in support of many popular radio 
contests. Please visit wwrof.org  for more information.


*About SCC***

The *Slovenia Contest Club* has a long tradition of supporting digital 
contesting with its annual RTTY Championship contest held the last 
weekend of August. For more information about SCC please visit 
http://lea.hamradio.si/scc/ 




___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] clock patch

[Dan Malcolm]

My $0.02 worth.  I have the exact same GPS Hasan has.  I’m also running 
Meinberg.  I have the advantage of running Meinberg with internet time pools 
alongside the GPS.  While the GPS show significant jitter, its availability to 
Meinberg consistently yields <5ms offset from time.is.  Without the GPS, offset 
from time.is will run to 10-15ms.  I realize that is not a problem for WSJT-X, 
but my point is that even with jitter, the UPS GPS does improve my time 
accuracy, even if only a smidgen (note the techno speak ☺ )

__
Dan – K4SHQ

From: Roeland Jansen [mailto:roeland.janse...@gmail.com]
Sent: Wednesday, July 3, 2019 10:07 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] clock patch

be aware of that if a) is 500 ms ahead and b) is 500 behind, the time skew is 
already 1 second between the signals.

Anything more than a few ms is not good imho. Anyways, use whatever deems 
suitable for you.


On Wed, Jul 3, 2019 at 4:33 PM Hasan al-Basri 
mailto:hbasri.schie...@gmail.com>> wrote:
Yep, I'm aware of the potential latency issues, again, 500 ms is quite 
acceptable for the X suite...and I see far better than that.

I haven't seen anywhere close to 500 ms errors against GPSDO (not usb) with my 
USB GPS. ..and that's with days of data collected and subject to statistical 
analysis. See the attached graphic.

Not perfect, but way better and way cheaper than most other alternatives, 
especially if stuck away from home. 73, N0AN
Hasan


On Wed, Jul 3, 2019 at 9:16 AM Roeland Jansen 
mailto:roeland.janse...@gmail.com>> wrote:
the issue is not the device but the USB protocol -- it's well known for latency 
issues. It's super that it works for you.

We have in .nl a few synchronized receivers and transmitters for repeaters and 
no way USB can be used there.

But hey -- if it works for you, it's ok. But be aware of the mentioned issues. 
And 500+ms wrong times are seen more.
I would not even consider it myself.


On Wed, Jul 3, 2019 at 3:57 PM Hasan al-Basri 
mailto:hbasri.schie...@gmail.com>> wrote:
Not all USB based GPS have issues. Not all software is the same. NMEATime2 does 
not show the issues you describe with a USB GPS. while the BKT software does. 
(for me)

This one, from Amazon works. I have two of them.

GlobalSat BU-353-S4 USB GPS Receiver (Black)

The above USB based GPS used with NMEATime2, is certainly accurate enough for 
all the WSJT-X suite of programsand many of us have the DT to prove it.

Please don't throw the baby out with the bath water, with a pursuit of 
unnecessary perfection.

73, N0AN
Hasan


On Wed, Jul 3, 2019 at 3:07 AM Matthew Miller 
mailto:mmill...@mail.umw.edu>> wrote:
Beware those GPS receivers – I got one (unstable latency was throwing me off by 
as much as 550mS on NTP) and I found that when I tried to set up ntpd to use 
GPS it was showing jitter of around 0.8 seconds.

Further research, USB GPS is a BAD IDEA because there is often buffering in the 
serial-USB converter chips as well as overhead with the USB protocol.  
Depending on what port you use it may also be connected thru one or more hubs 
adding additional overhead and latency.  You may not “see” a hub but many 
computers now have internal USB hubs for touchpad, keyboard, webcams, 
touchscreens, Bluetooth, and a variety of other “built in” features that now 
all hang off internal hubs.

If you are going to go with a proper GPS time sync you really need a non-USB 
serial GPS and PPS input…which is not trivial.

Its not cheap, but I solved my problem with one of these…its plug and play then 
just set your computer to point at its IP address.  I now have a reliable 
source that indicates it has only 0.5mS jitter and 3mS latency even going thru 
multiple network switches and a fairly busy WiFi network.
https://timemachinescorp.com/product/gps-time-server-tm1000a/

There are also other cheaper DIY Raspberry Pi projects (which have some of 
their own challenges I didn’t feel like dealing with right now) that can be 
built for under $100 to make a stratum-1 time server that works without 
Internet but PLEASE PLEASE do not tell people to use USB GPS for time, its 
going to increase the problems not fix them!

-Matt / KK4NDE

From: Neal Pollack [mailto:nea...@gmail.com]
Sent: Wednesday, June 26, 2019 12:08 PM
To: WSJT software development
Subject: Re: [wsjt-devel] clock patch

Only some are due to lack of internet.
USB GPS receivers are now approx $12 USD on Ebay.  I have tested a few and they 
work fine with NMEAtime2. Which is none simple software.
The message could suggest what to do for both internet connected and off-grid 
users.  But really, to keep the message short, it should point to a help page 
or file that is specific to time setting options, rather than a huge user 
guide, since the public no longer reads very much.

With regard to time setting software, I really can't recommend BKTtimeSync for 
the same reasons we are discussing this issue:  It works for me but 

Re: [wsjt-devel] clock patch

[Roeland Jansen]

be aware of that if a) is 500 ms ahead and b) is 500 behind, the time skew
is already 1 second between the signals.

Anything more than a few ms is not good imho. Anyways, use whatever deems
suitable for you.



On Wed, Jul 3, 2019 at 4:33 PM Hasan al-Basri 
wrote:

> Yep, I'm aware of the potential latency issues, again, 500 ms is quite
> acceptable for the X suite...and I see far better than that.
>
> I haven't seen anywhere close to 500 ms errors against GPSDO (not usb)
> with my USB GPS. ..and that's with days of data collected and subject to
> statistical analysis. See the attached graphic.
>
> Not perfect, but way better and way cheaper than most other alternatives,
> especially if stuck away from home. 73, N0AN
> Hasan
>
>
> On Wed, Jul 3, 2019 at 9:16 AM Roeland Jansen 
> wrote:
>
>> the issue is not the device but the USB protocol -- it's well known for
>> latency issues. It's super that it works for you.
>>
>> We have in .nl a few synchronized receivers and transmitters for
>> repeaters and no way USB can be used there.
>>
>> But hey -- if it works for you, it's ok. But be aware of the mentioned
>> issues. And 500+ms wrong times are seen more.
>> I would not even consider it myself.
>>
>>
>> On Wed, Jul 3, 2019 at 3:57 PM Hasan al-Basri 
>> wrote:
>>
>>> Not all USB based GPS have issues. Not all software is the same.
>>> NMEATime2 does not show the issues you describe with a USB GPS. while the
>>> BKT software does. (for me)
>>>
>>> This one, from Amazon works. I have two of them.
>>>
>>> GlobalSat BU-353-S4 USB GPS Receiver (Black)
>>>
>>> The above USB based GPS used with NMEATime2, is certainly accurate
>>> enough for all the WSJT-X suite of programsand many of us have the DT
>>> to prove it.
>>>
>>> Please don't throw the baby out with the bath water, with a pursuit of
>>> unnecessary perfection.
>>>
>>> 73, N0AN
>>> Hasan
>>>
>>>
>>> On Wed, Jul 3, 2019 at 3:07 AM Matthew Miller 
>>> wrote:
>>>
 Beware those GPS receivers – I got one (unstable latency was throwing
 me off by as much as 550mS on NTP) and I found that when I tried to set up
 ntpd to use GPS it was showing jitter of around 0.8 seconds.



 Further research, USB GPS is a BAD IDEA because there is often
 buffering in the serial-USB converter chips as well as overhead with the
 USB protocol.  Depending on what port you use it may also be connected thru
 one or more hubs adding additional overhead and latency.  You may not “see”
 a hub but many computers now have internal USB hubs for touchpad, keyboard,
 webcams, touchscreens, Bluetooth, and a variety of other “built in”
 features that now all hang off internal hubs.



 If you are going to go with a proper GPS time sync you really need a
 non-USB serial GPS and PPS input…which is not trivial.



 Its not cheap, but I solved my problem with one of these…its plug and
 play then just set your computer to point at its IP address.  I now have a
 reliable source that indicates it has only 0.5mS jitter and 3mS latency
 even going thru multiple network switches and a fairly busy WiFi network.

 https://timemachinescorp.com/product/gps-time-server-tm1000a/



 There are also other cheaper DIY Raspberry Pi projects (which have some
 of their own challenges I didn’t feel like dealing with right now) that can
 be built for under $100 to make a stratum-1 time server that works without
 Internet but PLEASE PLEASE do not tell people to use USB GPS for time, its
 going to increase the problems not fix them!



 -Matt / KK4NDE



 *From:* Neal Pollack [mailto:nea...@gmail.com]
 *Sent:* Wednesday, June 26, 2019 12:08 PM
 *To:* WSJT software development
 *Subject:* Re: [wsjt-devel] clock patch



 Only some are due to lack of internet.

 USB GPS receivers are now approx $12 USD on Ebay.  I have tested a few
 and they work fine with NMEAtime2. Which is none simple software.

 The message could suggest what to do for both internet connected and
 off-grid users.  But really, to keep the message short, it should point to
 a help page or file that is specific to time setting options, rather than a
 huge user guide, since the public no longer reads very much.



 With regard to time setting software, I really can't recommend
 BKTtimeSync for the same reasons we are discussing this issue:  It works
 for me but is far too complicated for the average ham, and lacks sufficient
 docs or help.



 But NMEAtime2 is really simple and just works, for using GPS.



 For internet users,  NetTime or Dimension4 for basic users or Meinberg
 NTP for more advanced users.



 BUT!!!  All of the users, both internet and GPS, need to be reminded to
 turn OFF windows automatic time setting before using the 

Re: [wsjt-devel] clock patch

[Roeland Jansen]

the issue is not the device but the USB protocol -- it's well known for
latency issues. It's super that it works for you.

We have in .nl a few synchronized receivers and transmitters for repeaters
and no way USB can be used there.

But hey -- if it works for you, it's ok. But be aware of the mentioned
issues. And 500+ms wrong times are seen more.
I would not even consider it myself.


On Wed, Jul 3, 2019 at 3:57 PM Hasan al-Basri 
wrote:

> Not all USB based GPS have issues. Not all software is the same. NMEATime2
> does not show the issues you describe with a USB GPS. while the BKT
> software does. (for me)
>
> This one, from Amazon works. I have two of them.
>
> GlobalSat BU-353-S4 USB GPS Receiver (Black)
>
> The above USB based GPS used with NMEATime2, is certainly accurate enough
> for all the WSJT-X suite of programsand many of us have the DT to prove
> it.
>
> Please don't throw the baby out with the bath water, with a pursuit of
> unnecessary perfection.
>
> 73, N0AN
> Hasan
>
>
> On Wed, Jul 3, 2019 at 3:07 AM Matthew Miller 
> wrote:
>
>> Beware those GPS receivers – I got one (unstable latency was throwing me
>> off by as much as 550mS on NTP) and I found that when I tried to set up
>> ntpd to use GPS it was showing jitter of around 0.8 seconds.
>>
>>
>>
>> Further research, USB GPS is a BAD IDEA because there is often buffering
>> in the serial-USB converter chips as well as overhead with the USB
>> protocol.  Depending on what port you use it may also be connected thru one
>> or more hubs adding additional overhead and latency.  You may not “see” a
>> hub but many computers now have internal USB hubs for touchpad, keyboard,
>> webcams, touchscreens, Bluetooth, and a variety of other “built in”
>> features that now all hang off internal hubs.
>>
>>
>>
>> If you are going to go with a proper GPS time sync you really need a
>> non-USB serial GPS and PPS input…which is not trivial.
>>
>>
>>
>> Its not cheap, but I solved my problem with one of these…its plug and
>> play then just set your computer to point at its IP address.  I now have a
>> reliable source that indicates it has only 0.5mS jitter and 3mS latency
>> even going thru multiple network switches and a fairly busy WiFi network.
>>
>> https://timemachinescorp.com/product/gps-time-server-tm1000a/
>>
>>
>>
>> There are also other cheaper DIY Raspberry Pi projects (which have some
>> of their own challenges I didn’t feel like dealing with right now) that can
>> be built for under $100 to make a stratum-1 time server that works without
>> Internet but PLEASE PLEASE do not tell people to use USB GPS for time, its
>> going to increase the problems not fix them!
>>
>>
>>
>> -Matt / KK4NDE
>>
>>
>>
>> *From:* Neal Pollack [mailto:nea...@gmail.com]
>> *Sent:* Wednesday, June 26, 2019 12:08 PM
>> *To:* WSJT software development
>> *Subject:* Re: [wsjt-devel] clock patch
>>
>>
>>
>> Only some are due to lack of internet.
>>
>> USB GPS receivers are now approx $12 USD on Ebay.  I have tested a few
>> and they work fine with NMEAtime2. Which is none simple software.
>>
>> The message could suggest what to do for both internet connected and
>> off-grid users.  But really, to keep the message short, it should point to
>> a help page or file that is specific to time setting options, rather than a
>> huge user guide, since the public no longer reads very much.
>>
>>
>>
>> With regard to time setting software, I really can't recommend
>> BKTtimeSync for the same reasons we are discussing this issue:  It works
>> for me but is far too complicated for the average ham, and lacks sufficient
>> docs or help.
>>
>>
>>
>> But NMEAtime2 is really simple and just works, for using GPS.
>>
>>
>>
>> For internet users,  NetTime or Dimension4 for basic users or Meinberg
>> NTP for more advanced users.
>>
>>
>>
>> BUT!!!  All of the users, both internet and GPS, need to be reminded to
>> turn OFF windows automatic time setting before using the software's above.
>> I see too many users whose DT is swinging wildly between plus and minus 2.5
>> seconds, then next at 0.2 DT.  This is because they have windows trying to
>> set time while also using the above programs to set time, and the two are
>> fighting a tug of war.
>>
>>
>>
>> If you guys put a DT warning message in the code that points to a time
>> help page, then I volunteer to be one of several editors for the above type
>> of help content about time sync'ing options.
>>
>>
>>
>> Cheers,
>>
>>
>>
>> Neal
>>
>> N6YFM
>>
>>
>>
>> On Wed, Jun 26, 2019, 3:16 AM 
>> wrote:
>>
>> Send wsjt-devel mailing list submissions to
>> wsjt-devel@lists.sourceforge.net
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>> or, via email, send a message with subject or body 'help' to
>> wsjt-devel-requ...@lists.sourceforge.net
>>
>> You can reach the person managing the list at
>> wsjt-devel-ow...@lists.sourceforge.net
>>
>> 

Re: [wsjt-devel] clock patch

[Hasan al-Basri]

Not all USB based GPS have issues. Not all software is the same. NMEATime2
does not show the issues you describe with a USB GPS. while the BKT
software does. (for me)

This one, from Amazon works. I have two of them.

GlobalSat BU-353-S4 USB GPS Receiver (Black)

The above USB based GPS used with NMEATime2, is certainly accurate enough
for all the WSJT-X suite of programsand many of us have the DT to prove
it.

Please don't throw the baby out with the bath water, with a pursuit of
unnecessary perfection.

73, N0AN
Hasan


On Wed, Jul 3, 2019 at 3:07 AM Matthew Miller  wrote:

> Beware those GPS receivers – I got one (unstable latency was throwing me
> off by as much as 550mS on NTP) and I found that when I tried to set up
> ntpd to use GPS it was showing jitter of around 0.8 seconds.
>
>
>
> Further research, USB GPS is a BAD IDEA because there is often buffering
> in the serial-USB converter chips as well as overhead with the USB
> protocol.  Depending on what port you use it may also be connected thru one
> or more hubs adding additional overhead and latency.  You may not “see” a
> hub but many computers now have internal USB hubs for touchpad, keyboard,
> webcams, touchscreens, Bluetooth, and a variety of other “built in”
> features that now all hang off internal hubs.
>
>
>
> If you are going to go with a proper GPS time sync you really need a
> non-USB serial GPS and PPS input…which is not trivial.
>
>
>
> Its not cheap, but I solved my problem with one of these…its plug and play
> then just set your computer to point at its IP address.  I now have a
> reliable source that indicates it has only 0.5mS jitter and 3mS latency
> even going thru multiple network switches and a fairly busy WiFi network.
>
> https://timemachinescorp.com/product/gps-time-server-tm1000a/
>
>
>
> There are also other cheaper DIY Raspberry Pi projects (which have some of
> their own challenges I didn’t feel like dealing with right now) that can be
> built for under $100 to make a stratum-1 time server that works without
> Internet but PLEASE PLEASE do not tell people to use USB GPS for time, its
> going to increase the problems not fix them!
>
>
>
> -Matt / KK4NDE
>
>
>
> *From:* Neal Pollack [mailto:nea...@gmail.com]
> *Sent:* Wednesday, June 26, 2019 12:08 PM
> *To:* WSJT software development
> *Subject:* Re: [wsjt-devel] clock patch
>
>
>
> Only some are due to lack of internet.
>
> USB GPS receivers are now approx $12 USD on Ebay.  I have tested a few
> and they work fine with NMEAtime2. Which is none simple software.
>
> The message could suggest what to do for both internet connected and
> off-grid users.  But really, to keep the message short, it should point to
> a help page or file that is specific to time setting options, rather than a
> huge user guide, since the public no longer reads very much.
>
>
>
> With regard to time setting software, I really can't recommend BKTtimeSync
> for the same reasons we are discussing this issue:  It works for me but is
> far too complicated for the average ham, and lacks sufficient docs or help.
>
>
>
> But NMEAtime2 is really simple and just works, for using GPS.
>
>
>
> For internet users,  NetTime or Dimension4 for basic users or Meinberg NTP
> for more advanced users.
>
>
>
> BUT!!!  All of the users, both internet and GPS, need to be reminded to
> turn OFF windows automatic time setting before using the software's above.
> I see too many users whose DT is swinging wildly between plus and minus 2.5
> seconds, then next at 0.2 DT.  This is because they have windows trying to
> set time while also using the above programs to set time, and the two are
> fighting a tug of war.
>
>
>
> If you guys put a DT warning message in the code that points to a time
> help page, then I volunteer to be one of several editors for the above type
> of help content about time sync'ing options.
>
>
>
> Cheers,
>
>
>
> Neal
>
> N6YFM
>
>
>
> On Wed, Jun 26, 2019, 3:16 AM 
> wrote:
>
> Send wsjt-devel mailing list submissions to
> wsjt-devel@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> or, via email, send a message with subject or body 'help' to
> wsjt-devel-requ...@lists.sourceforge.net
>
> You can reach the person managing the list at
> wsjt-devel-ow...@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of wsjt-devel digest..."
>
>
> Today's Topics:
>
>1. Re: Clock patch (DG2YCB, Uwe)
>2. Re: Clock patch (Roeland Jansen)
>3. Re: Clock patch (Bill Somerville)
>
>
> --
>
> Message: 1
> Date: Wed, 26 Jun 2019 11:36:58 +0200
> From: "DG2YCB, Uwe" 
> To: "'Black Michael'" , "'WSJT software
> development'" 
> Subject: Re: [wsjt-devel] Clock patch
> Message-ID: <004801d52c02$b33f1430$19bd3c90$@gmx.de>
> Content-Type: 

Re: [wsjt-devel] clock patch

[Matthew Miller]

Beware those GPS receivers – I got one (unstable latency was throwing me off by 
as much as 550mS on NTP) and I found that when I tried to set up ntpd to use 
GPS it was showing jitter of around 0.8 seconds.

Further research, USB GPS is a BAD IDEA because there is often buffering in the 
serial-USB converter chips as well as overhead with the USB protocol.  
Depending on what port you use it may also be connected thru one or more hubs 
adding additional overhead and latency.  You may not “see” a hub but many 
computers now have internal USB hubs for touchpad, keyboard, webcams, 
touchscreens, Bluetooth, and a variety of other “built in” features that now 
all hang off internal hubs.

If you are going to go with a proper GPS time sync you really need a non-USB 
serial GPS and PPS input…which is not trivial.

Its not cheap, but I solved my problem with one of these…its plug and play then 
just set your computer to point at its IP address.  I now have a reliable 
source that indicates it has only 0.5mS jitter and 3mS latency even going thru 
multiple network switches and a fairly busy WiFi network.
https://timemachinescorp.com/product/gps-time-server-tm1000a/

There are also other cheaper DIY Raspberry Pi projects (which have some of 
their own challenges I didn’t feel like dealing with right now) that can be 
built for under $100 to make a stratum-1 time server that works without 
Internet but PLEASE PLEASE do not tell people to use USB GPS for time, its 
going to increase the problems not fix them!

-Matt / KK4NDE

From: Neal Pollack [mailto:nea...@gmail.com]
Sent: Wednesday, June 26, 2019 12:08 PM
To: WSJT software development
Subject: Re: [wsjt-devel] clock patch

Only some are due to lack of internet.
USB GPS receivers are now approx $12 USD on Ebay.  I have tested a few and they 
work fine with NMEAtime2. Which is none simple software.
The message could suggest what to do for both internet connected and off-grid 
users.  But really, to keep the message short, it should point to a help page 
or file that is specific to time setting options, rather than a huge user 
guide, since the public no longer reads very much.

With regard to time setting software, I really can't recommend BKTtimeSync for 
the same reasons we are discussing this issue:  It works for me but is far too 
complicated for the average ham, and lacks sufficient docs or help.

But NMEAtime2 is really simple and just works, for using GPS.

For internet users,  NetTime or Dimension4 for basic users or Meinberg NTP for 
more advanced users.

BUT!!!  All of the users, both internet and GPS, need to be reminded to turn 
OFF windows automatic time setting before using the software's above.  I see 
too many users whose DT is swinging wildly between plus and minus 2.5 seconds, 
then next at 0.2 DT.  This is because they have windows trying to set time 
while also using the above programs to set time, and the two are fighting a tug 
of war.

If you guys put a DT warning message in the code that points to a time help 
page, then I volunteer to be one of several editors for the above type of help 
content about time sync'ing options.

Cheers,

Neal
N6YFM

On Wed, Jun 26, 2019, 3:16 AM 
mailto:wsjt-devel-requ...@lists.sourceforge.net>>
 wrote:
Send wsjt-devel mailing list submissions to

wsjt-devel@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
or, via email, send a message with subject or body 'help' to

wsjt-devel-requ...@lists.sourceforge.net

You can reach the person managing the list at

wsjt-devel-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of wsjt-devel digest..."


Today's Topics:

   1. Re: Clock patch (DG2YCB, Uwe)
   2. Re: Clock patch (Roeland Jansen)
   3. Re: Clock patch (Bill Somerville)


--

Message: 1
Date: Wed, 26 Jun 2019 11:36:58 +0200
From: "DG2YCB, Uwe" mailto:dg2...@gmx.de>>
To: "'Black Michael'" mailto:mdblac...@yahoo.com>>, "'WSJT 
software
development'" 
mailto:wsjt-devel@lists.sourceforge.net>>
Subject: Re: [wsjt-devel] Clock patch
Message-ID: <004801d52c02$b33f1430$19bd3c90$@gmx.de>
Content-Type: text/plain; charset="utf-8"

I?ve not yet seen the results, but your this approach really looks like 
something which could bring a substantial progress regarding the timing issue.



Reason why I am supporting a warning message is that, besides field days, I saw 
dozens of OMs/YLs who are not aware at all that system time of their PCs needed 
to by synced. Alone two examples yesterday. Contacted both. Seemed to be both 
are ?old? men, with no computer skills. One replied the following: ?I am no 
longer a very young