Cloudlog

I have decided to change from using QRZ.com to Cloudlog as my primary logging software. The main reason for doing this is so that I own the database on my machine, rather than trusting it to someone else's server.

It is installed on a Raspberry Pi - and that is where the database lives. Although this machine isn't on 24 hours/day, it is normally turned on when I'm doing anything related to amateur radio. If I need logging from a remote location (e.g. if I'm operating whilst on holiday), then I can leave the Pi running at home.

I followed the installation instructions here: https://github.com/magicbug/Cloudlog/wiki/Installation - except that the resulting installation had a problem with php-xml until I changed from PHP 7.3 to PHP 7.4, i.e.:

sudo apt-get install php7.4 php7.4-curl php7.4-mysql php7.4-mbstring php7.4-xml php7.4-openssl

Why this should be is a mystery... but it worked for me!

Next, I set my router's port forwarding so that incoming Port 80 points to the Raspberry Pi. I already use a Dynamic DNS, and this means I can access my log from anywhere.

Having followed the installation instructions, including setting up cron jobs, I then created two station locations. One is my primary "Home (IO91RG)" location, for general logging. The other is for repeater contacts (including DMR and D-Star). In this way I can segregate unassisted QSOs -- which count towards DXCC and other awards -- from repeater and internet-assisted QSOs.

I am still maintaining a free QRZ.com log, so now my logging work-flow is a little complex. Here is the strategy:

  1. For everyday HF and VHF QSOs, I will log these in Cloudlog. Periodically, I will create an ADIF export, and load this to QRZ.com.
  2. For VHF/UHF contests, I log these in Minos. From Minos, I save a record of the contest in ADIF, which is then used as my contest entry and also imported into Cloudlog and QRZ.com.
  3. For everyday FT8, the log is generated automatically by WSJT-X. Periodically, I load this ADIF into Cloudlog and QRZ.com.
  4. For FT8 contests, I temporarily rename WSJT-X's existing log files to wsjtx_log_temp.adi and wsjtx_temp.log. Then WSJT-X will automatically generate new wsjtx_log.adi and wsjtx.log log files for the contest. At the end of the contest I rename these to wsjtx_log_[date].adi and wsjtx_[date].log, using the date of the contest. The .adi file forms my contest entry; it is stored for posterity, and it is uploaded to Cloudlog and QRZ.com. Then I rename wsjtx_log_temp.adi and wsjtx_temp.log back to wsjtx_log.adi and wsjtx.log.

 

Comments

Post a Comment

Popular posts from this blog

Preventing "brown out" on a solar-powered Pi Pico

Image
The problem I have been experimenting with a solar-powered Meshtastic node, comprising a Pi Pico W and a Waveshare LoRA SX1262 board (also available from AliExpress , of course). I have housed these in a budget garden solar lamp (from eBay - many available - such as this ), which provides the charging circuit, the battery, and the enclosure. I had hoped that it would also provide the solar panel, but I found this to be insufficient so I replaced it with a larger 6V solar panel . The node runs fine when the battery is charged, but there is a problem when the battery runs down - which can happen overnight after a cloudy day. The next day when the sun comes up, the battery voltage starts to climb and at some point the Pico attempts to start up. This causes a current spike, which pulls the battery down, and the Pico shuts down. It then gets into a restart loop, which never properly resolves, and the node fails to start properly. What is needed is a way to cleanly switch the power on and...
Read more

Building a basic codeplug for DMR (DMR Part 2)

Image
What is a "codeplug"?  Confusingly, a codeplug is neither code, nor a plug! The term originates from a time when a physical plug was used to configure a radio's parameters. Nowadays it refers to a configuration file, which is typically prepared on an external PC and then uploaded to the radio. Overview This blog post continues from  Part 1 , and it assumes that you already have: A callsign A DMR ID A DMR rig - I will be using a Retevis RT3S for this example The programming software and cable for your rig. For the RT3S, the Windows software can be found here:  RT3S Software The example described below assumes that you are within reach of a DMR repeater on the Phoenix network, and that you know the details of that repeater (transmit and receive frequencies, color code). For now will configure the rig to access the DMR+ (Phoenix) network via a repeater. Subsequent posts will explain how to add analogue repeaters and simplex channels, hotspots, other networks, etc. The steps ...
Read more

Adding Brandmeister to the Hotspot (DMR Part 4)

Image
So far in this series of articles we have: Built a codeplug for the Retevis RT3S, enabling it to operate on the Phoenix (DMR+) network via a local repeater. Built a Hotspot and added a new zone to the codeplug, so that the RT3S can access the Phoenix (DMR+) network using the Hotspot. I chose Phoenix initially, because that is the network that my nearest repeater uses. Whilst this gives worldwide coverage, it is not the only DMR network. Confusingly, there are quite a few networks out there - including Brandmeister, TGIF, FreeDMR and probably others. Each has its own layout of talkgroups and timeslots. Sometimes these are similar, and there are links between networks so that some talkgroups are accessible on more than one network, but each has its own quirks and so they are different and mainly incompatible. With a Hotspot, it is possible to join more than one DMR network simultaneously - up to four networks - using functionality known as DMR Master. In this blog we will look at buildin...
Read more