aprs password for app_gps

I would like to set up my allstarlink system to report position information to the aprs system.

Can someone tell me how to set up this password? Also, are the default server and port listed in the example below what should be used?

I have searched the aprs site and couldn’t find who to request this information from.

Chuck Henderson, WB9UUS

···
; Configuration for app_gps
;
[general]
call = wb9uus-2 ; callsign (including SSID) for APRS purposes
**password = 12345 ; Password for APRS-IS server for above callsign**
comment = AllStar Node 27468 ; Text to be displayed associated with this station
**server = [second.aprs.net](http://second.aprs.net)  ; APRS-IS server to report information to**
**port = 10151 ; port on server to send data**
icon = r ; A CAR (default) Icon do be displayed for station on APRS display (see below)
comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this only if using GPS receiver)
baudrate = 4800 ; Baud rate for GPS receiver (specify this only if using GPS receiver)
;debug = y ; set this for debug output
freq=442.700 ; Display Frequency of station
tone=107.2 ; CTCSS tone of station (0.0 for none)
lat=40.508 ; Fixed (default) latitude in decimal degrees
lon=-88.988 ; Fixed (default) longitude in decimal degrees
elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT)
power=9 ; Power level (see below)
height=5 ; Antenna Height in HAAT (see below)
gain=8 ; Antenna Gain (see below)
dir=0 ; Antenna Direction (see below)

On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude telesistant@hotmail.com wrote:

There have (obviously) been some changes/improvements made to the
Echolink and APRS/GPS subsystems within app_rpt.

Included in these is the ability for a node to report its “fixed” GPS coordinates

to the APRS network, even if it does not have a GPS receiver connected.

Please see the following:

Setting up Echolink Connectivity
http://209.159.155.200/drupal/node/56

Setting Up APRS and GPS Configuration
http://209.159.155.200/drupal/node/179

Of course, the latest copies of app_gps and chan_echolink need to be

downloaded from the SVN.

JIM WB6NIL

Well – Google found this

http://zielkeassociates.com/~jack/aprs-xo/aprspass/

I took the first link provided and looked at the first few entries and there are emails for sysops who will give you a “passcode”

Apparently the passcode is generated from an algorithm using your call+SSID as input.

I have not tried it (yet)

Ken

···

From: app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Chuck Henderson
Sent: Sunday, January 23, 2011 5:53 AM
To: app_rpt mailing list
Subject: [App_rpt-users] aprs password for app_gps

I would like to set up my allstarlink system to report position information to the aprs system.

Can someone tell me how to set up this password? Also, are the default server and port listed in the example below what should be used?

I have searched the aprs site and couldn’t find who to request this information from.

Chuck Henderson, WB9UUS

; Configuration for app_gps
;
[general]
call = wb9uus-2   ; callsign (including SSID) for APRS purposes
**password = 12345 ; Password for APRS-IS server for above callsign**
comment = AllStar Node 27468 ; Text to be displayed associated with this station
**server = [second.aprs.net](http://second.aprs.net)  ; APRS-IS server to report information to**
**port = 10151 ; port on server to send data**
icon = r  ; A CAR (default)   Icon do be displayed for station on APRS display (see below)
comport = /dev/ttyS0  ; Serial port for GPS receiver (specify this only if using GPS receiver)
baudrate = 4800  ; Baud rate for GPS receiver (specify this only if using GPS receiver)
;debug = y ; set this for debug output
freq=442.700  ; Display Frequency of station
tone=107.2    ; CTCSS tone of station (0.0 for none)
lat=40.508    ; Fixed (default) latitude in decimal degrees
lon=-88.988   ; Fixed (default) longitude in decimal degrees
elev=123.4    ; Elevation of Antenna in Meters (*NOT* HAAT)
power=9       ; Power level (see below)
height=5      ; Antenna Height in HAAT (see below)
gain=8        ; Antenna Gain (see below)
dir=0         ; Antenna Direction (see below)

On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude telesistant@hotmail.com wrote:

There have (obviously) been some changes/improvements made to the
Echolink and APRS/GPS subsystems within app_rpt.

Included in these is the ability for a node to report its “fixed” GPS coordinates
to the APRS network, even if it does not have a GPS receiver connected.

Please see the following:

Setting up Echolink Connectivity
http://209.159.155.200/drupal/node/56

Setting Up APRS and GPS Configuration
http://209.159.155.200/drupal/node/179

Of course, the latest copies of app_gps and chan_echolink need to be
downloaded from the SVN.

JIM WB6NIL

The APRS-IS password could be generated using the callpass utility that
comes with xastir.

Bogdan - YO3IIU

···

I would like to set up my allstarlink system to report position
information
to the aprs system.

Can someone tell me how to set up this password? Also, are the default
server and port listed in the example below what should be used?
I have searched the aprs site and couldn't find who to request this
information from.

Chuck Henderson, WB9UUS

; Configuration for app_gps
;
[general]

call = wb9uus-2 ; callsign (including SSID) for APRS purposes*password
= 12345 ; Password for APRS-IS server for above callsign*
comment = AllStar Node 27468 ; Text to be displayed associated with this
station*server = second.aprs.net ; APRS-IS server to report information
to**port = 10151 ; port on server to send data*
icon = r ; A CAR (default) Icon do be displayed for station on APRS
display (see below)
comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this only
if using GPS receiver)
baudrate = 4800 ; Baud rate for GPS receiver (specify this only if
using GPS receiver)
;debug = y ; set this for debug output
freq=442.700 ; Display Frequency of station
tone=107.2 ; CTCSS tone of station (0.0 for none)
lat=40.508 ; Fixed (default) latitude in decimal degrees
lon=-88.988 ; Fixed (default) longitude in decimal degrees
elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT)
power=9 ; Power level (see below)
height=5 ; Antenna Height in HAAT (see below)
gain=8 ; Antenna Gain (see below)
dir=0 ; Antenna Direction (see below)

