❌

Normal view

There are new articles available, click to refresh the page.
Before yesterdayMain stream

The Great LoTW Outage - Continues.

By: AA4LR
28 June 2024 at 17:55

Update July 1, 2024. LoTW is back up! It is running slow, but it is available. Thank goodness.

--

When I wrote the article back in May, I hardly thought that LoTW would be down a month later.

Sadly, the outage continues.Β 

My suspicions were correct, however, that this was something more than a simple networking problem. The ARRL has since admitted their network was viciously and uniquely hacked. I can certainly understand their caution to make sure that every system linked to LoTW is given a clean bill of health before turning the system back on.

Earlier this week, on Tuesday there was apparently a brief period of time when LoTW was accessible. A couple of my ham buddies managed to upload some contacts. They'll have to wait for confirmations when the rest of us can get in.

I do hope it is soon. I'm really missing this service.

FT8 is supposed to make DXing easy, why is it so hard?

By: AA4LR
1 June 2024 at 12:00

FT8 has been a revolution. The technology has made DXing really easy. Or has it? I continue to be amazed at how much difficulty people have working DXpeditions on FT8.Β 

Last year, there were DXpeditions to Bouvet (3Y0J), Crozet (FT8WW) and Sable Islands (CY0S). The most recent DXpedition to Glorioso Islands (FT4GL) has brought it all back to me.

Let's start off with a few observations on people trying to work these DXpeditions:

  • Wrong Cycle - It's amazing the number of folks trying to work DX that are calling on the wrong cycle. FT8 has even and odd cycles. Even cycles start at 00 or 30 seconds, and odd cycles start on 15 and 45 seconds. You always call on the cycle the DX station is NOT transmitting. Indeed, if you double-click on a decode of the DX station, WSJT-X will set up the correct cycle. So how are people getting it wrong?
  • Endless Calling - I've noticed some stations keep calling the DX after the DX station has QSYed or QRTed. A little bit of hopeful calling isn't unusual on Phone or CW, or even RTTY. But stations continue to call much later -- like an hour later, and they are still calling.
  • Calling without Response - Some stations don't respond when the DX station calls them. They keep calling instead of advancing to the next step. This can get really bad. During the FT8WW expedition, I saw FT8WW keep responding to the same station for more than 10 minutes. Each response had a different signal report. This made it clear that FT8WW was heading this caller quite well, but the caller wasn't hearing FT8WW at all. Instead, that station took up a valuable response slot for 10 minutes -- denying perhaps 20-40 stations from working FT8WW.
  • Confusing Fox/Hound (FH) and MSHV - Most DXpeditions using FT8 use either FH or MSHV in order to maximize the number of contacts they can make. It is easy to get confused with these two modes. They appear similar. Both allow for the DX station to transmit multiple FT8 carriers at the same time. FH imposes additional behavior to both the Fox and Hound ends of the contact. In particular, there are audio-frequency dependencies that FH enforces. But, it is perfectly possible to work a Fox station even if you are not in Hound mode. MSHV requires no special modes. And yet someone accused people of DQRM, calling FT4GL below 1000 Hz, when the DX was using MSHV, not FH.
What causes all these odd observations? I believe they all resolve to a single cause -- people are calling DX they cannot hear. That's right, people are calling DX stations they aren't decoding at all.

This is fundamentally wrong. I wrote about this years ago on how to bust a pileup.Β You cannot work DX if you cannot hear them. If you aren't decoding the DX station, stop calling. Yeah, that's hard, but your calls won't net you a contact, and you may be actively depriving someone who canΒ hear the DX from making one.Β 

I think FT8 has made some people lazy. They hear some DX station is active on some frequency, probably through a spotting network. So they switch to that frequency, set their watchdog timers to an hour or more, and enable their transmitter. Then they go off and drink a few cool 807s while their computer works the DX for them.

Farfetched? No, it explains all the observations above.

Be a good FT8 operator -- don't call DX when you cannot decode them. Wait until you can decode them reliably, just about every cycle -- then start calling.


The Great LoTW Outage

By: AA4LR
27 May 2024 at 13:04

May 16th, there was an issue with Logbook of The World (LoTW). I could not load the main page at all -- receiving an error indicating the server wasn't responding.

That's pretty normal stuff, actually. There are dozens of problems that can result in this kind of error, so I wasn't surprised. I figured the ARRL staff would address it quickly. But, after much of the day, I was still getting the error.Β 

So, I sent a message to lotw-help@arrl.org, informing them that the web site wasn't responding, kindly asking when they expected it to be back up. I mentioned I was surprised there was no notice of the outage on the ARRL.org web site.

