Logging & Uploads

OrbitDeck keeps a satellite QSO log on your iPhone or iPad, tracks your VUCC, WAS and DXCC progress, and uploads the log to LoTW (signed right on the device) or your own Cloudlog/Wavelog server. ADIF import and export, PDF reports and voice memos round it out.

Overview & setup

Open the Log screen (Operating Tools), then … → Log settings and turn on Enable logging. That shows a Log QSO card on Home and fills the Log screen. Also in Log settings:

  • Station: My call and the Default RST (see RST by mode).
  • QRZ: fill in names and US states from QRZ (needs your QRZ XML username and password in Settings).
  • LoTW station location and LoTW certificate (see LoTW upload).
  • Cloudlog / Wavelog: instance URL, station profile ID and API key (see Cloudlog / Wavelog).

Every contact is stored on the device as JSON. Each QSO remembers which services it has been sent to, so a normal upload never sends it twice.

Quick-log on Home

The Home Log QSO card is prefilled from the selected satellite, the current transponder (uplink and downlink frequencies and mode) and your station grid. Type the other station's call, adjust the labeled RST sent / RST rcvd fields if needed, optionally add their grid, and tap Log QSO.

  • The reports default by mode: 59 for voice, 599 for CW and data. With CW chosen on Home's Live Doppler card for a linear transponder, the QSO logs as CW/599.
  • Tapping a callsign in the CW decoder's transcript puts it in the Call field with the mode set to CW; Use transponder mode undoes the override.
  • FT4 and packet log their own QSOs automatically when an exchange completes (see Digital Modes).

The Log screen

The Log screen lists your contacts, pass recordings and voice memos, and the FT4 activity log. Each QSO shows small L / C badges once it has been sent to LoTW / Cloudlog. The microphone button in the toolbar records a voice memo. The … menu has:

  • New QSO, Awards and Log report (PDF).
  • Export ADIF and Import ADIF.
  • Upload to LoTW (n) and Upload to Cloudlog (n), where n is the number not yet sent.
  • Re-send: re-send all to LoTW or Cloudlog, or select QSOs to re-send (see Re-sending).
  • Log settings.

Swipe a QSO to delete it; tap it to edit.

New QSO & the editor

New QSO opens the same editor used to change a logged contact, prefilled from the selected satellite and transponder like the Home card. The editor has:

  • Contact: call, name, labeled RST sent and RST rcvd, the worked station's grid(s), state, Time (UTC) (the date and time picker is in UTC, whatever your device's time zone), country and DXCC entity.
  • Satellite: satellite name, mode, optional separate uplink and downlink modes, and the downlink and uplink frequencies in Hz.
  • Station: your call and grid, and notes.
  • Uploads: Uploaded to LoTW, Uploaded to Cloudlog and Confirmed in LoTW toggles.

Mode menus offer the common satellite modes (SSB, USB, LSB, FM, CW, AM, FT4, FT8, PKT, SSTV, DATA); free text is allowed too. The State field has a menu of US states.

What's logged

Each QSO holds the worked call, satellite, mode, uplink and downlink frequencies, RST sent and received, the worked station's grid (several grids for a rover or a grid-line/corner contact, for VUCC), name, US state (or other primary subdivision), DXCC entity and country, your call and grid, the UTC time and notes. Satellite names are normalized to the correct LoTW SAT_NAME automatically (e.g. an in-app name like FOX-1B (AO-91) logs as AO-91).

  • RST by mode. The Default RST in Log settings is used as given for voice (59); CW and data modes add the tone digit (599). FT4 and FT8 log a dB report instead, so their RST starts empty.
  • Separate uplink and downlink modes. For a cross-mode contact (e.g. FM up, SSB down) set the uplink or downlink mode; leave them blank when they match. Mode stays the primary: it's what LoTW and ADIF MODE use. When SatNOGS lists a different uplink mode for the transponder, it's filled in for you.

DXCC, QRZ name & state

  • DXCC entity and country are resolved from the callsign for every QSO (from the Home card, the editor, FT4 and packet auto-logging, and ADIF import). QSOs logged before this existed are filled in once, automatically. You can correct either field in the editor.
  • QRZ name and state fill. With QRZ credentials set and Fill in names and states from QRZ on, OrbitDeck looks up the operator's first name (or QRZ nickname) in the background when a QSO is logged without one, and a US station's state (for WAS). It only fills empty fields, never overwrites what you typed, makes at most one lookup per second, and backs off after a login or network error. Logging never waits for it. ADIF imports are not looked up, so a big file can't flood QRZ.
  • From Awards, Fill n missing US state(s) from QRZ queues every US contact that has no state yet; they fill in at one lookup per second.