On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude >> <telesistant@hotmail.com>wrote:

There have (obviously) been some changes/improvements made to the
Echolink and APRS/GPS subsystems within app_rpt.

Included in these is the ability for a node to report its "fixed" GPS
coordinates
to the APRS network, even if it does not have a GPS receiver connected.

Please see the following:

Setting up Echolink Connectivity
http://209.159.155.200/drupal/node/56

Setting Up APRS and GPS Configuration
http://209.159.155.200/drupal/node/179

Of course, the latest copies of app_gps and chan_echolink need to be
downloaded from the SVN.

JIM WB6NIL

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org

The heck with all this confusion regarding APRS passwords!!

I just reverse engineered the password algorithm and will make
a password generator (and will also automatically generate a password
for Portal-generate configurations).

JIM

···

Date: Sun, 23 Jan 2011 15:49:55 +0200
From: yo3iiu@yo3iiu.ro
To: rpt2@chuck.midlandsnetworking.com
CC: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] aprs password for app_gps

The APRS-IS password could be generated using the callpass utility that
comes with xastir.

Bogdan - YO3IIU

I would like to set up my allstarlink system to report position
information
to the aprs system.

Can someone tell me how to set up this password? Also, are the default
server and port listed in the example below what should be used?
I have searched the aprs site and couldn’t find who to request this
information from.

Chuck Henderson, WB9UUS

; Configuration for app_gps
;
[general]

call = wb9uus-2 ; callsign (including SSID) for APRS purposespassword
= 12345 ; Password for APRS-IS server for above callsign

comment = AllStar Node 27468 ; Text to be displayed associated with this
stationserver = second.aprs.net ; APRS-IS server to report information
to**port = 10151 ; port on server to send data

icon = r ; A CAR (default) Icon do be displayed for station on APRS
display (see below)
comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this only
if using GPS receiver)
baudrate = 4800 ; Baud rate for GPS receiver (specify this only if
using GPS receiver)
;debug = y ; set this for debug output
freq=442.700 ; Display Frequency of station
tone=107.2 ; CTCSS tone of station (0.0 for none)
lat=40.508 ; Fixed (default) latitude in decimal degrees
lon=-88.988 ; Fixed (default) longitude in decimal degrees
elev=123.4 ; Elevation of Antenna in Meters (NOT HAAT)
power=9 ; Power level (see below)
height=5 ; Antenna Height in HAAT (see below)
gain=8 ; Antenna Gain (see below)
dir=0 ; Antenna Direction (see below)

On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > >> telesistant@hotmail.comwrote:

There have (obviously) been some changes/improvements made to the
Echolink and APRS/GPS subsystems within app_rpt.

Included in these is the ability for a node to report its “fixed” GPS
coordinates
to the APRS network, even if it does not have a GPS receiver connected.

Please see the following:

Setting up Echolink Connectivity
http://209.159.155.200/drupal/node/56

Setting Up APRS and GPS Configuration
http://209.159.155.200/drupal/node/179

Of course, the latest copies of app_gps and chan_echolink need to be
downloaded from the SVN.

JIM WB6NIL


App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org


App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org

Okay, the web site now has automatic APRS password generation for Web-based
configurations, and a page to do it manually (under “server”).

JIM WB6NIL

···

From: telesistant@hotmail.com
To: yo3iiu@yo3iiu.ro; rpt2@chuck.midlandsnetworking.com
Date: Sun, 23 Jan 2011 08:13:51 -0800
CC: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] aprs password for app_gps

The heck with all this confusion regarding APRS passwords!!

I just reverse engineered the password algorithm and will make
a password generator (and will also automatically generate a password
for Portal-generate configurations).

JIM

Date: Sun, 23 Jan 2011 15:49:55 +0200
From: yo3iiu@yo3iiu.ro
To: rpt2@chuck.midlandsnetworking.com
CC: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] aprs password for app_gps

The APRS-IS password could be generated using the callpass utility that
comes with xastir.

Bogdan - YO3IIU

I would like to set up my allstarlink system to report position
information
to the aprs system.

Can someone tell me how to set up this password? Also, are the default
server and port listed in the example below what should be used?
I have searched the aprs site and couldn’t find who to request this
information from.

Chuck Henderson, WB9UUS

; Configuration for app_gps
;
[general]

call = wb9uus-2 ; callsign (including SSID) for APRS purposespassword
= 12345 ; Password for APRS-IS server for above callsign

comment = AllStar Node 27468 ; Text to be displayed associated with this
stationserver = second.aprs.net ; APRS-IS server to report information
to**port = 10151 ; port on server to send data

icon = r ; A CAR (default) Icon do be displayed for station on APRS
display (see below)
comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this only
if using GPS receiver)
baudrate = 4800 ; Baud rate for GPS receiver (specify this only if
using GPS receiver)
;debug = y ; set this for debug output
freq=442.700 ; Display Frequency of station
tone=107.2 ; CTCSS tone of station (0.0 for none)
lat=40.508 ; Fixed (default) latitude in decimal degrees
lon=-88.988 ; Fixed (default) longitude in decimal degrees
elev=123.4 ; Elevation of Antenna in Meters (NOT HAAT)
power=9 ; Power level (see below)
height=5 ; Antenna Height in HAAT (see below)
gain=8 ; Antenna Gain (see below)
dir=0 ; Antenna Direction (see below)

On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > >> telesistant@hotmail.comwrote:

There have (obviously) been some changes/improvements made to the
Echolink and APRS/GPS subsystems within app_rpt.

Included in these is the ability for a node to report its “fixed” GPS
coordinates
to the APRS network, even if it does not have a GPS receiver connected.

Please see the following:

Setting up Echolink Connectivity
http://209.159.155.200/drupal/node/56

Setting Up APRS and GPS Configuration
http://209.159.155.200/drupal/node/179

Of course, the latest copies of app_gps and chan_echolink need to be
downloaded from the SVN.

JIM WB6NIL


App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org


App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org


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

The protocol is quite simple and the source for callpass is included in
the xastir source. Though, reverse engineering it seems a lot more fun :slight_smile:

Regards,
Bogdan - YO3IIU

···

The heck with all this confusion regarding APRS passwords!!

I just reverse engineered the password algorithm and will make
a password generator (and will also automatically generate a password
for Portal-generate configurations).

JIM

Date: Sun, 23 Jan 2011 15:49:55 +0200
From: yo3iiu@yo3iiu.ro
To: rpt2@chuck.midlandsnetworking.com
CC: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] aprs password for app_gps

The APRS-IS password could be generated using the callpass utility that
comes with xastir.

Bogdan - YO3IIU

> I would like to set up my allstarlink system to report position
> information
> to the aprs system.
>
> Can someone tell me how to set up this password? Also, are the
default
> server and port listed in the example below what should be used?
> I have searched the aprs site and couldn't find who to request this
> information from.
>
> Chuck Henderson, WB9UUS
>
>
>>
>> ; Configuration for app_gps
>> ;
>> [general]
>>
>> call = wb9uus-2 ; callsign (including SSID) for APRS
purposes*password
>> = 12345 ; Password for APRS-IS server for above callsign*
>> comment = AllStar Node 27468 ; Text to be displayed associated with
this
>> station*server = second.aprs.net ; APRS-IS server to report
information
>> to**port = 10151 ; port on server to send data*
>> icon = r ; A CAR (default) Icon do be displayed for station on
APRS
>> display (see below)
>> comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this
only
>> if using GPS receiver)
>> baudrate = 4800 ; Baud rate for GPS receiver (specify this only if
>> using GPS receiver)
>> ;debug = y ; set this for debug output
>> freq=442.700 ; Display Frequency of station
>> tone=107.2 ; CTCSS tone of station (0.0 for none)
>> lat=40.508 ; Fixed (default) latitude in decimal degrees
>> lon=-88.988 ; Fixed (default) longitude in decimal degrees
>> elev=123.4 ; Elevation of Antenna in Meters (*NOT* HAAT)
>> power=9 ; Power level (see below)
>> height=5 ; Antenna Height in HAAT (see below)
>> gain=8 ; Antenna Gain (see below)
>> dir=0 ; Antenna Direction (see below)
>>
>> On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude >> >> <telesistant@hotmail.com>wrote:
>>
>>> There have (obviously) been some changes/improvements made to the
>>> Echolink and APRS/GPS subsystems within app_rpt.
>>>
>>> Included in these is the ability for a node to report its "fixed"
GPS
>>> coordinates
>>> to the APRS network, even if it does not have a GPS receiver
connected.
>>>
>>> Please see the following:
>>>
>>> Setting up Echolink Connectivity
>>> http://209.159.155.200/drupal/node/56
>>>
>>> Setting Up APRS and GPS Configuration
>>> http://209.159.155.200/drupal/node/179
>>>
>>> Of course, the latest copies of app_gps and chan_echolink need to be
>>> downloaded from the SVN.
>>>
>>> JIM WB6NIL
>>>
>>>
>>>
>>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users@ohnosec.org
> ohnosec.org
>

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org

