| |
ZL3AI > APRDIG 23.06.03 09:20l 187 Lines 6995 Bytes #999 (0) @ WW
BID : 1519-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jun 20, 2/2
Path: DB0FHN<DB0RGB<OK0PPL<RZ6HXA<SP7MGD<7M3TJZ<ZL2TZE<N1UAN<ZL2BAU<ZL3VML
Sent: 030622/1332Z @:ZL3VML.#80.NZL.OC #:2890 [Chch-NZ] FBB7.00i $:1519-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Wx problem
From: Linda <ad4bl@mosquitonet.com>
Date: Fri, 20 Jun 2003 12:56:41 -0800
X-Message-Number: 9
I am switching my APRS program to a different computer. I finally got
my APRS program to run...using DosAPRS851 on com1 at 1200b. I have a
Davis Wx Monitor II on com4 set up at 2400b [which is what Davis sets]
and I have it in the APRS config file but APRS is not picking up the wx
at all. Davis WX will run coms 1-4 and I have confirmed that the wx
station is working fine on com4. How do I get the wx station to work
with APRS? It worked fine on the old computer.
--
Linda <><
Linda AD4BL
ALASKA SEC STM
ad4bl@mosquitonet.com
Fairbanks, Alaska
He came to pay a debt He didn't owe,
because we owed a debt we couldn't pay!
----------------------------------------------------------------------
Subject: Re: Wx problem
From: Bob Bruninga <bruninga@usna.edu>
Date: Fri, 20 Jun 2003 18:09:20 -0400 (EDT)
X-Message-Number: 10
On Fri, 20 Jun 2003, Linda wrote:
>I am switching my APRS program to a different computer. I finally got
>my APRS program to run...using DosAPRS851 on com1 at 1200b. I have a
>Davis Wx Monitor II on com4 set up at 2400b [which is what Davis sets]
>and I have it in the APRS config file but APRS is not picking up the wx
>at all. Davis WX will run coms 1-4 and I have confirmed that the wx
>station is working fine on com4. How do I get the wx station to work
>with APRS? It worked fine on the old computer.
Unfortunately, APRSdos only works on COM1 and Com2.
That was all that Bill Gates QBASIC would allow...(back then)
Sorry...
BOb
de WB4APR@amsat.org, Bob
PCsat WEB page http://www.ew.usna.edu/~bruninga/pcsat.html
ISS-APRS FAQ: http://www.ew.usna.edu/~bruninga/iss-faq.html
CUBESAT Designs http://www.ew.usna.edu/~bruninga/cubesat.html
APRS LIVE pages http://www.ew.usna.edu/~bruninga/aprs.html
APRS SATELLITES http://www.ew.usna.edu/~bruninga/astars.html
MIM/Mic-E/Mic-Lite http://ssdl.stanford.edu/mims/
----------------------------------------------------------------------
Subject: Re: WinAPRS Support for Server Filters?
From: "Phil Pacier, AD6NH" <ad6nh@arrl.net>
Date: Fri, 20 Jun 2003 18:1:21
X-Message-Number: 11
On 06/20/03, "Dennis Hudson <n2lbt@n2lbt.com>" wrote:
>If it gets added it would be good to have it be port agile. Port 14580
>is the default raw TNC port on aprsd. aprsd's omniport portfilter
>default is 14600.
Too late to change. Port 14580 will remain the user-defined filter port as
it has been for the last 6 months. I looked at documentation for many
different server types and I never ever saw any reference to 14580. Sorry
for the confusion, but it would add much more to change at this point. 73
Phillip Pacier - AD6NH
socal.aprs2.net
http://www.aprsca.net
http://www.aprs2.net
----------------------------------------------------------------------
Subject: Re: WinAPRS Support for Server Filters?
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Fri, 20 Jun 2003 19:28:33 -0500
X-Message-Number: 12
>-----Original Message-----
>From: Dennis Hudson [mailto:n2lbt@n2lbt.com]
>Posted At: Friday, June 20, 2003 12:43 PM
>Subject: [aprssig] Re: WinAPRS Support for Server Filters?
>
>If it gets added it would be good to have it be port agile.
>Port 14580
>is the default raw TNC port on aprsd. aprsd's omniport portfilter
>default is 14600.
All of the implementations that I am aware of do not force the client to
a particular port. They simply add the filter definition to the
existing connection definition.
aprsd's omniport is not really a filter. It is a way to define the port
type that you want to connect to. It uses a different command format
than that used by javAPRSFilter. javAPRSFilter is a true APRS-IS stream
filter allowing multiple filter definitions for each client.
Omniport only supports APRS messages for commands. javAPRSSrvr supports
login, comment line and APRS messages for commands. Client support for
server filters has centered on login and/or comment line formats. I
would recommend that if the Sprouls implement a connection command
capability, they should look at the login method.
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
Subject: Re: WinAPRS Support for Server Filters?
From: Dennis Hudson <n2lbt@n2lbt.com>
Date: Fri, 20 Jun 2003 22:05:16 -0400
X-Message-Number: 13
Okey-dokey, call it what you will. But it's how I specify what data I
get from my aprsd server by sending ascii data after my login, and it
happens on port 14600.
Port 14580 has been used on aprsd servers as the default raw tnc data
for as long as I've been using it, 1998 is as far back as I can find
any of my own documentation. I really don't care what happens on that
port on other servers. I'm really only concerned that users don't
expect something else when connecting to my server or any of the other
hundreds of aprsd servers on that port.
73,
Dennis, N2LBT
--
Dennis, N2LBT
Sysop aprsdALY IGate
http://www.n2lbt.com
n2lbt@n2lbt.com
----------------------------------------------------------------------
Subject: Re: WinAPRS Support for Server Filters?
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Fri, 20 Jun 2003 21:57:14 -0500
X-Message-Number: 14
Hundreds, huh? No matter. I was simply quoting from the documentation
for the latest version of aprsd on Sourceforge. It does say "The
command may be issued in raw ascii form prior to user logon or as a
message addressed to "SERVER" after logon." If they have added the
ability to put the command on the same line as the login, it is not
specified in the documentation. The documentation also says "Currently
the only filter available is the Port Filter." which indicates that no
filtering beyond standard port type filtering is implemented.
javAPRSSrvr is not tied to any specific ports as aprsd is. The choice
by many sysops for port 14580 is their choice, not dictated by software.
There is no "standard" port specification for APRS-IS as there is no
APRS-IS specification. There is also no "command" specification for
filters, etc. for the same reason. If you want to make sure that users
of your server know which ports are available and their capabilities, I
recommend you put in your status page a link to a web page showing
those. Most javAPRSSrvr servers (not hundreds, but substantially more
than 10 :-) make use of a port table on the status page to inform their
users of available ports.
I would still maintain that the client software authors focus on using
the login command format as it is apparent that the primary filter usage
is javAPRSFilter in conjunction with javAPRSSrvr (and that filtering has
been the driving force to other client adaptations). Again, this is
port number independent but gives the user access to the most flexible
filtering configurations.
73,
Pete Loveall AE5PL
pete@ae5pl.net
---
END OF DIGEST
Read previous mail | Read next mail
| |
