[App_rpt-users] Fwd: Adding APRStt tp my node

David KE6UPI dshaw at ke6upi.com
Wed Feb 15 22:20:58 EST 2012


Here is an old email you can red.

David

---------- Forwarded message ----------
From: Michael Kaufman <captmick at charter.net>
Date: Mon, Dec 19, 2011 at 6:12 PM
Subject: Re: [App_rpt-users] Adding APRStt tp my node
To: Jim Duuuude <telesistant at hotmail.com>
Cc: app_rpt mailing list <app_rpt-users at ohnosec.org>


Hi Jim:

Thanks for the info which was quite helpful:

I have tried some of your recommendations with good results but more
testing to do. I will publish more information later for anyone interested
in adding this feature to their nodes, a great enhancement!!!!

Mike

WB9SLI

Node 27558


On Dec 17, 2011, at 4:07 PM, Jim Duuuude wrote:

 of course, this only applies to the sources in SVN. please update to them.

JIM

------------------------------
From: telesistant at hotmail.com
To: captmick at charter.net; app_rpt-users at ohnosec.org
Date: Sat, 17 Dec 2011 14:06:55 -0800
Subject: Re: [App_rpt-users] Adding APRStt tp my node

Without spending a lot of time (which I dont have) to rigorously
re-figure out exactly what all this stuff means, I will give you
some background information, and let you experiment with it and
see what you get out of it. Please share your findings.

First of all, the app_gps module supports multiple "gps" personalities.

The "default" personality is the one normally referred to in the gps.conf
file.
Additional personalities may also be specified in the file with different
stanza
names.

Here is an example of my gps.conf file (with the password omitted):

; Configuration for app_gps
;
[general]

call = A2115-1
password = XXXXX
interval = 600
icon = r
comment = AllStar Link Node
server = second.aprs.net
port = 14580
;comport = /dev/ttyS0
baudrate = 4800
;debug = y ; set this for debug output
lat=37.153
lon=-119.4218
elev=123.69
power=2
height=1
gain=7
dir=0

[gene]

call = A2115-2
interval = 600
icon = r
comment = AllStar Link Node
lat=37.153
lon=-119.4218
elev=123.69
power=2
height=1
gain=7
dir=0

This file is in use for my 2 site voter/simulcast system here in Coarsegold.
The [general] (default) personality is my main site at my QTH. The [gene]
personality is the other site at the QTH of Gene, KE6YMW.

I am using this in this manner, to represent the locations of the 2 site of
my voter/simulcast system, and not primarily for ARPStt use. However, the
APRStt functionality *is* working for the main site.

In the rpt.conf (and voter.conf) files, the various app_gps personalities
are
referred to by their stanza name. or blank for the default ([general])
stanza.

So, in the stanza for your node number in rpt.conf, to use the main app_gps
personality, you would include the following line:

aprstt=

If, for example, you wanted to use the [gene] personality, instead, you
would
include the following line:

aprstt=gene


In addition, the following configuration parameters that have to do with
APRStt
may optionally be included in any of the stanzas in the gps.conf file:

ttlat=XXXX
ttlon=XXXX
ttlist=XXXX
ttoffset=XXXX
ttsplit=(y/n)

The APRStt stuff generates a list of Callsigns associated with a station's
location. What they want you to do is place the origin position (lat/lon)
of the list *near* the station, but not directly on top of it, since the
list would obscure the station entry (on a map) itself.

These parameters have default values, which place the list some amount of
space away from the station, and make the list do default kinds of things.
I'm not sure whether these defaults are sane and/or resonable, but they
are, at least, defaults.

ttlat and ttlon allow specification of the station list's origin in
absolute lat/lon position.

ttlist. ttoffset and ttsplit speficy (somehow) the spacing and orientation
of each entry in the station list, relative to the specified (or default)
origin position. ttsplit, specifies that the list should center around the
origin, rather then start at the origin.

In addition of accepting the standard (rather cumbersome)
APRStt key signon sequence, we also support the cop,63
function, which allows you to specify a normal DTMF function
to log in a particular user (for APRStt) with of without a
sub-id (or whatever those things are).

Here is an example from my [functions] stanza:

900=cop,63,wb6nil,1
901=cop,63,wa6aaa

*900 loggs in wb6nil with sub-whatever-it-is-id of 1
*900 loggs in wa6aaa with no sub-whatever-it-is



Thats about all I know (or remember at this point).

Play with it, see what it does, and let me know.

JIM

> From: captmick at charter.net
> Date: Thu, 15 Dec 2011 15:33:34 -0600
> To: App_rpt-users at ohnosec.org
> Subject: [App_rpt-users] Adding APRStt tp my node
>
> I have read on some websites that an APRStt function was being added to
Allstar. I have not seen any documentation or information on the progress
of this feature. I would like to add this to my node and would appreciate
any help or information on implementing this feature if it is available.
>
> Mike
>
> WB9SLI
>
> Node 27558
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

_______________________________________________ App_rpt-users mailing list
App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users



_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.allstarlink.org/pipermail/app_rpt-users/attachments/20120215/d34bbd6a/attachment.html>


More information about the App_rpt-users mailing list