开云体育

Dave,

First, both the Windows Mobile and the Win32 clients expect an "always on" connection. They are first and foremost an APRS-IS (not RF) client and cannot get data without the Internet. With that said...

If you want to always receive a particular station's packets when you are connected and regardless of where it goes, you can add it as a buddy or a friend filter. The difference is whether you receive just that station, or the station and other stations within a specified radius of that station. The two filters would be added to the (blank delimited) Add Filter field of the configuration dialog.

As you can see below, the Budlist supports both wildcards and multiple calls in a single instance while the friend filter needs to specify the full call-ssid of the moving station along with a range in kilometers from that station's most recently beaconed position. You can even put a b/ filter for the call-* (all -ssids) along with an f/call-ssid/range filter for the particular -ssid you're most interested in. That way you receive any packets from the station before any position beacons have been received.

Finally, the client automatically adds an f/call-ssid/range filter using the configured range whenever you click on the station and select "Center" from the pop-up menu. The map will move to the center and will automatically move to the most recently received position of that station. This is very handy for just watching a truck go by on the local interstate, for instance, whereas configuring explicit b/ or f/ filters is good for when your son and daughter head out of state on a road trip!

The centered station is not remembered when the client is restarted, but the filter settings are, although you'd still have to find the station and re-initiate the Center action to get the map to track it after restarting.

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

From


#3 b/ Budlist filter

The budlist filter will pass traffic based on exact match of the sender's
call or call starts with a specific pattern (from V 1.4). Also the SSID is part
of the exact match.

Syntax: b/call1/p1*/call3/p2*...

Where: b = budlist command
call# = The prefix (starting) pattern
p# = The prefix (starting) pattern

Samples:

*b/SM5NRK * This will pass all traffic from SM5NRK
without any SSID
*b/SM5NRK-5/SK5UM * This will pass all traffic from SM5NRK-5
and from SK5UM
*b/K** This will pass all traffic from stations
starting with K
*b/SM5NRK/F* * This will pass all traffic from SM5NRK and
all stations starting with F



#11 f/ Friend Range filter

The friend filter works the same as My range filter, except you define which
call-ssid should be used (see more above). Up to 9 friend filters can be defined.
This is a moving filter so it follows the call-ssid last known position.


Note: This will not work until a valid position has been sent from the
call-ssid defined.

Syntax: f/call/dist

Where: f = friend range command
call = call to be used as center of the range
dist = distance in kilometers from lat/lon.

Samples:
*f/SM5NRK/500* This will pass all traffic within 500 km from
SM5NRK's last position.

David Shrum wrote: