SymbolsAndSSIDs - Revision history

UR3IRS: /* SSID's (Secondary Station Identifiers) */

2010-05-29T06:43:16Z

‎SSID's (Secondary Station Identifiers)

UR3IRS: /* SSID's (Secondary Station Identifiers) */

2009-02-01T07:43:21Z

‎SSID's (Secondary Station Identifiers)

UR3IRS: /* SSID's (Secondary Station Identifiers) */

2008-12-14T14:14:44Z

‎SSID's (Secondary Station Identifiers)

W6DTW: Multiple edits, added SSID defs

2008-08-21T06:06:56Z

Multiple edits, added SSID defs

We7u at 16:21, 24 October 2007

2007-10-24T16:21:39Z

We7u: SymbolsSSIDs moved to SymbolsAndSSIDs: Easier-to-read title.

2007-10-24T16:11:25Z

SymbolsSSIDs moved to SymbolsAndSSIDs: Easier-to-read title.

We7u at 16:08, 24 October 2007

2007-10-24T16:08:48Z

LanceKJ5O: Corrected punctuation

2007-10-24T16:05:20Z

Corrected punctuation

We7u at 16:04, 24 October 2007

2007-10-24T16:04:31Z

We7u at 15:48, 24 October 2007

2007-10-24T15:48:53Z

@@ Line 14: / Line 14: @@
 It is important to select a different SSID for each on-the-air station.  A common "newbie" mistake is to use CALLSIGN-0 for the home station -and- for the mobile station.  If they then drive a slow circle around their house, where the house station is beaconing at the same time, it makes a pretty flower pattern on everyone's map.  The symbol keeps darting from the car's location to the house location leaving a track line on the map each time.  The fix for this is to set a different SSID for each station so that software can track each one separately.
-Originally the protocol was to use CALLSIGN-0 for the house, -1 for the first vehicle, -2 for the next, and so on.  The more modern protocol (as defined by Bob Bruninga, WB4APR) assigns a meaning to each SSID; however [[RegionalPages|local custom]] can vary quite a bit on this.
+Originally the protocol was to use CALLSIGN-0 for the house, -1 for the first vehicle, -2 for the next, and so on.  The more modern protocol (as defined by [[Bob Bruninga]] ([[WB4APR]])) assigns a meaning to each SSID; however [[RegionalPages|local custom]] can vary quite a bit on this.
 It has also been noted that Bruninga's modern protocol does not address the numbering of multiple mobile stations.  However when one considers that FCC Part 97 rules do not allow operation without a licensed radio amateur at the control point, then the argument that a licensed amateur would need mutiple SSIDs for more than one vehicle is a bit specious.

@@ Line 22: / Line 22: @@
 :: -0 Home station, or a home station running [[IGate|IGate]].
 :: -1 Digipeater, home station running a relay [[Digipeater|Digipeater]] and/or WX Digipeater
-:: -2 Digipeater on 70CM
+:: -2 Digipeater on 70 cm
 :: -3 Digipeater
 :: -4 HF to VHF gateway
 :: -5 IGate (not home station)
 :: -6 Operations via satellite
-:: -7 Handheld radios ([[Kenwood TH-D7]], Yaesu VX-8R, ICOM D-Star, etc)
+:: -7 Handheld radios ([[Kenwood TH-D7]], [[Yaesu VX-8R]], ICOM D-Star, etc)
 :: -8 Boats, sailboats and ships (maybe 802.11 in the future)
 :: -9 Mobiles

@@ Line 27: / Line 27: @@
 :: -5 IGate (not home station)
 :: -6 Operations via satellite
-:: -7 Handheld radios (Kenwood D7, Yaesu VX-8R, ICOM D-Star, etc)
+:: -7 Handheld radios ([[Kenwood TH-D7]], Yaesu VX-8R, ICOM D-Star, etc)
 :: -8 Boats, sailboats and ships (maybe 802.11 in the future)
 :: -9 Mobiles

@@ Line 1: / Line 1: @@
-*Symbols
+== Symbols ==
 Symbols are set by the symbol table character, symbol character, and overlay character in the APRS packet for most APRS stations.
-The only APRS stations that currently rely on default-symbol-by-SSID (see below) are those stations that have no capability to send APRS-formatted packets. The only ones currently like this are MIM's and old generic TNC's that are "aprs-capable". In this case they send a complete NMEA string from the GPS and limited symbol information is carried in a separate part of the packet. Sending the ultra-long NMEA strings are starting to be considered bad practice anyway: Much shorter APRS-format, Base91-format, or Mic-E format packets are the norm.
+The only APRS stations that currently rely on default-symbol-by-SSID (see below) are those stations that have no capability to send APRS-formatted packets. The only ones currently like this are MIM's and old generic TNC's that are "APRS-capable". In this case they send a complete NMEA string from the GPS and limited symbol information is carried in a separate part of the packet. Sending the ultra-long NMEA strings are starting to be considered bad practice anyway: Much shorter APRS-format, Base91-format, or Mic-E format packets are the norm.  Please note that by default UI-View and UI-View32 PC client software will reject Mic-E packets unless this option is turned off.
 So...  99.8% of the people out there will be setting their symbol in their APRS client software or in their configuration software for their tracker, and the SSID (see below) has no influence whatsoever on what symbol is displayed.
