OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   19.09.06 22:07l 249 Lines 8605 Bytes #999 (0) @ WW
BID : 8759-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 27 #12, 1/2
Path: DB0FHN<DB0MRW<OK0PPL<DB0RES<ON0AR<VK6HGR<ZL2BAU
Sent: 060915/0051Z @:ZL2BAU.#87.NZL.OC #:4156 [Waimate] $:8759-ZL3AI
From: ZL3AI@ZL2BAU.#87.NZL.OC
To  : APRDIG@WW

Today's Topics:

1. Re: Recommended IGate Connection (Joel Maslak)
2. RE: GPS Display of D700 stations (KC2MMI (Jared))
3. [OT] Some interesting Display Developments with K107 (Brian Riley)
4. RE: Recommended IGate Connection (Cap Pennell)
5. Re: Recommended IGate Connection (Joel Maslak)
6. Path Loss (Ron)
7. Re: Recommended IGate Connection (James Washer)
8. RE: Path Loss (Robert Bruninga)
9. Re: Packet Node on 144.390 ? (Patrick Green)
10. Re: Recommended IGate Connection (Charles Doughtie)
11. Re: Recommended IGate Connection (Brian Riley)
12. Re: Packet Node on 144.390 ? (Ray McKnight)
13. Re: Packet Node on 144.390 ? (Gregg Wonderly)
14. AGWTracker Users (Phillip B. Pacier)
15. RE: Packet Node on 144.390 ? (Robert Bruninga)

----------------------------------------------------------------------

Message: 1
Date: Mon, 11 Sep 2006 13:56:50 -0600
From: Joel Maslak <jmaslak-aprs_at_antelope.net>
Subject: Re: [aprssig] Recommended IGate Connection

On Sep 11, 2006, at 7:49 AM, AE5PL Lists wrote:

>If you are using aprsD as only an IGate, have it connect to port 14580
>on the servers.  This is minimal bandwidth but fully supports messaging.
>You can also use javAPRSSrvr which gives you the ability to add filters
>to the upstream login if you want to see certain other things.
>javAPRSSrvr is free for amateur use by emailing to me directly at
>pete_at_ae5pl.net (not my list address).

I moved things to port 14580.  I'm not particularly concerned about
bandwidth on my end, but I figure no use in tying up the core with packets
the core doesn't need to send.

Other than a JVM (are there any versions that are a gotcha?), are their any
requirements for running javAPRSSrvr?  Is performance going to be
reasonable on a 256 MB RAM/Pentium III 700 MHz machine?

------------------------------

Message: 2
Date: Mon, 11 Sep 2006 17:13:22 -0400
From: "KC2MMI \(Jared\)" <kc2mmi_at_verizon.net>
Subject: RE: [aprssig] GPS Display of D700 stations

] In other words what NMEA GPS's do not accept the $GPWPL
] Sentence That the D7 and D700 use to send positions to

Bob, couldn't that be rephrased a bit more to ask:
What NMEA standards implement the $GPWPL sentence?
{and}
What GPSes are known to support that NMEA version?

Many GPSes support multiple NMEA versions. Rather than try to determine
every version supported by every GPS out there...mightn't it be easier to
look at this the other way around? i.e., which NMEA versions require that
sentence to be supported, and then ask case-by-case if a particular GPS
supports that standard?
(Still a huge question!)

------------------------------

[commercial content deleted]

------------------------------

Message: 4
Date: Mon, 11 Sep 2006 14:46:05 -0700
From: "Cap Pennell" <cap_at_cruzio.com>
Subject: RE: [aprssig] Recommended IGate Connection

I was going to suggest that just like using WIDE2-1 you could use "SSn-N",
"SS"1-1 (WY1-1 in WYoming), for that one digi hop without tripping any
fill-in digis.  But that would trip the digi on top of the very tall
mountain (you mentioned) too.

The fill-in digis operate WIDE1-1 ONLY and their own MYcall, but don't
operate any "SSn-N".

Often, a _little bit_ of redundancy can be worthwhile.  Using a named digi's
MYcall is fine until that particular digi goes down.
73, Cap

>-----Original Message-----
>
>On Sep 11, 2006, at 5:19 AM, Jason Winningham wrote:
>
>>On Sep 10, 2006, at 11:08 PM, Joel Maslak wrote:
>>
>>>I'm running an IGate for a relatively small geographic area
>>>(transmit path of WIDE2-1, considering shortening even more to one
>>>specific named WIDE).
>>
>>WIDE2-1 is a one hop path; the only way to get it shorter is to
>>transmit with an empty path, direct only.
>>
>>WIDE is a one hop path element, obsolete in most areas.  WIDE2-1
>>(or WIDE1-1) is the "newN-N paradigm" equivalent.
>
>Actually, I meant to say I'd be using the actual call of the digi I'd
>be interested in (a digi that kind of sits in a hole with me, versus
>WIDE2-1 which hits both that digi and one on top of a very tall
>mountain).

