[aprssig] [RFC] Power Source Data Extension (symbol update)

Robert Bruninga bruninga at usna.edu
Mon Feb 13 10:43:54 EST 2017

To help correct some of the noted gaps in symbol overlays noted below, I
just updated the symbol overlay definitions.

The intent of these symbols are to allow a user to indicate an unusual or
relevant facet of his station or mobile at zero added overhead to his
packet since the info is contained simply in his symbol.

For example for cars, I added  P for Plugin hybrid, B for battery electric
and F for Fuelcell, H for homemade, etc.    For houses, there is no need
for Utiiltiy or Mains since that is assumed as a default.

I do not object to adding a Power extension, but abhor its suggestion of
deprecating the Symbol Overlay indicators.   The symbol overlays are zero
cost to the network load.  But suggesting the addition of an added 6+ bytes
of overhead to every packet is not efficient use of the channel.  Such
addition should only be used when the symbol overlay is for some reason

To that end I suggest the following changes to the proposed PWR extension:

1)      Do not deprecate any symbol characters or overlays

2)      Strongly caution against use when a symbol overlay will do

3)      Eliminate the default UTILITY and mains options, since that invites
people to add 6 bytes of channel overhead to repeat the obvious.

I welcome any other requests for Symbol Overlays.  Bob, WB4APR

*From:* aprssig [mailto:aprssig-bounces at tapr.org] *On Behalf Of *Kenneth
*Sent:* Sunday, February 12, 2017 3:27 AM
*To:* TAPR APRS Mailing List
*Subject:* [aprssig] [RFC] Power Source Data Extension

As I continue to study the APRS symbol set this year, I've noticed a set of
symbol overlays indicating the power source for APRS stations, but their
documented application is limited to only a few base symbols and is
somewhat sporadic. Houses get all sorts of options for symbol overlays
indicating their power, but shelters get none.

In an effort to free the symbol overlay from trying to indicate both the
type of station and the type of power source for the station, I'm proposing
a new data extension to indicate power source.


Why was 50Hz vs 60Hz handled for houses? I'm a bit at a loss where that
would be an issue.


Power Source Data Extension

There has been a proliferation of APRS symbol overlays trying to encode the
power source for stations, which suffers from a few issues:

   1. Several duplicated sets of symbol overlays for power sources per
   station type (i.e. solar powered plane, solar powered car, and solar
   powered house)
   2. Prevents the symbol overlay from being used to convey more important
   information than the station's power source
   3. Is unable to represent more than one power source at a time
   4. Only gives the ability to indicate power source to a limited list of
   station types which have symbol power overlays defined

To correct these issues, I am proposing the definition of a new station
capability field to be included in the < capability packet or included as a
data extension in location or status comment fields.

PWR=[Unordered list of power source codes]

   - B - Battery
   - C - Coal, natural gas, wood, etc
   - F - H2 fuel cells
   - G - Internal combustion generator
   - H - Hydroelectric
   - N - Nuclear
   - S - Solar
   - T - GeoThermal
   - U - Utility mains
   - W - Wind

Multiple sources should be listed as several power source codes immediately
following the = with no seperator between power source codes. The list of
power sources is terminated by any character which is not an upper case
letter [A-Z].

The PWR extension is not meant to differentiate between different sources
for utility mains power. The availability of power codes such as geothermal
and nuclear are only for completeness, and should not be used by stations
which are simply paying their local utility company to operate these sorts
of power sources. This means that a power source like PWR=N would be very
unusual, since it indicates that the station is operating a nuclear power

Stations should indicate the power sources they typically have available,
which may not currently all be active. For example, an off-the-grid solar
site would beacon PWR=SB to indicate that they are a solar + battery
station, despite the fact that the solar panels aren't necessarily
producting power during the night.

This means that the PWR extension should never be used as a way to remotely
monitor power sources like whether a site has utility power or not (i.e. it
switching between PWR=UB and PWR=B). The correct way to monitor if a site
has power or not is to use one of the boolean telemetry fields to encode
the power state and beacon a telemetry formatter such as :MYCALL
:PARM.,,,,,AC Power.

The PWR extension may be foregone when the power source for a station is
unremarkable. For example, house stations only running on wall power (PWR=U)
or car mobile stations only running on internal combustion generator (PWR=G)
may forego the additional packet length taken to indicate the obvious.

This power source capability / data extension field deprecates the
following symbol overlays (with possible replacements indicated):

   - E^ = Electric aircraft (PWR=B)
   - S^ = Solar powered airplane (PWR=S)
   - E> = Electric car (PWR=B)
   - H> = Hybrid car (PWR=BG)
   - S> = Solar powered car/vehicle (PWR=S)
   - V> = GM Volt (PWR=BG)
   - E# = Emergency powered digipeater (PWR=?)
   - 5- = 50Hz mains power, house (PWR=U)
   - 6- = 60Hz mains power, house (PWR=U)
   - B- = Backup battery power, house (PWR=UB)
   - E- = Emergency power, house (PWR=?)
   - G- = Geothermal, house (PWR=T)
   - H- = Hydro powered, house (PWR=H)
   - S- = Solar Powered, house (PWR=S)
   - W- = Wind powered, house (PWR=W)

Many of these symbols would likely be replaced with something other than
what's listed; e.g. the overlay for a solar-powered house lacked the
expressiveness to distinguish if it's a grid-tied solar-powered house (
PWR=SU) or if it's an off-the-grid house with a battery bank (PWR=SB).

The distinction between 60Hz utility power and 50Hz utility power is not
made in this data extension since the possible application of where that
distinction would need to be made is incredibly small. For the very few
applications where mains frequency would be of any concern to other users,
APRS nodes may otherwise include a note on the power frequency. One
possible method would be PWR=U(50Hz); power capability parsers should
terminate at the '(' and need not process the frequency indication after it.

Kenneth Finnegan, W6KWF
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20170213/999320d7/attachment.html>

More information about the aprssig mailing list