it was!! :slight_smile:

···

Date: Mon, 24 Jan 2011 00:27:16 +0200
Subject: RE: [App_rpt-users] aprs password for app_gps
From: yo3iiu@yo3iiu.ro
To: telesistant@hotmail.com
CC: yo3iiu@yo3iiu.ro; rpt2@chuck.midlandsnetworking.com; app_rpt-users@ohnosec.org

The protocol is quite simple and the source for callpass is included in
the xastir source. Though, reverse engineering it seems a lot more fun :slight_smile:

Regards,
Bogdan - YO3IIU

The heck with all this confusion regarding APRS passwords!!

I just reverse engineered the password algorithm and will make
a password generator (and will also automatically generate a password
for Portal-generate configurations).

JIM

Date: Sun, 23 Jan 2011 15:49:55 +0200
From: yo3iiu@yo3iiu.ro
To: rpt2@chuck.midlandsnetworking.com
CC: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] aprs password for app_gps

The APRS-IS password could be generated using the callpass utility that
comes with xastir.

Bogdan - YO3IIU

I would like to set up my allstarlink system to report position
information
to the aprs system.

Can someone tell me how to set up this password? Also, are the
default
server and port listed in the example below what should be used?
I have searched the aprs site and couldn’t find who to request this
information from.

Chuck Henderson, WB9UUS

; Configuration for app_gps
;
[general]

call = wb9uus-2 ; callsign (including SSID) for APRS
purposespassword
= 12345 ; Password for APRS-IS server for above callsign

comment = AllStar Node 27468 ; Text to be displayed associated with
this
stationserver = second.aprs.net ; APRS-IS server to report
information
to**port = 10151 ; port on server to send data

icon = r ; A CAR (default) Icon do be displayed for station on
APRS
display (see below)
comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this
only
if using GPS receiver)
baudrate = 4800 ; Baud rate for GPS receiver (specify this only if
using GPS receiver)
;debug = y ; set this for debug output
freq=442.700 ; Display Frequency of station
tone=107.2 ; CTCSS tone of station (0.0 for none)
lat=40.508 ; Fixed (default) latitude in decimal degrees
lon=-88.988 ; Fixed (default) longitude in decimal degrees
elev=123.4 ; Elevation of Antenna in Meters (NOT HAAT)
power=9 ; Power level (see below)
height=5 ; Antenna Height in HAAT (see below)
gain=8 ; Antenna Gain (see below)
dir=0 ; Antenna Direction (see below)

On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > >> >> telesistant@hotmail.comwrote:

There have (obviously) been some changes/improvements made to the
Echolink and APRS/GPS subsystems within app_rpt.

Included in these is the ability for a node to report its “fixed”
GPS
coordinates
to the APRS network, even if it does not have a GPS receiver
connected.

Please see the following:

Setting up Echolink Connectivity
http://209.159.155.200/drupal/node/56

Setting Up APRS and GPS Configuration
http://209.159.155.200/drupal/node/179

Of course, the latest copies of app_gps and chan_echolink need to be
downloaded from the SVN.

JIM WB6NIL


App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org


App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org

Since adding the gps.conf, which is working and puts me on the aprs maps, I started getting the following messages on the console….
[Jan 24 08:59:57] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:07] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:17] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:27] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:37] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:47] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

I then enabled debugging in the gps.conf file and this is what I got…

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:22] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers “Asterisk app_gps”

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468

[Jan 24 09:14:32] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:32] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:42] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:42] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:52] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers “Asterisk app_gps”

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468

[Jan 24 09:15:02] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:15:02] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

**I suspect that it is expecting a radio to be connected for it to send packets out over the air. **

How do I configure this so it can work or, if that isn’t what it is about, then how do I get rid of the warning?

Chuck Henderson, WB9UUS

···

On Sun, Jan 23, 2011 at 6:42 PM, Jim Duuuude telesistant@hotmail.com wrote:

it was!! :slight_smile:

Date: Mon, 24 Jan 2011 00:27:16 +0200
Subject: RE: [App_rpt-users] aprs password for app_gps
From: yo3iiu@yo3iiu.ro
To: telesistant@hotmail.com

