APRS Coverage

APRS-IS feed

Feed servers

Register a station

Igates and digipeaters

APRS-IS server: the server named after qAC on the last beacon, status or telemetry packet the station sent over its own APRS-IS login. Your server's name comes from the duplicates feed's login reply. A station that only beacons over RF never shows one.

APRS-IS: copies on the main feed, where this igate was first to gate the packet. Dupes: copies on the duplicates feed, gated after another igate already had. An igate that never shows dupes while others do is probably connected to a different APRS-IS server than your aprsc.

Mobiles

Rejected packets (data quality)

Packets from registered mobiles that were dropped: not over RF, ambiguous or bad positions, impossible jumps, duplicates. Shows the newest 100.

New accounts

New devices from approved users

Rejected devices

Their owners see the reason, and can fix and resubmit them, or delete them.

Users

Deleting a user also deletes their pending and rejected devices. Their approved devices stay on the map, managed by the admins. New sign-ups are approved or rejected on the Approvals tab.

My devices

Once a device is approved, its callsign and type are fixed. To change them, add a new device and delete the old one. Deleting a device takes it off the map; the coverage it already recorded stays.

Add a device

Remote config

Commands are sent from this callsign, so use one you are licensed for. The passcode is calculated from it. Use an SSID that nothing else is logged in to APRS-IS with (not your igate's), or APRS-IS drops that station's connection while you send. Remembered in this browser only, never on the server.

Reads and changes settings on LoRa FieldOps igates and digis with APRS messages (CSR read, CSU unlock, CSW write), sent over a separate APRS-IS connection as that callsign; the coverage feed stays read-only. The connection closes after 5 minutes without a command. An igate gets them over its own APRS-IS connection. A digi gets them only if an igate with IS-to-RF downlink has heard it directly in the last 30 minutes. The node must have remote config turned on (serial remotecfg on), and writes need its unlock token. Each command can take up to 45 s, and only one runs at a time.

Activity

Newest 50 commands and replies. Unlock tokens are not logged.

Account

Change password

Withdraw sign-up

Deletes your account and the devices you submitted.