OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   26.10.03 16:22l 262 Lines 10208 Bytes #999 (0) @ WW
BID : 2207-ZL3AI
Read: GUEST
Subj: TAPR Digest, Oct 24, 1/4
Path: DB0FHN<DB0THA<DB0ERF<DB0MRW<DB0PV<OE2XOM<OE5XBL<OE3XSR<OK0PBX<OK0PHK<
      OK0NAG<OK0PPL<DB0RES<ON0AR<WB0TAX<IW7CHV<WA7V<VK7AX<ZL2BAU<ZL3VML
Sent: 031026/1234Z @:ZL3VML.#80.NZL.OC #:11286 [Chch-NZ] FBB7.00i $:2207-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

TAPR APRS Special Interest Group Digest for Friday, October 24, 2003.

1. RE: OpenTracker
2. Re: 48V Powerpoles?
3. Re: 48V Powerpoles?
4. Re: 48V Powerpoles?
5. RE: aprs1
6. A Low-Tech APRSteward Proposal [was: SMART digi paths]
7. Solar Wx
8. REF: nc4cv
9. RE: [amsat-bb] AO-40 data mode...  APRS???
10. Re: SMART digi paths
11. RE: OpenTracker PCB run
12. Re: OpenTracker PCB run
13. RE: OpenTracker
14. Re: Solar Wx
15. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
16. Re: Solar Wx
17. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
18. Re: 48V Powerpoles?
19. Re: 48V Powerpoles?
20. Re: 48V Powerpoles?
21. Re: 48V Powerpoles?
22. Re: 48V Powerpoles?
23. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
24. Re: 48V Powerpoles?
25. Re: 48V Powerpoles?
26. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
27. WINAPRS Problem
28. RE: WINAPRS Problem [ADDITIONAL INFO]
29. WXTrak
30. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
31. APRSdigi for DOS
32. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
33. Re: 48V Powerpoles?
34. Re: A Low-Tech APRSteward Proposal [was: SMART digi paths]
35. Re: WXTrak
36. ahubswe.net
37. RE: WXTrak
38. RE: WINAPRS Problem [ADDITIONAL INFO]

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

Subject: RE: OpenTracker
From: "Scott Miller" <scott@3xf.com>
Date: Thu, 23 Oct 2003 21:05:01 -0700
X-Message-Number: 1

Motorola MC68HC908KX8.  Sorry, haven't got all the labels straightened out
yet - especially for the custom symbols.  It's an HC08 family part, a
descendant of the HC05 with a 16-bit index register.  It's got about 8k of
flash and 192 bytes of RAM.  It's probably $2.50 more than the PIC used by
the TT3, but I think it's generally more capable.  In any case, I don't
like the PIC architecture.

Scott
N1VG

-----Original Message-----
From: Adi Linden [mailto:adil@adis.on.ca]
Sent: Thursday, October 23, 2003 8:45 PM
To: Scott Miller
Cc: TAPR APRS Special Interest Group
Subject: Re: [aprssig] OpenTracker

>A couple more items... first, the current draft of the schematic is at
>http://www.opentrac.org/opentracker-schematic.png.  Second, I'd like to

What processor is on there?

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

Subject: Re: 48V Powerpoles?
From: "Mark Fellhauer" <sparkfel@qwest.net>
Date: Thu, 23 Oct 2003 21:36:54 -0700
X-Message-Number: 2

At 07:55 AM 10/23/2003, Dave VanHorn wrote:

>So now that the day of 48V is approaching, any ideas on standards?

Gonna need something to prevent arcing...

Mark
KC7BXS

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

Subject: Re: 48V Powerpoles?
From: Dale Blanchard <wa7ixk@arrl.net>
Date: Thu, 23 Oct 2003 22:07:32 -0700
X-Message-Number: 3

Power poles will handle 48 volts. and not arc. The are used on 125 v ac in
a lot of places. I just don't understand why go to 42 volts instead of 24
or 48. 24 v has been standard in the military for ever.. 36 v on electric
golf carts and some other wierd things.  Even most of the big trucks are on
12 volts now instead of 24. The electric cars run as high as 150 volts. All
you gain is smaller wire, which makes every thing else smaller and lighter.
Any way that 42 v thing buggs me as why that particulay voltage, unless it
is political. And the more cells in the battery pack the more potential
problems you are going to have.

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

Subject: Re: 48V Powerpoles?
From: "Laurie - g6isy" <g6isy@dsl.pipex.com>
Date: Fri, 24 Oct 2003 12:15:54 +0100
X-Message-Number: 4

Dale Blanchard <wa7ixk@arrl.net> wrote:
>I just don't understand why go to 42 volts

Really it is 36v.
The 42v comes from the 14v fully charged voltage of a 12v battery.
3x12=36 ; 3x14=42

The reason for going to a higher voltage is to reduce the current that is
being drawn and hence reduce the losses (and potential for fire) in the
vehicle wiring harness.

73 Laurie - G6ISY

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

Subject: RE: aprs1
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Fri, 24 Oct 2003 06:24:32 -0500
X-Message-Number: 5

This is generated by first.aprs.net.  If you are connecting to
first.aprs.net, check the status page (http://first.aprs.net:14501) to
ensure that your login is being accepted.  If you are not connecting to
first.aprs.net, then you are seeing messages destined for someone else
who is logging on to first.aprs.net without validation (possibly the
server you are connected to).

javAPRSSrvr neither generates these messages nor does it allow these
messages to pass as they are intended only for the specific user
connecting to aprsD.

73,

Pete Loveall AE5PL
pete@ae5pl.net

>-----Original Message-----
>From: bounce-aprssig-19826@lists.tapr.org
>[mailto:bounce-aprssig-19826@lists.tapr.org] On Behalf Of
>Darrell Sutton
>Posted At: Thursday, October 23, 2003 9:52 PM
>Posted To: APRS SIG
>Conversation: [aprssig] aprs1
>Subject: [aprssig] aprs1
>
>Who sends the APRS-1 messages telling users to get
>registered.  I am running
>winaprs reg. for years and this progam tells me I need to register..

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

Subject: A Low-Tech APRSteward Proposal [was: SMART digi paths]
From: "Ev Tupis (W2EV)" <w2ev@arrl.net>
Date: Fri, 24 Oct 2003 09:03:37 -0400
X-Message-Number: 6

The "SMART digi paths" proposal seem to have two components:
#1 being a good network neighbor within a LAN, without knowing what the
   acceptible UNPROTO settings for that particular LAN
#2 reaching a particular class of client/network appliance within the LAN
   without knowing the best/shortest path to take to get there

Stepping back though...this begs the question, "since both of the facets of
the proposal include the phrase 'without knowing...' wouldn't such a
proposal be unnecessary if we would simply tell our users the information
that they seem to lack?"

Try this on for size (as a concept, don't pick apart the details):

Each LAN identifies a SINGLE digipeater AT ALTITUDE (greatest coverage) and
configures it to cyclicly TX LAN information as a BLN: to the area!  This
proposal addresses the #1 question that APRS newcomers have: "What's the best
path to use?".  When they ask it "on SIG", the answer becomes: "Power up and
lurk for 1-hour, then read your BLN's".

LTP 2 ID VIA WIDEn-N          (where n & N = LAN hop count + 1 or 2 more)
LTP 3 ID VIA WIDEn-N          (where n & N = LAN hop count + 1 or 2 more)
LTP 4 ID VIA WIDEn-N          (where n & N = LAN hop count + 1 or 2 more)

BLT 2 EVERY 00:15:00
BLT 3 EVERY 00:15:00
BLT 4 EVERY 00:15:00

LT 2 BLN1:Unattended mobile stations use national standard: RELAY,WIDE,WIDE
LT 3 BLN2:In this LAN, all others should use RELAY,TRACE2-2 and TXD of 100ms
                                                NOTE:   ^-^
                                                        may be different for u
LT 4 BLN3:Be a good network neighbor - play nice or be SUPLISTed :)

-----Optional, but worth considering-----------------------------------------
LTP 1 ID VIA TRACEn-N         (where n & N = LAN hop count + 1 or 2 more)
BLT 1 EVERY 00:30:00
LT 1 >GR##idS#PHGabcdef/      (this will display an "S-Star" icon [id-ing
                               the APRSteward] and providing enough position
                               ambiguity so as to protect your un-attended
                               asset's exact location...but being close enough
                               for 'normal' APRS operation)
-----------------------------------------------------------------------------

Ev Tupis, W2EV

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

Subject: Solar Wx
From: dale huguley <kg5qd@wxsvr.net>
Date: Fri, 24 Oct 2003 13:16:55 +0000
X-Message-Number: 7

Hi All-
 From the Space Environment Center on October 21st:
**** INTENSE ACTIVE REGIONS EMERGE ON SUN ****
Two very dynamic centers of activity have emerged on the sun. NOAA 
Region 484 developed rapidly over the past three days and is now one of 
the largest sunspot clusters to emerge during Solar Cycle 23, 
approximately 10 times larger than Earth. This region, which is nearing 
the center of the solar disk, already produced a major flare (category 
R3 Radio Blackout on the NOAA Space Weather Scales) on 19 October at 
1650 UTC. The region continues to grow, and additional substantial flare 
activity is likely.
A second intense active region is rotating around the southeast limb of 
the sun. Though the sunspot group is not yet visible, two powerful 
eruptions occurred on 21 October as seen from the LASCO instrument on 
the SOHO spacecraft. These eruptions may herald the arrival of a 
volatile active center with the potential to impact various Earth systems.
Further major eruptions are possible from these active regions as they 
rotate across the face of the sun over the next two weeks. Agencies 
impacted by solar flare radio blackouts, geomagnetic storms, and solar 
radiation storms may experience disruptions over this two-week period. 
These include satellite and other spacecraft operations, power systems, 
HF communications, and navigation systems.  *****

You will notice aprs has all of the impacted systems.  There is a major 
storm predicted for today (Oct 24th).  I modified Wxsvr this morning to 
parse all space alerts, warnings, watches etc to the apparent "from 
Call" of SECALT , and the message group is "SKYSEC".  The Hourly indices 
are still from SECIND.  This is sent as an object near Boulder Colorado 
with a "sun" icon and the solar information in the comment field.  The 
"BK" portion is the 3-hourly average Boulder Kindex - each digit 
representing 3 hours beginning at 0000z.  the scale is 0 to 9 with  5  
being a minor storm- 7  being a major storm-  9 meaning put on your 
tin-foil hat.     The flux has jumped to 183 with the a index about 6 - 
so there may be some good DX before the ionoshere goes haywire during 
the storm. 

73 de kg5qd Dale

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



Read previous mail | Read next mail


 23.10.2026 23:44:29lGo back Go up