snabelen.no is one of the many independent Mastodon servers you can use to participate in the fediverse.
Ein norsk heimstad for den desentraliserte mikroblogge-plattformen.

Administrert av:

Serverstatistikk:

444
aktive brukere

#hamchallenge

8 innlegg7 deltakere5 innlegg i dag

For this week's #hamchallenge I observed the QRSS transmissions of S52AB on 30m. They're running 24/7 so it's a good indicator for the propagation on this 800km path. Each day I noted the times when the signal became visible in the morning and when it disappeared. The results are tabulated below. Typically the signal comes out of the noise with a big peak in the morning and then becomes weaker again, the same peak can be observed before it fades out. HC15S @hamchallenge

For #hamchallenge week 15 (#HC15) I will monitor the QRSS transmissions on 30m by S52AB. The reception usually follows a clear pattern: The signal appears in the morning when the skip zone gets small enough to arrive, during the day we see increased D layer absorption, and some time at night the signal disappears again. Interestingly, if often briefly re-appears at night, probably due to sporadic E. #hamradio @hamchallenge

For #hamchallenge HC14S I do on- and off-site backups of my computers regularly. So my logs are also in the backup. I use @restic for backup for some years already (and it is developed by a fellow amateur radio operator). From time to time I already restored some data from the backup, so this works as well.

The bigger problem are too many logfiles. Quite every digimode app comes with its own logging abilities. And I did not find a proper way to merge all logs yet.

@hamchallenge

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

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!