Radio and rails...

Yeah ok, naff title. A new toy arrived today, I've been thinking about getting one of these for a while now and not doing anything about it. The lack of accessible (i.e. ones not too far away) radio rallies puts a damper on acquiring stuff so this was an eBay find. The meter had no slugs but I had ordered a couple from Vintage Electronics as well and all arrived at the same time. Of course I had to test it having never used one before, but as my radio's and patch leads are all currently PL259 I had to use an adapter. Actually three adapters! I ended up going from the rig via an SO239 to BNC male, BNC female to SMA male, and SMA female to N male! But hey, it works. And yes, I really do intend to convert to all N type connectors here… I even have them ready to make up. Lazy...

I received a few reasonable images early this morning between 5 and 6am. Hopefully later passes will yield better images. These were received on a 2m FM set with a loft mounted collinear, and decoded by qsstv on Linux.

So... having an Allstar node I wanted to configure it for Echolink. It seemed this was just a matter of editing the pre-prepared configuration file echolink.xxx and renaming it to echolink.conf. Edits in place, this I did. Oh yes, and I set our broadband router up to forward the relevant ports to the hub. On restarting asterisk it gave numerous errors of the form 'Error in parsing header on servers.echolink.org'. Hmmm. Ok, scratching around the web I found that Echolink has a firewall test service at https://secure.echolink.org/pingTest.jsp. It failed. Ugh. Then it dawned on me (meaning I read the documentation a little better!). I had set a callsign with '-L' at the end which appeared to be the way to go. But this needed separate validation! Once that was done it all sprang into life. Simple, and also obvious when I realised. Old age? http://km6uso.net/index.php/2021/02/27/adding-echolink-to-your-allstar-hub/ is an excellent guide - there are others of course but this one pointed out clearly the need to register the -L or -R callsign.

Up until now I've used generic QSL cards rather than an actual design. These served well as an M6 and a 2E but I always planned to design a card once I passed the full exam. So, one year on (no sense in rushing!) here it is: The basic design was done by one of my boys with the final layout and production carried out by fdsQSL who also produced my previous generic cards. The photo is my own, the logo as explained previously was basically why I chose RVB because the Morse fits the wheels. The rear has all the usual stuff including an area for 'Via' above the target callsign, both top right to hopefully make it easy for the bureau. I have only just got these and have yet to try one in the laser printer - which would make filling the details in easier. But given I hardly send any cards that is a lot of faff when a pen does just as well!

I only managed one almost decent image from the 1st December ISS SSTV event, the others being partial or very noisy. I am not bothering with the diplomas this time. When I checked most of them use a Google form that required me to log in (twice in one case), failed to submit and, in one case set 40 (!) cookies for the trouble.