← Main Page   |   ← Back

🛰️ Ham Satting

Support & Help Center
by A46UNX - Unixeer™

📧 Contact Support

Get in Touch

For technical support, bug reports, feature requests, or general inquiries:

Email: [email protected]
Website: https://unixeer.com
Callsign: A46UNX

We typically respond within 24-48 hours. For urgent issues, please include "URGENT" in your email subject line.

❓ Frequently Asked Questions

Q: What languages does Ham Satting support?

A: Ham Satting now ships in 10 languages: English, العربية (Arabic), Español, Français, Deutsch, 日本語, 中文, Português, Русский, and Italiano. Switch from Settings → Default Values → Language. Arabic flips RTL on most pages. The Map and AR Tracking pages stay left-to-right by design (so chart and AR-overlay positions stay consistent), and image exports always read "Generated by Ham Satting" in English so QSL cards and screenshots look the same worldwide. Technical ham-radio terms (callsign, AOS, LOS, SSTV, ADIF, NORAD, APRS, MHz…) stay English everywhere for ADIF/CSV/JSON export compatibility with LoTW, eQSL, ClubLog, and desktop loggers.

Q: Why is my app not showing satellite positions?

A: Make sure you have:

  • Granted location permissions to the app
  • An active internet connection
  • For satellites Predictions and Tracking: Added your N2YO API key in Settings

Q: How do I get an N2YO API key?

A: Visit https://www.n2yo.com/api/ and register for a free API key. All satellites Predictions and Tracking requires one.

Q: Can I use Ham Satting offline?

A: Ham Satting requires internet connection to fetch real-time satellite orbital data (TLE).

Q: How do I export / Import my QSO log?

A: Go to your QSO list, tap the export / Import button, and choose from many formats. You can then share via email or save to your device.

Q: Why aren't I receiving notifications for satellite passes?

A: Check that:

  • Notifications are enabled in Settings
  • Your device allows notifications from Ham Satting
  • You have satellites enabled in the satellite selection menu
  • Battery optimization is not blocking the app (Android)

Q: How accurate are the pass predictions?

A: Pass predictions use real-time TLE data and are accurate within minutes for most satellites. Low-orbit satellites like ISS may have slight variations due to atmospheric drag and orbital adjustments.

Q: What satellites does Ham Satting support?

A: Ham Satting tracks a curated list of active amateur radio + weather + music-broadcast satellites including ISS, SO-50, AO-91, AO-123, IO-86 (now also SSDV on 2m), RS-44, AO-73, PO-101, FO-29, JO-97, TO-108 (CAS-6), STARS (JR5YBO), Ten-Koh 2 (JS1YKI), SONATE-2 (now also APRS), NO-44 (PCSAT, APRS), GRBBeta (Slovak digipeater), Foresail-1p (Aalto Skylink digipeater), Horizon (RS59S), 239Alferov (RS61S), Luca (RS90S) — the latter three are Russian Geoscan-family SSDV birds — Meteor-M N2-3 / N2-4 (weather), and the April 2026 batch: HADES-SA (SpinnyONE, Spain), PARUS-T3 (Taiwan, APRS digi), HYPERVIEW-1G (Russia, Robot 36 SSTV), MAGNARO-II Piscis, ARICA-2, FSI-SAT2 (Japan, DTMF-triggered SSTV — unique), WASEDA-SAT-ZERO-II, OrigamiSat-2. A new Music Broadcast service tracks four non-amateur satellites that transmit short music tones on UHF 400–402 MHz as a unique RF identifier: BALKAN-1, Flamingo-1, OTP-2, and T.MicroSat-1 (which transmits Beethoven’s “Ode to Joy”). The list is curated and kept current — satellites that have re-entered the atmosphere (BOTAN, e-kagaku-1, NANOZOND-1, SilverSat, HADES-ICM / SO-125) are removed. Check the satellite selection menu in Settings for the complete live list.

Q: How do I change my grid locator?

A: Go to Settings → Default Grid Location and enter your Maidenhead grid square (e.g., LL93eo33). The app can also auto-detect your location if you grant location permissions.