CC: yo3iiu@yo3iiu.ro; rpt2@chuck.midlandsnetworking.com; app_rpt-users@ohnosec.org

The protocol is quite simple and the source for callpass is included in
the xastir source. Though, reverse engineering it seems a lot more fun :slight_smile:

Regards,

Bogdan - YO3IIU

The heck with all this confusion regarding APRS passwords!!

I just reverse engineered the password algorithm and will make
a password generator (and will also automatically generate a password

for Portal-generate configurations).

JIM

Date: Sun, 23 Jan 2011 15:49:55 +0200
From: yo3iiu@yo3iiu.ro

To: rpt2@chuck.midlandsnetworking.com
CC: app_rpt-users@ohnosec.org

Subject: Re: [App_rpt-users] aprs password for app_gps

The APRS-IS password could be generated using the callpass utility that
comes with xastir.

Bogdan - YO3IIU

I would like to set up my allstarlink system to report position
information
to the aprs system.

Can someone tell me how to set up this password? Also, are the
default
server and port listed in the example below what should be used?
I have searched the aprs site and couldn’t find who to request this

information from.

Chuck Henderson, WB9UUS

; Configuration for app_gps

;
[general]

call = wb9uus-2 ; callsign (including SSID) for APRS
purposespassword
= 12345 ; Password for APRS-IS server for above callsign

comment = AllStar Node 27468 ; Text to be displayed associated with
this
station*server = second.aprs.net ; APRS-IS server to report

information

to**port = 10151 ; port on server to send data*
icon = r ; A CAR (default) Icon do be displayed for station on
APRS
display (see below)

comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this
only
if using GPS receiver)
baudrate = 4800 ; Baud rate for GPS receiver (specify this only if

using GPS receiver)
;debug = y ; set this for debug output
freq=442.700 ; Display Frequency of station
tone=107.2 ; CTCSS tone of station (0.0 for none)

lat=40.508 ; Fixed (default) latitude in decimal degrees
lon=-88.988 ; Fixed (default) longitude in decimal degrees
elev=123.4 ; Elevation of Antenna in Meters (NOT HAAT)

power=9 ; Power level (see below)
height=5 ; Antenna Height in HAAT (see below)
gain=8 ; Antenna Gain (see below)
dir=0 ; Antenna Direction (see below)

On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > > >> >> telesistant@hotmail.comwrote:

There have (obviously) been some changes/improvements made to the
Echolink and APRS/GPS subsystems within app_rpt.

Included in these is the ability for a node to report its “fixed”
GPS
coordinates
to the APRS network, even if it does not have a GPS receiver

connected.

Please see the following:

Setting up Echolink Connectivity
http://209.159.155.200/drupal/node/56

Setting Up APRS and GPS Configuration
http://209.159.155.200/drupal/node/179

Of course, the latest copies of app_gps and chan_echolink need to be
downloaded from the SVN.

JIM WB6NIL


App_rpt-users mailing list

App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users


App_rpt-users mailing list
App_rpt-users@ohnosec.org

http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

seeing the same thing…

Also...is there any variable possible to set to cut down the

reporting interval? For a stationary system…like a
repeater…every 30 seconds seems a bit much (maybe if it was
located on the San Andreas fault, it would be moving, though…;))

···

-- 73 all...and thanks, Jim, for the great functionality.
Bryan
Echolink WB0YLE-R
Allstar 27294
APRS WB0YLE-8
LS/MFT
YMMV
ROTFLMAO
etc...

could you send me a tarball of your entire /etc/asterisk directory, so that I may duplicate
the problem here?

Thanks

JIM

···

From: rpt2@chuck.midlandsnetworking.com
Date: Mon, 24 Jan 2011 09:32:41 -0600
Subject: Re: [App_rpt-users] aprs password for app_gps
To: app_rpt-users@ohnosec.org
CC: telesistant@hotmail.com
Since adding the gps.conf, which is working and puts me on the aprs maps, I started getting the following messages on the console….
[Jan 24 08:59:57] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:07] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:17] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:27] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:37] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:47] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

I then enabled debugging in the gps.conf file and this is what I got…

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:22] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers “Asterisk app_gps”

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468

[Jan 24 09:14:32] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:32] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:42] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:42] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:52] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers “Asterisk app_gps”

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468

[Jan 24 09:15:02] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:15:02] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

**I suspect that it is expecting a radio to be connected for it to send packets out over the air. **

How do I configure this so it can work or, if that isn’t what it is about, then how do I get rid of the warning?

Chuck Henderson, WB9UUS

On Sun, Jan 23, 2011 at 6:42 PM, Jim Duuuude telesistant@hotmail.com wrote:

it was!! :slight_smile:

