Connection Problems
- Most servers require log-on to send you data.
- Most servers pass only verified and validated amateur connections. If you do not have your callsign validation code, contact your program developer or the SysOp to obtain it.
- If you use a filter like "m/distance" you have to send a position beacon in order to receive data from the server. If you do not want to send a position beacon, use the area or friend filter.
- If you don't have a validated connection with a server, you can't send a position report to the server and filters like "m/distance" will consequently not work.
- Do not use the same callsign-ssid for more than one application at a time, each use for data entering the APRS-IS must use a unique callsign-ssid.
- Any APRS-IS aware applications will connect trouble free to the servers. UI-View, WinAPRS, Xastir and AGWTracker are some of the most popular examples.
- 99% of connection problems are traced to a slow internet connection or one with high packet loss. Keep this in mind when picking the size of your filtered feed, if a stable connection is desired.
- The actual status of all Tier 2 servers is shown here.