Amateur Radio – Public Emergency Service

Our History:

Believe I’ve mentioned it before, but it was the “Cedar Fire – October, 2003” in San Diego County that definitely drove home the need to expand our ability to gather emergency information.  The fire stopped 1 mile from our home, but burned heck out of a lot of the community of Crest – I was driving to pick up Mexican takeout and just happened to spot the fire “tornado” at the top of the mountain – had heard nothing on television nor broadcast radio about it being that close.  (All of the broadcast media seemed to be focused on areas like Rancho Bernardo, etc., that day).  Came home, we packed up and got ready to “get out of Dodge” if necessary.

Later on, speaking of my disgust with personal lack of situation awareness with a good friend over in La Mesa, CA, he recommended I consider finally getting my Amateur Radio License – assuring me I would have little difficulty considering my communications/electronics background from the Navy.  In 2004 I aced the Technician’s exam with little preparation.

In August of 2015, Heidi mentioned several times that I should “get back into Ham Radio”…

Present:

Here it is, one year later, I am now a licensed Amateur Extra, and Heidi is an Amateur General…  We are slowly rebuilding our home “Ham Shack”, which will have HF, VHF, UHF capability, covering virtually all modes of operation.  It will have sufficient battery backup power to remain on-line for a significant amount of time – and eventually those batteries will have their own, dedicated, Solar Panels to keep them topped off and recharging when the sun is out.

If we absolutely have to, we will be prepared to go portable – still covering HF/VHF/UHF with battery backup.  (HF at present, would require us to park somewhere and set up).  Eventually, I plan to add digital mode capability to our portable ops setup.

Anyhoo, we continue to work, (slowly), on our Ham Shack and its capabilities.  Yesterday, I made the decision to join the San Diego Amateur Radio Emergency Service Group (SDGARES), and was gratified to be immediately accepted.  Now, we have even more to study/learn to determine exactly where we fit in, and how we can contribute.  There is a huge need, throughout the various Emergency Communications (EMCOMM) organizations supported by Amateur Radio, for folks in good physical condition that can go out and provide such service – at this age and state of life, that part will probably be prohibitive for us, but we will do what we can to help.  We *will* find a niche where we can be of service. 😉

Much, much more to follow…

The Amateur’s Code

I am re-posting this here as much of a reminder to myself as anyone else. Folks aren’t always what you want them to be, but this is something to strive for. IMHO

The Amateur’s Code is the creed by which all ham radio operators should aspire to live by. Written in 1928 by Paul M. Segal, then general counsel for the ARRL. You can still find the code published to this day in many ARRL books and publications.

The Amateur’s Code

by Paul M. Segal, W9EEA (1928)

The Radio Amateur is:

CONSIDERATE….. never knowingly operating in such a way as to lessen the pleasure of others.

LOYAL….. offering loyalty, encouragement and support to other amateurs, local clubs and the American Radio Relay League, through which Amateur Radio in the United States is represented nationally and internationally.

PROGRESSIVE….. with knowledge abreast of science, a well built and efficient station, and operation beyond reproach.

FRIENDLY….. with slow and patient operation when requested, friendly advice and counsel to the beginner, kindly assistance, co-operation and consideration for the interests of others. These are the hallmarks of the amateur spirit.

BALANCED….. Radio is an avocation, never interfering with duties owed to family, job, school or community.

PATRIOTIC….. with station and skill always ready for service to country and community.


The best advice I ever received in the Navy was “Be Fair, Be Firm, Be Friendly”.  I still try to live up to that, and it is well met by the above Code – it isn’t always easy.

dave

Our “Ham Shack” – starting over…

Originally, our Son claimed the back bedroom when we moved into this house, but he was near grown and it wasn’t too long before he moved out on his own, found work, married, and started a family. Eventually, I converted that room into a Home Office, and it stayed that way for many years – finally converted into a kind of “guest room”. Eventually, it simply became a kind of storage room, so I moved the old oak credenza and 4 drawer file cabinet back in. Last year, it became our “Ham Shack” in name only. Oh, there are radios crammed in there on the desk, but that was just cramming more “stuff” in on top of what was already there.

Now, it is finally time to set things up as a more proper “Ham Shack”, but I’m afraid that means pulling *everything* out first – then putting those things related to Radio operation first. I will be re-visiting the Shack’s RF ground early on as “Step #1” after everything is out of there.

This weekend, I plan to start building a “Ham Shack Desk Riser”, similar to one found on-line.  My design, while similar, will be made from Melamine White Shelf Board from our local Home Depot – and the layout will include risers inside the end pieces to provide more durability/strength, including plenty of additional risers to keep individual compartments relatively short, (to prevent sagging).  I have previously used Melamine to construct a workbench surface and “attic” in our shed and was very impressed by its durability.  In that project, I discovered that particular material is a bear to cut at home, so will go into Home Depot armed with an outline of each cut I want made on *their* setup.  Should come home with what equates to a “kit” that needs gluing, drilling, screwing, and edge finishing. 😉

Will try to update this entry as time passes.

Ham on Linux – be reluctant to upgrade

Freedom from Winders isn’t exactly “free” on Linux. Freedom *always* comes with a price. This is particularly true when it comes to doing a major software upgrade – whether you are running Winders, Linux, Unix, MAC OS, etc.  There will always be some “stuff” that needs to be overcome. (At least Linux doesn’t call home to the mother ship). 😉

Previously, a few of us were talking about waiting to try an “upgrade” from Linux Mint 17.3 to the new 18.0 version. I very much agree with avoiding jumping on the “bleeding edge” just because its there.  Linux Mint 18 is a major upgrade and a long term support (LTS) version, one that will be supported for years to come (2021).  In the past, each time I have gone to a new LTS, I’ve had problems with those programs I chose to install “in addition to” their normal support. (I was on Ubuntu for years and ran into this more than once). It pays to keep track of those “special” items as you add them, including any “PPAs” and stuff like the 64 bit version of Chrome from Google, CQRLOG, CHIRP, Oracle Virtual Box, etc.  Chances are you may need to do a reinstall of them.

This is particularly true if you are running CQRLOG. If you are building a fresh install, everything goes perfectly well at present, however, if you attempt to upgrade or reuse your old configuration (~/config/cqrlog), you will run into tons of errors. This has already been reported on the Program Author’s CQRLOG forums as several have attempted to jump the gun. In the end, it may be necessary for us to do a fresh install of CQRLOG anyway, then restore our data from backups. (You *are* backing up your data right? Right?) 😉

In the mean time, my old 17.3 continues to run CQRLOG and CAT our IC-718 quite satisfactorily, and there is simply no reason for me to mess with the our Shack computer – it is doing everything I/we need it to do. Any testing I’m doing with the new stuff is on a separate virtual machine.

PCWorld put out an article on this stuff yesterday – 11 July 2016 – here is the pertinent part – although they say “Soon”, that doesn’t mean the extra items you have installed outside the “normal” system upgrades will work, (i.e. any PPA’s, etc.):


The Linux Mint project released the final version of Linux Mint 18 “Sarah” on June 30. The project is now working on an upgrade path for Linux Mint 17.3 users.
Linux Mint 17.3 users can upgrade soon

As usual, two editions of Linux Mint are available: one with the more modern Cinnamon desktop and one with the more traditional MATE desktop.

This release is a big one, being the first major new version of Linux Mint in more than two years, and a release that bumps the underlying code from Ubuntu 14.04 to Ubuntu 16.04. That means lots of polish and new features for Linux Mint users.

At the moment, you can only get Linux Mint 18 by installing it from scratch. The Linux Mint project is working on an easy upgrade path from Linux Mint 17.3, the previous release and final version of the Linux Mint 17 series. Linux Mint 17.3 users should get a notification in Linux Mint’s Update Manager when it’s ready.

Also in July, the Linux Mint project will be working on versions of Linux Mint 18 with theKDE Plasma and Xfce desktops. If you prefer one of those desktops, stay tuned to Linux Mint’s website for more details.


UPDATE:  Well, its July 15, 2016 – and I see Linux Mint now has an upgrade path from 17.3 to 18.0 – via using the command line, the apt tool, and installing an upgrade tool named “mintupgrade” they have prepared.  Lots of command line work, and if you haven’t used “terminal” and the “apt” command – you might want to reconsider doing this.  I have not run this in our Ham Shack – (did you know Linux Mint 17.3 will be supported until 2019?) – instead, I will eventually consider doing a fresh install and simply rebuilding that system, restoring data from backups.  If you must, here is a link to their article:

