this post was submitted on 22 Jul 2023
9 points (100.0% liked)

Amateur Radio

1069 readers
1 users here now

A Lemmy Community to share links about and for amateur (ham) radio to advance the technology, and promote communication and international goodwill. This community IS NOT for CB, GMRS, MURS, FRS, etc topics unless they are related to ham radio in some way.

We won't tolerate personal insults, illegal activity, or anything contrary to good amateur practice.

If asking questions about regulations, please include your country because we recognize that, while the hobby is international, regulations often aren't.

founded 2 years ago
MODERATORS
 

How do you log your QSOs ( if at all if that's something allowed in by your regualtor ?). Share your best practices, software and tips !

top 9 comments
sorted by: hot top controversial new old
[–] TrojanHam 3 points 1 year ago* (last edited 1 year ago) (1 children)

On the computer, I use cqrlog. As a Linux-user I've found it integrates well with flrig.

When out in the field, I'm using paper and pencil. Paper doesn't need batteries, will dry out if it gets wet, and pencil won't run. I write everything consistent with Fast Log Entry (FLE). When I get home, I use Vim and flecli to make adif files for upload, etc.

[–] martin77 1 points 1 year ago (1 children)

Thanks for sharing about flecli ! I'm also a VIM and FLE user but didn't know about that one !

[–] TrojanHam 2 points 1 year ago* (last edited 1 year ago) (1 children)

I also use vim-fle-syntax to have a nice color scheme. It helps find errors.

[–] m_randall 1 points 1 year ago

Ha. FLE looks awesome and the vim syntax highlighting is icing on the ZZ cake.

[–] martin77 2 points 1 year ago* (last edited 1 year ago)

When I first ot licensed back in the early 90's I started logging on paper. Back then I only had a novice licence allowing me 10w on 2m. Nevertheless I made thousands of QSOs over the years on FM and SSB.

A PC only became part of my amateur radio station when I got hooked by packet radio. That's also when I started logging on PC rather than on paper.

I could't remember all of the software I used to log but here are the ones I finally settled on :

  • Fast Log Entry by DF3CB : Fast Log Entry isn't a logbook as such. Instead it's a piece of software designed to convert paper logs to digital logs. For every QSO you only have to enter the information that changed from the previsous QSO. I still use it to this day when I'm just going out for a few QSO's on portable and log them on a paper notebook. If you are into SOTA or POTA it's definitely something to look into. I used it to convert years of paper logbooks to digital logbooks. DF3CB is also the author of BV7 a fantastic software used by QSL Managers.

  • Logger32 by K4CY has been my general purpose logbook. It's the one that's installed and that is used to log casual QSOs. It's full featured, interfaces with all my equipement and rather easy to use once setup. It also has support for LotW through an extension.

  • WinTest by F5MZN is what I will use if I join an HF contest those days ( that's becoming rare). It has support for pretty much any contest and is the go to application for SSB/CW and also RTTY contests. It's also offten used by DX-Expedition due to it's simplicity. While I would not recommend WinTest as a general logging application, I did use it for that purporse when I was operating from 9V but I did mostly run pile-ups during that time which made it usable for that purpose but don't do it if you want something that register's the other's stations operator's name and QTH.

  • Tucnak by OK1ZIA. Unlike the other applications listed above Tucknak is designed first and foremost for VHF+ contests. Initially develloped for Linux systems only, it since became available also on Windows, Android and even jailbraiked Kindle ! What makes Tucnak unique is the entry which is inheritaed from Taclog from OZ2M. Due to the bands conditions and the amount of information ( Callsign / report / QRA locator) it's not rare to miss a part of the exchange. Tucnak allows you to enter any information into a buffer and will automatically allocate it to the right field. Once all the information is completed a specific command stores the QSO. This associated to a large station database built over the years makes it a very strong application but with a steep learning curve. If you are going to use Tucnak during a contest, make sure to practice first so you don't loose a QSO during the contest. Tucnak has various functions dedicated to VHF+ contest, including networking allowing you to send skeds to other stations, ON4KST chat integration, log synchronisation, etc. It uses very little ressources so you can easily stick it on a Raspeberry PI behind a monitor.

That's it ! What do you use ?

[–] [email protected] 2 points 1 year ago

I do a paper log and then transfer it to QRZ, but I just started out. Still shaking some things out in my process.

[–] m_randall 2 points 1 year ago (1 children)

I’m using QRZs logger (free version). I like that it’s online and I like that it automatically validates contacts.

Most of my contacts are FT4/8 so I auto log there, then periodically upload the adi to QRZ. For my CW contacts I make a note of the frequency and time in my notebook (I’m not able to headcopy yet) and enter them manually after I’m done.

I’m gearing up for my first POTA activation and will probably use HAMRS for the CW portion there.

Are there any other online log books out there?

[–] TrojanHam 1 points 1 year ago (1 children)

There's Cloudlog. I've looked at it but am happy with cqrlog. I believe you can either self-host it (Raspberry Pi) or find an online host.

[–] martin77 1 points 1 year ago* (last edited 1 year ago)

Yes CQRLOG is great and graphically very pleasant. For some reasons I have never managed to fully switch my desktop to Linux but if was ever, this would most likely become my application of choice for general logging.

Thanks for sharing about cloudlog. I'm not a fan of subscription based applications but as I see you can self host I will definitely start a docker instance to see how it runs.