Date: Mon, 24 Jan 2011 00:27:16 +0200
Subject: RE: [App_rpt-users] aprs password for app_gps
From: yo3iiu@yo3iiu.ro
To: telesistant@hotmail.com

CC: yo3iiu@yo3iiu.ro; rpt2@chuck.midlandsnetworking.com; app_rpt-users@ohnosec.org

The protocol is quite simple and the source for callpass is included in
the xastir source. Though, reverse engineering it seems a lot more fun :slight_smile:

Regards,

Bogdan - YO3IIU

The heck with all this confusion regarding APRS passwords!!

I just reverse engineered the password algorithm and will make
a password generator (and will also automatically generate a password

for Portal-generate configurations).

JIM

Date: Sun, 23 Jan 2011 15:49:55 +0200
From: yo3iiu@yo3iiu.ro

To: rpt2@chuck.midlandsnetworking.com
CC: app_rpt-users@ohnosec.org

Subject: Re: [App_rpt-users] aprs password for app_gps

The APRS-IS password could be generated using the callpass utility that
comes with xastir.

Bogdan - YO3IIU

I would like to set up my allstarlink system to report position
information
to the aprs system.

Can someone tell me how to set up this password? Also, are the
default
server and port listed in the example below what should be used?
I have searched the aprs site and couldn’t find who to request this

information from.

Chuck Henderson, WB9UUS

; Configuration for app_gps

;
[general]

call = wb9uus-2 ; callsign (including SSID) for APRS
purposespassword
= 12345 ; Password for APRS-IS server for above callsign

comment = AllStar Node 27468 ; Text to be displayed associated with
this
station*server = second.aprs.net ; APRS-IS server to report

information

to**port = 10151 ; port on server to send data*
icon = r ; A CAR (default) Icon do be displayed for station on
APRS
display (see below)

comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this
only
if using GPS receiver)
baudrate = 4800 ; Baud rate for GPS receiver (specify this only if

using GPS receiver)
;debug = y ; set this for debug output
freq=442.700 ; Display Frequency of station
tone=107.2 ; CTCSS tone of station (0.0 for none)

lat=40.508 ; Fixed (default) latitude in decimal degrees
lon=-88.988 ; Fixed (default) longitude in decimal degrees
elev=123.4 ; Elevation of Antenna in Meters (NOT HAAT)

power=9 ; Power level (see below)
height=5 ; Antenna Height in HAAT (see below)
gain=8 ; Antenna Gain (see below)
dir=0 ; Antenna Direction (see below)

On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > > >> >> telesistant@hotmail.comwrote:

There have (obviously) been some changes/improvements made to the
Echolink and APRS/GPS subsystems within app_rpt.

Included in these is the ability for a node to report its “fixed”
GPS
coordinates
to the APRS network, even if it does not have a GPS receiver

connected.

Please see the following:

Setting up Echolink Connectivity
http://209.159.155.200/drupal/node/56

Setting Up APRS and GPS Configuration
http://209.159.155.200/drupal/node/179

Of course, the latest copies of app_gps and chan_echolink need to be
downloaded from the SVN.

JIM WB6NIL


App_rpt-users mailing list

App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users


App_rpt-users mailing list
App_rpt-users@ohnosec.org

http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

also, did you update everything to the latest SVN, or just app_gps and chan_echolink??

My copy of chan_usbradio.c does not have that line in the same location, which leads me to
believe that you didnt update from the whole SVN.

Heck, just send me a copy of your chan_usbradio.c file, too while youre at it.

Thanks

JIM

···

From: rpt2@chuck.midlandsnetworking.com
Date: Mon, 24 Jan 2011 09:32:41 -0600
Subject: Re: [App_rpt-users] aprs password for app_gps
To: app_rpt-users@ohnosec.org
CC: telesistant@hotmail.com
Since adding the gps.conf, which is working and puts me on the aprs maps, I started getting the following messages on the console….
[Jan 24 08:59:57] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:07] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:17] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:27] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:37] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:47] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

I then enabled debugging in the gps.conf file and this is what I got…

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:22] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers “Asterisk app_gps”

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468

[Jan 24 09:14:32] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:32] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:42] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:42] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:52] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers “Asterisk app_gps”

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468

[Jan 24 09:15:02] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:15:02] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

**I suspect that it is expecting a radio to be connected for it to send packets out over the air. **

How do I configure this so it can work or, if that isn’t what it is about, then how do I get rid of the warning?

Chuck Henderson, WB9UUS

On Sun, Jan 23, 2011 at 6:42 PM, Jim Duuuude telesistant@hotmail.com wrote:

it was!! :slight_smile:

Date: Mon, 24 Jan 2011 00:27:16 +0200
Subject: RE: [App_rpt-users] aprs password for app_gps
From: yo3iiu@yo3iiu.ro
To: telesistant@hotmail.com