Q: Is my data safe?

A: Yes! All your data (QSO logs, settings, credentials) is stored locally on your device. Ham Satting does not collect or transmit your personal data to any servers. See our Privacy Policy for details.

📺 SSTV Decoder FAQ NEW

Q: What is the SSTV Decoder?

A: The SSTV (Slow Scan Television) Decoder allows you to decode images from audio recordings of SSTV transmissions. These transmissions are commonly used by satellites like the ISS and amateur radio operators to send images over radio frequencies.

Q: What SSTV modes are supported?

A: Ham Satting supports multiple SSTV modes:

  • Robot: Robot 36, Robot 72
  • Scottie: Scottie 1, 2, 3, 4, DX
  • Martin: Martin 1, 2, 3
  • PD: PD 50, 90, 120, 160, 180, 240, 290

Q: How do I decode an SSTV image?

A: Follow these steps:

  • Record the SSTV audio transmission as a WAV file
  • Open the SSTV Decoder in Ham Satting
  • Tap "Browse File" and select your audio file
  • Select the correct SSTV mode (e.g., Robot 36, PD 180)
  • The image will decode automatically
  • Use Shift, Slant, and Start controls to fine-tune if needed

Q: My decoded SSTV image has color bands or looks misaligned. How do I fix it?

A: Use the adjustment controls:

  • Shift: Moves the image horizontally. Use if you see color bars on edges.
  • Slant: Corrects diagonal skewing. Use if the image appears tilted.
  • Start: Adjusts where decoding begins. Increase if colors are misaligned or you see noise at the start.
Also try selecting a different SSTV mode - the image may have been transmitted in a different format than expected.

Q: What audio format should I use for SSTV decoding?

A: WAV format at 44100 Hz sample rate is recommended for best results. The decoder also supports MP3, M4A, AAC, OGG, and FLAC formats.

Q: What SSTV mode does the ISS use?

A: The ISS commonly uses PD 120 or PD 180 modes for SSTV transmissions. During special events, they may use other modes - check ARISS announcements for specific event details.

Q: Can I save and share decoded SSTV images?

A: Yes! After decoding, use the download button to save to your photo gallery, or use the share button to share directly. Shared images include a "Generated by Ham Satting" watermark.

🎛️ CAT Control & Yaesu Mobile Rigs FAQ

Q: Does Ham Satting support CAT control on my Yaesu FTM-100 / FTM-200 / FTM-300 / FTM-400 / FTM-500?

A: No — the Yaesu FTM mobile family (FTM-100, 200, 300, 400, 500, and related) does NOT expose bidirectional CAT control. This is a hardware-level limitation of the radios, not a Ham Satting one. No amateur-radio app can control these rigs over CAT because the radios themselves don’t speak the protocol. For CAT-capable rigs (FT-817/818, FT-991A, FTDX series, IC-705, IC-9700, etc.) the app can display tuning info but does not transmit commands.

📡 APRS FAQ NEW

Q: What does the APRS feature do?

A: Once you enter an APRS callsign in Settings and tap the purple APRS FAB on the map, Ham Satting connects read-only to public APRS-IS and filters for your own beacons. Beacons that reach an iGate show as pulsing purple markers — proof-of-transmission testing. Ham Satting does not transmit; your radio does.

Q: Why is the APRS callsign separate from my default callsign?

A: So SSIDs like -13 (weather) or -9 (mobile) can be used for APRS without stamping them into your QSO logbook. Keep your QSO identity clean and your APRS identity flexible.

Q: What is “heard by” and do I need an aprs.fi API key?

A: The aprs.fi API key is optional and unlocks the “heard-by” sub-feature, showing which iGates and digipeaters received your APRS beacon with bearing lines and themed popups. Without the key APRS still works — you just won’t see heard-by details. Get a free key at aprs.fi/account.

Q: Is my location transmitted when I use APRS?