-*SSID's (Secondary Station Identifiers)
+== SSID's (Secondary Station Identifiers) ==
-An SSID is the number following the callsign, which can range from -0 to -15 on the air (internet-only stations have different rules).  A -0 (dash-zero) station shows up as the plain-Jane callsign without the -0.  For instance W7ABC-0 will show up as just W7ABC.  A person may have 16 different APRS stations on the air at one time using only the SSID's to differentiate between them.
+An SSID is the number following the callsign, which can range from -0 to -15 on the air (internet-only stations have different rules).  A -0 (dash-zero) station shows up in mapping as the callsign without the -0.  For instance W7ABC-0 will show up as simply W7ABC.  A person may have 16 different APRS stations on the air at one time using only the SSID's to differentiate between them.
-It is important to select a different SSID for each on-the-air station.  A common "newbie" mistake is to use callsign-0 for the home station -and- for the mobile station.  If they then drive a slow circle around their house, where the house station is beaconing at the same time, it makes a pretty flower pattern on everyones maps.  The symbol keeps darting from the car's location to the house location leaving a track line on the map each time.  The fix for this is to set a different SSID for each station so that software can track each one separately.
+It is important to select a different SSID for each on-the-air station.  A common "newbie" mistake is to use CALLSIGN-0 for the home station -and- for the mobile station.  If they then drive a slow circle around their house, where the house station is beaconing at the same time, it makes a pretty flower pattern on everyone's map.  The symbol keeps darting from the car's location to the house location leaving a track line on the map each time.  The fix for this is to set a different SSID for each station so that software can track each one separately.
-The most common setup is to use callsign-0 for the house, -1 for the first vehicle, -2 for the next, and so on.  Some local customs vary this a bit.
+Originally the protocol was to use CALLSIGN-0 for the house, -1 for the first vehicle, -2 for the next, and so on.  The more modern protocol (as defined by Bob Bruninga, WB4APR) assigns a meaning to each SSID; however [[RegionalPages|local custom]] can vary quite a bit on this.
-* Default Symbol by SSID
+Here is the modern protocol:
 As mentioned above, choosing the symbol based on SSID is ONLY done by the client software when there is no other symbol information in the packet to draw from.  Right now this includes only MIM trackers and old generic packet TNC's that send NMEA-formatted strings.  These are rare and getting more rare on the air.  See the "SYMBOLS WITH STAND-ALONE GPS TRACKERS" section on this page: [[http://www.aprs.net/vm/DOS/SYMBOLS.HTM APRS Display Symbols]] for information on this (again rarely used) technique of specifying symbols.

← Older revision		Revision as of 16:21, 24 October 2007
Line 19:		Line 19:
	* Default Symbol by SSID		* Default Symbol by SSID

−	As mentioned above, choosing the symbol based on SSID is ONLY done by the client software when there is no other symbol information in the packet to draw from. Right now this includes only MIM trackers and old generic packet TNC's that send NMEA-formatted strings. These are rare and getting more rare on the air. See the "SYMBOLS WITH STAND-ALONE GPS TRACKERS" section on this page: [[http://www.aprs.net/vm/DOS/SYMBOLS.HTM\|APRS Display Symbols]] for information on this (again rarely used) technique of specifying symbols.	+	As mentioned above, choosing the symbol based on SSID is ONLY done by the client software when there is no other symbol information in the packet to draw from. Right now this includes only MIM trackers and old generic packet TNC's that send NMEA-formatted strings. These are rare and getting more rare on the air. See the "SYMBOLS WITH STAND-ALONE GPS TRACKERS" section on this page: [[http://www.aprs.net/vm/DOS/SYMBOLS.HTM APRS Display Symbols]] for information on this (again rarely used) technique of specifying symbols.

@@ Line 3: / Line 3: @@
 Symbols are set by the symbol table character, symbol character, and overlay character in the APRS packet for most APRS stations.
-The only APRS stations that currently rely on default-symbol-by-SSID are those stations that have no capability to send APRS-formatted packets.  The only one's I know of that are currently like this are MIM's and old generic TNC's that are "aprs-capable.  In this case they send a complete NMEA string from the GPS and carry no symbol information.
+The only APRS stations that currently rely on default-symbol-by-SSID (see below) are those stations that have no capability to send APRS-formatted packets.  The only one's currently like this are MIM's and old generic TNC's that are "aprs-capable.  In this case they send a complete NMEA string from the GPS and limited symbol information is carried in a separate part of the packet.
 So...  99.8% of the people out there will be setting their symbol in their APRS client software or in their configuration software for their tracker, and the SSID (see below) has no influence whatsoever on what symbol is displayed.
@@ Line 15: / Line 15: @@
 The most common setup is to use callsign-0 for the house, -1 for the first vehicle, -2 for the next, and so on.  Some local customs vary this a bit.