Hardware Interfaces

Your callsign, Hardware Interfaces. This is the CAT list: radios Cloudlog has heard from. Cloudlog does not open a COM port or a USB socket. A program on the shack PC reads the rig and tells Cloudlog the name, the frequency, and the mode. Cloudlog Aurora is the usual program. Others are listed under other programs. Each one needs a read and write API key.

Until something has reported in, the table says no CAT interfaced radios were found.

Picture needed: radios.png Hardware Interfaces with one radio. Frequency, mode, and the time of the last report visible.

What a row means

• Radio. The name the program sent. That is the name you will see in the dropdown on the logging screen.
• Frequency. One number is the frequency the rig is on. Two numbers, written as receive / transmit, mean split, or a satellite with a downlink and an uplink.
• Mode. What the rig reported. FM narrow is shown as FM. A row that has not sent a mode shows N/A.
• Timestamp. When that report arrived. A radio that has gone quiet stays in the list. The time tells you it is stale.
• Delete. Removes that radio from the list. The program will add it again the next time it reports.

Choose the radio on General Logging, on Contest Logging, or on the DX Cluster page. The frequency box then follows the reports. The bandmap uses that same choice for Auto Track and for a click that should tune the rig.

Asking the rig to move

A click on a spot does not talk to the radio from the browser. Cloudlog stores a request: go to this frequency, and for a skimmer spot, go to CW. Aurora, or whichever program is polling for those requests, picks it up and sends it to the rig. The request expires if nothing collects it.

Radio Commands, the button at the top of Hardware Interfaces, is that queue. You can see what is waiting, and you can send a request yourself. If a click on the bandmap does nothing, look here. An empty queue and a radio that never updates means the program on the shack PC is not connected.