How to upgrade to Linux Mint 18

Did I mention you should reconsider? 😉

Ham on Linux – IC-706MkIIG Rig Control

Working on this page for a good friend who has been more than just generous with her time, and friendship, as I’ve fumbled through life as a brand-new General, then Amateur Extra, and Volunteer Examiner since last September or so…  She, and her husband, are Amateur Extras too and inspired me to serve as a Volunteer Examiner here in our local area. I know a bit about computers and this is my way of returning some of the past favors – believe me this IS worth my time. 🙂

I am drawing heavily on my previous post on the IC-718 radio, this copy will be tailored to the incredibly popular Icom IC-706MkIIG radio.  Both radios are similar in function and setup, so it should be a fairly easy task.  Our IC-718 is currently working *very* happily being controlled by CQRLOG and I anticipate very little difficulty translating that success over to her 706. 🙂

Unless you already have the appropriate cable for the IC-706MkIIG, you will need to acquire one.  If you are like me and have moved to newer laptop computers, you probably don’t have a true “Comm Port” on your computer and will need to pick up an appropriate FTDI USB-serial cable.  (I am continuing to use another Ham operator’s eBay Store – BlueMax49ers – one whom I’ve had excellent results with in the past, solely as a customer/consumer – he hasn’t failed me yet).

That cable will permit you to establish CAT control over your radio – but it will not permit you to do those fancy digital modes of operation that are so popular these days. To do so will require another cable and box, (something like the Tigertronics Signalink USB-13I if it has the 13 pin Accessory connector on the back). None of that is required if you are sticking with regular voice/CW/RTTY modes, just CAT control is sufficient.


Must start with the rig itself

