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.
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:
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.
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 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:
Swipe a QSO to delete it; tap it to edit.
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:
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.
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).
MODE use. When SatNOGS lists a different uplink mode for the transponder, it's filled in for you.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 opens a sheet with your totals, computed from the log:
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.
OrbitDeck signs a standard .tq8 entirely on your device, with no computer and no TQSL round-trip:
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.
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.
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.
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.
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.
… → 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.
Your log is written atomically, so a save can never leave a half-written file.
<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.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.
The Exports screen (Operating Tools) has a Station & outreach reports card, all shared through the share sheet so you can print them:
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.