Main menu:


Login

Username

Password

Remember me

Recent Posts

Recent Comments

Feeds

Site search


September 2018
M T W T F S S
« Aug    
 12
3456789
10111213141516
17181920212223
24252627282930

Categories

#154 and #155 on 6M with Z68M and 3A/EA6SX in the log


Posted: August 3rd, 2018 under 6M, DX, Hamradio.

z68m_logsearch Z68M logsearch on Club LogAfter working two new ones on 6M, I didn’t really have my hopes very high for this season. New countries are difficult to come by, but suddenly they show up. So here is another dx report from me.

On July 3rd, I managed to get KH1/KH7Z on 20M CW. I didn’t really think I would work them, as the time of year makes this one difficult. Combine this with full time work and small kids, and the difficulty increases a lot. I did hear them on Sunday morning on 20M CW, but I could not break the pile-up. I didn’t copy them on FT8 either. But when I checked 20M CW after the kids went to bed, they had a readable signal. After a few tries, I managed to work them. This just shows that having a station on 20M at all times, does pay off. KH1 was a new one on 20M CW for me.

On July 6th, I got a text from LA4GHA alerting me of Z6 and 3A on 6M. As I had to pick up the kids and get them home, I rushed to get on the air. Z68M was strong on 6M CW, and after a few calls, he came back. That was #154 on 6M. I changed to FT8 and started listening for 3A. I could see him, and started calling. He came right back to me, and after a few periods, I got the 73. 3A/EA6SX was #155 in the log on 6M. I’ve been hunting 3A for many years, but I have had no success on getting one in the log. I’ve heard them, and almost made a qso, but this was the first time I finally logged Monaco on 6M.

On July 11th, I worked OX3LX on 6M FT8. I’ve been listening for Bo for several days without success. Usually the conditions appeared after I went to bed. While sitting in front of my PC, Bo suddenly came in here on FT8. I quickly worked him for a new field (HQ) and grid (HQ90). I also worked TF1A on 6M FT8.

On July 11th, I worked Z68M on FT8 and SSB on 6M. Z66X was also worked on 6M FT8.


Comments: No comment yet, you could be the first

#153 on 6M with PZ5RA in the log


Posted: July 22nd, 2018 under 6M, DX, Hamradio.

pz5ra_qsl By now the 6M band has been open several days. Here is a short list of some of the highlights of what I worked in June.

On June 2nd, I worked UN3M on 6M FT8.

On June 3rd, I was surprised to suddenly see PZ5RA running on 6M FT8. I gave him a call and quickly logged him for #153 on 6M. That was the first time I have every heard PZ on 6M. I know it was worked from Norway during the F2 days several years ago, but I never heard PZ back then. I worked S01WS on 6M FT8. CU2AP, VP2EIH, YV5LI and TF8V was also worked on 6M FT8. CT1JML (LA9PJA) was worked on 6M CW from his QTH in Portugal.

On June 4th, I worked OH0Z and ZA/OG2M on 6M CW.

On June 5th, I worked 7X2TT and EA8CNR on 6M FT8.

On June 6th, I worked SM/DM3CK on 6M JTMS from JO98 for a new grid on 6M.

On June 9th, I worked Z37M on 6M FT8. I didn’t have Z3 on 6M LoTW, so that was new one for LoTW.

On June 10th, I worked 9G5AR and NL8F on 20M FT8. NL8F was operating from NA-059. If you have watched Deadliest Catch, you have heard about Dutch Harbor. That was his qth.

On June 14th, I worked D41CV on 6M FT8. That was a new one on 6M LoTW. I did hear 5T2BI?, but I didn’t manage to work him. I also heard TZ4AM on 6M CW, and he heard me, but conditions faded before we could make a contact.

On June 24th, I had my first opening this year on 6M to North America. I worked 10 contacts from AZ, TX, CO and MO on FT8. K1USA from MO, was state #43 on 6M.

On June 25th, we had some strange conditions. It was a mix of aurora and auroral-e. OX3XR was booming in on 6M CW from GP44. That was a new grid on 6M. I did manage to work LA5SJA in KQ50 and LA1PHA in JP76, both on 6M FT8. with those 3 new grids, I passed #800 grids worked on 6M. I did also hear several other LA, OH and SM stations in that opening.


Comments: No comment yet, you could be the first

#152 on 6M with TY2AC in the log


Posted: July 7th, 2018 under 6M, Soundclips.

ty2ac_qsl This was a contact I’ve been waiting on for years. TY2AC is quite active on 6M, but I always miss the openings. I know several LA’s have worked him on 6M, but I have not been home when many of those openings have occured. On one occation, I was working USA on 6M, and I was not listening to the south. I did hear TY2AC weakly, but not enough for a contact a few days prior to the contact. On May 26th, it was finally time. I was listening on his frequency for a while, and suddenly I started to hear him on 6M CW. After calling a few times, Nicolas came back to me, giving me #152 in the log on 6M.