Before we get started, lets pay attention to the rig itself.  We need to access the IC-706MkIIG initial set mode via the Menu button/switch – (not certain, don’t own this rig, but “I think” you press and hold Menu to switch between quick set mode and initial set mode).  Once in the initial set mode menus – use the “Up | Down” buttons to navigate through the menu, and turn the main knob to change a setting on the menu.  I most strongly recommend you do *NOT* change anything, except those listed below, at this point – just use the “Up | Down” buttons to find the:

  • 34 CI-V ADDRES – (CI-V address) the default address should be “4E” (if it is not, there may be reason for that – but the default load of rigctld, (the rig control daemon) will expect to find this radio with an address of “4E”.
  • 35 CI-V BAUD – (CI-V data rate) set to “Auto” (If that doesn’t work, we will try 19200).
  • 36 CI-V TRN – (CI-V transceive) set to “off“.
  • 37 CI-V 731 – (CI-V operating frequency data length) set to “off“. (Only used when rig connected to IC-735 unit)

You should now be able to turn the radio off and those settings will be remembered by your rig.

Have to admit, I used a downloaded copy of the “Instruction Manual” for this rig to determine the above menu items.  I have no actual experience operating the IC-706MkIIG, but will have soon.


Now lets get started on the software

The first step is to assure your Linux account has access to the serial ports:

Even if you are using an FTDI USB-serial cable purchased for the purpose – you still have to be in the appropriate Linux “group”…

Add your user account name to the “dialout” group via Menu | Administration | Users and groups

Click on your account, then in the right click on the groups you are currently a member of – a list will pop-up and all you have to do is put a check mark next to the “dialout” group


Why the group name “dialout”? Every file in Linux has a security setting for access in terms of read/write/execute “permissions”. You are either the owner, member of a group, or “other” – the owner of most things in the system is “root”, but you should never use root as your normal user within Linux to avoid accidents and security problems.  So – the next best thing is to be member of the group that has rights on the item you want to use. For instance, in this case we want to access/control the ttyUSBx port. (Probably ttyUSB0, [“zero”], but it may be 1, 2 or 3 depending upon your computer/peripherals).

Back in the ’80s and early ’90s, most of us hooked up a telephone modem, which is a serial device, so they named the group given control over serial devices “dialout”.  Know it seems a weird name today, but that is how it came about and it still is in use.  Adding your account to Group dialout will give you the desired rights/control over serial communication on Linux, including ttyUSBx (usually ttyUSB0).


Second Step – let’s download and install those “other” packages for associated software programs you may eventually want to use in conjunction with CQRLOG and get them set up to automatically get updated with system updates by enabling their PPA repositories where we can, that way they will be “ready” when you are.

Use Administration | Synaptic Package Manager to install the following:

In filter type xplanet and then select the xplanet and xplanet-images (Mark for install) go ahead and Apply (install).. Then delete the xplanet from filter box.

In left column click on Ham Radio Universe and mark the following for installation:

Chirp (if not already installed – very handy if you have a uhf/vhf radio – not applicable to CQRLOG)
FLdigi (if not already installed)
TrustedQSL (need this if you use Logbook of the World)
xdx

Go ahead and “Apply”/install the packages then close Synaptic Package Manager

Note: We skipped over wsjt – will get that later by other means rather than old package

Open a terminal – we will be installing PPA Updates one line at a time Terminal;

sudo rm -f /etc/apt/sources.list.d/ubuntu-hams-ppa-­*
# type your password when prompted

sudo apt-add-repository ppa:ubuntu-hams-updates/ppa
# press ENTER when prompted

sudo apt-get update
# wait for the “$” prompt to reappear

That’s it, now Linux Mint will keep all your Ham Apps up to date automatically. You can refresh updates, and all the latest updates will be installed.

sudo add-apt-repository ppa:kamalmostafa/hamlib
# press ENTER when prompted

sudo apt-get update
# wait for the “$” prompt to reappear

———-

Now for WSJTX: The version in the software center is way out of date, so you will want to add the PPA for this as well, If you already installed, no worry, this will update that version. Open termial, copy and paste: again one line at a time and hit enter, follow prompts.

sudo add-apt-repository ppa:ki7mt/wsjtx

sudo apt-get update

sudo apt-get install wsjtx

Now you will want to install the Encoder:

sudo add-apt-repository ppa:ki7mt/kvasd-installer

sudo apt-get update

sudo apt-get install kvasd-installer

TO RUN
– Open A terminal and type: kvasd-installer
– Then, select Install decoder from the menu.

If you have difficulty with WJSTx, as far as selecting the sound card, you will need to install this as well. Open Terminal:

sudo apt-get install libqt5multimediawidgets5 libqt5multimedia5-plugins
libqt5multimedia5

Note copied from K8WDX blog: Then set it up, and you should be good to go. more info on future releases can be found here: https://launchpad.net/~ki7mt I strongly suggest going to this site and reading through it, there are a couple of things to do to get the latest updates as well and info about the future of WJSTX. I just like to wait until the versions are out of the development stage before I take the plunge.


Third Step – if you haven’t already done so, let’s install the latest CQRLOG package:

A *very* good installation can be had with a single command in terminal mode:

sudo add-apt-repository ppa:ok2cqr/ppa;sudo apt-get update;sudo apt-get install cqrlog

That command, (described here for version 2.0.1-1), will first, add the ppa repository to your linux system’s list of authorized spots to check for updates, then update the system list itself, and finally install the latest version found in that repository.

OK, you can finally close terminal – open Update Manager, click on Refresh, then install any new packages it found. Because you added the PPAs above, Update Manager will check and install updates to your Ham programs.


Its finally time to run CQRLOG!  (You will find it in your menu system, I recommend right-clicking on that menu item and pinning it to your panel).  When the program opens you will see the “Database Connection” window, which contains a default log file #1 entry.  Highlight that and click “Open”.  The system “should” ask you to agree to download/install a couple of necessary databases – click Yes for each of them.  (It will check for updates each time you open the program).  The Database Connection window will close and the “New QSO” window will open.

Configuring CQRLOG

In New QSO click on File | Preferences which will open the Preferences window to start your configuration of CQRLOG.  Down the left side of Preferences is a vertical column of tabs which lead to pages of settings.  I won’t cover all of them but here are my current recommendations for some of the more important stuff – you will have to play with them to suit your own desires – but pay particular attention to the TRX control stuff below:

Program tab:

  • Select “Show statistics in” MHz if it isn’t already checked
  • Select “Check for newer version of dxcc tables after program startup”
  • Select “Check for newer version of qsl managers database after program startup”
  • Select “Show distance in miles”
  • Select “get UTC time from computer time
  • Set “Grayline” to -1.25 (this setting worked for me on 05/24/2016)

Station tab:

  • Set “Call” to your FCC approved Call Sign
  • Set “Name” normally use your first name but…
  • Set “QTH” to your home area, (i.e. San Diego County, CA)
  • Set “Loc” to your Grid Square Locator (Hint – go here and type in your zip code if unsure) – This is a critical entry for the system to work correctly, make certain you have it right.

New QSO tab: (These are in addition to the defaults – some may now be new defaults in the latest version)

  • For now, I left the “Default values” at the top alone, including “Comment for QSO”
  • Also left “Enable auto mark QSO QSL_S field” as marked but with no value
  • Set “Use spacebar to move between fields”
  • Set “Skip over mode and frequency when radio is connected”
  • Set “Enable autosearch on HamQTH.com/QRZ.com”
  • Set “If ‘QSL via’ field contains other than a call sign, move to ‘Comment to QSO’ field”
  • Set “Show recent QSO records for last” to 7 days (rather than 5)
  • Set “In previous QSO list show QSO with call/p, call/m, W6/call etc.”
  • Set “Always overwrite info from previous QSO with callbook data”
  • Set “Always overwrite only CQ, ITU zones, County and US state”
  • Set “Capitalise first letter in QTH field (yeah I know how to spell capitalize, but they are from Europe).

Visible Columns tab:

  • Set “Date”
  • Set “Time on”
  • Set “CallSign” and “IOTA”
  • Set “Mode”
  • Set “Freq” and “QSL sent date”
  • Set “RST sent”
  • Set “RST Received” and DXCC
  • Set “Name” and “Comment to QSO”
  • Set “QTH” and “WAZ”
  • Set “QSL sent”
  • Set “QSL received”, “State”, and “Received QSL, LoTW, eQSL”
  • Set “Country Name”

Bands tab:

  • Set each band you plan to use your rig on

TRX control tab:  (many of these will now be default settings)

  • Set “Path to rigctl binary” to /usr/bin/rigctld
  • Set “Radio one Desc.” to IC-706MkIIG
  • Set “Host” to localhost
  • Set “Rig Model” to 311 Icom IC-706MkIIG (using the drop-down menu)
  • Set “Device” to /dev/ttyUSB0 (that last character is a zero – need to verify yours may be 1, 2, 3, etc.)
  • Set “Poll Rate” to 500
  • Set “Port Number” to 4532
  • Click to “X” Run rigctld when program starts
  • For now, leave the rest at their default settings

You should not need any additional arguments added for rigctld. CQRLOG will start it with the rig model number – it looks like “rigctld -m 311”, (mine is -m 313 for my IC-718), and that automatically sets it up for that specific radio, ready to communicate with CQRLOG via the Hamlib library, in other words “pure magic”. 🙂

ROT control tab:

  • ***To be determined at a later date – I do not currently own a rotor nor directional antenna

Modes tab:

  • You *must* set all modes to a value of Zero for your Icom radio.
  • I would have left the defaults for a rig other than Icom – (note on Icom radios for rig control the CQRLOG FAQ says to set them all to zero – I have confirmed my IC-718 will not accept Bandwidth changes via CAT cable)

 

QTH profiles tab:

  • ***To be determined at a later date

Export tab:

  • I set each and every item on this page – if I am “exporting” my log, I want *everything*.

DXCluster tab:

  • Colors are purely a personal decision – the darker colors generally work better for my eyes, but I wound up selecting Red, Lime, Blue and Navy respectively
  • Set “Show only spots” to those freqs/bands you are interested in – mine currently spans from 1.8 MHz to 28 MHz
  • Set “Show country name in the DX cluster spot”
  • Set “Connect to DX cluster after program startup”

Fonts tab:

  • I left this at defaults, (for now)

WAZ, ITU zones tab:

  • Colors are purely a personal decision – I am currently using Red, Red, Blue, Blue, and Fuchsia, Fuchsia
  • Set “Show info” for both WAZ and ITU

IOTA tab:

  • I chose to set “New IOTA” to Red and QSL needed for IOTA to Blue
  • Set “Show info”

Membership tab:

  • ***I haven’t set this up yet – not currently a member of anything associated with this

Bandmap Tab:

  • Set “Use the same color as the spot
  • Set “Ignore DX spots with freq equals to the start of the band (21.000, 14.000 etc., usually notes)”
  • ***I will need to revisit this one later on

xplanet support tab:

  • Set “Path for the xplanet” to /usr/bin/xplanet
  • I set “‘Window size” to 340 x 340 for now, will revisit later
  • Set “Show stations from” bandmap
  • Set “Projection” to azimuthal without background
  • Set “Use this xplanet font color” my selection was “White” by default, works well.

Zip code tracking tab:

  • ***I left at default settings for now

LoTW/eQSL support tab:

  • To use this tab, you will need an account with LoTW, (gained through TrustedQSL program), and register for an account on the eQSL web site.  I have done so, but with LoTW – now waiting on a snail-mail card from ARRL telling me how to proceed.  Note that part of this is to have a digital “certificate” file on your system to prove its actually “you” and your system doing the uploads to LoTW
  • Set “Include LoTW and eQSL confirmed countries in DXCC statistic”
  • Set “Use LoTW and eQSL confirmed countries for New country or New band etc. info”
  • Set “Show info in New QSO window if station uses LoTW/eQSL
  • Set “Use this color as a background in DX cluster and band map for stations using LoTW” (I chose Money Green)
  • Set “Use this color as a background in DX cluster and band map for stations using eQSL” (I chose Sky Blue)
  • Set “Upload to eQSL also data in COMMENT field”

CW interface tab:

  • ***Left at defaults until I discuss this with a very experienced Elmer

fldigi/wsjt interface tab:

  • ***Left at defaults until I have time to research this one

Auto backup tab:  I consider this one to be IMPORTANT!

  • Set “Enable autobackup after program ends
  • Set “Save backup to:” using the browse button – mine worked out to be /home/dave/.config/cqrlog/database/
  • Set “Backup file” by selecting “callsign, date and time (yourcall_yyyy-mm-dd_hh-mm-ss.adi)
  • Set “Compress backup with tar.gz

External viewers tab:

  • I left this one at defaults, it will probably stay that way for now

Callbook support tab:

  • Set Callbook search to either your HamQTH account or QRZ account.  Ham QTH is free – there is a minimal annual fee for QRZ – I elected to go with HamQTH for now – entering my User name and Password for that account in this tab

RBN support tab:

  • Left “Server:” at the default telnet address and port – telnet.reversebeacon.net:7000 – for now, (but know my friend will want to change it to his favorite)
  • Set “Login:” to your own callsign
  • For now, I also set “Watch for:” to my own callsign
  • Colors being subjective, I am using White, Purple, Maroon and Red in that order from the top down, (pretty sure these are now default colors)
  • Set “Delete old information after” 180 seconds, (I’m getting older, the default 60 seconds was too fast)

Online log upload tab:

  • Set “Enable upload to HamQTH” (if you have an account there)
  • Set in your Username and Password for HamQTH
  • I elected to “Set this” Blue “color to show information in status upload windowI left Clublog blank – not a member
  • Set “Use this” Red “color to show information in status upload window” in case I use Clublog in future
  • Left HRDLog.net entries blank
  • Set “Use this” Purple “color to show information in status upload window” in case I use HRDLog in future

Propagation tab:

  • Set “Show propagation as image
  • I was not happy with the tiny default display, so changed “Download data from:” to http://www.hamqsl.com/solar101pic.php
  • Set “Show A, K, SSN, FOF2 etc.”
  • Set “Show calculated prediction for HF bands”
  • Set “Show calculated prediction for VHF bands if you are interested

It should be as easy as that to get this going.

I spent over a week, troubleshooting a situation where some other (unknown) process, unrelated to CQRLOG, was periodically interfering with comms on device ttyUSB0, so I simply did a completely fresh install of Linux Mint 17.3 Cinnamon, then ran through the procedures above. CQRLOG has been running quite well and controlling our IC-718 rig very happily ever since. On a relatively “clean” Linux Mint installation, it should go well indeed – and you should be able to simply cut commands out of this document and past them into your linux terminal session to make it go *very* rapidly.

Its pretty easy to feel the installation for the Icom IC-706MkIIG should go a lot easier with the above procedure! 🙂

When I re-edit this post next time, will try to include the IC-706MkIIG specific settings that have to be made at the rig itself.


REFERENCE LINKS:

CQRLOG

Ham Radio Control Libraries

USB Serial Converter support

Linux Ham apps, install | K8WDX

CQRLOG configure <–YouTube video on a previous version of CQRLOG also by K8WDX

Ham on Linux – FT-950 Rig Control

Worked on this page for a good friend who has been generous with his time, etc., as I’ve fumbled through life as a brand-new General, then Amateur Extra, and Volunteer Examiner since last September or so…  I know a bit about computers and he knows a *ton* about radio – believe me its worth my time. 🙂

I am drawing heavily on my previous post on the IC-718 radio, this copy will be tailored to the excellent Yeasu FT-950 radio.  We tested this procedure on his rig, using an FTDI USB-serial cable.  The rig defaults to 4800 baud, which we bumped up to 19200.  It worked fine, he will let me know if it starts acting up at that speed, but tested for about half an hour and it was both fast and rock solid.

Unless you already have the appropriate cable for the FT-950, you will need to acquire one.  If you are like me and have moved to newer laptop computers, you probably don’t have a true “Comm Port” on your computer and will need to pick up an appropriate FTDI USB-serial cable.  (I am continuing to use another Ham operator’s eBay Store – BlueMax49ers – one whom I’ve had excellent results with in the past, solely as a customer/consumer – he hasn’t failed me yet).


Before we get started, lets have a look at the rig

I took a very hard look and a downloaded copy of the FT-950 Operating Manual – specifically for CAT-related items in the “Menu Mode”.  Found the following to be on target:

Menu Mode:

Press the “MENU” button momentarily, to engage the Menu Mode.
Display will show the Menu Number, Menu Group Name, and Menu Item.
Press the “SELECT” knob momentarily to toggle the display between “Menu Number & Menu Group Name” and “Menu Item”. The Multi-Display Window shows the current setting of the currently selected Menu item.
Rotate the “SELECT” knob to select the menu item you wish to modify.
Rotate the “CLAR/VFO-B” knob to chnge the current setting of the selected Menu item.
Press the “CLEAR” button (located at the upper right of the “SELECT” knob momentarily to reset the selected Menu item to factory default value.

When you have finished making your adjustments, press and hold “MENU” button for one second to save the new setting and exit to normal operation. If you only momentarily press the “MENU” button, the new settings will NOT be retained.

Then I found the following CAT items:

GENERAL GROUP:

O26 GENE CAT BPS – Default = 4800 bps (CAT data rate in baud) believe this should be set to 19200 for operation with a FTDI USB-serial Cable, but the default would probably be OK for a standard Comm port/cable
027 GENE CAT TOT – default = 10 msec TOT=time out timer
028 GENE CAT RTS – Default = On

SO – I suspect the only default menu item parameter that would need adjustment from the default setting would be the baud rate if you are using an FTDI USB-serial cable. Remember, to press and hold “MENU” button for one second after you have set the parameter to assure you actually SAVE the new setting.

Just a note, for CAT operation, I suspect you will want to have the radio in VFO mode rather than Memory… When it doubt, go for VFO.


The first step is to assure your Linux account has access to the serial ports:

Even if you are using an FTDI USB-serial cable purchased for the purpose – you still have to be in the appropriate Linux “group”…  This is most important on any Debian/Ubuntu/Linux Mint installation as it is *not* a default group when you build your account(s).

Added my account name to the “dialout” group via Menu | Administration | Users and groups

Click on your account, then in the right click on the groups you are currently a member of – a list will pop-up and all you have to do is put a check mark next to the “dialout” group


Why the group name “dialout”? Every file in linux has a security setting for access in terms of read/write/execute “permissions”. You are either the owner, member of a group, or “other” – the owner of most things in the system is “root”, but you should never use root as your normal user within linux to avoid accidents and security problems.  So – the next best thing is to be member of the group that has rights on the item you want to use. For instance, in this case we want to access/control the ttyUSBx port. (Probably ttyUSB0, [“zero”], but it may be 1, 2 or 3 depending upon your computer/peripherals).

Back in the ’80s and early ’90s, most of us hooked up a telephone modem, which is a serial device, so they named the group given control over serial devices “dialout”.  Know it seems a weird name today, but that is how it came about and it still is in use.  Adding your account to Group dialout will give you the desired rights/control over serial communication on Linux, including ttyUSBx (usually ttyUSB0).


Second Step – let’s download and install those “other” packages for associated software programs you may eventually want to use in conjunction with CQRLOG and get them set up to automatically get updated with system updates by enabling their PPA repositories where we can, that way they will be “ready” when you are.

Use Administration | Synaptic Package Manager to install the following:

In filter type xplanet and then select the xplanet and xplanet-images (Mark for install) go ahead and Apply (install).. Then delete the xplanet from filter box.

In left column click on Ham Radio Universe and mark the following for installation:

Chirp (if not already installed – very handy if you have a uhf/vhf radio – not applicable to CQRLOG)
FLdigi (if not already installed)
TrustedQSL (need this if you use Logbook of the World)
xdx

Go ahead and “Apply”/install the packages then close Synaptic Package Manager

Note: We skipped over wsjt – will get that later by other means rather than old package

Open a terminal – we will be installing PPA Updates one line at a time Terminal;

sudo rm -f /etc/apt/sources.list.d/ubuntu-hams-ppa-­*
# type your password when prompted

sudo apt-add-repository ppa:ubuntu-hams-updates/ppa
# press ENTER when prompted

sudo apt-get update
# wait for the “$” prompt to reappear

That’s it, now Linux Mint will keep all your Ham Apps up to date automatically. You can refresh updates, and all the latest updates will be installed.

sudo add-apt-repository ppa:kamalmostafa/hamlib
# press ENTER when prompted

sudo apt-get update
# wait for the “$” prompt to reappear

———-

Now for WSJTX: The version in the software center is way out of date, so you will want to add the PPA for this as well, If you already installed, no worry, this will update that version. Open termial, copy and paste: again one line at a time and hit enter, follow prompts.

sudo add-apt-repository ppa:ki7mt/wsjtx

sudo apt-get update

sudo apt-get install wsjtx

Now you will want to install the Encoder:

sudo add-apt-repository ppa:ki7mt/kvasd-installer

sudo apt-get update

sudo apt-get install kvasd-installer

TO RUN
– Open A terminal and type: kvasd-installer
– Then, select Install decoder from the menu.

If you have difficulty with WJSTx, as far as selecting the sound card, you will need to install this as well. Open Terminal:

sudo apt-get install libqt5multimediawidgets5 libqt5multimedia5-plugins
libqt5multimedia5

Note copied from K8WDX blog: Then set it up, and you should be good to go. more info on future releases can be found here: https://launchpad.net/~ki7mt I strongly suggest going to this site and reading through it, there are a couple of things to do to get the latest updates as well and info about the future of WJSTX. I just like to wait until the versions are out of the development stage before I take the plunge.


Third Step – if you haven’t already done so, let’s install the latest CQRLOG package:

A *very* good installation can be had with a single command in terminal mode:

sudo add-apt-repository ppa:ok2cqr/ppa;sudo apt-get update;sudo apt-get install cqrlog

That command, (described here for version 2.0.1-1), will first, add the ppa repository to your linux system’s list of authorized spots to check for updates, then update the system list itself, and finally install the latest version found in that repository.

OK, you can finally close terminal – open Update Manager, click on Refresh, then install any new packages it found. Because you added the PPAs above, Update Manager will check and install updates to your Ham programs.


Its finally time to run CQRLOG!  (You will find it in your menu system, I recommend right-clicking on that menu item and pinning it to your panel).  When the program opens you will see the “Database Connection” window, which contains a default log file #1 entry.  Highlight that and click “Open”.  The system “should” ask you to agree to download/install a couple of necessary databases – click Yes for each of them.  (It will check for updates each time you open the program).  The Database Connection window will close and the “New QSO” window will open.

Configuring CQRLOG

In New QSO click on File | Preferences which will open the Preferences window to start your configuration of CQRLOG.  Down the left side of Preferences is a vertical column of tabs which lead to pages of settings.  I won’t cover all of them but here are my current recommendations for some of the more important stuff – you will have to play with them to suit your own desires – but pay particular attention to the TRX control stuff below:

Program tab:

  • Select “Show statistics in” MHz if it isn’t already checked
  • Select “Check for newer version of dxcc tables after program startup”
  • Select “Check for newer version of qsl managers database after program startup”
  • Select “Show distance in miles”
  • Select “get UTC time from computer time
  • Set “Grayline” to -1.25 (this setting worked for me on 05/24/2016)

Station tab:

  • Set “Call” to your FCC approved Call Sign
  • Set “Name” normally use your first name but…
  • Set “QTH” to your home area, (i.e. San Diego County, CA)
  • Set “Loc” to your Grid Square Locator (Hint – go here and type in your zip code if unsure) – This is a critical entry for the system to work correctly, make certain you have it right.

New QSO tab: (These are in addition to the defaults – some may now be new defaults in the latest version)

  • For now, I left the “Default values” at the top alone, including “Comment for QSO”
  • Also left “Enable auto mark QSO QSL_S field” as marked but with no value
  • Set “Use spacebar to move between fields”
  • Set “Skip over mode and frequency when radio is connected”
  • Set “Enable autosearch on HamQTH.com/QRZ.com”
  • Set “If ‘QSL via’ field contains other than a call sign, move to ‘Comment to QSO’ field”
  • Set “Show recent QSO records for last” to 7 days (rather than 5)
  • Set “In previous QSO list show QSO with call/p, call/m, W6/call etc.”
  • Set “Always overwrite info from previous QSO with callbook data”
  • Set “Always overwrite only CQ, ITU zones, County and US state”
  • Set “Capitalise first letter in QTH field (yeah I know how to spell capitalize, but they are from Europe).

 

Visible Columns tab:

  • Set “Date”
  • Set “Time on”
  • Set “CallSign” and “IOTA”
  • Set “Mode”
  • Set “Freq” and “QSL sent date”
  • Set “RST sent”
  • Set “RST Received” and DXCC
  • Set “Name” and “Comment to QSO”
  • Set “QTH” and “WAZ”
  • Set “QSL sent”
  • Set “QSL received”, “State”, and “Received QSL, LoTW, eQSL”
  • Set “Country Name”

 

Bands tab:

  • Set each band you plan to use your rig on

TRX control tab:

  • Set “Path to rigctl binary” to /usr/bin/rigctld
  • Set “Radio one Desc.” to FT-950
  • Set “Host” to localhost
  • Set “Rig Model” to 128 Yaesu FT-950 (using the drop-down menu)
  • Set “Device” to /dev/ttyUSB0 (that last character is a zero – need to verify yours may be 1, 2, 3, etc.)
  • Set “Poll Rate” to 500
  • Set “Port Number” to 4532
  • Click to “X” Run rigctld when program starts
  • For now, leave the rest at their default settings

You should not need any additional arguments added for rigctld. CQRLOG will start it with the rig model number – it looks like “rigctld -m 128”, (mine is -m 313 for my IC-718), and that automatically sets it up for that specific radio

ROT control tab:

  • ***To be determined at a later date

Modes tab:

  • I would leave the defaults for this Yeasu rig – (note on ICOM radios for rig control the CQRLOG FAQ says to set them all to zero, and that works – but for ICOM rigs only)

QTH profiles tab:

  • ***To be determined at a later date

Export tab:

  • I set each and every item on this page – if I am “exporting” my log, I want *everything*.

DXCluster tab:

  • Colors are purely a personal decision – the darker colors generally work better for my eyes, but I wound up selecting Red, Lime, Blue and Navy respectively
  • Set “Show only spots” to those freqs/bands you are interested in – mine currently spans from 1.8 MHz to 28 MHz
  • Set “Show country name in the DX cluster spot”
  • Set “Connect to DX cluster after program startup”

 

Fonts tab:

  • I left this at defaults, (for now)

WAZ, ITU zones tab:

  • Colors are purely a personal decision – I am currently using Red, Red, Blue, Blue, and Fuchsia, Fuchsia
  • Set “Show info” for both WAZ and ITU

 

IOTA tab:

  • I chose to set “New IOTA” to Red and QSL needed for IOTA to Blue
  • Set “Show info”

 

Membership tab:

  • ***I haven’t set this up yet – not currently a member of anything associated with this

Bandmap Tab:

  • Set “Use the same color as the spot
  • Set “Ignore DX spots with freq equals to the start of the band (21.000, 14.000 etc., usually notes)”
  • ***I will need to revisit this one later on

xplanet support tab:

  • Set “Path for the xplanet” to /usr/bin/xplanet
  • I set “‘Window size” to 340 x 340 for now, will revisit later
  • Set “Show stations from” bandmap
  • Set “Projection” to azimuthal without background
  • Set “Use this xplanet font color” my selection was “White” by default, works well.

Zip code tracking tab:

  • ***I left at default settings for now

LoTW/eQSL support tab:

  • To use this tab, you will need an account with LoTW, (gained through TrustedQSL program), and register for an account on the eQSL web site.  I have done so, but with LoTW – now waiting on a snail-mail card from ARRL telling me how to proceed.  Note that part of this is to have a digital “certificate” file on your system to prove its actually “you” and your system doing the uploads to LoTW
  • Set “Include LoTW and eQSL confirmed countries in DXCC statistic”
  • Set “Use LoTW and eQSL confirmed countries for New country or New band etc. info”
  • Set “Show info in New QSO window if station uses LoTW/eQSL
  • Set “Use this color as a background in DX cluster and band map for stations using LoTW” (I chose Money Green)
  • Set “Use this color as a background in DX cluster and band map for stations using eQSL” (I chose Sky Blue)
  • Set “Upload to eQSL also data in COMMENT field”

 

CW interface tab:

  • ***Left at defaults until I discuss this with a very experienced Elmer

fldigi/wsjt interface tab:

  • ***Left at defaults until I have time to research this one

Auto backup tab:  I consider this one to be IMPORTANT!

  • Set “Enable autobackup after program ends
  • Set “Save backup to:” using the browse button – mine worked out to be /home/dave/.config/cqrlog/database/
  • Set “Backup file” by selecting “callsign, date and time (yourcall_yyyy-mm-dd_hh-mm-ss.adi)
  • Set “Compress backup with tar.gz

External viewers tab:

  • I left this one at defaults, it will probably stay that way for now

Callbook support tab:

  • Set Callbook search to either your HamQTH account or QRZ account.  Ham QTH is free – there is a minimal annual fee for QRZ – I elected to go with HamQTH for now – entering my User name and Password for that account in this tab

RBN support tab:

  • Left “Server:” at the default telnet address and port – telnet.reversebeacon.net:7000 – for now, (but know my friend will want to change it to his favorite)
  • Set “Login:” to your own callsign
  • For now, I also set “Watch for:” to my own callsign
  • Colors being subjective, I am using White, Purple, Maroon and Red in that order from the top down, (pretty sure these are now default colors)
  • Set “Delete old information after” 180 seconds, (I’m getting older, the default 60 seconds was too fast)

 

Online log upload tab:

  • Set “Enable upload to HamQTH” (if you have an account there)
  • Set in your Username and Password for HamQTH
  • I elected to “Set this” Blue “color to show information in status upload windowI left Clublog blank – not a member
  • Set “Use this” Red “color to show information in status upload window” in case I use Clublog in future
  • Left HRDLog.net entries blank
  • Set “Use this” Purple “color to show information in status upload window” in case I use HRDLog in future

Propagation tab:

  • Set “Show propagation as image
  • I was not happy with the tiny default display, so changed “Download data from:” to http://www.hamqsl.com/solar101pic.php
  • Set “Show A, K, SSN, FOF2 etc.”
  • Set “Show calculated prediction for HF bands”
  • Set “Show calculated prediction for VHF bands if you are interested

 


I will be counting on help about the rest of the settings from that same experienced Ham who has done many years of DX, and has experience with a different logging program.  Between the two of us, we were able to whip his FT-950 into shape with CQRLOG, and in return, I will learn a ton about making effective *use* of it now that we both have rig control working.

A ton of credit for what you find on this page goes to K8WDX – his work, although on a previous version of CQRLOG and a different radio, inspired me to pursue installing everything needed now and for future work with those “other” digital modes.  Many thanks to K8WDX for sharing his own experiences.


REFERENCE LINKS:

CQRLOG

Ham Radio Control Libraries

USB Serial Converter support

Linux Ham apps, install | K8WDX

CQRLOG configure <–YouTube video on a previous version of CQRLOG also by K8WDX

Ham on Linux – IC-718 Rig Control

This project got started when another Ham, (also a Linux Mint enthusiast), asked me to take a look at a package called “CQRLOG”.  I did, and after lots of research plus trial and error – have got it working, also have a growing love for CQRLOG.

I am currently running Linux Mint 17.3 Cinnamon (64 bit), and CQRLOG 2.0.1-1 (64 bit) on a 4 year old Toshiba laptop.

NOTE:  I will continue to update this page as I make new discoveries about CQRLOG v/s IC-718


Before we get started, lets pay attention to the rig itself.  We need to access the IC-718 initial start menus – turn the radio off, press and hold the “Set” button on the radio while turning it back on.  You should now see the menus – use the “Up | Down” buttons to navigate through the menu, and turn the main knob to change a setting on the menu.  I most strongly recommend you do *NOT* change anything, except those listed below, at this point – just use the “Up | Down” buttons to find the:

  • CIV 731  set to “of” (off).
  • CIV TRN – set to “of” (off).
  • CIV ADD – the default address should be “5E” (if it is not, there may be reason for that – but the default load of rigctld, (the rig control daemon) will expect to find this radio with an address of “5E”.
  • CIV BAUD – set to “Hi” (I don’t remember if that is default, but this works well for me).

You should now be able to turn the radio off and those settings will be remembered by your rig.

Note:  These are the settings that are currently working for me – and, following the list below, I now have rock-solid control over my rig with CQRLOG v. 2.0.1-1 (of course that applies as I write this – your mileage may vary). 🙂


Let’s tackle the software!

The first step is to assure your Linux account has access to the serial ports, (this has to be set in Mint and other Debian Linux derivatives/forks):

Even if you are using an FTDI USB-serial cable purchased for the purpose, (as I am) – you still have to be in the appropriate Linux “group”…

Added my account name to the “dialout” group via Menu | Administration | Users and groups

Click on your account, then in the right click on the groups you are currently a member of – a list will pop-up and all you have to do is put a check mark next to the “dialout” group


Why the group name “dialout”? Every file in linux has a security setting for access in terms of read/write/execute “permissions”. You are either the owner, member of a group, or “other” – the owner of most things in the system is “root”, but you should never use root as your normal user within linux to avoid accidents and security problems.  So – the next best thing is to be member of the group that has rights on the item you want to use. For instance, in this case we want to access/control the ttyUSBx port. (Probably ttyUSB0, [“zero”], but it may be 1, 2 or 3 depending upon your computer/peripherals).

Back in the ’80s and early ’90s, most of us hooked up a telephone modem, which is a serial device, so they named the group given control over serial devices “dialout”.  Know it seems a weird name today, but that is how it came about and it still is in use.  Adding your account to Group dialout will give you the desired rights/control over serial communication on Linux, including ttyUSBx (usually ttyUSB0).


Second Step – let’s download and install those “other” packages for associated software programs you may eventually want to use in conjunction with CQRLOG and get them set up to automatically get updated with system updates by enabling their PPA repositories where we can, that way they will be “ready” when you are.

Use Administration | Synaptic Package Manager to install the following:

In filter type xplanet and then select the xplanet and xplanet-images (Mark for install) go ahead and Apply (install).. Then delete the xplanet from filter box.

In left column click on Ham Radio Universe and mark the following for installation:

Chirp (if not already installed – very handy if you have a uhf/vhf radio – not applicable to CQRLOG)
FLdigi (if not already installed)
TrustedQSL (need this if you use Logbook of the World)
xdx

Go ahead and “Apply”/install the packages then close Synaptic Package Manager

Note: We skipped over wsjt – will get that later by other means rather than old package

Open a terminal – we will be installing PPA Updates one line at a time Terminal;

sudo rm -f /etc/apt/sources.list.d/ubuntu-hams-ppa-­*
# type your password when prompted

sudo apt-add-repository ppa:ubuntu-hams-updates/ppa
# press ENTER when prompted

sudo apt-get update
# wait for the “$” prompt to reappear

That’s it, now Linux Mint will keep all your Ham Apps up to date automatically. You can refresh updates, and all the latest updates will be installed.

sudo add-apt-repository ppa:kamalmostafa/hamlib
# press ENTER when prompted

sudo apt-get update
# wait for the “$” prompt to reappear

———-

Now for WSJTX: The version in the software center is way out of date, so you will want to add the PPA for this as well, If you already installed, no worry, this will update that version. Open termial, copy and paste: again one line at a time and hit enter, follow prompts.

sudo add-apt-repository ppa:ki7mt/wsjtx

sudo apt-get update

sudo apt-get install wsjtx

Now you will want to install the Encoder:

sudo add-apt-repository ppa:ki7mt/kvasd-installer

sudo apt-get update

sudo apt-get install kvasd-installer

TO RUN
– Open A terminal and type: kvasd-installer
– Then, select Install decoder from the menu.

If you have difficulty with WJSTx, as far as selecting the sound card, you will need to install this as well. Open Terminal:

sudo apt-get install libqt5multimediawidgets5 libqt5multimedia5-plugins
libqt5multimedia5

Note copied from K8WDX blog: Then set it up, and you should be good to go. more info on future releases can be found here: https://launchpad.net/~ki7mt I strongly suggest going to this site and reading through it, there are a couple of things to do to get the latest updates as well and info about the future of WJSTX. I just like to wait until the versions are out of the development stage before I take the plunge.

NOTE:  Most of the above are for the newer digital communication modes – something I will eventually want to get into and investigate.


Third Step – if you haven’t already done so, let’s install the latest CQRLOG package:

I’ve previously describe how to do so in the post entitled:

Ham with Linux – CQRLOG

OK, you can finally close terminal – open Update Manager, click on Refresh, then Install the new packages it found. Because you added the PPAs above, Update Manager will check and install updates to your Ham programs.


Its finally time to run CQRLOG!  (You will find it in your menu system, I recommend right-clicking on that menu item and pinning it to your panel).  When the program opens you will see the “Database Connection” window, which contains a default log file #1 entry. (You can edit the log name and add new logs later on).  For now, click on the default log to highlight it, then click “Open”.  The system “should” ask you to agree to download/install a couple of necessary databases – click Yes for each of them.  (It will check for updates each time you open the program after we get it configured).  The Database Connection window will close and the “New QSO” window will open.

Configuring CQRLOG

In New QSO click on File | Preferences which will open the Preferences window to start your configuration of CQRLOG.  Down the left side of Preferences is a vertical column of tabs which lead to pages of settings.  I won’t cover all of them but here are my current recommendations for some of the more important stuff – you will have to play with them to suit your own desires – but pay particular attention to the TRX control stuff below:

Program tab:

  • Select “Show statistics in” MHz
  • Select “Check for newer version of dxcc tables after program startup”
  • Select “Check for newer version of qsl managers database after program startup”
  • Select “Show distance in miles”
  • Select “get UTC time from computer time
  • Set “Grayline” to -1.25 (this setting worked for me on 05/24/2016)

Station tab:

  • Set “Call” to your FCC approved Call Sign
  • Set “Name” normally use your first name but…
  • Set “QTH” to your home area, (i.e. CA-USA, or San Diego County, USA)
  • Set “Loc” to your Grid Square Locator (Hint – go here and type in your zip code if unsure) – This is a critical entry for the system to work correctly, make certain you have it right.

New QSO tab: (These are in addition to the defaults – some may now be new defaults in the latest version)

  • For now, I left the “Default values” at the top alone, including “Comment for QSO”
  • Also left “Enable auto mark QSO QSL_S field” as marked but with no value
  • Set “Use spacebar to move between fields”
  • Set “Skip over mode and frequency when radio is connected”
  • Set “Enable autosearch on HamQTH.com/QRZ.com”
  • Set “If ‘QSL via’ field contains other than a call sign, move to ‘Comment to QSO’ field”
  • Set “Show recent QSO records for last” to 7 days (rather than 5)
  • Set “In previous QSO list show QSO with call/p, call/m, W6/call etc.”
  • Set “Always overwrite info from previous QSO with callbook data”
  • Set “Always overwrite only CQ, ITU zones, County and US state”
  • Set “Capitalise first letter in QTH field (yeah I know how to spell capitalize, but they are from Europe).

Visible Columns tab:

  • Set “Date”
  • Set “Time on”
  • Set “CallSign” and “IOTA”
  • Set “Mode”
  • Set “Freq” and “QSL sent date”
  • Set “RST sent”
  • Set “RST Received” and DXCC
  • Set “Name” and “Comment to QSO”
  • Set “QTH” and “WAZ”
  • Set “QSL sent”
  • Set “QSL received”, “State”, and “Received QSL, LoTW, eQSL”
  • Set “Country Name”

Bands tab:

  • Set each band you plan to use your rig on – for now I skipped, (left unselected), 136 kHz, 472 kHz then 5 MHz and everything 50 MHz or above.  Will revisit this tab as I gain more experience with my Amateur Extra license

TRX control tab:

  • Set “Path to rigctl binary” to /usr/bin/rigctld
  • Set “Radio one Desc.” to IC-718
  • Set “Host” to localhost
  • Set “Rig Model” to 313 ICOM IC-718 (using the drop-down menu)
  • Set “Device” to /dev/ttyUSB0 (that last character is a zero – need to verify yours may be 1, 2, 3, etc.)
  • Set “Poll Rate” to 500
  • Set “Port Number” to 4532
  • Click to “X” Run rigctld when program starts  <– this is *very* important for rig control
  • For now, leave the rest at their default settings

You should not need any additional arguments added for rigctld. CQRLOG will start it with the rig model number, (mine is -m 313), and that automatically sets it up for that specific radio

ROT control tab:

  • ***To be determined at a later date

Modes tab:

  • I would have left the defaults for a rig other than ICOM – (note on ICOM radios for rig control the CQRLOG FAQ says to set them all to zero – my IC-718 will not accept Bandwidth changes via CAT cable)

QTH profiles tab:

  • ***To be determined at a later date

Export tab:

  • I set each and every item on this page – if I am “exporting” my log, I want *everything*.

DXCluster tab:

  • Colors are purely a personal decision – the darker colors generally work better for my eyes, but I wound up selecting Red, Lime, Blue and Navy respectively
  • Set “Show only spots” to those freqs/bands you are interested in – mine currently spans from 1.8 MHz to 28 MHz
  • Set “Show country name in the DX cluster spot”
  • Set “Connect to DX cluster after program startup”

Fonts tab:

  • I left this at defaults, (for now)

WAZ, ITU zones tab:

  • Colors are purely a personal decision – I am currently using Red, Red, Blue, Blue, and Fuchsia, Fuchsia
  • Set “Show info” for both WAZ and ITU

IOTA tab:

  • I chose to set “New IOTA” to Red and QSL needed for IOTA to Blue
  • Set “Show info”

Membership tab:

  • ***I haven’t set this up yet as I haven’t joined anything associated with this tab

Bandmap Tab:

  • Set “Use the same color as the spot
  • Set “Ignore DX spots with freq equals to the start of the band (21.000, 14.000 etc., usually notes)”
  • ***I will need to revisit this one later on

xplanet support tab:

  • Set “Path for the xplanet” to /usr/bin/xplanet
  • I set “‘Window size” to 340 x 340 for now
  • Set “Show stations from” bandmap
  • Set “Projection” to azimuthal without background
  • Set “Show xplanet after program startup”
  • Set “Close xplanet with CQRLOG”
  • Set “Use this xplanet font color” my selection was “White” by default, works well.

Zip code tracking tab:

  • ***I left at default settings for now – will revisit this tab later

LoTW/eQSL support tab:

  • To use this tab, you will need an account with LoTW, (gained through TrustedQSL program), and register for an account on the eQSL web site.  I have done so, but with LoTW – now waiting on a snail-mail card from ARRL telling me how to proceed.  Note that part of this is to have a digital “certificate” file on your system to prove its actually “you” and your system doing the uploads to LoTW
  • Set “Include LoTW and eQSL confirmed countries in DXCC statistic”
  • Set “Use LoTW and eQSL confirmed countries for New country or New band etc. info”
  • Set “Show info in New QSO window if station uses LoTW/eQSL
  • Set “Use this color as a background in DX cluster and band map for stations using LoTW” (I chose Money Green)
  • Set “Use this color as a background in DX cluster and band map for stations using eQSL” (I chose Sky Blue)
  • Set “Upload to eQSL also data in COMMENT field”

CW interface tab:

  • ***Left at defaults until I discuss this with a very experienced Elmer

fldigi/wsjt interface tab:

  • ***Left at defaults until I have time to research this one

Auto backup tab:  I consider this one to be IMPORTANT!

  • Set “Enable autobackup after program ends
  • Set “Save backup to:” using the browse button – mine worked out to be /home/dave/.config/cqrlog/database/
  • Set “Backup file” by selecting “callsign, date and time (yourcall_yyyy-mm-dd_hh-mm-ss.adi)
  • Set “Compress backup with tar.gz

External viewers tab:

  • I left this one at defaults, it will probably stay that way for now

Callbook support tab:

  • Set Callbook search to either your HamQTH account or QRZ account.  Ham QTH is free – there is a minimal annual fee for QRZ – I elected to go with HamQTH for now – entering my User name and Password for that account in this tab

RBN support tab:

  • Left “Server:” at the default telnet address and port – telnet.reversebeacon.net:7000 – for now, (but know my friend will want to change it to his favorite)
  • Set “Login:” to your own callsign
  • For now, I also set “Watch for:” to my own callsign
  • Colors being subjective, I chose White, Purple, Maroon and Red in that order from the top down, (I believe these may now be the default colors)
  • Set “Delete old information after” 180 seconds, (I’m getting older, the default 60 seconds was too fast)

Online log upload tab:

  • Set “Enable upload to HamQTH” (if you have an account there)
  • Set in your Username and Password for HamQTH
  • I elected to “Set this” Blue “color to show information in status upload windowI left Clublog blank – not a member
  • Set “Use this” Red “color to show information in status upload window” in case I use Clublog in future
  • Left HRDLog.net entries blank
  • Set “Use this” Purple “color to show information in status upload window” in case I use HRDLog in future

Propagation tab:

  • Set “Show propagation as image
  • I was not happy with the tiny default display, so changed “Download data from:” to http://www.hamqsl.com/solar101pic.php
  • Set “Show A, K, SSN, FOF2 etc.”
  • Set “Show calculated prediction for HF bands”
  • Set “Show calculated prediction for VHF bands” if you are interested

I spent over a week, frustrated with a situation where the TRX control window would lose communication with the rig after about 20 seconds – after which I would be forced to refresh the rigctld process. It would regain comms only to fail again.  In that week I tried varying each and every setting on both the rig’s initial setup menu and in the preferences – but kept having this feeling I was missing something obvious.  Finally determined some other (unknown) process was periodically interfering with comms on device ttyUSB0, so I simply did a completely fresh install of Linux Mint 17.3 Cinnamon, then ran through the procedures above. CQRLOG has been running quite well and controlling our IC-718 rig very happily ever since.

A ton of credit for what you find on this page goes to K8WDX – his work, although on a previous version of CQRLOG and a different radio, inspired me to pursue installing everything needed now and for future work with those “other” digital modes.  Many thanks to K8WDX for sharing his own experiences.

I will be counting on help from a good friend, an experienced Ham who has done many years of DX, then will revisit the Log specific stuff, including LoTW/QSL settings, etc.  Have a lot to learn about that arena myself.


REFERENCE LINKS:

CQRLOG

Ham Radio Control Libraries

USB Serial Converter support

Linux Ham apps, install | K8WDX

CQRLOG configure <–YouTube video on a previous version of CQRLOG also by K8WDX

Ham with Linux – TeamViewer

OK, so I am an admitted lazy old bum that spends entirely too much time setting on his comfortable couch with a notebook computer handy, an FT-60 handheld radio connected to a J-Pole antenna next to him, TV remote, radio, snacks, refreshments, etc. Ayup, the “life of Riley” around the old Pondee and life is good…

slothfulness, noun used to describe “slothful”, meaning “sluggardly; indolent; lazy”.

We have several computers, (including Heidi’s notebook [Linux], my Notebook [Linux & Windows 10], the old Toshiba laptop back in the shack [Linux]) – as we have had for many years, and naturally all are connected via our WiFi/LAN, along with a somewhat embarrassing number of tablets and other devices. <blush>  (Hey, I am an ancient computer/device geek who never quit that part).

Last year, I ran across a “remote control” software package, which is free for home use, called TeamViewer described as:

Remote support, remote access, and online meeting software that the world relies on – 1 billion installations and 20+ million devices online at any time.

Noting they had versions available for virtually every operating system, I decided to give it a workout between Windows to Linux, and Linux to Linux, etc. – and as a result, am still using it today.  (Haven’t tried it on iOS, Android, etc., yet – but that is probably going to happen sooner or later).

I’ve been fully retired for a very long time now, so I wasn’t interested in the corporate aspect/usage, nor even going out across the Internet to remote control a computer – BUT, being a lazy old dinosaur, thought I might be able to make use of it to save having to leave my couch to go back to the shack and check for updates, or fix something on Heidi’s computer (ALL the way over on our Love seat).

Darned if it didn’t work, and work very well!  The user interface is a bit cumbersome at first, but after running it for about a year it does everything they advertise, and since I’m only using it at home – it is still FREE!  They are up to version 11 as this is being written, and there have been updates in this past year, but we have simply never had a problem with it.

Two days ago, it was used to install/configure/test CQRLOG on that old computer in our ham shack from our couch – reflecting upon that inspired me to write this post.  TeamViewer just works for us!

Disclaimer:  Being fully retired for well over 10 years, I am no longer any kind of “computer professional” nor otherwise qualified to even talk about what is going on “today” with computers and software.  It takes far too much work to stay on top of technology, and more effort than this old retiree is going to be willing to spend.  TeamViewer works well for our purposes, your own mileage may vary.  I can, however, tell ya what works for me, and I happen to like TeamViewer. 🙂

Over my working years, operating remote desktop or server control software, (especially with cross-platform support), was a very important aspect of my business, especially from the early 90’s to about 2004. At one point or another, I’ve used many, many different “brands” – this product has to be near the top for ease of use. <two thumbs up>

Ham with Linux – CQRLOG

You might want to skip this one if you have no interest in Linux v/s Ham Radio.  It is no secret that yours truly is somewhat of a Linux enthusiast. “TUX” is the name given to the little penguin which became a symbol for Linux long ago, and you are currently reading this on InTUX 🙂 … These days, Heidi and I like Linux Mint, using Cinnamon for the user interface on our modern notebook computers, and I have Mate running on a 10+ year old Toshiba laptop in our shack. All are on version 17.3 as I type, but will soon be testing the upcoming version 18…

Earlier this week, one of our friends, also a member of ARCEC, asked me to take a look at a Ham package called CQRLOG – took a brief scan of what was said on eHam.net about it and I was off to the races.

“CQRLOG is an advanced ham radio logger based on MySQL database. Provides radio control based on hamlib libraries (currently support of 140+ radio types and models), DX cluster connection, online callbook, a grayliner, internal QSL manager database support and a most accurate country resolution algorithm based on country tables developed by OK1RR. CQRLOG is intended for daily general logging of HF, CW & SSB contacts and strongly focused on easy operation and maintenance.”

One of the lessons learned, back in the ’90s, was to expect poor documentation on just about any/all open-source projects.  Cutting my teeth on “Slackware” around version 3, that was quite a source of frustration back then.  However, that arena has definitely shown improvement by leaps and bounds as time has moved forward.  Unfortunately, documentation continues to lag development on most projects I’ve seen – its simply not as bad as it once was.

The first pass at attempted installation was using Linux Mint’s “Software Manager” to download and install the package that was on their (Mint’s) package server at that time.  Without going into details, that was not a good user experience, resulting in the package alarming – telling of missing dependencies with no effort on its part to install several those dependent packages, including MySQL Server and Client as an example.  In my opinion, that package should not have been available on their server.  Being a long-time command line user, I opened a terminal session and proceeded to clean everything back up.  It was then time to see if there was a PPA repository available for CQRLOG and I discovered there was.  There is a lot more to this story, but seeing your eyes glaze 😀 , (or is that my imagination?), in the end I discovered a good installation could be had with a single command in terminal mode:

sudo add-apt-repository ppa:ok2cqr/ppa;sudo apt-get update;sudo apt-get install cqrlog

That command, (described here for version 2.0.1-1), will first, add the ppa repository to your linux system’s list of authorized spots to check for updates, then update the system list itself, and finally install the latest version found in that repository.  As I type, that is version 2.0.1 which has been fixed and does a complete install of CQRLOG and all of the packages necessary to run it.  After a bit of a struggle, including cleaning up after those same previous abortive attempts at installation earlier described, CQRLOG has been running on the aforementioned friend’s Linux Mint Cinnamon 17.3 computer.  I have had it running now for well over 24 hours on that very old laptop in our shack, without a single glitch or problem.  Really looking forward to a deeper look at its capabilities, features, and nuances.

Not mentioned in the brief description of CQRLOG above is the capability to control your ham radio from the program via a CAT cable between the computer and radio. I will be attempting to explore that capability soon, (cable is on the way from another Ham operator’s eBay Store – BlueMax49ers – one whom I’ve had excellent results with in the past, solely as a customer/consumer).

More on that aspect later on….

Guess I really should add some form of disclaimer here – the above post describes my personal experience, from my own viewpoint, with installing CQRLOG on multiple Linux Mint computers this past week – YOUR mileage may vary. 🙂


Update:  I have CQRLOG running under Linux Mint 17.3 Cinnamon back in our Shack and controlling our HF radio like a big dog.  VERY happy with it.  Spent a week or 10 days trying to chase down a problem, totally unrelated to Linux/CQRLOG, that was interfering with CAT on my system. When I blew everything away and went with a fresh install – it just worked!

Our Tiny Tri-bander HT Is Back In Service…

Back in early 2004, we took a chance and purchased a used ICOM IC-T90A from a Ham Operator on eBay. When it arrived, I was elated to find it worked like a charm – once we figured out how to operate it. Back then, had to take a drive to Ham Radio Outlet and picked up a wallet sized “Nifty card” for it and was soon able to figure out how to program it from the tiny little touch pad. It served as my first Ham radio as a licensed operator, and worked about as well as a handheld radio could in those days.

ICOM IC-T90A, circa 2004, tri-band handheld radio. About the size of an old pack of cigarettes.

ICOM IC-T90A, circa 2004, tri-band handheld radio. About the size of an old pack of cigarettes.

Over the last six months, we’ve even located the old little case containing the accessories bought for it some 10-12 years ago, located a provider for new batteries on Amazon.com, and upgraded the little antenna to a Diamond SRH77CA for 2m and 70cm operation. (Don’t currently use 6m, but if I do, will revert to the old antenna with extension).

What I couldn’t seem to do, is figure out how to manually program the odd offset for the ARCEC 2m repeater – this despite reading a downloaded copy of the manual, and doing many a search on google.  I now know that you simply set it up for “Dup -“, (Duplex with negative offset), and manually set the offset to 0.945000 instead of the typical 0.600000). DOH!

Have never bothered with trying to program that old radio with a computer and cable before, but having acquired the CS-T90A software plus the appropriate FTDI USB Programming Cable Icom IC-T70A IC-T70E IC-T90 IC-T90A IC-T90E OPC-478 from eBay,  (that link is to another Ham operator’s eBay Store – BlueMax49ers – one whom I’ve had excellent results with in the past, solely as a customer/consumer), – sat down yesterday to give it a shot, and its now fully in service for our local area.

Between the calling frequencies, several other simplex frequencies, and over 50 local 2m and 70cm repeaters – you can see why hand-programming is a bit of a challenge in our area – far, far easier to do it via a full keyboard and mouse than poking at the keypad.  This has proven true of all our radios – be they ICOM, Yeasu, Baofeng, or whatever.  In all, we have purchased about 6 or 7 of those FTDI USB cables from that same seller, (who is also a Ham), and have never had a problem. (He ships right away too!)

Up to this point, have only had to use radio-specific software to program our old IC-V8000, (CS V-8000 software), and this old handheld.  For everything else I’ve used the free, open-source, CHIRP software from DanPlanet.com with great success.  That software covers a tremendous number of Ham radios and works sweet IF you have a proper programming cable.

Life is good!

Update: Upon further testing, discovered while listening to QSO’s on the ARCEC 2m repeater that the receiver was cutting out every 5 seconds for about 1 second.  Set it aside until I found time to look into the problem.  Sure enough, some time later remembered something about both the ICOM IC-V8000 and IC-T90A from that time frame, (circa 2004), about the Weather Alert setting being a problem.  Pressed and held the “Set” button to access the settings that are infrequently changed – worked down through the list and discovered somehow Wx Alt had been enabled.  Turned it off and problem went away. 🙂