norden.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Moin! Dies ist die Mastodon-Instanz für Nordlichter, Schnacker und alles dazwischen. Folge dem Leuchtturm.

Administered by:

Server stats:

3.6K
active users

#hamchallenge

12 posts11 participants0 posts today

The important bits of my ham radio log are kept in Obsidian, and my backup strategy for that is to have a copy synced to git on another machine, and another copy backed up with Backblaze.

It's not a contest log (I don't do that) and I'm not perfect about keeping it, but when it works right it lets me keep track of things like who is interested in what on various local discussion nets.

Bonus: completion on call signs, tagging, hyperlinks etc.

#hamchallenge HC14S @hamchallenge

For the 14th challenge, 'Implement and describe a backup solution for your ham radio log.’, I realised that my backup options are simple. I keep copies of my ham log in different places like QRZ, Club Log, HamQTH etc., a copy taken automatically into my personal cloud backup, and my favourite paper logbook. I’m not an active operator and do not have the need for an offsite backup. #hamchallenge HC14S @hamchallenge

#hamchallenge @hamchallenge HC12S

Today I made a QSO with an unusual antenna (Nigel M0NGN on 7 MHz). It is a linear loaded vertical with 2 radials. The radiator is 7 meters long and consist of 450 Ohm ladder shorted at the top. This runs along a 10 meter Spiderbeam mast, so the feed point is at 3 meters high.

#hamchallenge Week 14: My #hamradio logbook #backup system is simple: My central log (to which I live-log contacts and import all my contest logs) is the console logger "YFKlog", which uses a MySQL database backend. It's running on a Hetzner VPS which creates nightly snapshots of the system disk that reach back seven days. In addition, a nightly cron-job creates a database dump which gets rsynced to another VPS in another datacenter. I also regularly upload my log to LoTW. #HC14S @hamchallenge

@hamchallenge HC22S #HamChallenge: Simulate an electric circuit. Used free LT-Spice to model a ~35W P-P RF power amplifier. Included a simple output graph showing dB gain of the circuit. Other possible simulations include input return loss, output match, time domain waveforms, harmonic distortion vs. drive level, and much more. Lots of fun to learn and experiment with this circuit simulation tool.
#HamRadio #RFDesign #Simulation

For this week's #hamchallenge : My primary logging software is #Wavelog. The webserver and backend database both run on virtualized machines in a #HighAvailability #Proxmox #cluster (same one that hosts this instance!). Those are backed up daily to another machine on site via PBS, then those backups are synced to a remote server running in a house in another city.

In addition, my log is also synced to both #QRZ and #LOTW every 6 hours or so, but I didn't think it qualifies as a true backup, since there is some data which those logs don't record.

#HC14S @hamchallenge #hamradio #amatuerradio

#hamchallenge week 14: Implement and describe a #backup solution for your #hamradio logbook

Describe/document your logging arrangements. Which software do you use, how do you merge logs (if at all)? Do you keep separate logs for different callsigns? How you can export/save your log, e.g. into an ADIF file? Describe how you back up your file. Do you use a cloud service? Save it on a memory stick, external HDD, or NAS?

Let's hear all about it, and hope you will never need it!

I'm really struggling with this week's #hamchallenge HC13. I cannot think of an "unusual location" for doing a QSO. I would do a QSO from quite everywhere as long as it is not risky. So, I think, I'll skip this challenge for the time being and probably I'll find a suitable location later on this year. @hamchallenge

Completed an unusual location QSO with John K9WIC on morning of March 14. Was up on the fifth floor of a senior independent living facility and looking out the south side window onto the golf course below. Repeater was a-bit north of this location — suspecting backscatter/reflections helped to complete this 2m contact.
@hamchallenge HC13S #HamChallenge #HamRadio
(Repost with added inclusions for the ham challenge report/boost.)

There is a 10m/70cm linked repeater on a nearby mountain, which is (nearly) los to my qth, so I usually use the 2m or 70cm repeaters there. Today I had two qsos via the 10m/70cm linked repeater, one with me using 10m and one where I used the 70cm part. Well, I guess it's my (compromised) 10m-setup, but 10m did not work as neatly as 70cm. Still: HC09S I guess :).

#hamchallenge @hamchallenge

p.s. Edit, yeah, numbers confused... sri :(.

I admit that I was lagging 5+ years behind on sending #hamradio QSL cards, mostly because the task "if I am sending a card to someone anyway, let's include all the other QSOs with them on the same card" sounded hard to express in SQL. (It is not.)

The #hamchallenge was a good excuse to finally fix that problem. Now I have both paper and electronic QSL cards, and the first bunch of 1000 cards is on the way to the press. HC01S!

df7cb.de/df7cb/log/qsl.cgi?cal

@hamchallenge