Help & contact
The most common questions when setting up and operating; text in quotes is a button or message of the app.
- What you need
- Set up rig
- Settings on the rig
- Other rigs
- TX level and power
- Your first QSO
- FT4
- WSPR beacon
- Logbook, upload and export
- Map
- Two-factor authentication
- Passkeys
- Download your data, delete your account
- Chrome permissions
- The rig does not answer
- Good level but no decodes
- The clock is wrong
- The server cannot be reached
- Glossary
- More about CloudHamSuite
- Feedback and contact
What you need
To operate you need a desktop browser, a rig with USB and its driver.
- Browser. There is exactly one control path: Chrome or Edge on the desktop talks to the rig over Web Serial. Firefox, Safari and every browser on a phone or tablet do not control a rig; there you can view the logbook and the map.
- Driver. No CloudHamSuite software is set up on the computer. The operating system only needs the USB driver for the serial port of the rig, as for any other program (for the IC-7300 and IC-9700 the Silicon Labs driver for CP210x).
- Rig. Control and transmitting work only over USB. The rig needs a USB connection with a serial CAT port. Audio works best from the built-in USB audio codec.
- Demo. No rig at hand yet? As long as none is set up, the station shows “Try the demo”: the real interface with sample data and invented stations. Nothing is transmitted and nothing is saved to the logbook; “Leave the demo” leads back.
Set up rig
“Detect rig automatically” fills in the steps for a connected rig by itself; by hand, “Set up rig” leads you through these six steps.
- Callsign and locator. The app derives the licence class from a German callsign. With any other callsign you choose “Full licence” or “Entry level” under “Your licence” and tick the box to confirm that you hold the licence; the locator sets the ITU region. Without a callsign or without that declaration the station only receives.
- Rig. A tile for the IC-7300 or IC-9700 fills in model, Hamlib ID, baud rate and CI-V address from the preset. For every other rig there is the “Other Hamlib rig …” tile (see Other rigs).
- Connect. “Find rig …” opens the port chooser of Chrome. If your rig has another USB chip, click “Show all devices”. After the choice the app tests the connection by itself.
- Audio. Here you choose the audio devices of the rig under “Input” and “Output”. If there are two USB Audio CODEC devices, the one that belongs to this rig is the one whose meter moves with the noise.
- Transmit. You can choose “CAT (recommended)” or “None (receive only)”. “Test transmit (PTT)”: the app keys briefly and checks that the rig then reads back as off.
- Done. “Save and start station” saves the profile and starts the station.
Settings on the rig
On the rig itself three things matter (menu paths of the IC-7300; on the IC-9700 and other Icom rigs the menu items have similar names).
- No other program on the port. Only one program at a time can open the serial port. If WSJT-X, flrig, a logging program or a second browser tab with CAT is running, the app stays silent.
- CI-V over USB. The CI-V baud rate for USB is under Menu › Set › Connectors › CI-V › CI-V USB Baud Rate. The connection test finds the set baud rate by itself.
- USB audio on AF. FT8 needs the demodulated AF signal. The app reads the setting on every connect and switches it to AF by itself. If that fails: Menu › Set › Connectors › USB AF/IF Output › Output Select = AF.
Other rigs
Only the IC-7300 and IC-9700 are proven on the air; every other rig, including every other Icom rig, is only assumed.
- Choice. In the “Rig” step choose the “Other Hamlib rig …” tile, then the model from the list.
- Transmitting. An unverified rig transmits only with PTT via CAT, not with DTR or RTS, and only after you allow it for exactly this model: the tick box in the “Transmit” step. With it you confirm that CloudHamSuite has not yet verified the model on a real rig and that you stay at the rig for the first transmission to switch it to receive by hand if needed. Test into a dummy load first.
- Transmit power. If CloudHamSuite cannot set the transmit power of the model, the tick box says so: then you set the power on the rig yourself.
TX level and power
Set power and level before your first QSO, into an antenna or a dummy load.
- Under “Transmit settings”, set the power of the rig with “TX power (W)”.
- Start the station. In “My QSO” the “TX audio level” sits next to “Tune”: it says how loud the browser sends the transmit signal to the rig; −12 dBFS is the maximum.
- Click “Auto-level”. Tune transmits a carrier and adjusts the level until the ALC just moves; the result is saved in the rig profile. If the level is too high, the rig turns it down with its ALC, and the signal gets distorted and wider.
- If the app reports “Level at maximum, ALC stays off”, raise the USB MOD level on the rig (IC-7300: Menu › Set › Connectors › USB MOD Level); on “Level at minimum and ALC still too high”, lower it. Then click “Auto-level” again.
- If the rig reports no ALC, set the level by hand: “Tune” transmits a carrier for at most 10 s; meanwhile set the TX audio level so that the ALC just moves.
- While transmitting, watch the meters next to “Tune”: ALC, SWR and transmit power as the rig reports them. “ALC at its limit” means: lower the TX level. “SWR high” means: check the antenna and its matching.
Your first QSO
A QSO takes six steps, and “Stop TX” or the Esc key ends any transmission at once.
- Set the TX level once (see TX level and power).
- On the station, “Start station”. Listen first: the first line appears after the end of the first full period.
- Click a line in “Band activity”. That only prepares the station; nothing is transmitted. In “My QSO”, “On my RX frequency” then shows what goes on at that frequency and whether the station is working someone else right now.
- In “My QSO”, click “Reply”. Before the first transmission of a session the station shows the rig's frequency, transmit power and callsign; it transmits only after “Understood, transmit”. Alternatively “Call CQ” calls by itself.
- The station transmits in its own period, repeats each message (under “Transmit settings”, “Tries per message”, default 3) and moves on by itself as soon as the other station answers. A run transmits at most 12 times and at most 10 minutes.
- When the exchange is over, the “Log card” opens; “Save” writes the contact into the logbook.
FT4
“Mode” switches between FT8, FT4 and WSPR; it is locked during a transmission.
- Period. FT4 has 7.5 s periods instead of 15 s.
- Transmit frequency. The default transmit frequency is 1400 Hz instead of 850 Hz.
- Switching. Switching ends any running exchange and tunes the rig to the FT4 frequency in the same band.
- QSO. The first QSO works as in FT8; a call to you is fresh for only 30 s in FT4 (60 s in FT8).
WSPR beacon
In WSPR mode only the beacon transmits (besides “Tune”); there is no “Reply” or “Call CQ”.
- Callsign and locator. Both come from the rig profile.
- Reported power. Here you set the reported value; it must match the power set on the rig, the beacon does not set it.
- TX share. It sets how many of the 2-minute slots transmit (default 20 %).
- Operation. “Transmit beacon” switches the beacon on, “Stop beacon” or Esc ends it at once, “Transmit next slot” transmits exactly one slot.
- Bands and duration. The beacon transmits on the WSPR bands your licence allows and ends by itself after 2 hours without any operation.
- Reception. Your WSPR receptions are reported to WSPRnet automatically.
Logbook, upload and export
A contact is stored only with “Save”, and saving uploads nothing.
- eQSL and QRZ. Under Settings › Log services, use “Add service account” for your credentials and tick “Upload QSOs here” there. After that, one click on “Upload to …” in the logbook (the button names the services set up, for example “Upload to eQSL”) uploads all new contacts and shows the result per service right there. If something is still missing, it reads “Set up upload” and leads straight to the missing step. For a single service account there is “Send” under Settings › Log services; it first asks how many contacts go to the service. Each contact goes at most once to the same service. Whether the service accepted it shows in the logbook's “Status” column.
- LoTW. “Upload to LoTW” in the logbook signs the contacts with your LoTW certificate here in the browser and uploads them. You load the .p12 file from TQSL once; it stays in this browser. With a LoTW service account, “LoTW confirmations” fetches what LoTW has confirmed.
- Backup. Besides the ADIF export there are “Export as CSV” and “Logbook backup” (all data as one JSON file). “Import ADIF” reads an ADIF file. Export your logbook regularly.
Map
With “Who hears me?” the map shows who hears your callsign, with “Who do I hear?” whom you hear.
- Sources. The reports come from PSKReporter, RBN, POTA and SOTA; new ones appear without reloading.
- Callsign. If no callsign is entered in the account or the rig profile, the map asks you for one.
- Filters. Filters for band, time span, source and mode are under “More filters”.
- Range. Reports of the last 48 hours are shown, up to 300 per page.
Two-factor authentication
Under Settings › Account, the optional “Two-factor authentication” protects your account further: after the password, sign-in asks for a six-digit code from an authenticator app.
- Turning it on. Click “Turn on”, enter your password (“Next”), scan the QR code and confirm the first code with “Confirm”.
- Recovery codes. The codes shown appear only this one time: write them down and keep them apart from your phone.
- Phone gone. Then “Use a recovery code instead” helps at sign-in; each code works once.
Passkeys
With a passkey you sign in without a password – with Windows Hello, your fingerprint, your face or your phone.
- Creating. Under Settings › Account, “Add passkey” creates one: enter your password, give it a name such as “Laptop” if you like, click “Create passkey” and confirm in the browser’s dialog.
- Signing in. After that, “Sign in with a passkey” on the sign-in page is all it takes; many browsers also suggest the passkey right in the email field.
- Administration. For operators, a sign-in with a passkey counts as the second factor: “Administration” opens without a code from the authenticator app. If you signed in with your password, tap “Confirm with passkey” there once.
- Removing. “Remove” in the list deletes a passkey again.
- Key. The secret key stays on your device; CloudHamSuite stores only the public part.
Download your data, delete your account
You find both under Settings › Account.
- Download data. “Download data” (section “Download my data”) saves a JSON file with everything stored for your account, including the whole logbook. Passwords and the credentials of your service accounts are not in it.
- Delete account. “Delete account” removes the account for good, with logbook, rig profiles and service profiles. It asks for your password, and only “Delete” really deletes. Export your logbook as ADIF first.
Chrome permissions
Chrome needs your permission for the rig's port and for the microphone.
- The port does not appear. Chrome's chooser first shows only ports that fit the chosen model. Check the cable and the rig, then “Show all devices”. If the port does not appear there either, install the driver for the USB chip.
- Linux: the chooser stays empty. Ubuntu installs Chromium as a snap, and a snap sees no USB ports – even when WSJT-X works on the same PC. Run
sudo snap connect chromium:raw-usbin a terminal and close and restart Chromium completely, or install Google Chrome as a .deb package from google.com/chrome. Still no access: join thedialoutgroup withsudo usermod -aG dialout $USER, then log out and back in. Close WSJT-X and other programs using the port first. Firefox cannot use serial ports. - “Chrome did not grant access to the port.” Chrome no longer knows the permission for this port, for example after the site data was cleared or in a different Chrome profile. Grant it again in setup.
- Microphone. Chrome treats every audio input as a microphone. In the lock icon left of the address, allow “Microphone”, then “Start station”. Without this permission Chrome also shows no device names.
- Tidy up permissions. Remove the port grants you do not need in Chrome's site settings (lock icon in the address bar or
chrome://settings/content/serialPorts).
The rig does not answer
Almost always another process holds the port: a second tab with CloudHamSuite, WSJT-X, JTDX, a program from the manufacturer or a process that hung while closing.
- Close all other tabs with CloudHamSuite and all other radio programs. If a process hangs, end it in the Task Manager.
- Switch the rig off and on again.
- “Test connection” or “Start station”.
- Only if that does not help, check the CI-V USB baud rate on the rig.
Good level but no decodes
If audio arrives at a good level but no line appears, it is usually one of these.
- First period. The first line appears at the earliest after the end of the first full period; up to 30 s (FT8) is normal.
- USB audio on IF. If the rig's USB audio output is set to IF instead of AF, audio arrives, but no decodable signal. “Start station” switches it to AF by itself. If “Details ▾” still shows “IF” for “USB audio AF/IF”, use “Set USB audio to AF”.
- Quiet band. 2 m and 70 cm are often empty by day. Check on pskreporter.info whether anyone is transmitting on this frequency right now.
- Clock. The computer's clock is wrong (see The clock is wrong).
The clock is wrong
FT8 tolerates only a small offset, so synchronise the computer's system time.
- Windows 11. Settings › Time & language › Date & time › Sync now.
- macOS. System Settings › General › Date & Time › set automatically.
- Linux. Turn on time synchronisation (NTP), for example with
timedatectl set-ntp true.
The server cannot be reached
During an update the service is briefly unreachable; your data is safe on the server.
- “The server can't be reached right now.” Wait a moment, the notice goes away by itself. Repeat an action that failed because of it. Reloading is not needed and would end a running station.
- “Rig control (Hamlib) could not be loaded.” Usually the page was loaded during an update, or the connection broke off while loading. Reload the page.
Glossary
The technical terms used in the app and on this page.
- CAT. Control of the rig over the serial port: frequency, mode, power and the transmit key.
- PTT. The transmit key (push to talk). CloudHamSuite switches it via CAT.
- DTR and RTS. Two control lines of the serial port. Some rigs are keyed through them instead of via CAT.
- Hamlib. A free library that knows the CAT commands of very many rig models. CloudHamSuite uses it in the browser; the Hamlib ID names the model.
- CI-V address. On Icom rigs, the address under which the rig accepts CAT commands (factory setting IC-7300: 0x94, IC-9700: 0xA2). It must be the same in the profile and in the rig's menu.
- Baud rate. The speed of the serial port. The app and the rig must use the same one.
- dBFS. A level relative to full scale (0 dBFS); the lower the number, the quieter.
- ALC. The rig's automatic level control. If it moves a lot while transmitting, the TX level is too high (see TX level and power).
- AF and IF. AF is the audible, demodulated audio signal, IF the signal before demodulation. FT8, FT4 and WSPR need AF.
- Locator. The Maidenhead locator describes your location with letters and digits, for example JO31 or JO31LK. You find yours with an online locator calculator from your address or coordinates.
- Tune. An unmodulated carrier for adjusting level and antenna, at most 10 s.
- Period. The fixed time slice for transmitting or receiving: 15 s in FT8, 7.5 s in FT4, 2 minutes in WSPR (called “slot” there). Even and odd periods alternate, and the two stations of a QSO take turns. That is why the computer's clock must be accurate.
More about CloudHamSuite
These pages explain CloudHamSuite to people who do not know it yet.
- FT8 in the browser shows what you need and what the station can do.
- WSJT-X alternative without installing anything compares the two programs.
- WSPR in the browser describes receiving and the beacon.
- SSTV in the browser lists the picture modes and their limits.
- JS8 in the browser says what works and what has not been checked yet.
- Study for the German amateur radio exam introduces Funklehrer.
Feedback and contact
Send a bug, something unclear or an idea to kontakt@cloudhamsuite.de; every report helps, even a single sentence.
- Time. For a bug, add when it happened (time with time zone) and what you clicked last.
- Setup. Name your browser and operating system.
- On the air. Name the rig, band and mode, for missing decodes also the level.
- Message. Add the exact wording of the message or a screenshot.
- Never send. Your password or a code from your two-factor app.
- Provider. Provider and address are in the legal notice.