A: Ham Satting itself transmits nothing. Your radio beacons your callsign + GPS position over RF; once an iGate forwards that to APRS-IS it is public information by design. See our Privacy Policy Section 4.2.

Q: I enabled APRS but no packets appear on the map.

A: Your rig must beacon on an APRS frequency (typically 144.39 MHz in the Americas, 144.800 in Europe) and an iGate must be in RF range to forward your packet to APRS-IS. If your rig isn’t beaconing or no iGates are nearby, there’s nothing for the app to show. Search your callsign on aprs.fi to confirm recent activity.

Q: Why does changing the APRS callsign wipe the map?

A: By design — a different callsign is a different identity. The old TCP session is disposed, visible stations are cleared, and a fresh session opens with the new filter.

Q: What do the SSID filter chips at the bottom of the map do?

A: They narrow what kinds of APRS stations you see: All, -9 (mobile), -13 (weather), -11 (aircraft / balloon), or Other. The strip docks above the bottom navigation bar, and reflows above the station-details panel when you tap a station. Your selection persists across restarts.

Q: I tapped a station to track it and now my YOU marker is gone.

A: That's intentional. When the tracked station's screen position is within roughly 24 pixels of your live GPS location (occluding it), the YOU marker is hidden so the two pins don't overlap. Zoom out and YOU reappears the moment the markers are visually distinguishable. Tap the station again to deselect.

Q: Why does the station I'm following look smaller than the others?

A: The station you're tracking is rendered about 30% smaller for precision — its smaller pin gives a more accurate position fix and reduces occlusion of nearby markers you're comparing against. The thicker outline still distinguishes it from inactive stations.

🌦️ Weather Satellite FAQ NEW

Q: What is “purple mode” weather satellite tracking?

A: Purple mode tracks Russian Meteor-M weather satellites (N2-3 and N2-4) on 137.900 MHz LRPT. LRPT is a digital QPSK signal, not audio — it must be decoded by external SDR software (SatDump or MeteorDemod) from IQ feeds. The app’s audio-recording button in purple mode captures session audio for post-processing, not direct LRPT decoding.

Q: Which weather satellites are supported?

A: Meteor-M N2-3 (NORAD 57166) and Meteor-M N2-4 (NORAD 59051). Meteor-M N2-5 and N2-6 will be added once they launch and receive permanent NORAD IDs.

Q: Universal VHF Doppler — why do I need it for weather sats?

A: LRPT transmissions at 137.9 MHz have measurable Doppler shift during a pass. Ham Satting applies Doppler correction to the displayed frequency even for VHF sats (not just UHF) so you track the correct instantaneous frequency for your SDR.

📅 Scheduled Service Events FAQ

Q: What are Scheduled Service Events?

A: A frequency-override schedule for satellites that occasionally use a non-primary frequency for short windows. Covers four services: SSTV (alternate freqs for special transmissions), SSDV (occasional schedule shifts on Geoscan-style birds), Digital (ARISS school contacts moving APRS or voice to other channels), and Weather (Roscosmos rotates Meteor-M N2-3 / N2-4 between 137.900 and 137.100 MHz). Music broadcasts are excluded — their frequency is the unique identifier so they don’t drift.

Q: How do I schedule an event?

A: Settings → tap “Add Scheduled Event (SSTV / SSDV / Dig / WX)”. Pick the service type, satellite, date range, and override frequency. Tap the (i) icon next to the button for a quick refresher. Events are stored locally on your device — nothing uploaded. When today falls within an active event, the AR page auto-switches to the override frequency for that service and falls back to the default outside the window.

Q: Can I import events from elsewhere?

A: No — the events scheduler is intentionally closed-loop. Events are created in-app via the date picker only. This avoids malformed-import issues and keeps the feature simple. Expired events are removed automatically on app launch.

🟢 AMSAT Live Activity Indicator FAQ NEW

Q: What does the small colored dot on each prediction card mean?

