¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

SSID's


 

Hello all.

I understood that we should put -3 in our UI-View callsigns in order to be
compatible with APRS. However, I have received a packet message about this,
of which the following is the relevant extract.

What do you think?

-3 is the wrong SSID. Will you inform whoever told him that -3 is for
NODES -4 is for DIGIPEATERS and as UI-View is generally a digipeater (when
it is set up right), then -4 is correct.

As soon as I get the full list of the meanings of SSID's I'll let you have a
copy. -2=PMS's -3=Nodes -4=Digipeaters -8=Nodes(but not the same
as-3) -9 was originally spare but has been adopted for Mobiles on UI-View
along with -7, which was also spare. I will send you the proper
Internationally agreed
list when I get it.

A belated Happy New Year.

Keith G4JVX

keithp@...


Hamish Moffatt <[email protected]
 

On Fri, Jan 07, 2000 at 11:51:46AM -0000, Keith wrote:
I understood that we should put -3 in our UI-View callsigns in order to be
compatible with APRS. However, I have received a packet message about this,
of which the following is the relevant extract.

What do you think?
I think SSIDs are a poor way to identify your station type. Some of
the APRS message formats include a station type identifier; only formats
which don't use the SSID (eg NMEA strings from GPS trackers).

With a little bit more code inside the TNC, the APRS protocol could
be greatly simplified.


Hamish vk3sb
--
Hamish Moffatt Mobile: +61 412 011 176 hamish@...
Rising Software Australia Pty. Ltd.
Phone: +61 3 9894 4788 Fax: +61 3 9894 3362 USA: 1 888 667 7839


Ian Wade <[email protected]
 

In article <000001bf590b$10bb83e0$5338832c@...>, Keith
<keithp@...> writes
Hello all.

I understood that we should put -3 in our UI-View callsigns in order to be
compatible with APRS.
This is not true.


However, I have received a packet message about this,
of which the following is the relevant extract.

What do you think?

The APRS Protocol Specification says the following SSIDs may be used in
the source address:

-1 ambulance
-2 bus
-3 fire truck
-4 bike
-5 yacht
-6 helicopter
-7 small aircraft
-8 ship (power boat)
-9 car
-10 motorcycle
-11 balloon
-12 jeep
-13 recreational vehile
-14 truck
-15 van

IMPORTANT NOTE: These Source Address SSIDs are intended *ONLY* for
stand-alone trackers where there is *NO* other method of specifying a
display symbol.

Thus they are not applicable to nodes or digipeaters -- these will
usually be able to include a symbol code in the beacon text.

73
Ian, G3NRW
Technical Editor, APRS Protocol Specification

--
+-----------------------------------------------------------------+
| APRS on 144.800 [IO91SX] ~55km/35 miles NNW of London |
| email: g3nrw@... |
| |
| APRS PROTOCOL SPEC:
+-----------------------------------------------------------------+


Roger Barker <[email protected]
 

In article <000001bf590b$10bb83e0$5338832c@...>, Keith
<keithp@...> writes
Hello all.

I understood that we should put -3 in our UI-View callsigns in order to be
compatible with APRS. However, I have received a packet message about this,
of which the following is the relevant extract.
If you're running UI-View or any other APRS software system, then the
SSID has no meaning - your station symbol is specified in your posit
beacon.

If you're operating as a tracker, and not using the recommended GPSxyz
method of specifying your symbol, then -3 means you're a fire truck!

--
Roger Barker, G4IDE roger@...
Boston
Lincolnshire, UK


Roger Barker <[email protected]
 

In article <20000107233539.B13490@...>, Hamish Moffatt
<hamish@...> writes
On Fri, Jan 07, 2000 at 11:51:46AM -0000, Keith wrote:
I understood that we should put -3 in our UI-View callsigns in order to be
compatible with APRS. However, I have received a packet message about this,
of which the following is the relevant extract.

What do you think?
I think SSIDs are a poor way to identify your station type. Some of
the APRS message formats include a station type identifier; only formats
which don't use the SSID (eg NMEA strings from GPS trackers).

With a little bit more code inside the TNC, the APRS protocol could
be greatly simplified.
No, that's been the great problem with APRS!

Putting the intelligence in the hardware has been great for the TNC
manufacturers, who suddenly found that they could suddenly start selling
TNCs again.

However, from the point of view of allowing the mode to develop, it's
been very bad. Other than for systems where a PC can't be used, e.g.
standalone digis and trackers, the intelligence should be in the
software, and the TNC should be used in KISS mode. Once you do that, you
get rid of many of the current performance restrictions.

