Let’s talk about Cloudlog. I have been using for a few years now Log4OM which is definitely doing everything I need. UDP in/out good management, labels printing, normal logging with good support for everything such as lookups on QRZ.com, HamQTH and so on…also all I need in terms of DX Cluster as well. Automated upload of QSOs in QRZ.com, Clublog, LoTW and eQSL.cc. It is also supporting TCI and Winkeyer which makes it perfect for all my needs.

One of the only issue I face with Log4OM is it is very slow especially while running a pile up. It cannot catch up when logging contacts very fast despite trying everything to optimize it. The computer I use is definitely not the problem as it is a very good configuration.

While looking for other logbook I came across Cloudlog. The good thing of Cloudlog is that it is web based. Developped in php/MySQL with CodeIgniter framework. But I also think it is one of the weakness as I think it becomes more complicated to interface with a lot of things.

For now I like very much the interface which is very nice and intuitive. I have installed the bridge for TCI which interface very well with SunSDR 2 DX but also Hermes Lite 2. I do not really like the management of cluster which uses a third party cluster cache and also one of my major issue is that when you click on a spot on the cluster it will not change the frequency on the radio which means the CAT on Cloudlog is basically one way only from the radio to Cloudlog not the other way around.

In the things I like though there is the management of different logbook as well as locations.

In Vietnam I use two calls: XV9BPO and XV9Q, I use XV9BPO from two different locations, from home (OK30IT) and from Tri Ann lake (OK31NC). While for XV9Q I can use from three different locations, from home (OK30IT), at the beach around 2h drive from home (OK30TO) and from Tri Ann Lake (OK31NC).

With Cloudlog it makes it very easy to switch from one call to the other or from one location to another.

All of the QSOs because they are made from same country are in the same logbook which makes it easy to check your DXCC with the two calls no matter which location. This part is very well managed in Cloudlog. You can do the same in Log4OM but I face a few bugs from time to time.

I am still testing Cloudlog and it misses a few things before I completely switch to it but it is promising.

If some ham actually check this post feel free to let me know which logbook you use.