| |
ZL3AI > APRDIG 19.02.04 13:50l 250 Lines 9866 Bytes #999 (0) @ WW
BID : 2863-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 17, 2/7
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0NOS<DB0BI<DB0FBB<DB0GOS<ON0AR<ON0AR<
ON0AR<F6KMO<7M3TJZ<EA5AKC<ZL2BAU<ZL2BAU<ZL3VML
Sent: 040219/1112Z @:ZL3VML.#80.NZL.OC #:19399 [Chch-NZ] FBB7.00i $:2863-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: re: Alinco DJ-S11, Tx Audio, PTT...
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Tue, 17 Feb 2004 09:22:11 -0500
X-Message-Number: 7
>>>"Rick Bolen (HM)" <rickbol@hotmail.com> 2/16/04 5:45:38 PM >>>
Thanks to Bobs... I've managed to achieve a working interface between the
Alinco DJ-S11 and the TNC-X....
I haven't opened squelch yet (don't know how exactly), but the DJ-S11
allows one to turn off the auto-power off, which I have done, so the radio
stays on all the time. I'd still like to open the squelch though.
REPLY: Just to clarify, yes, the auto-power-off must be turned off, but
the real problem that you cannot fix is the "power-saver" circuit that
causes the receiver to turn off for 90% of every second. This saves
receiver power and is common in most HT's these days. This makes the
receiver useless for packet as it will not hear the first part of any
packet and will thus receive NOTHING.
Do not be fooled by monitoring 144.39 too. Yes once the receiver wakes up,
it will receive the SECOND of two packets if the second one occurs within 4
seconds of the first one. But you might not notice that you are missing
EVERY packet that is preceeded by 4 or more seconds of silence.
For my projects, a BIG rubber band around the HT to hold in the MON button
was the cheap fix (actually a metal bracket, but you get the picture...
de WB4APR, Bob
----------------------------------------------------------------------
Subject: D-700 Questions
From: Rick Stoneking <w2rds@arrl.net>
Date: Tue, 17 Feb 2004 09:27:30 -0500
X-Message-Number: 8
First, let me apologize in advance for this somewhat off topic post, but I
have completely given up on getting an acknowledgement, let alone an
answer, from the Kenwood list. I have a D-700 that I am using for APRS in
the vehicle and I have a couple of questions about it that I am hoping the
other D-700 owners on this list can addres.
Number one: does the mute function actually work on this radio? I have
tried every combination of internal/external speaker combinations and
settings and the mute key does nothing except add the word mute to the
display.
Number two: Once upon a time I had heard a rumor of a firmware
revision. Does anyone know if this was ever released? Is it still
planned? Dead or just a myth? If it did actually happen how can I get the
upgrade?
Number three: I have two gripes about the volume control. First, the audio
abruptly disappears when lowering the volume, instead of getting lower and
lower until it is gone. And this happens at an audio level that is louder
than I would expect (granted it is pretty low, but if the car is not
running it does not go low enough for my taste). The second problem with
the audio is that when the audio does cut out completely there is a
noticeable (if the car is not running) 'hiss' from the speaker. Has anyone
else experienced (and hopefully fixed) this?
Thanks for the bandwith.
Rick
W2RDS
----------------------------------------------------------------------
Subject: RE: ISS in PCsat compatiblity mode
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Tue, 17 Feb 2004 09:41:53 -0500
X-Message-Number: 9
>>>"Scott Miller" <scott@3xf.com> 2/17/04 1:15:08 AM >>>
>Bob, if I get a chance tomorrow I'll see if I can run an access opportunity
>prediction in STK. What's an appropriate sun angle constraint? Or should I
>just show anything with PCsat in sunlight?
We have found that PCsat charges up enough for a few packets by about 20
minutes after it enters sunlight. Thus if you are in the footprint then,
you might get a successful packet.
Since PCsat's days are 100 minutes long and ours are 24 hours long, that
means each one of PCsat's minutes is about 14.4 earth minutes. THus when
PCsat has been in the sun for 20 minutes, the observer underneath will have
been in the sun for about 5 hours.
So inother words, you need to have mid-day passes inorder to be under PCsat
during its best times. And presently this is only occuring in the Southern
Hemisphere...
unfortunately for us...
Bob
----------------------------------------------------------------------
Subject: Re: APRS enabled balloon on 144.39 over Colorado
From: Steve Dimse <k4hg@tapr.org>
Date: Tue, 17 Feb 2004 09:48:07 -0500
X-Message-Number: 10
On 2/16/04 at 11:04 PM K. Mark Caviezel <kmcaviezel@yahoo.com> sent:
>I'm planning to run a flight test of the Pocket
>Tracker on the EOSS flight this upcoming Saturday,
>February 21, the flight will be north of the Denver
>Metro Area. I was planning to run the pocket tracker
>on 144.39 with path of "WIDE" and one packet per
>minute.
>Do you think this will inordinately hammer the system
>capacity ?
It won't hammer my system at all. However, it may cause QRM on the local RF
network. At high altitude, you could hit dozens of digiteaters, each of
which will retransmit the position. Since at the same time the balloon will
be heard directly by dozens of IGates and most local users, all most of
these digipeated packets are a waste.
>Issue: the pocket track can only run on 144.34 or .39.
> Another payload is on .34 (experimental EBBE with
>balloon groups in adjacent states)
>For flight tracking purposes, transmission intervals
>greater than one minute are not desired as the
>position updates become pretty time critical as we can
>sometimes manuever with the descending balloon to
>effect a rendezvous with the balloon as it lands. It
>will sound odd, but we have had at least two cases of
>payload purloinment from recently landed balloons in
>the past couple years. Being the first one there
>eliminates this possiblity.
>I was thinking about putting in the single 'WIDE' so I
>can get a hop as a lot of the i gate stations run gain
>antennas that are looking at horizon, not up in the
>air. The flight duration should be less than 3
>hours.
Not an easy call to make. If you look at all the packets received by
yesterday's balloon flight
http://www.findu.com/cgi-bin/raw.cgi?call=KC8UCH-11
you can see the vast majority were heard directly by IGates. Still there
were some areas where there was no IGate hearing them directly, of
particular note, the final few packets were heard through a digi, so there
would be less specific information about the touchdown point had they not
used RELAY.
I'd say the single most important thing is to make sure that there is no
other event occuring in the flight path. Yesterday the balloon traveled
directly over an area that had a dozen or more objects placed on the map in
Canada, looked like some sort of race or other event:
http://www.findu.com/cgi-bin/dmap.cgi?zoom=1&click.x=305&click.y=255&=
offsetx=578
&offsety=105&map=usa.mp&scale=0.0254683533312&last=96&maplist=mas=
ter.txt&width=
640&height=480
Fortunately the symbols had been placed the previous day, but imagine if
this balloon, tranmitting multiple long NMEA packets every minute with a
path of RELAY,WIDE,WIDE had passed over an active APRS event, like the
Baker to Vegas run. It would have completely disrupted the use of APRS for
this event! May be there needs to be some sort of event coordination...
Steve K4HG
----------------------------------------------------------------------
Subject: Re: New option for HF 30M APRS -- TinyTrak 3b (Review)
From: "Scott Miller" <scott@3xf.com>
Date: Tue, 17 Feb 2004 06:58:38 -0800
X-Message-Number: 11
I'd had it on second originally and it wasn't working either... turns out
the Xastir guys changed the filter function so it sends the 'filter' part
automatically now. The servers were choking on my 'filter filter' command.
Scott
N1VG
-----Original Message-----
From: bounce-aprssig-31505@lists.tapr.org
[mailto:bounce-aprssig-31505@lists.tapr.org]On Behalf Of Roger Bille
Sent: Tuesday, February 17, 2004 1:23 AM
To: TAPR APRS Special Interest Group
Subject: [aprssig] Re: New option for HF 30M APRS -- TinyTrak 3b
(Review)
Scott,
The filter command is correct but first.aprs.net is an aprsd server and
does not support the javAPRSFilter functions. Use one of the javAPRSSrvr
based servers, e.g. second, third, fourth or any of the tier2 servers.
Also be aware that I'm Swedish so the range is in km (kilometers) and not
miles. You need to change the filter to 161 km and you will get a 100 miles
range.
73 de sm5nrk/Roger
----------------------------------------------------------------------
Subject: A LITTLE EXCESSIVE PATH, MAYBE?
From: "David Dobbins" <ddobbinswa@yahoo.com>
Date: Tue, 17 Feb 2004 07:23:42 -0800
X-Message-Number: 12
I regularly see some outrageous paths in use overseas, and wonder why in
the hell some of these aren't blocked from the servers until they cut
back to something reasonable. This is about the worst I've seen.
EA8ADH-15>APU24V,RELAY,TRACE3-3,RELAY,TRACE7-7,WIDE,TRACE7-7,RELAY,TRACE
7-7,qAO,F6CDD:=2759.59N\01523.95W-GATEWAY EN 12128 21117 14103 10150
{UIV32}
Dave/K7GPS
----------------------------------------------------------------------
Subject: Re: APRS enabled balloon on 144.39 over Colorado
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Tue, 17 Feb 2004 10:33:42 -0500
X-Message-Number: 13
My two cents on BALLOON paths:
BALLOONS = WIDE
REASON: It is not needed for 99% of the flight, but it is absolutely
essential when it lands.
The effect of any Balloon using WIDE is no worse than one more local
mobile anywhere in anyone's system. No big deal.
If UIDWAIT is OFF in all digipeaters as it should be, then the total
network resources required is a single digipeat time, no matter how many
digiepaters hear it at the same time. They are all supposed to key up at
the same time if UIdwait is set properly. Thus only one time slot
independent of the number of digis.
de WB4APR, Bob
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