A: It’s a real-world activity indicator sourced from the public AMSAT Live OSCAR Satellite Status page. The dot uses the AMSAT cell palette directly — blue = Active (Heard), purple = ISS Crew Voice, amber = Telemetry/Beacon only, orange = Conflicting reports (small “?” overlay glyph), magenta = No-signal reported, grey = no reports — so what you see in Ham Satting matches what you’d see on the AMSAT page. The dot reflects the best-of status across all of that satellite’s mode rows over the last 24 hours UTC. Hollow ring means AMSAT does not currently track that satellite. Solid grey means the data hasn’t been fetched yet (give it a few seconds on first launch).

Q: What happens when I tap the dot?

A: A themed popup opens showing the last 48 hours of activity from AMSAT in a tight grid: dates header on top (today + yesterday UTC), services stacked on the left (so for ISS you’ll see Crew, FM, SSTV, UHF Digi, VHF Digi as parallel rows). Each cell is a 2-hour UTC window; tap a cell to see the individual reports under it — reporter callsign, Maidenhead grid, status, and the precise 15-minute UTC slot. The cell-detail panel has its own × dismiss button. AMSAT-tracked modes with no recent reports are listed as a footer (“No reports in last 6 days: SSDV, VHF Digi”) so the absence of a row is never silent. There’s a small refresh button, an expandable Source / About section with the AMSAT attribution, and a compact share-image button. The share image includes whatever you have open — if a cell-detail panel is showing, it’s included; dismiss it first for a strip-only image.

Q: How often does the data refresh?

A: Once every 15 minutes while a prediction page or the notification list is open. The same in-memory snapshot is shared across all dots in the app — no extra fetches per card. You can also tap the refresh button inside the popup to force a fresh fetch. Errors are retried silently in the background; you don’t need to do anything.

Q: Why does my satellite show a hollow ring?

A: AMSAT’s status page only covers a subset of amateur satellites — primarily the active linear / FM / digital birds the AMSAT community reports on. Many of the satellites Ham Satting tracks (Meteor-M weather sats, the Tevel constellation, formation-flying CubeSats, etc.) aren’t reported on AMSAT’s page. The hollow ring tells you the indicator has nothing to say for that bird; you can still log QSOs, set notifications, and see passes normally.

Q: Does the app submit my own reports back to AMSAT?

A: No. Ham Satting only READS the AMSAT status page; it does not submit reports. If you’d like to contribute your own “Heard” / “Telemetry Only” / “Not Heard” reports, visit amsat.org/status/ in a browser and use AMSAT’s own submission form.

Q: What does the “?” overlay glyph mean? What about “!”?

A: “?” is a conflict marker — multiple operators submitted reports that disagreed with each other in the same window (e.g. one Heard + one Not Heard). “!” means the cached data is older than the 15-minute refresh window (probably because your network was offline); the indicator is still showing the last data we had, but it’s stale.

🐛 Report a Bug

Found a bug? Help us improve Ham Satting by reporting it! When reporting bugs, please include:

Email bug reports to: [email protected] with subject "Bug Report: Ham Satting"

Q: I saw a snackbar saying "Something went wrong. Tap to email diagnostics." What is that?

A: A new diagnostic capture mechanism (v4.2.0+42, May 2026). When the app catches an unexpected error during your session, it stores the last 50 events in an in-memory ring buffer and shows that one-shot snackbar. Tap EMAIL to open your mail app pre-filled with a plain-text report (callsign, app version, error trace) addressed to support. Nothing is sent automatically — you control whether the report goes anywhere. If the same underlying error fires repeatedly, the snackbar stays silent for 5 minutes after the first surface so you don't get spammed.

💡 Feature Requests

Have an idea for a new feature? We'd love to hear from you! Please email your suggestions to [email protected] with subject "Feature Request: Ham Satting"

📚 Documentation & Resources

📱 Platform Support

Ham Satting is available on multiple platforms:

🔄 Updates & Changelog

Still Need Help?

If you couldn't find an answer to your question, please don't hesitate to contact us:

📧 Email: [email protected]
🌐 Website: https://unixeer.com
📻 Callsign: A46UNX

73 de A46UNX - Happy satellite hunting! 🛰️