This was a special one for me. The last I tried to activate the Marshlands Conservation Area I had an equipment malfunction and as such it was a “Failed Activation”.

Today I headed out to get the one that got away.

I set up (red dot on the map) and operated with my FT891 set at 30w , 40m EFHF and proceeded to give out contacts….

In one hour I had managed to make 23 contacts in Ontario, and the Eastern Parts of the USA.

In the “learning part” of my activation I still have to find a way to carry more stuff and also make the kit lighter… It was a 4 km walk there and back (thats almost 2.5 miles to those of you south of the border) and to be honest I was really glad to get home and get my feet up.

I mentioned a few posts back about using some sort of trailer to carry the kit and today’s effort reinforces that thought….

Anyway I did have fun…. and if I worked you I hope you had fun as well….. If you don’t see our QSO today in your Hunters Log let me know and I’ll try to figure out why not…

73bob

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

Some time ago I wanted a logging program that would do things my way. Although there is absolutely nothing wrong with any of the various offerings they generally try to be everything for everyone and none of them really sat well with me. So I wrote my own in PHP (learning Python is high on my list of things to do, along with Mandarin, Morse, cooking…) which uses the QRZ.com logbook as the backend. Ok then, really I wrote a series of various scripts in PHP that make it all work. The advantage is it does just what I need and nothing more and can easily be modified to add functionality. The downside is I never was a coder (well, ok, I have a certification in COBOL from the 1970’s!) and it is not going anywhere other than my own server. So you can’t have it…

The way I tend to log stuff is via wsjt-x or other software that logs to a local file. I then have a script that takes the ADIF data and populates QRZ.com on a QSO-by-QSO basis. Somehow having to actually do something after each QSO feels like I am actually engaging in the process. But I am not a contester… it would simply not work for any stress situations (but then I could easily make it work if I so desired…)

With QRZ.com being the master a script then populates a local database which does all manner of stuff that I personally need. For example, it holds records of eQSL sent/received, real QSL sent/received, and various tabular data for Worked All Britain (WAB).

Scripts also modify the wsjt-x log file on all my systems such that each has a record of all QSOs. As QRZ.com is globally accessible (not tried from China mind… not that I plan to take any radio gear there anyway) and my main database is on a VPS so is also globally accessible the various scripts work from anywhere.

I do plan to move the database from the VPS to a system at home once we get FTTP broadband and use the VPS as a backup, synchronising between the two. But that will wait.

One plan which is more immediate is LoTW integration because as yet my LoTW logging is via QRZ.com which means an extra step. No biggie, I mean it’s its a few clicks and a password… but it would be nice to integrate it. The same goes for eQSL sends, but as yet I only send on receipt and I have scripts to deal with that anyway.