CC: yo3iiu@yo3iiu.ro; rpt2@chuck.midlandsnetworking.com; app_rpt-users@ohnosec.org

The protocol is quite simple and the source for callpass is included in
the xastir source. Though, reverse engineering it seems a lot more fun :slight_smile:

Regards,

Bogdan - YO3IIU

The heck with all this confusion regarding APRS passwords!!

I just reverse engineered the password algorithm and will make
a password generator (and will also automatically generate a password

for Portal-generate configurations).

JIM

Date: Sun, 23 Jan 2011 15:49:55 +0200
From: yo3iiu@yo3iiu.ro

To: rpt2@chuck.midlandsnetworking.com
CC: app_rpt-users@ohnosec.org

Subject: Re: [App_rpt-users] aprs password for app_gps

The APRS-IS password could be generated using the callpass utility that
comes with xastir.

Bogdan - YO3IIU

I would like to set up my allstarlink system to report position
information
to the aprs system.

Can someone tell me how to set up this password? Also, are the
default
server and port listed in the example below what should be used?
I have searched the aprs site and couldn’t find who to request this

information from.

Chuck Henderson, WB9UUS

; Configuration for app_gps

;
[general]

call = wb9uus-2 ; callsign (including SSID) for APRS
purposespassword
= 12345 ; Password for APRS-IS server for above callsign

comment = AllStar Node 27468 ; Text to be displayed associated with
this
station*server = second.aprs.net ; APRS-IS server to report

information

to**port = 10151 ; port on server to send data*
icon = r ; A CAR (default) Icon do be displayed for station on
APRS
display (see below)

comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this
only
if using GPS receiver)
baudrate = 4800 ; Baud rate for GPS receiver (specify this only if

using GPS receiver)
;debug = y ; set this for debug output
freq=442.700 ; Display Frequency of station
tone=107.2 ; CTCSS tone of station (0.0 for none)

lat=40.508 ; Fixed (default) latitude in decimal degrees
lon=-88.988 ; Fixed (default) longitude in decimal degrees
elev=123.4 ; Elevation of Antenna in Meters (NOT HAAT)

power=9 ; Power level (see below)
height=5 ; Antenna Height in HAAT (see below)
gain=8 ; Antenna Gain (see below)
dir=0 ; Antenna Direction (see below)

On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > > >> >> telesistant@hotmail.comwrote:

There have (obviously) been some changes/improvements made to the
Echolink and APRS/GPS subsystems within app_rpt.

Included in these is the ability for a node to report its “fixed”
GPS
coordinates
to the APRS network, even if it does not have a GPS receiver

connected.

Please see the following:

Setting up Echolink Connectivity
http://209.159.155.200/drupal/node/56

Setting Up APRS and GPS Configuration
http://209.159.155.200/drupal/node/179

Of course, the latest copies of app_gps and chan_echolink need to be
downloaded from the SVN.

JIM WB6NIL


App_rpt-users mailing list

App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users


App_rpt-users mailing list
App_rpt-users@ohnosec.org

http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

Agreed, it would be good if there was a way to set this interval.

···

--
Tim
:wq

On Jan 24, 2011, at 8:00 AM, Bryan D. Boyle wrote:

Also...is there any variable possible to set to cut down the reporting interval? For a stationary system...like a repeater...every 30 seconds seems a bit much

Ladies & Gentlemen…

The simplest solution to get individual APR passcodes is to use the APRSPASS program that’s installed with APRSD. There’s nothing mysterious or secret about acquiring APRS passcodes. Here’s a cut and paste about APRSPASS:

···

APRS passcode calculator (new in 2.1.1)

The aprspass program is located in the /home/aprsd2 directory. You may move it to another more convienient location if you wish. To determine the aprs passcode required for a callsign “N0CALL”:

Change to the /home/aprsd2 directory.

./aprspass N0CALL
APRS passcode for N0CALL = 12345

I’ve used APRSPASS to generate passwords for several programs, including UIVIEW32, javAPRS, APRSD, Xastir, etc.

I hope this is what you were looking for, and has helped to solve your problems.


Best regards,

Gary E. Kohtala - K7EK / AFF0WA / AFA0IU / AFE0DM

Personal Web Page: www dot k7ek dot net

On Mon, Jan 24, 2011 at 8:57 AM, Jim Duuuude telesistant@hotmail.com wrote:

could you send me a tarball of your entire /etc/asterisk directory, so that I may duplicate
the problem here?

Thanks

JIM


From: rpt2@chuck.midlandsnetworking.com
Date: Mon, 24 Jan 2011 09:32:41 -0600

Subject: Re: [App_rpt-users] aprs password for app_gps

To: app_rpt-users@ohnosec.org
CC: telesistant@hotmail.com