Soundclip:


Comments: No comment yet, you could be the first

Mode statistics with data from Clublog


Posted: June 18th, 2018 under Hamradio.

modestats Back in late May of 2018, I noticed an email on the Club Log mailing list from Michael G7VJR, the author of Clublog. He wrote about the interest in the growth of the FT8 mode, and if other modes are losing out to it. He made the raw data available to anyone who wants to make anything out ot it. As I’ve played around a lot with databases, statistics and graphs, I thought, why not try to make something out of it. I made a page with graphs that present the data in different forms. As the possibilities with data like this are endless, I chose to make available yearly, monthly and daily graphs within the year specified. The data starts at January 1st 1990, and the raw data is usually updated from Club Log around the 10th of each month.

As for my own use of FT8, I’ve played with it since the first beta was out last year. I was running a few openings to North America on 6M last year, and I noticed that the openings were too short for JT65. That’s one of the reasons why FT8 was developed, and I also worked K1JT himself on 6M in July last year. The most interesting aspect with using a mode like FT8, is the opportunity to look at a map and see where I’ve been heard, and what I have heard. I use pskreporter all the time for this. I often leave my radio on when I am not in front of the radio, and then check the map later on to see how the propagation has been.

The problem with FT8, in my experience, seems to be that “everyone” are using it. If you listen on the FT8 frequencies, you hear a lot of activity. If you check the CW or SSB portion of the band, you either hear nothing, or very little. I don’t know if this is a period that will pass, but for the time being, FT8 is very popular. I use it, but at the same time, I found it a bit boring and unpersonal when it comes to making contacts on the radio.

Ok, enough with that, take a look at the statistics here.


Comments: No comment yet, you could be the first

#339 worked with Z60A in the log


Posted: June 16th, 2018 under DX, Hamradio.

z60a_qsl In January this year, it was announced that the Republic of Kosovo would be added to the DXCC list. It wasn’t long until a group started the activity on the bands.

My first qso this year, was 6O6O on 30M CW on January 2018. My previous qso was made back in November 2017. 6O6O was a joint expedition by LA7GIA and KO8SCA. That was the only band I managed to work them on.

On January 12th, I worked TY2AC on 40M CW for a new one on 40M.

On January 14th, I worked PJ7/UT6UD on 40M CW for a new one on 40M.

On January 24th, I worked Z60A on 30M CW for and all time new one. That means I’ve worked 339 DXCC’s. I only need 5 DXCC’s now to have worked them all. That was my first qso with Z6. I worked them on 40M, 20M and 17M CW a few days later.

On January 29th, I worked C81G on 30M CW from iota AF-061.

On March 6th, I worked Z2LA on 30M FT8. Z2LA was a joint dxpedition by LA7WCA, LA7THA and LA9VPA.

Om March 7th, I worked XV9DLH on 30M FT8 for a new one on digi.

On March 9th, I worked Z61AS on 30M FT8 for a new one on digi.

Om March 11th, I worked 3B9FR and C93PA on 30M FT8. Those were new on digi. I also worked 3D2EU and XR0YD on 30M CW.

On March 12th, I worked 3D2EU on 30M FT8 for a new one on digi.

On March 17th, I worked TN5R on 20M CW for a new one on 20M.

On March 18th, I Worked 3C0W on 20M for a new one on 20M. TJ2TT was worked on 17M CW for a new one on 17M. 5A1AL was worked on 17M FT8 for a new one on digi.

On March 20th, I worked TI2CC on 30M FT8 for a new one on digi.

On March 24th, I worked TJ2TT on 20M CW for a new one on 20M. I worked 9L/KW4XJ on 40M FT8 for a new one on digi.

On March 27th, I worked 9G5ZS on 30M FT8 for a new one on digi.

On April 1th, I worked JW7QIA on 40M FT8.

On April 2nd, I worked 5B/LA7THA on 20M CW. I worked YB6/JA1PBV on 30M CW from iota OC-161 for a new iota.

On April 7th, I worked VA7XW/VE2 on 30M CW from NA-038 for a new iota.

On April 11th, I worked VE7ACN/VE2 on 30M CW from NA-083 for a new iota.

On April 30th, I worked C96RRC on 17M CW from iota AF-088 for a new iota. YB3LZ/8 was worked on 30M FT8 from iota OC-242 for a new iota.

On May 1st, I worked AP2MQ on 20M FT8 for a new one on digi.

On May 7th, I worked C98RRC on 17M CW from iota AF-066 for a new iota.

That pretty much sums up the first half of this year. I’ve been playing around with FT8 (who hasn’t these days?) quite a lot. In that process, I’ve worked several new ones on digital. I’ve also gotten several confirmations on previous worked dxcc’s that weren’t confirmed. Hopefully I’ll write more often here, but I see that I’m not that motivated, or inspired, to write here. Life is busy, and I’ve been doing a lot of programming lately. I’ll write about that in a later post here.


Comments: No comment yet, you could be the first