AmateurRadio.com

OHB ver 4.23

 I have been sitting back and watching the many Hamclock projects evolve. What I was looking for was a project that, when finished, resembled Elwood's Hamclock. I am happy to report that I have settled on using OHB or Open Hamclock Backend. This has a very polished look and looks and operates, in my humble opinion, the closest to Elwood's Hamclock. It is a group effort and has progressed at a smooth pace. There is an OHB web page that offers support and status updates. I operate HamClock on my Pi4B, and if you operate Elwood's HamClock on a Pi, below is the process you go through to move from Elwood's version 4.22 HamClock to OHB version 4.23 HamClock. 

This script will download the script that you are going to need when entering the script listed below. As a side note, with some Pi OS's like Trixie, you will be prompted to enter your password whenever a "sudo" command is used. Just be aware that your password may be needed.  

 

4. The next command is: 

sudo fix-hosts

 I have read that you only need to enter if you are running Trixie or newer. In my case, I entered it anyway, as the instructions indicate you can if you would like to. I just did it as a just-in-case. 

5. After the above command has been entered, you may or may not be asked to reboot. I was not, but again I did anyway just to make sure. So I entered this command: 

sudo reboot now

 And it reboots the Pi, and if your HamClock starts up and is on the desktop, you need to again click on the lock and exit HamClock. 

6. You are now able to move over to either OHB, or you can also move to Hamclock.com backend. I will just be dealing with OHB in this post, but I will give you the command script for Hamclock.com backend as well. For moving to OHB enter this command: 

sudo ohb

If you want to move to Hamclock.com backend, then enter this script: 

sudo hcdc

7. Once you have done this, you can confirm that you have actually moved by entering this script: 

what

And it will confirm that you have moved to either OHB or HCDC, which over sudo command you entered above. In my case, the return script was: 

Your HamClock is set to Open HamClock Backend

   This confirmed to me that I had moved to OHB. 

 

8. The final step is to restart by entering this script: 

sudo reboot now

And once you have rebooted and HamClock goes through its startup, you will be asked if you want to go from version 4.22 to 4.23 and click YES.  

Updating

As a way of 2 side notes:

1. I did have to, for reasons not known to me, do the above process twice, as when I rebooted into the new feed for HamClock, I was not asked if I wanted to upgrade to 4.23. For some reason, it stayed on 4.22. Once I did steps 1-8 again, I was then asked to upgrade to 4.23.  

Ver 4.22 poor quality compared to 4.23

2. If you are operating Elwood's version of HamClock while it is loading, you will be asked if you want to upgrade to version 4.23, but as you say YES, you will be greeted with the following error message. To fix this, you need to change your back end. This is done by following the above 8 steps.