A QRZ fill counts as an edit: if it adds a name or state to a QSO already sent to Cloudlog, that QSO's Cloudlog mark is cleared so the completed record is sent again.

Voice memos

Tap Voice memo (on Home's Pass recording card, or the microphone button on the Log screen) and speak a note, for example the calls you worked while your hands were busy. A memo can run up to 2 minutes. When you stop, the clip is saved with your recordings and a QSO stub is added to the log with the UTC time, satellite, mode and frequencies, but no callsign.

Stubs are marked Tap to add the callsign and complete this contact. Open one to play the memo and fill in the call and anything else you noted, then save. Stubs without a callsign are left out of uploads, award totals, ADIF exports and PDF reports until you complete them.

Memos use the built-in microphone or a headset, or, with a USB audio interface connected, that interface's input.

Awards

… → Awards opens a sheet with your totals, computed from the log:

  • QSOs and satellites worked.
  • VUCC grids: every 4-character grid in each QSO's grid field (all grids of a rover or grid-line contact).
  • WAS: US states out of 51 (50 states + DC), from each QSO's State field (typed, imported from ADIF or filled from QRZ). States are never guessed from a grid, since a grid can straddle a state line. The count of US QSOs still missing a state is shown.
  • DXCC entities, from the entity resolved from each call.

Each total shows worked and, once your log carries LoTW QSL status, confirmed counts. Lists of grids, states and DXCC entities show each item as worked or confirmed; the state list is a full 51-item checklist with the ones you still need dimmed. By satellite drills down to one satellite's totals, lists and QSOs.

Export CSV gives a totals block, one row per worked grid, state and entity (with the satellites it was worked on) and the per-satellite tally. Export PDF / Print makes a printable summary.

The awards view is a working estimate for your own tracking, not an official award check. Confirmations come only from a LoTW download you import (see below).

LoTW upload (signed on device)

OrbitDeck signs a standard .tq8 entirely on your device, with no computer and no TQSL round-trip:

  1. In TQSL on a computer, export your callsign certificate to a .p12 file (with a passphrase).
  2. In OrbitDeck, Log settings → Import .p12 certificate, then enter the passphrase and tap Import. The certificate file stays on your device; the passphrase is stored in the iOS Keychain. Remove certificate deletes both.
  3. Set your LoTW station location:
    • Callsign (cert), filled from the certificate.
    • DXCC entity: a searchable list, with the entities that have subdivisions first.
    • The entity's primary subdivision and, where LoTW has one, the secondary subdivision, exactly as LoTW lists them: US state and county, Canadian province, Japanese prefecture and city/gun/ku, Russian oblast, and the others LoTW supports. US, Alaska and Hawaii stations must set a state (Alaska and Hawaii fill it in for you).
    • Grid, CQ zone, ITU zone, and an optional IOTA reference (e.g. NA-005).
    These are signed into every upload, so set them before uploading.
  4. Choose Upload to LoTW. OrbitDeck signs each QSO not yet sent (RSA over SHA-1, as LoTW requires), gzips the batch and posts it to LoTW in one upload. QSOs are marked as sent only when LoTW accepts the file.
The signature format (field order, normalization and dates) follows TQSL's LoTW V2.0 specification exactly; anything else makes LoTW silently drop the QSO. Getting a certificate in the first place still requires ARRL's one-time enrollment through TQSL, which can't happen on device.

Importing LoTW confirmations

Download your QSLs from LoTW as an ADIF file and import it with Import ADIF. A record that matches a QSO already in your log (same base call, same satellite, same mode group (phone, CW or data), within ±2 minutes) is merged, not added again: the QSO is marked confirmed (LOTW_QSL_RCVD Y or V) and any empty state, grid, name or DXCC fields are filled from the download. What you logged is never overwritten, and upload marks are kept. Unmatched records are added as new QSOs.

After the import, the awards view shows confirmed totals alongside worked ones.

Cloudlog / Wavelog

In Log settings → Cloudlog / Wavelog, enter your instance URL (e.g. https://log.example.org/index.php), the station profile ID and a read-write API key. The key is kept in the iOS Keychain. Then choose Upload to Cloudlog: OrbitDeck posts the QSOs not yet sent as ADIF in one request.

The https rule

Cloudlog's API carries the key in the request body, so the address must start with https://. The one exception is a server on your local network (a private or link-local IP address, localhost, an unqualified name such as shack, or a .local name), where plain http:// is allowed because many shack servers have no certificate. Log settings then warns: Unencrypted: your API key is sent in plain text on this network. Plain http to an internet host (including a public IP address) is blocked with an explanation.

Checking the result

Cloudlog and Wavelog answer "created" even when they reject individual records (duplicates, invalid fields), so OrbitDeck reads the whole reply. QSOs are marked as uploaded only when the server reports that every QSO in the batch was imported with no errors. Otherwise nothing is marked, and you see how many were accepted along with the server's own messages. Records the server already has may show as duplicates when you try again.

A self-hosted Cloudlog can also be set up to forward to LoTW on the server, as an alternative to signing on the device.

Re-sending

  • Edits re-send automatically. Changing the call, time, satellite, mode or frequencies clears both upload marks (those are what LoTW signs). Changing any other exported field (reports, grids, name, state, country, DXCC, notes, per-leg modes, or your own call or grid) clears only the Cloudlog mark. The corrected QSO goes out with the next upload.
  • Edits during an upload. If a QSO is edited (or filled from QRZ) while an upload is in progress, it isn't marked as sent; the status message says so and the new version goes next time.
  • Per-QSO marks. In the editor, turn Uploaded to LoTW or Uploaded to Cloudlog off to re-send just that QSO, or on to stop it being sent.
  • Re-send all sends the whole log again, including QSOs already marked as sent (after a confirmation). LoTW ignores exact duplicates.
  • Select QSOs to re-send… lets you pick contacts, then Re-send to LoTW or Re-send to Cloudlog. The selection can also be turned into a PDF.

ADIF import/export

Export ADIF shares your whole log (completed QSOs) to any app. Exports use the satellite ADIF conventions: PROP_MODE=SAT, SAT_NAME, uplink→FREQ/BAND, downlink→FREQ_RX/BAND_RX, GRIDSQUARE plus VUCC_GRIDS for several grids, and NAME, STATE, DXCC, COUNTRY and LOTW_QSL_RCVD where known. FT4 is written as MODE=MFSK with SUBMODE=FT4. Field lengths are counted in bytes, so names with accents and other non-ASCII characters export correctly. Separate uplink and downlink modes travel in OrbitDeck's own application fields.

Import ADIF reads an .adi file and merges it as described under LoTW confirmations: matching QSOs are updated, the rest are added. The importer is hardened against malformed files: impossible field lengths, a file truncated mid-value, and out-of-range or non-numeric frequencies are handled without losing the records that are readable.

PDF log report

… → Log report (PDF) makes a landscape, paginated table of your QSOs: UTC, call, satellite, mode (uplink/downlink for cross-mode), uplink and downlink MHz, reports, grid, state, country, name and flags (L = sent to LoTW, C = sent to Cloudlog, Q = LoTW confirmed). Limit it to a date range (UTC) or one satellite, or make it from QSOs you selected. It opens in the share sheet: choose Print for AirPrint, or save or send the PDF. Voice-memo stubs without a callsign are left out.

Log file safety

Your log is written atomically, so a save can never leave a half-written file.

  • An unreadable log is never overwritten. If the QSO log (or the recordings list, SSTV image list or FT4 activity log) can't be read at launch, OrbitDeck moves it aside to <name>.corrupt-<UTC timestamp>.json in its Application Support folder and starts a new, empty file. A banner on the Log screen explains what happened and has a Share the preserved file button so you can send it to yourself or to the developer for recovery. If the file can't even be moved aside, OrbitDeck refuses to save over it for that session and tells you to restart the app.
  • Save errors are shown. If a save fails (for example, the device is full), a banner on the Log screen says so. Your latest changes are kept in memory and saved with the next successful write; the banner clears itself then.

Recordings & FT4 activity

With an audio interface connected (see Digital Modes), the Home Pass recording card records the received audio to a compressed AAC .m4a tagged with the satellite and time. Recordings and voice memos appear on the Log screen with playback and share. The FT4 traffic log keeps every FT4 decode and transmission for later review and can be shared as text.

Station reports

The Exports screen (Operating Tools) has a Station & outreach reports card, all shared through the share sheet so you can print them:

  • Favorites' keps: your favorite satellites' element sets as TLE text or a PDF.
  • Station readiness (PDF): the readiness checklist as a report.
  • Support AMSAT sheet (PDF): a one-page handout.
  • Contact card: your callsign, the name you type next to the button, your grid and a QR code to your QRZ page (set your callsign in Settings → Operator identity first).

Permissions & privacy

The log, recordings and your LoTW certificate stay on your device. QSOs are sent to LoTW (ARRL) or your Cloudlog/Wavelog server only when you upload. The LoTW certificate passphrase, the Cloudlog API key and your QRZ password are stored in the iOS Keychain. QRZ lookups send the worked station's callsign to QRZ. Voice memos need microphone permission. See the privacy policy.