OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   27.05.03 21:07l 328 Lines 9880 Bytes #999 (0) @ WW
BID : 1390-ZL3AI
Read: GUEST
Subj: TAPR Digest, May 24, 1/3
Path: DB0FHN<DB0RGB<OE5XBL<OE3XSR<OK0PCC<OK0NAG<OK0PPL<DB0RES<ON0AR<ZL2BAU<
      ZL3VML
Sent: 030526/1328Z @:ZL3VML.#80.NZL.OC #:1085 [Chch-NZ] FBB7.00i $:1390-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

TAPR APRS Special Interest Group Digest for Saturday, May 24, 2003.

1. Error output from xastir
2. Re: GE master II
3. Re: aprssig digest: May 23, 2003
4. Re: [amsat-bb] PCSAT2 (prototype) on AIR
5. RE: Certification???
6. Re: Error output from xastir
7. WINAPRS / TCP
8. Re: WINAPRS / TCP
9. Re: Error output from xastir
10. Deluo GPS/Dr-135
11. Excessive Path?!
12. Re: Deluo GPS/Dr-135
13. Balloon Position Report Page
14. Re: Balloon Position Report Page
15. RE: Garmin Rhino?
16. Re: Balloon Position Report Page
17. RE: Garmin Rhino?
18. mic-e progress report
19. RE: Garmin Rhino?
20. RE: Garmin Rhino?
21. RE: Garmin Rhino?
22. ANET/Radio Mirror/HAM WEB
23. RE: Garmin Rhino?
24. field day
25. RE: Garmin Rhino?
26. Manual for IC-T8A

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

Subject: Error output from xastir
From: Andrew Rich <andrew.rich@bigpond.com>
Date: 24 May 2003 17:57:37 +1000
X-Message-Number: 1

Am I missing something ?

Warning:
    Name: create_appshell text_output2
    Class: XmTextField
    Character '\260' not supported in font.  Discarded.

Warning:
    Name: create_appshell text_output2
    Class: XmTextField
    Character '\260' not supported in font.  Discarded.

Warning:
    Name: create_appshell text_output2
    Class: XmTextField
    Character '\260' not supported in font.  Discarded.

Warning:
    Name: create_appshell text_output2
    Class: XmTextField
    Character '\260' not supported in font.  Discarded.

-- 
Andrew Rich <andrew.rich@bigpond.com>

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

Subject: Re: GE master II
From: kd4ydc@juno.com
Date: Sat, 24 May 2003 09:02:11 GMT
X-Message-Number: 2

Wes,
Without me digging through my notebook, I can remember seeing varing
voltages from 5 to 8 or so volts (not from the same rig ;-)  Keep in mind
that the RUS can do the same thing probably to a little lower degree than
the COR.  A good source of GE stuff is at
http://www.repeater-builder.com/rbtip/geindex.html .  I watching am
watching this thread with "baited breath" ;-)

Thanks,
Robert
KD4YDC

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

Subject: Re: aprssig digest: May 23, 2003
From: rwf <rwf@bsrg.org>
Date: Sat, 24 May 2003 08:22:42 -0400
X-Message-Number: 3

It goes "High" on received signal.
Level is about 10 volts.
Signal is on CAS and RUS
There is a slight difference in hysteresis between the two.

Ralph
N4NEQ

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

Subject: Re: [amsat-bb] PCSAT2 (prototype) on AIR
From: Bob Bruninga <bruninga@usna.edu>
Date: Sat, 24 May 2003 08:25:55 -0400 (EDT)
X-Message-Number: 4

>>PCSAT2 prototype is on the air in Annapolis, Maryland (USA)
>> *APRS/UI digipeater  (145.825 up and down)
>> *PSK-31 transponder  (10m ssb up 435.250 down) (see note below)
>> *FM Voice repeater.  (145.800 up 437.975 down)
>>See:     http://web.usna.navy.mil/~bruninga/pcsat2.html

After putting it on the air, I had family obligations and so could only
monitor it with the APRS radio in my car.  But just half way to our
appointement, I started hearing lots of packets.  I thought, wow, someone
is trying it already.

Then I noticed that most of the packets were from PCsat who must have just
come over the horizon.  Then I had the brilliant idea of trying a
cross-satellite link (what PCSAT2 is deisgned for)....  But then my idea
was dashed by the realization that PCSAT2 is operating through 200' of
coax from the basement.

But, on a CLEAR day with no chance of rain, it will be fun to roll PCSAT2
outside into the open air (no coax loss) and let everyone digi through it
by going through PCsat first.  In fact, lets plan on it for Tuesday.

The near noontime pass when PCsat goes over the east coast.  The path will
be to digi via APRSAT,APRSAT,APRSAT so that it gets through PCsat, then
PCSAT2 and back to PCsat and to you.

Bob

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

Subject: RE: Certification???
From: "Bob D." <n2iph@comcast.net>
Date: Sat, 24 May 2003 09:06:06 -0400
X-Message-Number: 5

>>Certification???

As in the manufacturers certification of the equipment, 
NOT the operators certification(license).

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

Subject: Re: Error output from xastir
From: "J. Lance Cotton" <joe@lightningflash.net>
Date: Sat, 24 May 2003 09:14:25 -0500
X-Message-Number: 6

You're probably using RedHat, which uses Unicode unicode for text display.

Xastir doesn't jive with that (yet).

