Main menu:




Remember me

Recent Posts

Recent Comments


Site search

August 2021


VE1PZ worked during an aurora on 6M

Posted: July 8th, 2016 under 6M, Hamradio, Soundclips.

ve1pz_qsl On June 5th, I noticed we had an ongoing aurora on 6M. I turned the yagi to the north and started listening on the band. I worked LA1NG in JP66 on SSB. He was very strong, and didn’t have the characteristic aurora on him. Instead it was more like auroral-e. LA4IX in Tromsø called me as well, but since it wasn’t my frequency, I lost him. The signals peaked at around 330 deg. This was quite unusual and the aurora was quite intense. I went to CW and started calling, and got a few calls from LA and SM. I also got a call from MM0BSM, and I turned the yagi a bit to around 300 degrees to peak his signal. When I finished with MM0BSM, I suddenly heard a VE station calling me. He had to repeat his call, and it turned out that it was VE1PZ on aurora. We quickly exchanged reports, and I called, hoping for more. Unfortunately, the opening went away after that.

VE1PZ heard me a little while after we worked, and I asked if he could record me. The recording can be heard below. VE1PZ said that the signal peaked at 350 degrees for him. They did have a good aurora at the same time. I have worked USA on aurora before, but that was way back in 2002 when we had F2. This was very fun, and openings like this is what makes 6M fun.


LA8AJA 6M CW – aurora recorded by VE1PZ

Comments: No comment yet, you could be the first


Posted: July 5th, 2016 under Hamradio, Software.

timeplot This idea came into life after I read about MD0CCE plotting the time for all his contacts with USA on 6M. G0JHC wondered which tool he used. MD0CCE had done it manually. So I thought to myself that a tool like this is quite like my Distance Statplotter.

I modified my code, and here is my Timeplotter tool. You upload an ADIF-file, or a ZIP-file with an ADIF-file in it. You select which DXCC you want to see at which times you worked. And finally you select which band you want to plot. The intervalls are divided into 30 minutes. In the picture, you can see an example from my own log.

Comments: No comment yet, you could be the first

#148 worked on 6M with 3B9FR

Posted: June 27th, 2016 under 6M, DX, Soundclips.

3b9fr_qsl The 6M sporadic-e season started out pretty early for me this year. Usually the good openings starts well into May.

On May 4th, I worked UB7K on 6M CW. Since Russia hasn’t been allowed on 6M, except for a few special cases, this was the first contact with Russia that had a valid licence. UB7K is also on LoTW, that means that I finally got Russia confirmed on 6M. A bit later that day, TEP lined up with sporadic-e. The surprise was that I could suddenly hear 3B9FR. After a few calls, I got him in the log for #148 on 6M. Robert is also on LoTW, so I got that one quickly confirmed as well.

On May 8th, we had a small aurora on 6M. I worked OH, LA, SM, ES, YL, OZ, OY and G.

On May 15th, I worked R6KA on 6M CW. He does also have a valid licence for 6M.

On May 21st, I worked SU1SK on 6M CW. SU is pretty rare on 6M, and I heard him for a while.

On May 25th, I worked IT9PQJ on 6M CW.

On May 26th, I worked EI, SV, OE, CN, C3 and Z3 on 6M.

On May 27th, I worked UN6T on 6M CW. I did copy 3A2MW with a good signal, but I could not break the pile-up. I still need 3A on 6M, and I have only heard a signal a few times from there. This was the best ever heard.

On May 29th, I got a surprise opening to Japan on 6M. I managed to two stations, and heard a few others. The opening didn’t last more than perhaps 10-15 minutes. That’s only my fourth opening to Japan on 6M.

On May 30th, I worked EX8M on 6M CW.

On May 31st, I had an opening to JT1CO on 6M. But I didn’t manage to work him. I was out for around 30 minutes, when I got him, another LA had worked him. I checked my CW Skimmer, and it was clear that I had copied him quite well. It only shows that 6M can be a frustrating band. You have to be in front of the radio all the time if you want to get all the action. This is just not possible.


Comments: No comment yet, you could be the first

Not so delayed dx report…

Posted: June 20th, 2016 under DX, Soundclips.

1u4un Here is the DX report from April till today. The 6M report will come in another post.

On April 1st, I worked VK0EK on 40M CW for a new one on 40M. I haven’t worked them on any higher bands, and the conditions hasn’t been too good for propagation to that area from my QTH. But they have been quite good on 40M and 30M at times.

On April 2nd, I worked Nicolas TY2AC on 30M CW.

On April 5th, I worked FT4JA on 15M and 30M CW. That was a new dxcc on CW, and a new country on both bands. They have had quite a good signal, but the pile-up has also been quite big.

On April 7th, I worked FT4JA on 12M CW. 9M0O was worked on 30M CW.

On April 8th, I worked FT4JA on 15M SSB and RTTY. That was a new one on RTTY and 15M. 3B8MM was worked on 40M CW.

On April 9th, I worked ET7L on 30M CW and ZF2LC on 20M CW.

On April 14th, I worked A25UK on 17M CW.

On April 16th, I worked EP2A on 30M CW, 15M CW and 20M CW. T88SM was worked on 20M CW for a new one on 20M.

On April 17th, I worked A25UK on 10M CW.

On April 18th, I worked EP2A on 17M CW, 40M CW and 30M RTTY. V55DX was worked on 15M RTTY for a new one on RTTY.

On April 19th, I worked Dima 1U4UN on 30M CW. Read the story about the King here.

On April 20th, I worked EP2A on 20M SSB. RT92KA was worked on 20M CW from iota AS-092 for a new iota.

On April 21st, I worked EP2A on 15M SSB.

On April 22nd, I worked 5W0XG and KH8/KC0W on 20M CW. Both were new ones on 20M. That means I have over 300 dxcc’s worked on 20M.

On April 28th, I worked A91HI on 15M SSB and 30M CW from iota AS-202. That was a new iota for me.

On May 20th, I worked J68GU on 20M RTTY for a new one on RTTY.

On May 29th, I worked SV2RSG on 20M CW. That’s the new ham that is active from Mount Athos.


Comments: No comment yet, you could be the first

Broken logsearch has been fixed

Posted: June 18th, 2016 under Homepage.

I just noticed today that my logsearch seemed to be broken. I don’t know when that happened, but I think it was because of the upgrade to PHP 7 on this page. I don’t remember when I switched over. Anyway, I’ve been meaning to rewrite the logsearch for a long time. I never got around to it until today. The logsearch was something I wrote several years ago. That was before I really knew too much about programming, and most of it was hacked together code from some search script I found on the web.

Today it got a major rewrite. It really needed it. While doing it, I found out that some functions were deprecated. I think that was why it was broken. The search still uses text-files, but that will change as soon as I rewrite it to use MySQL instead. For now I refactored and rewrote most of the code.

The search is a plugin for WordPress. It’s pretty basic and crude, but it does what I want it to do. I’m not sure if I want to release it or not, but we’ll see. It needs to be rewritten for MySQL and it needs a lot more polishing. Only time will tell.

Comments: No comment yet, you could be the first