Since adding the gps.conf, which is working and puts me on the aprs maps, I started getting the following messages on the console….
[Jan 24 08:59:57] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:07] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:17] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:27] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:37] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:00:47] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

I then enabled debugging in the gps.conf file and this is what I got…

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:22] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers “Asterisk app_gps”

[Jan 24 09:14:22] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468

[Jan 24 09:14:32] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:32] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:42] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:42] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:14:52] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:518 gpsthread: sent packet: user wb9uus-r pass 18598 vers “Asterisk app_gps”

[Jan 24 09:14:52] NOTICE[2658]: app_gps.c:527 gpsthread: sent packet: wb9uus-r>APRS,qAR,wb9uus-VS:=4030.48N/08859.28WrPHG9580/AllStar Node 27468

[Jan 24 09:15:02] NOTICE[2658]: app_gps.c:456 gpsthread: got lat: 4030.48N, long: 08859.28W, elev: 123.4M

[Jan 24 09:15:02] WARNING[2659]: chan_usbradio.c:2152 sound_thread: select failed: Interrupted system call

**I suspect that it is expecting a radio to be connected for it to send packets out over the air. **

How do I configure this so it can work or, if that isn’t what it is about, then how do I get rid of the warning?

Chuck Henderson, WB9UUS

On Sun, Jan 23, 2011 at 6:42 PM, Jim Duuuude telesistant@hotmail.com wrote:

it was!! :slight_smile:

Date: Mon, 24 Jan 2011 00:27:16 +0200
Subject: RE: [App_rpt-users] aprs password for app_gps
From: yo3iiu@yo3iiu.ro
To: telesistant@hotmail.com

CC: yo3iiu@yo3iiu.ro; rpt2@chuck.midlandsnetworking.com; app_rpt-users@ohnosec.org

The protocol is quite simple and the source for callpass is included in
the xastir source. Though, reverse engineering it seems a lot more fun :slight_smile:

Regards,
Bogdan - YO3IIU

The heck with all this confusion regarding APRS passwords!!

I just reverse engineered the password algorithm and will make
a password generator (and will also automatically generate a password

for Portal-generate configurations).

JIM

Date: Sun, 23 Jan 2011 15:49:55 +0200
From: yo3iiu@yo3iiu.ro

To: rpt2@chuck.midlandsnetworking.com
CC: app_rpt-users@ohnosec.org

Subject: Re: [App_rpt-users] aprs password for app_gps

The APRS-IS password could be generated using the callpass utility that
comes with xastir.

Bogdan - YO3IIU

I would like to set up my allstarlink system to report position
information
to the aprs system.

Can someone tell me how to set up this password? Also, are the
default
server and port listed in the example below what should be used?
I have searched the aprs site and couldn’t find who to request this

information from.

Chuck Henderson, WB9UUS

; Configuration for app_gps

;
[general]

call = wb9uus-2 ; callsign (including SSID) for APRS
purposespassword
= 12345 ; Password for APRS-IS server for above callsign

comment = AllStar Node 27468 ; Text to be displayed associated with
this
station*server = second.aprs.net ; APRS-IS server to report

information

to**port = 10151 ; port on server to send data*
icon = r ; A CAR (default) Icon do be displayed for station on
APRS
display (see below)

comport = /dev/ttyS0 ; Serial port for GPS receiver (specify this
only
if using GPS receiver)
baudrate = 4800 ; Baud rate for GPS receiver (specify this only if

using GPS receiver)
;debug = y ; set this for debug output
freq=442.700 ; Display Frequency of station
tone=107.2 ; CTCSS tone of station (0.0 for none)

lat=40.508 ; Fixed (default) latitude in decimal degrees
lon=-88.988 ; Fixed (default) longitude in decimal degrees
elev=123.4 ; Elevation of Antenna in Meters (NOT HAAT)

power=9 ; Power level (see below)
height=5 ; Antenna Height in HAAT (see below)
gain=8 ; Antenna Gain (see below)
dir=0 ; Antenna Direction (see below)

On Sat, Jan 22, 2011 at 10:30 PM, Jim Duuuude > > > >> >> telesistant@hotmail.comwrote:

There have (obviously) been some changes/improvements made to the
Echolink and APRS/GPS subsystems within app_rpt.

Included in these is the ability for a node to report its “fixed”
GPS
coordinates
to the APRS network, even if it does not have a GPS receiver

connected.

Please see the following:

Setting up Echolink Connectivity
http://209.159.155.200/drupal/node/56

Setting Up APRS and GPS Configuration
http://209.159.155.200/drupal/node/179

Of course, the latest copies of app_gps and chan_echolink need to be
downloaded from the SVN.

JIM WB6NIL


App_rpt-users mailing list

App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users


App_rpt-users mailing list
App_rpt-users@ohnosec.org

http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users


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