<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
The heck with all this confusion regarding APRS passwords!!<br><br>I just reverse engineered the password algorithm and will make<br>a password generator (and will also automatically generate a password<br>for Portal-generate configurations).<br><br>JIM<br><br>> Date: Sun, 23 Jan 2011 15:49:55 +0200<br>> From: yo3iiu@yo3iiu.ro<br>> To: rpt2@chuck.midlandsnetworking.com<br>> CC: app_rpt-users@ohnosec.org<br>> Subject: Re: [App_rpt-users] aprs password for app_gps<br>> <br>> The APRS-IS password could be generated using the callpass utility that<br>> comes with xastir.<br>> <br>> Bogdan - YO3IIU<br>> <br>> > I would like to set up my allstarlink system to report position<br>> > information<br>> > to the aprs system.<br>> ><br>> > Can someone tell me how to set up this password? Also, are the default<br>> > server and port listed in the example below what should be used?<br>> > I have searched the aprs site and couldn't find who to request this<br>> > information from.<br>> ><br>> > Chuck Henderson, WB9UUS<br>> ><br>> ><br>> >><br>> >> ; Configuration for app_gps<br>> >> ;<br>> >> [general]<br>> >><br>> >> call = wb9uus-2 ; callsign (including SSID) for APRS purposes*password<br>> >> = 12345 ; Password for APRS-IS server for above callsign*<br>> >> comment = AllStar Node 27468 ; Text to be displayed associated with this<br>> >> station*server = second.aprs.net ; APRS-IS server to report information<br>> >> to**port = 10151 ; port on server to send data*<br>> >> icon = r ; A CAR (default) Icon do be displayed for station on APRS<br>> >> display (see below)<br>> >> comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this only<br>> >> if using GPS receiver)<br>> >> baudrate = 4800 ; Baud rate for GPS receiver (specify this only if<br>> >> using GPS receiver)<br>> >> ;debug = y ; set this for debug output<br>> >> freq=442.700 ; Display Frequency of station<br>> >> tone=107.2 ; CTCSS tone of station (0.0 for none)<br>> >> lat=40.508 ; Fixed (default) latitude in decimal degrees<br>> >> lon=-88.988 ; Fixed (default) longitude in decimal degrees<br>> >> elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT)<br>> >> power=9 ; Power level (see below)<br>> >> height=5 ; Antenna Height in HAAT (see below)<br>> >> gain=8 ; Antenna Gain (see below)<br>> >> dir=0 ; Antenna Direction (see below)<br>> >><br>> >> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude<br>> >> <telesistant@hotmail.com>wrote:<br>> >><br>> >>> There have (obviously) been some changes/improvements made to the<br>> >>> Echolink and APRS/GPS subsystems within app_rpt.<br>> >>><br>> >>> Included in these is the ability for a node to report its "fixed" GPS<br>> >>> coordinates<br>> >>> to the APRS network, even if it does not have a GPS receiver connected.<br>> >>><br>> >>> Please see the following:<br>> >>><br>> >>> Setting up Echolink Connectivity<br>> >>> http://209.159.155.200/drupal/node/56<br>> >>><br>> >>> Setting Up APRS and GPS Configuration<br>> >>> http://209.159.155.200/drupal/node/179<br>> >>><br>> >>> Of course, the latest copies of app_gps and chan_echolink need to be<br>> >>> downloaded from the SVN.<br>> >>><br>> >>> JIM WB6NIL<br>> >>><br>> >>><br>> >>><br>> >><br>> > _______________________________________________<br>> > App_rpt-users mailing list<br>> > App_rpt-users@ohnosec.org<br>> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br>> ><br>> <br>> <br>> _______________________________________________<br>> App_rpt-users mailing list<br>> App_rpt-users@ohnosec.org<br>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br> </body>
</html>