[Elecraft] Elecraft CW Net Announcement
Good Evening, A small sunspot group appeared this week. It was unable to improve propagation. We had a short taste of the rainy season too. Lows dipped into the 30s and more leaves fell. The layer of shrubs underneath the canopy have turned yellow, gold, and red. The fir trees were also effected; losing more needles than they have in months. Any sort of breeze creates a shower of them. The squirrels are active, they clip the new crop of fir cones. When two of them are snipping cones there is a steady sound of cones hitting the ground and many branches on the way down. One can strip a thirty foot branch in less than a minute. The clear cut is creeping closer but they have dropped into a canyon so the noise is less. Please join us tomorrow on: 14050 kHz at 2200z Sunday (3 PM PDT Sunday) 7047 kHz at z Monday (5 PM PDT Sunday) 73, Kevin. KD5ONS _ __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] CODEC
But if they want to install a third party time sync program they are better off installing W3HCF's definitive implementation of the NTP protocol, rather than a program that was, I believe, really designed for Windows 3.1/95. In 06/10/18 21:15, Larry (K8UT) wrote: The user has two choices: use Regedit and mess with the Windows registry to reduce the interval; or install a time sync program. For most, the second option is easier. __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] CODEC
Except, again, MS hacked NTP years ago to lose accuracy to assist their sloppy legacy networking, with the results being that it's considered 'good' if within several MINUTES. This could explain why some FT8 users are lagging by a second or two, which is fatal for decoding (plus it's not 'on' by default). If it works for you, great, it's not by design. Add the new NTP program over it (Dimension 4, Meinburg) and you never have to remember to update before playing, plus it's accurate within .02 or less seconds. The other (minor) bonus is that these provide tracking so when you boot, the median error is already known so you're accurate more quickly. For me, simple just ROCKS. Rick nhc On 10/6/2018 1:39 PM, Bob McGraw K4TAX wrote: Or if you will, when you sit down to operate, go to Windows Time and Date and update the time. More than adequately accurate for several hours of operation. Bob, K4TAX Sent from my iPhone On Oct 6, 2018, at 3:15 PM, Larry (K8UT) wrote: David There should be very little reason to use Dimension 4 There is often a significant gap between Theory and Practice, and such is the case with using Windows as a self-regulated timepiece. True, Windows is a well behaved ntp client, but the default interval for Windows "phoning home" to resync is 7 days. In 7 days my PC has drifted so far that FT8 operation is impossible. The user has two choices: use Regedit and mess with the Windows registry to reduce the interval; or install a time sync program. For most, the second option is easier. -larry (K8UT) -- Original Message -- From: "David Woolley" To: "Mike Greenway" ; elecraft@mailman.qth.net Sent: 2018-10-06 08:27:19 Subject: Re: [Elecraft] CODEC There should be very little reason to use Dimension 4, with step updates at fixed intervals. The full implementation of ntpd is available for all the Windows NT family, i.e. everything after Windows 95, and versions or w32time that can be configured to implement the older version of NTP have been supplied with Windows since at least Windows XP. The standard ntpd always works by managing clock frequency, so there are no abrupt time steps unless something has gone sufficiently wrong to result in a step of at least 200ms. w32time can be configured to work that way, although generally installing the standard (reference) version of ntpd is preferred. (ntpd can be configured to almost never step the time.) Although Windows is not a good platform for time keeping, both these approaches ought to produce times accurate to about 20ms, and only slowly changing with time. In some circumstances, Linux can produce several orders of magnitude better results. On 04/10/18 22:32, Mike Greenway wrote: As previously posted the problem had nothing to do with CODEC or the K3S. Problem turned out to be the time update of the computer by Dimension 4. I had it set for updates every 1 sec as I didn’t think that was a problem. I now have it set for 30 Mins and probably and hour would not hurt anything as every 15 secs it does about .049 correction on my computer. I don’t think it is abnormal for the Rates on WSJT-10 to jump out of range when a time update is done to the computer. Something you cant see on WSJT-X or JTDX. Thanks to all that wrote with suggestions, all of them good. 73 Mike K4PI __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to k...@charter.net __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to rmcg...@blomand.net __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to wa6...@gmail.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] CODEC
On 2018-10-06 4:15 PM, Larry (K8UT) wrote: The user has two choices: use Regedit and mess with the Windows registry to reduce the interval; or install a time sync program. For most, the second option is easier. Actually, there is a third option ... install a proper NTP service like Meinberg NTP to replace the Windows NTP client. Once Meinberg is installed and configured, Windows time never drifts more than a fraction of a millisecond. 73, ... Joe, W4TV __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] CODEC
Or if you will, when you sit down to operate, go to Windows Time and Date and update the time. More than adequately accurate for several hours of operation. Bob, K4TAX Sent from my iPhone > On Oct 6, 2018, at 3:15 PM, Larry (K8UT) wrote: > > David > > >There should be very little reason to use Dimension 4 > There is often a significant gap between Theory and Practice, and such is the > case with using Windows as a self-regulated timepiece. True, Windows is a > well behaved ntp client, but the default interval for Windows "phoning home" > to resync is 7 days. In 7 days my PC has drifted so far that FT8 operation is > impossible. > > The user has two choices: use Regedit and mess with the Windows registry to > reduce the interval; or install a time sync program. For most, the second > option is easier. > > -larry (K8UT) > > -- Original Message -- > From: "David Woolley" > To: "Mike Greenway" ; elecraft@mailman.qth.net > Sent: 2018-10-06 08:27:19 > Subject: Re: [Elecraft] CODEC > >> There should be very little reason to use Dimension 4, with step updates at >> fixed intervals. The full implementation of ntpd is available for all the >> Windows NT family, i.e. everything after Windows 95, and versions or w32time >> that can be configured to implement the older version of NTP have been >> supplied with Windows since at least Windows XP. >> >> The standard ntpd always works by managing clock frequency, so there are no >> abrupt time steps unless something has gone sufficiently wrong to result in >> a step of at least 200ms. w32time can be configured to work that way, >> although generally installing the standard (reference) version of ntpd is >> preferred. (ntpd can be configured to almost never step the time.) >> >> Although Windows is not a good platform for time keeping, both these >> approaches ought to produce times accurate to about 20ms, and only slowly >> changing with time. In some circumstances, Linux can produce several orders >> of magnitude better results. >> >> >>> On 04/10/18 22:32, Mike Greenway wrote: >>> As previously posted the problem had nothing to do with CODEC or the K3S. >>> Problem turned out to be the time update of the computer by Dimension 4. I >>> had it set for updates every 1 sec as I didn’t think that was a problem. I >>> now have it set for 30 Mins and probably and hour would not hurt anything >>> as every 15 secs it does about .049 correction on my computer. I don’t >>> think it is abnormal for the Rates on WSJT-10 to jump out of range when a >>> time update is done to the computer. Something you cant see on WSJT-X or >>> JTDX. Thanks to all that wrote with suggestions, all of them good. 73 >>> Mike K4PI >>> >> >> >> __ >> Elecraft mailing list >> Home: http://mailman.qth.net/mailman/listinfo/elecraft >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:Elecraft@mailman.qth.net >> >> This list hosted by: http://www.qsl.net >> Please help support this email list: http://www.qsl.net/donate.html >> Message delivered to k...@charter.net > __ > Elecraft mailing list > Home: http://mailman.qth.net/mailman/listinfo/elecraft > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:Elecraft@mailman.qth.net > > This list hosted by: http://www.qsl.net > Please help support this email list: http://www.qsl.net/donate.html > Message delivered to rmcg...@blomand.net __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] CODEC
David >There should be very little reason to use Dimension 4 There is often a significant gap between Theory and Practice, and such is the case with using Windows as a self-regulated timepiece. True, Windows is a well behaved ntp client, but the default interval for Windows "phoning home" to resync is 7 days. In 7 days my PC has drifted so far that FT8 operation is impossible. The user has two choices: use Regedit and mess with the Windows registry to reduce the interval; or install a time sync program. For most, the second option is easier. -larry (K8UT) -- Original Message -- From: "David Woolley" To: "Mike Greenway" ; elecraft@mailman.qth.net Sent: 2018-10-06 08:27:19 Subject: Re: [Elecraft] CODEC There should be very little reason to use Dimension 4, with step updates at fixed intervals. The full implementation of ntpd is available for all the Windows NT family, i.e. everything after Windows 95, and versions or w32time that can be configured to implement the older version of NTP have been supplied with Windows since at least Windows XP. The standard ntpd always works by managing clock frequency, so there are no abrupt time steps unless something has gone sufficiently wrong to result in a step of at least 200ms. w32time can be configured to work that way, although generally installing the standard (reference) version of ntpd is preferred. (ntpd can be configured to almost never step the time.) Although Windows is not a good platform for time keeping, both these approaches ought to produce times accurate to about 20ms, and only slowly changing with time. In some circumstances, Linux can produce several orders of magnitude better results. On 04/10/18 22:32, Mike Greenway wrote: As previously posted the problem had nothing to do with CODEC or the K3S. Problem turned out to be the time update of the computer by Dimension 4. I had it set for updates every 1 sec as I didn’t think that was a problem. I now have it set for 30 Mins and probably and hour would not hurt anything as every 15 secs it does about .049 correction on my computer. I don’t think it is abnormal for the Rates on WSJT-10 to jump out of range when a time update is done to the computer. Something you cant see on WSJT-X or JTDX. Thanks to all that wrote with suggestions, all of them good. 73 Mike K4PI __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to k...@charter.net __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] CODEC
There should be very little reason to use Dimension 4, with step updates at fixed intervals. The full implementation of ntpd is available for all the Windows NT family, i.e. everything after Windows 95, and versions or w32time that can be configured to implement the older version of NTP have been supplied with Windows since at least Windows XP. The standard ntpd always works by managing clock frequency, so there are no abrupt time steps unless something has gone sufficiently wrong to result in a step of at least 200ms. w32time can be configured to work that way, although generally installing the standard (reference) version of ntpd is preferred. (ntpd can be configured to almost never step the time.) Although Windows is not a good platform for time keeping, both these approaches ought to produce times accurate to about 20ms, and only slowly changing with time. In some circumstances, Linux can produce several orders of magnitude better results. On 04/10/18 22:32, Mike Greenway wrote: As previously posted the problem had nothing to do with CODEC or the K3S. Problem turned out to be the time update of the computer by Dimension 4. I had it set for updates every 1 sec as I didn’t think that was a problem. I now have it set for 30 Mins and probably and hour would not hurt anything as every 15 secs it does about .049 correction on my computer. I don’t think it is abnormal for the Rates on WSJT-10 to jump out of range when a time update is done to the computer. Something you cant see on WSJT-X or JTDX. Thanks to all that wrote with suggestions, all of them good. 73 Mike K4PI __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
Re: [Elecraft] CW with my K3s and KX3
A suggestion I didn't see suggested - mine is ditch the cw readers. If you use a reader, cw is going to be purely digital and its not meant to be that.Its not ft8! Yes get over the shy thing too. You won't get a report card on your Qso ability. You know what they say - the more you do it - - -.It will get to be fun, or it should. Thats the way its supposed to work anyway, hi. CW is a special thing but when you can get your head to read it instead of a reader it might surprise you. You're missing a lot with a reader I think. Just my opinion. GL Mike. BillK3WJV On Friday, October 5, 2018, 3:19:13 PM EDT, Michael Blake via Elecraft wrote: I have received many very good suggestions which I will give a try. I think the term “key shyness” is what I need to get over. All were very good suggestions! Thanks. Several questions (2) about readers. I find the Elecraft K3s, and KX3 readers along with the K42, CWGet and fldigi readers to all be equal over time. My favorite reader is “CW Morse” which runs on Mac OS and iOS. They all seem to detract from the fun of the hunt in some way. Again, thanks for the nudges and pushes which I will try. Time to close the thread I suppose. Very 73 - Mike - K9JRI > On Oct 5, 2018, at 11:29 AM, Michael Blake wrote: > > A bit off topic but I think many Elecraft users are CW people. My station is > completely set up for good CW (K3s, KPA500, KAT500, KX3 with paddle, > Vibroplex Code Warrior) and I can send and copy relatively well up to about > 20 WPM but I seem to lack the interest to grab the horns and actually engage > in a CW contact. I have several very good code readers and CW keyboard > applications but I believe they actually prevent me from really getting into > it. > > Any suggestions in how to actually create some interest or thrill that will > entice me to engage in more CW operations? > > If you wish to reply off line please use k9jri at Mac dot com. > > Very 73 - Mike - K9JRI > > > > > > __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to k3...@yahoo.com __ Elecraft mailing list Home: http://mailman.qth.net/mailman/listinfo/elecraft Help: http://mailman.qth.net/mmfaq.htm Post: mailto:Elecraft@mailman.qth.net This list hosted by: http://www.qsl.net Please help support this email list: http://www.qsl.net/donate.html Message delivered to arch...@mail-archive.com