From the Xastir FAQ:
    4.13 Why do I see "Character '\55' not supported in font"?

    This message and similar have to do with localization and OpenMotif/
    Lesstif.  For most of us this is a benign message and can be ignored.
    If you simply can't stand it any more set LANG = C or en_US.  In RH 9
    the default LANG is set to en_US.UTF-8 and this is where the "warning"
    are coming from.

    A quick way to address this on RedHat 8 and 9 is to edit your
    /etc/sysconfig/i18n config file.  I believe the original file looks
    like:

    LANG="en_US.UTF-8"
    SUPPORTED="en_US.UTF-8:en_US:en"
    SYSFONT="latarcyrheb-sun16"

    Change the "LANG=" line to:

    LANG="en_US"

    and reboot.

J. Lance Cotton, KJ5O
joe@lightningflash.net
Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat the
cookies.

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

Subject: WINAPRS / TCP
From: Skip Allison <skipk9sa@ameritech.net>
Date: Sat, 24 May 2003 09:12:40 -0500
X-Message-Number: 7

WINAPRS starts up every time trying to connect TCP/IP.  I must have done
something to get it to do that, but I can't figure out what.  Anybody
know how to keep it from connecting to TCP/IP every time I start the
program?

Skip
K9SA

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

Subject: Re: WINAPRS / TCP
From: "Dick Stanich" <dick@kb7zva.com>
Date: Sat, 24 May 2003 10:4:38
X-Message-Number: 8

Settings, TCP/IP Connections, TCP server settings. Unchecked all the 
boxes... Autostart TCP connection (random APRS server), etc.

Hope that helps.

Dick, KB7ZVA
APRSWEST
http://kb7zva.com

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

Subject: Re: Error output from xastir
From: "Curt Mills, WE7U" <archer@eskimo.com>
Date: Sat, 24 May 2003 07:45:46 -0700 (PDT)
X-Message-Number: 9

On 24 May 2003, Andrew Rich wrote:

Wrong mailing list.

>Am I missing something ?
> 
>Warning:
>  Name: create_appshell text_output2
>  Class: XmTextField
>  Character '\260' not supported in font.  Discarded.

Yea.  Read the FAQ.  You're probably running RedHat, and they changed
to unicode fonts.

Curt, WE7U.				archer@eskimo.com
http://www.eskimo.com/~archer
  Lotto:  A tax on people who are bad at math. - unknown
Windows:  Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me:  I picked the coordinate system!"

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

Subject: Deluo GPS/Dr-135
From: Stan <stan911@optonline.net>
Date: Sat, 24 May 2003 11:56:10 -0400
X-Message-Number: 10

Have a tracker using the Deluo GPS and an Alinco DR-135. Seems to work OK
but I don't get an altitude readout. Wondering if it's something I missed.
Stan N2NKI

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

Subject: Excessive Path?!
From: "M. Schneider" <msokla@brightok.net>
Date: Sat, 24 May 2003 11:34:35 -0500
X-Message-Number: 11

Saw this station show up on my APRS screen, and I think this path is a bit
over the top.
From Findu:

Position of KD5STN

19.1 miles northwest of FAYETTEVILLE, AR

Status: 190128zARES/RACES I-Gate - Benton County

Raw packet:
KD5STN>APU256,DECATU,CLRMRE*,TRACE7-5,WIDE3-3,I,qAO,KD5LDQ:=3622.94N/09412.7
2WIAPRS I-Gate www.bcar.us

This guy is an I-gate, does he really need TRACE7-7,WIDE3-3?  When he makes
it to Stillwater, OK (my QTH, 159 miles away), he's still got
TRACE7-2,WIDE3-3

Perhaps somebody in the Benton County, Arkansas area could get with him on
his path?

Mark Schneider - K5MAR

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

Subject: Re: Deluo GPS/Dr-135
From: "Kurt O. Jauss" <kf6hjo@earthlink.net>
Date: Sat, 24 May 2003 09:54:23 -0700
X-Message-Number: 12

Your GPST in the Alinco is probably set to $GPRMC. This gives you course 
and speed. $GPGGA will give you altitude but not course and speed.

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

Subject: Balloon Position Report Page
From: "Russ Chadwick" <russ@wxqa.com>
Date: Sat, 24 May 2003 19:05:17 -0000
X-Message-Number: 13

Many of you may not be aware of yet another use for APRS-IS and findu.com.
People involved in amateur balloonacy often need to notify the FAA as to the
location of their balloons.  Using position data collected by APRS-IS and
findu.com the Balloon Position Report Page provides a way to get this
information to the FAA air traffic controllers in near-real time.  Access to
this page is through

http://www.wxqa.com/

and then go to the bottom of the page and click on Balloon Position Report.

If you select Hugo-11 (a simulated balloon above the Hugo VOR), and the BRK
and LAA VORs, you can see the same display that an FAA controller would see
for a balloon about 25,000 feet above the Hugo VOR.  Also, if you look at
the position of the simulated balloon and go to the overhead photo link at
the bottom of the findu map page, you'll get an overhead view of the Hugo
VOR.

The Balloon Position Report Page was developed by a team consisting of,

Russ Chadwick  KB0TVJ
Steve Dimse  K4HG
Nick Hanks  N0LP
Joe Chadwick  KB0TVK
Michelle Smith  FAA

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



Read previous mail | Read next mail


 14.11.2026 06:40:09lGo back Go up