--
Roger Barker, G4IDE roger@...
Boston
Lincolnshire, UK


Roger Barker <[email protected]
 

In article <oCyZ+AAtVfd4EwkA@...>, Roger Barker
<roger@...> writes
manufacturers, who suddenly found that they could suddenly start selling
Sorry about the sudden excess of suddenlys. That's what comes of writing
email and talking on the phone at the same time!

--
Roger Barker, G4IDE roger@...
Boston
Lincolnshire, UK


Hamish Moffatt <[email protected]
 

On Fri, Jan 07, 2000 at 02:17:18PM +0000, Roger Barker wrote:
However, from the point of view of allowing the mode to develop, it's
been very bad. Other than for systems where a PC can't be used, e.g.
standalone digis and trackers, the intelligence should be in the
software, and the TNC should be used in KISS mode. Once you do that, you
get rid of many of the current performance restrictions.
As someone who has written code to decode all the position reports,
don't you find the sheer number of different position report types
excessive? I would prefer that a GPS-aware TNC had a little more intelligence
and could convert an NMEA $GP... string into a standard position report
format, rather than broadcasting it as-is. For example.


Hamish
--
Hamish Moffatt Mobile: +61 412 011 176 hamish@...
Rising Software Australia Pty. Ltd.
Phone: +61 3 9894 4788 Fax: +61 3 9894 3362 USA: 1 888 667 7839


Ian Wade <[email protected]
 

In article <oqoqpFAs5ed4Ew2L@...>, Ian Wade
<ian@...> writes

IMPORTANT NOTE: These Source Address SSIDs are intended *ONLY* for
stand-alone trackers where there is *NO* other method of specifying a
display symbol.

Thus they are not applicable to nodes or digipeaters -- these will
usually be able to include a symbol code in the beacon text.

Someone asked me out-of-band if you can still use GPSxyz to specify a
digi or node. The answer is yes. e.g.

GPSBD digi (white center)
GPSODz green star. "z" is an overlay character.
Thus GPSOD1 is a star containing a "1"
GPSODT is a star containing a "T"
GPSBG HF gateway
GPSLN Node


These are DESTINATION calls, set with UNPROTO. For example:

UNPROTO GPSBD via WIDE, WIDE



See pages 83-85 of the draft APRS Protocol Spec for the full list of
GPSxyz symbols, in


73
Ian, G3NRW
Technical Editor, APRS Protocol Specification

--
+-----------------------------------------------------------------+
| APRS on 144.800 [IO91SX] ~55km/35 miles NNW of London |
| email: g3nrw@... |
| |
| APRS PROTOCOL SPEC:
+-----------------------------------------------------------------+


Ian Wade
 

In article <E126sSA-0003Tk-00@...>, David J. Ackrill
<dave.g0dja@...> writes

I don't remember seeing any great problem with -3 or even -4!

Some people say you shouldn't put any SSID in at all.
The APRS spec says it should only be used for trackers which have no
other means of specifying a symbol. If a symbol code is specified
elsewhere in a packet as well as in the source SSID, then the SSID-
specified symbol is ignored.

For example:

MYCALL G3NRW-9 by itself (with no other symbol specified in packets)
means I am a car.

MYCALL G3NRW-9
UNPROTO GPSLV via RELAY means I am a jeep (i.e. GPSLV overrides -9)

MYCALL G3NRW-9
BT =5152.53N&#92;00029.30WU means I am a little ray of sunshine
(i.e. &#92;U overrides -9)



Tell you what, why don't we have a committee to discuss it ;-)
What a splendid idea ..... :^)


Just don't ask me to sit on it - HI!
And don't ask me what happens if you specify SSID *and* GPSxyz *and* a
symbol code in the Information field .......!

TBD.

73
Ian, G3NRW
Technical Editor, APRS Protocol Specification

--
+-----------------------------------------------------------------+
| APRS on 144.800 [IO91SX] ~55km/35 miles NNW of London |
| email: g3nrw@... |
| |
| APRS PROTOCOL SPEC:
+-----------------------------------------------------------------+


 

Hello all.

I understood that we should put -3 in our UI-View callsigns in order to be
compatible with APRS. However, I have received a packet message about this,
of which the following is the relevant extract.
I don't remember seeing any great problem with -3 or even -4!

Some people say you shouldn't put any SSID in at all.

Tell you what, why don't we have a committee to discuss it ;-)

Just don't ask me to sit on it - HI!

de Dave (G0DJA)
or even G0DJA-3