| |
ZL3AI > APRDIG 21.08.03 14:28l 198 Lines 7983 Bytes #999 (0) @ WW
BID : 1795-ZL3AI
Read: GUEST
Subj: TAPR Digest, Aug 16, 1/1
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<VK6HGR<VK3KAY<ZL2BAU<ZL3VML
Sent: 030818/1342Z @:ZL3VML.#80.NZL.OC #:6729 [Chch-NZ] FBB7.00i $:1795-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Saturday, August 16, 2003.
1. Re: dead D700A
2. LaCrosse 2310 to KPC3+
3. APRSfl.net - fourth.aprs.net - status update...
4. Re: APRSfl.net - fourth.aprs.net - status update...
5. Re: APRSfl.net - fourth.aprs.net - status update...
6. Re: APRSfl.net - fourth.aprs.net - status update...
7. Re: APRSfl.net - fourth.aprs.net - status update...
----------------------------------------------------------------------
Subject: Re: dead D700A
From: "Sean \\The RIMBoy\\" <sean@rimboy.com>
Date: Fri, 15 Aug 2003 23:13:45 -0500 (CDT)
X-Message-Number: 1
On Fri, 15 Aug 2003, James Jefferson wrote:
>But the story doesn't end there. By replacing the fuse I was once again
>seeing voltage to the control head, but I still couldn't get it to turn
>on. I hooked up to the radios serial port and determined that it worked
>properly. Measuring the voltage to the control head showed that it put out
>the proper voltage (basically it is a filtered version of the DC input to
>the radio). I was most mystified by this, so I took apart the control head
>and fed 12 volts from my bench power supply to the input of the 7805 in
>the control head and it worked just fine. Subsequent measurements showed
>that the voltage to the control head was stable without load, but with
>load it dropped to about 4.65 volts ... not the 7+ volts required to run
>the 7805.
>
>Since I didn't have a service manual I decided not to dive into the D700
>further and repair the power supply, but instead I added a small 1 amp
>mini ATX fuse and feed the control head directly with the DC input.
One of the other things that happens (as I found out) is that it takes a
power regulator with it when that fuse blows. It to me sounds like that
is the problem since you're not getting enough voltage to the head. The
regulator as I recall looks like a regulator should (it's not SMT). The
repair shop that did the work snipped the leads and soldered a new
regulator into place (therefore avoiding work on the circuit board
itself).
Sean...
--
Believing I had supernatural powers, I slammed into a brick wall.
--Paul Simon
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
----------------------------------------------------------------------
Subject: LaCrosse 2310 to KPC3+
From: "john van sandt" <n9yrx@hotmail.com>
Date: Sat, 16 Aug 2003 09:58:03 +0000
X-Message-Number: 2
I have a KPC3+ and a Yaesu Ft8500 set up as a digipeater and it was working
great. Now I am wanting to set it up as a weather reporter to Findu. I
have the LaCrosse 2310 weather station and it is working as expected.
Can anyone help by sending the file you use to program the KPC3? Also how
did you wire up the LaCrosse to the KPC3? Do you have pin to pin
connections that you could share?
N9YRX
ARRL Clark County ILL Emergency Coordinator
ILL Section Offical Emergency Station
For present APRS location:
http://www.findu.com/cgi-bin/find.cgi?n9yrx
ARO John W. Van Sandt
1302 Beech St.
Marshall, ILL 62441
Ph 217-826-8821
----------------------------------------------------------------------
Subject: APRSfl.net - fourth.aprs.net - status update...
From: "Dave Anderson" <dandersn@citicom.com>
Date: Sat, 16 Aug 2003 17:53:23 -0400
X-Message-Number: 3
Network status update of fourth.aprs.net AKA aprsfl.net....
It was the goal of this SysOp to have a standby server in place, at a
alternate location (we have two lit network facilities), so that any single
failure in my network (we are a regional ISP) or of the server itself will
not drasticlaly affect APRS users of my server.
I utilize a F5 Big-IP load balancing appliance to allow multiple servers to
appear as one to the outside "world". (which for our network is UUnet,
Sprintlink and AT&T) The catch here is that I'm having to somewhat invent
the wheel with the F5 software, as it is not aware of how APRS-IS behaves
100%. It's all done around existing telnet redundancy features, but the
timing issues, latency issues, and duplicate packet issues has made it a
bit of an "odd" configuration.
Basically the process is setup as follows as of last nights testing. Simply
put, the F5 Box detects "telnet" sessions on the various ports aprs-is uses
on the primary server. If it sees massive connections staling out, or finds
the primary box is not accessible, it will automatically kick over to the
second box via port address translation. Due to concerns of duplicates,
i've set a 120 second time out for this to occur. At the end of that 120
seconds worth of time, the other box goes online, will at that time link up
with the other core servers, and allow connections from the outside. When
the primary box returns, 15 minutes later, it will move traffic back to the
primary box. All this moving is transparent to the end user outside, the
only noticeable event would be the 120 seconds of no server availability.
I'm of course open to any suggestions from the folks what author the servers
that run APRS-IS to tweak this further.
Just "fyi"....
73 de Dave
KG4YZY
www.aprsfl.net
----------------------------------------------------------------------
Subject: Re: APRSfl.net - fourth.aprs.net - status update...
From: Steve Dimse <k4hg@tapr.org>
Date: Sat, 16 Aug 2003 18:18:34 -0400
X-Message-Number: 4
On 8/16/03 at 5:53 PM Dave Anderson <dandersn@citicom.com> sent:
>I'm of course open to any suggestions from the folks what author the servers
>that run APRS-IS to tweak this further.
Something I don't see addressed in the above message, how do you handle the
incoming data? Here is what I mean...
Say you have two load-sharing servers, let's call them 4a and 4b. Normally
each of the the three other servers connect to 4 on 1313, and pull the data
that enters from them. Suppose first's 1313 connection get load-shared to
4a, second's goes to 4b. User X is connected to 4a and User Y is connected
to 4b.
X's packets will be seen on first but not second, Y's on second but not
first. I don't seee an easy way out of this, unless perhaps to get 1, 2,
and 3 to connect to each server. However, in this scheme, what you are
essentially doing is creating fifth, and in that that case, why not just
call it that (or actually, what I'd rather do is call the new one third,
since its connect limit is too low to be useful these days, and make third
become fifth)? After all, the central hubs are essentially a load-sharing
system already, albeit not as intelligent as the F5 system.
Perhaps you have found a good way to handle this upstream data problem, in
which case this is moot...
Steve
----------------------------------------------------------------------
Subject: Re: APRSfl.net - fourth.aprs.net - status update...
From: "David Thege" <dthege@conpoint.com>
Date: Sat, 16 Aug 2003 17:19:56 -0500
X-Message-Number: 5
I'm curently conected to arizona.aprs2.net prot 14580 and only wx data is
coming thru. I increased my ragne out to 250 from 150 and am not sseing any
stations other than the noes I hear direct. This on Ui-Veiw. Is there a
probelm with the APRS-IS system Dave N0XBN
----------------------------------------------------------------------
Subject: Re: APRSfl.net - fourth.aprs.net - status update...
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Sat, 16 Aug 2003 18:15:13 -0500
X-Message-Number: 6
From the arizona.aprs2.net:14501, the filter setting for N0XBN-5 is
"r/42/97/500 t/n". Your range is for East 97 longitude, not West 97.
Correct your filter setting to "r/42/-97/500 t/n" and it should work
well.
73,
Pete Loveall AE5PL
pete@ae5pl.net
----------------------------------------------------------------------
Subject: Re: APRSfl.net - fourth.aprs.net - status update...
From: "David Thege" <dthege@conpoint.com>
Date: Sat, 16 Aug 2003 19:28:57 -0500
X-Message-Number: 7
Thanks I must have accidentally changed it. Switched it to -97 working now.
Dave n0xbn
---
END OF DIGEST
Read previous mail | Read next mail
| |