Later that day, the ARRL put up a noticeΒ that there was a service disruption involving access to the network, and that it affected LoTW and the ARRL Learning Center. They even updated it the next day, addressing concerns users had over information privacy.

But then, nothing happened. Not until May 22nd, when they updated the notice without really adding any information.Β 

Now, part of this delay may be due to the fact that much of the ARRL staff were all out at the Xenia Hamvention. But, that was a week ago.

What gives? Sure, networking problems. Honestly, though, as a computer professional, networking problems generally don't take more than a week to solve. I'm beginning to suspect there's something more than the ARRL hasn't told us, but I can't be sure.

I'm really missing access to LoTW. In the last 20 years, it has really become central in my enjoyment of the hobby. I do hope I'm wrong, and that ARRL manages to fix this problem soon.

At the end of the CQ WW Wpx

By: VA3QV
1 April 2024 at 17:25

As always the CQWW Contests are a great source of entertainment and also a great chance to increase your DXCC totals…. This one was no different

This year I operated in a S & P (search and pounce) mode for approximately 8 hours in total. The rig I used was my Yaesu FT991a and the antenna of choice was my β€œModified” Coastal-20 vertical antenna

I made 42 contacts in 22 DXCC entities covering 4 continents (NA/SA/AF/EU) using 10m-15m and 20m

I was able to contact stations in:

Alaska, Argentina, Aruba, Bonaire, Brazil, Canada, Canary Islands, England, Finland, France, Greece, Ireland, Italy, Latvia, Morocco, Poland, Portugal, Scotland, Slovenia, St Lucia, Turkey (Turkiye), United States of America

Now if everyone confirms I believe that there will be one new DXCC for my DXCC totals, but also there should be a couple of new ones for my 5 Band DXCC which I am hoping to complete sooner or later but most likely later

More on this once the confirmations come in via either LoTW, QRZ.com or EQSL.

For now its back to Playing POTA…

73b0b

I’ve worked 300 DXCC entities

By: g6nhu
28 November 2023 at 13:48

It’s been a while since I posted any updates here, not because I’ve got nothing to say but because I’ve been busy working on the station and playing radio. My new aerial is up but I’m not going to say anything about that now, that’s for a future update. I’ve had a good year so […]

The post I’ve worked 300 DXCC entities first appeared on QSO365.

Halfway through the DXCC Challenge

By: AA4LR
26 November 2023 at 13:39

Twenty years ago, when I first started uploading my logs to Logbook of the World, I began to pursue the DXCC Challenge award. I created lists of confirmations that I had, and began to try to fill in the band / countries I was missing. This has continued for years.Β 

In April of 2016, I gathered sufficient confirmations to earn the DXCC Challenge award. Since then, I've continued to pursue new band / countries practically every time I am on the air.

This month, I passed another milestone. Currently, there are 340 entities on the DXCC list. And the DXCC Challenge counts on ten bands, from 160m through 6m. That makes 3400 total items for DXCC Challenge.Β 

I recently collected confirmations over 1700 items on the DXCC Challenge. That's the half-way point. It's only going to get harder after this.

FT8 – Lazy, Computer Scripted β€œCrapola”

By: N0UN
23 September 2023 at 02:05

FT8 - THIS is the "new" Ham Radio DXer. No skill required. Set your computer, go to dinner, come back after dessert and claim your DXCC "Participation Trophy".

The post FT8 – Lazy, Computer Scripted β€œCrapola” first appeared on N0UN.net.

DX Century Club – RTTY

By: g6nhu
22 February 2023 at 16:15

Some years ago, the ARRL decided to stop issuing a DXCC certificate for just RTTY and merged the various digital modes all together for a single β€˜digital’ certificate. I obtained the β€˜digital’ certificate back in 2012 with just RTTY QSOs and was always a little sad that my certificate said β€˜digital’. Last year, I heard […]

The post DX Century Club – RTTY first appeared on QSO365.

3Y0J Bouvet Is On The Air!

By: N0UN
7 February 2023 at 04:24

The massive Bouvet pile-ups have begun! 3Y0J trimmed their camp back to two stations, 100 watts with wire antennas, but they made it on the air around 1600Z!

The post 3Y0J Bouvet Is On The Air! first appeared on N0UN.net.

πŸ’Ύ

πŸ’Ύ

πŸ’Ύ

3Y0J Bouvet – They Have Arrived!

By: N0UN
30 January 2023 at 22:26

3Y0J Bouvet - They Have arrived! From their Facebook Page today: 3Y0J Bouvet Island 2023 Update: "3Y0J Team Co-Leader Ken LA7GIA reports, β€œWe are at Bouvet"

The post 3Y0J Bouvet – They Have Arrived! first appeared on N0UN.net.
❌
❌