[OKDXA] OKDXA Digest, Vol 220, Issue 2

kodiak kodiakat777 at gmail.com
Mon Jan 2 12:09:43 EST 2023 

Finally snagged Crozet at 0900 local yesterday, after an hour of
failed attempts on 20M FT8.

Like most I broke through using Long Path, the signal was next to nil on
SP.

Most folks were following the FT8 rules, but every 10 minutes or so
someone would start transmitting on even time slots; it usually stopped
after a few
minutes after they were either contacted or figured it out themselves.

I did have some concerns it was a pirate station but was pleasantly
surprised when FT8WW showed up in Clublog this morning.

LOTW has been struggling since New Year's rolled over.  A lot of folks dump
complete logs on Jan 1, so their db servers are overwhelmed.
All seems normal on LOTW this morning, so the initial load must have
leveled off.

73's

Brian, AA5H
3W9OK





On Mon, Jan 2, 2023 at 10:45 AM <okdxa-request at mailman.qth.net> wrote:

> Send OKDXA mailing list submissions to
>         okdxa at mailman.qth.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mailman.qth.net/mailman/listinfo/okdxa
> or, via email, send a message with subject or body 'help' to
>         okdxa-request at mailman.qth.net
>
> You can reach the person managing the list at
>         okdxa-owner at mailman.qth.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of OKDXA digest..."
>
>
> Today's Topics:
>
>    1. FT8 Notes... (Kim Elmore)
>    2. LoTW is down this morning... (N5OK)
>    3. Re: LoTW is down this morning... (Marcus Sutliff)
>    4. Re: LoTW is down this morning... (N5OK)
>    5. FT8WW (Jeff Martin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 1 Jan 2023 23:43:33 -0600
> From: Kim Elmore <cw_de_n5op at sbcglobal.net>
> To: okdxa at mailman.qth.net
> Subject: [OKDXA] FT8 Notes...
> Message-ID: <ecfc2af4-802f-fb5f-2be8-f98f8292875a at sbcglobal.net>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> As an admitted radio luddite (I prefer CW to just about anything) and
> I've been dragged wailing, moaning, and gnashing my teeth into the age
> of FT8. Mind! I used to do AMTOR, I've done RTTY, MFSk16, and,
> naturally, PSK31 both standard and quadrature. To me, FT8 was simply
> another digital mode and, frankly, I'd been there and done that. FT8 is
> a very clever digital mode, but digital notwithstanding. AMTOR ARQ was,
> perhaps the most fun to monitor as it was possible to see the old KAM
> TNC switch from rx to tx with the blinkimg lights. Besides, my cats
> loved the sound of AMTOR ARQ; it sounded like deranged crickets. I've
> even done the AOR digital HF voice mode.
>
> All of these went by the wayside because the KAM didn't support the more
> modern HF modes, 2) I got a new radio replacing my Kenwood TS930SAT with
> a TT Orion 2 meaning none of my older interface harnesses worked, and 3)
> My old computer developed bizarre issues with its USB hub and so needed
> replacement meaning all of my carefully crafted COM port numbers were
> toast. Setting these is like pulling teeth. Regardless, it's done.
>
> So, I finish the audio connections and am faced with the ability to
> receive, but no transmit audio is fed to the radio. For a long time, I
> let it be as I have bigger fish to fry. But still, there it was. So
> close! Crozet has given me a reason to get it all going, again. It looks
> like the only chance I'll ever have is FT8, so when in Rome...
>
> Peter, N5UWY, helped me with the initial set up and how to interpret
> what I decoded (all done via 70 cm FM). But, when I tried to transmit it
> was... Well, not FT8 tones. It was almost like audio feedback. We got
> that fixed and I actually made a QSO. But then, I learned that having a
> single sound card came with limitations. On Peter's recommendation, I
> got a USB sound card . Simply mic in and headphones out. How simple!
> Except that the headphone out port was silent. Regardless of what I
> tried, it remained silent. Apparently, I got one that's dead out of the
> carton. I have some more on the way, so we'll see if any of those work
> OK.I feel a bit like the guys that didn't want to give up spark. But,
> technology grinds on. Like rock'n'roll: CW will never die, but there are
> other modes in which I truly should be conversant.
>
>
> So, here I am.
>
> 73 & CU in the Pileups,
>
> Kim N5OP
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 2 Jan 2023 07:48:04 -0600
> From: N5OK <coyday62 at gmail.com>
> To: Oklahoma DX Association <okdxa at mailman.qth.net>
> Subject: [OKDXA] LoTW is down this morning...
> Message-ID:
>         <CAO2D16fHuDAyrYyYfwa7EjNNByz2W2GL=
> gzjaUDHB6Wy+F3mKg at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Coy C Day, N5OK
> 20685 SW 29
> Union City, OK 73090
> H(405) 483-5632 C(405) 448-2368
> n5ok at arrl.net
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 2 Jan 2023 08:36:52 -0600
> From: Marcus Sutliff <cqn5zy at gmail.com>
> To: n5ok at arrl.net, Oklahoma DX Association <okdxa at mailman.qth.net>
> Subject: Re: [OKDXA] LoTW is down this morning...
> Message-ID:
>         <
> CAHEJB2bfub05CTcPt64V+Ea2bpP7xjKLpUVdR8AfC77U4ot+zg at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> It's been having trouble since 1-Jan.. there is a discussion on groups.io
> The problem yesterday was so many people uploading logs on new years day..
> and apparently a backup didn't run normally (possibly leaving the database
> not accepting connections but that's just me speculating).
>
> I was receiving 500 errors on the web interface yesterday.. they got it
> going again but there are still 1mil qso's in the log.
>
> They said one huge problem is a lot of people having their logging program
> to auto upload  every single QSO, one at a time, into LoTW.  A lot of
> overhead to authenticate, receive data, write file to the inbound queue,
> process the file into the log, check for QSLs, end the session, delete the
> file, write transactions to log.. all for one qso.. overburdening the
> system...
> That's all I know.
>
> I've been looking at it with a lot of eagerness as I finally have the QSO's
> for DXCC on 10 and 12m and I'm watching for the QSL's in LoTW.. :-D  If I
> can just get 80m DXCC..
>
> Sincerely,
> Marcus Sutliff/N5ZY
>
>
> On Mon, Jan 2, 2023 at 7:48 AM N5OK <coyday62 at gmail.com> wrote:
>
> > Coy C Day, N5OK
> > 20685 SW 29
> > Union City, OK 73090
> > H(405) 483-5632 C(405) 448-2368
> > n5ok at arrl.net
> > ______________________________________________________________
> > OKDXA mailing list
> > Home: http://mailman.qth.net/mailman/listinfo/okdxa
> > Help: http://mailman.qth.net/mmfaq.htm
> > Post: mailto:OKDXA at mailman.qth.net
> >
> > This list hosted by: http://www.qsl.net
> > Please help support this email list: http://www.qsl.net/donate.html
> >
>
>
> ------------------------------
>
> Message: 4
> Date: Mon, 2 Jan 2023 09:04:22 -0600
> From: N5OK <coyday62 at gmail.com>
> To: Marcus Sutliff <cqn5zy at gmail.com>
> Cc: Oklahoma DX Association <okdxa at mailman.qth.net>, n5ok at arrl.net
> Subject: Re: [OKDXA] LoTW is down this morning...
> Message-ID:
>         <CAO2D16fVF8ZocfwB+SwHbrK+TpHrKuPVvJvvXX+b_U=0KkZ=_
> A at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Marcus,
>
> Thanks for the update.   Be careful.  80M DXCC can be harmful to
> your hearing.
>
> 73, Coy
>
> Coy C Day, N5OK
> 20685 SW 29
> Union City, OK 73090
> H(405) 483-5632 C(405) 448-2368
> n5ok at arrl.net
>
>
> On Mon, Jan 2, 2023 at 8:37 AM Marcus Sutliff <cqn5zy at gmail.com> wrote:
>
> > It's been having trouble since 1-Jan.. there is a discussion on
> groups.io
> > The problem yesterday was so many people uploading logs on new years
> day..
> > and apparently a backup didn't run normally (possibly leaving the
> database
> > not accepting connections but that's just me speculating).
> >
> > I was receiving 500 errors on the web interface yesterday.. they got it
> > going again but there are still 1mil qso's in the log.
> >
> > They said one huge problem is a lot of people having their logging
> program
> > to auto upload  every single QSO, one at a time, into LoTW.  A lot of
> > overhead to authenticate, receive data, write file to the inbound queue,
> > process the file into the log, check for QSLs, end the session, delete
> the
> > file, write transactions to log.. all for one qso.. overburdening the
> > system...
> > That's all I know.
> >
> > I've been looking at it with a lot of eagerness as I finally have the
> > QSO's for DXCC on 10 and 12m and I'm watching for the QSL's in LoTW.. :-D
> > If I can just get 80m DXCC..
> >
> > Sincerely,
> > Marcus Sutliff/N5ZY
> >
> >
> > On Mon, Jan 2, 2023 at 7:48 AM N5OK <coyday62 at gmail.com> wrote:
> >
> >> Coy C Day, N5OK
> >> 20685 SW 29
> >> Union City, OK 73090
> >> H(405) 483-5632 C(405) 448-2368
> >> n5ok at arrl.net
> >> ______________________________________________________________
> >> OKDXA mailing list
> >> Home: http://mailman.qth.net/mailman/listinfo/okdxa
> >> Help: http://mailman.qth.net/mmfaq.htm
> >> Post: mailto:OKDXA at mailman.qth.net
> >>
> >> This list hosted by: http://www.qsl.net
> >> Please help support this email list: http://www.qsl.net/donate.html
> >>
> >
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 02 Jan 2023 16:45:01 +0000
> From: "Jeff Martin" <jeffk5we at gmail.com>
> To: "Oklahoma DX Association" <okdxa at mailman.qth.net>
> Subject: [OKDXA] FT8WW
> Message-ID: <em77593f5a-809a-4fbc-9bda-5a825009fd83 at 521df36a.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> FT8WW - Crozet
> Now on 14.031 CW listening up - long path, loud...
> GL...
> 73,
> Jeff - K5WE
>
>
>
> ------------------------------
>
> _______________________________________________
> OKDXA mailing list
> OKDXA at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/okdxa
>
>
> End of OKDXA Digest, Vol 220, Issue 2
> *************************************
>

More information about the OKDXA mailing list