------------------------------

Message: 5
Date: Mon, 11 Sep 2006 16:13:35 -0600
From: Joel Maslak <jmaslak-aprs_at_antelope.net>
Subject: Re: [aprssig] Recommended IGate Connection

On Sep 11, 2006, at 3:46 PM, Cap Pennell wrote:

>Often, a _little bit_ of redundancy can be worthwhile.  Using a named digi's
>MYcall is fine until that particular digi goes down.

True, I'll think that through and leave it as WIDE2-1 right now, maybe
changing it to WY2-2 - that's actually not a bad idea... There's not a lot
of redundancy of IGates at the local level, although almost every WIDEn-n
in the area has a local IGate.  Mine fills a very small hole.  And I'm not
sending much traffic (far more beacons than actual traffic).

Now if only I could figure out the best way to route a power wire from my
battery to my truck cab in my 2003 Chevy Silverado...probably time to get
the hole saw out.

------------------------------

Message: 6
Date: Mon, 11 Sep 2006 19:00:18 -0400
From: "Ron" <rgilson_at_adelphia.net>
Subject: [aprssig] Path Loss

While path loss between 2 and 440 is 9db, you can pick up some of the loss
with antenna gain and a lower noise floor on 440.  A local agency claims to
have better building coverage on 800mhz  vs. 164mhz and better
penenertration in tunnels.  Apparently, the higher freq. gets thru windows
etc?  Could have fool me.  Any ideas???

Ron

------------------------------

Message: 7
Date: Mon, 11 Sep 2006 16:46:29 -0700
From: James Washer <washer_at_trlp.com>
Subject: Re: [aprssig] Recommended IGate Connection

If your truck in an automatic, there's almost certainly an unused hole for
the clutch mechanism

On Mon, 11 Sep 2006 16:13:35 -0600
Joel Maslak <jmaslak-aprs_at_antelope.net> wrote:

>Now if only I could figure out the best way to route a power wire
>from my battery to my truck cab in my 2003 Chevy Silverado...probably
>time to get the hole saw out.

------------------------------

Message: 8
Date: Mon, 11 Sep 2006 20:05:57 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Path Loss

>While path loss between 2 and 440 is 9db, you can pick up
>some of the loss with antenna gain and a lower noise floor on
>440.

Very true, but note that the 9 dB applies to OMNI antennas, Which by
definition have no gain.  As soon as you add "gain" then you loose omni
coverage which is what we need for the Satellite to Mobile service I am
suggesting.

Also true that there is a lower noise, so the actual difference Might only
be 6 dB or so?  But that is a factor of 4 on Spacecraft power...

Bob, WB4APR

------------------------------

Message: 9
Date: Mon, 11 Sep 2006 21:38:34 -0500
From: "Patrick Green" <pagreen_at_gmail.com>
Subject: Re: [aprssig] Packet Node on 144.390 ?

On 9/8/06, William McKeehan <mckeehan_at_mckeehan.homeip.net> wrote:
>
>I'm really looking for reasons to give someone to NOT put a packet node
>(BBS or just PBBS) on 144.39.

Watch how busy a channel becomes when people try to connect:

Connecting to something that isn't there = 10 packets in a couple minutes.

Now add a digi that you need to get anywhere more than 10 miles around you:
20 packets and this all in 5 minutes or so.

This is one station I'm talking about ;-)

The APRS design doesn't work for conventional packet.  I recall that this
all started on 145.01 and channelized because of congestion in the late '80s

73 de Pat --- KA9SCF.

------------------------------

Message: 10
Date: Mon, 11 Sep 2006 20:34:59 -0700 (PDT)
From: Charles Doughtie <n5exy_at_yahoo.com>
Subject: Re: [aprssig] Recommended IGate Connection

Hole, no! Don't saw!

Raise the mat/carpet on the passenger side. There are probably one or more
assembly access holes covered by grommets or metal plates. Also, there may
be a space covered by the kick panels (can't think of a better word) for
the driver's left foot and the passenger's right. There are probably other
covered holes at the back of the cab for the co-ax. I am a Ford guy so I am
not certain about Chevys.

de Charlie, N5EXY
South Suburban Greater Hutto, Texas

--- James Washer <washer_at_trlp.com> wrote:
>
>If your truck in an automatic, there's almost
>certainly an unused hole for the clutch mechanism
> 
>On Mon, 11 Sep 2006 16:13:35 -0600
>Joel Maslak <jmaslak-aprs_at_antelope.net> wrote:
> 
>>Now if only I could figure out the best way to
>route a power wire
>>from my battery to my truck cab in my 2003 Chevy
>Silverado...probably
>>time to get the hole saw out.

------------------------------




Read previous mail | Read next mail


 21.02.2026 17:04:26lGo back Go up