Who knew that Log4OM 2 was such an incredibly powerful and complete logging package!
#log4om2 #log4om
Das (mรถgliche) Problem mit WSJT-X, GridTracker und Log4OM.
UDP Ports, Forwarding und Probleme mit Datenverbindungen.
https://blog.schwenke.de/2023/ft4-8-mit-wsjt-x-gridtracker-mit-log4om
@ve3qbz That's Log4OM http://www.log4om.com/
Its a great general purpose logger and award tracker. Give it a try!
I consolidate logs from N1MM https://n1mmwp.hamdocs.com/
and FLDigi https://sourceforge.net/projects/fldigi/ into it
It can interface with WSJT and lots of other things.
Figured out filters in #Log4OM, and I think that was #MorseCode QSO number 29. First was exactly eight months ago, but the pace is picking up.
How to log a Satellite (SAT) QSO in Log4OM [QSL, eQSL, LOTW] https://flip.it/otd8v5
#radioamateur #hamradio #swl #log4om #satellite #tuto
Also, having #log4om just watch adif files created by #js8call and #jtdx is SO MUCH easier than trying to get tcp stuff to work.
And now I have log4om writing an adif that #gridTracker will read on startup.
Next up: why doesn't log4om keep the #flrig connection alive? :alex_grimace:
@kelvin0mql @michael @ParksOnTheAir I've set up #log4om to use that one, but it doesn't seem to include all the spots on the website.
Still have no idea what I'm doing, though.
I'm new to logging #hamradio contacts or using spotting outside of FT8. Is there a way to set up alerts for spots from a list of people? So if I had a list of mastodon.radio friends, the logging/spotting program would let me know when they pop up?
I'm using #log4om right now, but not super tied down.
#log4om certainly seems overwhelming on first look. Ugh.