| |
ZL3AI > APRDIG 05.05.07 08:03l 254 Lines 9466 Bytes #999 (0) @ WW
BID : 10107-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 34 #25, 1/3
Path: DB0FHN<DB0FOR<DB0SIF<HB9EAS<DB0FSG<OE7XLR<OE2XUM<DB0WGS<OE6XPE<IW2OHX<
I0TVL<DK0WUE<7M3TJZ<ZL2BAU
Sent: 070505/0543Z @:ZL2BAU.#79.NZL.OC #:46292 [Waimate] $:10107-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Today's Topics:
1. Off Topic - KPG87DL (Richard N. Piper IV)
2. Re: RE: "Local Info" confusion... (Tim Cunningham)
3. Re: Cheap laptops (jack swift)
4. Re: RE: "Local Info" confusion... (Keith VE7GDH)
5. PCSATs, 1 & 2 Frequencies (Matthew Stennett)
6. RE: PCSATs, 1 & 2 Frequencies (Robert Bruninga)
7. Re: RE: "Local Info" confusion... (Tim Cunningham)
8. APRS Client for OS X (Jeff Davis)
9. Re: APRS Client for OS X (Jason Winningham)
10. PIC and Modem experienting (Andrew Rich)
11. Re: PIC and Modem experienting (Jason Winningham)
12. RE: Cheap laptops (Nick Kotch)
13. RE: PIC and Modem experienting ('Scott Miller')
14. Re: RE: "Local Info" confusion... (Keith VE7GDH)
15. RE: [SPAM] RE: [aprssig] PIC and Modem experienting (Andrew Rich)
16. Re: RE: "Local Info" confusion... (Richard Montgomery)
17. RE: [SPAM] RE: [aprssig] PIC and Modem experienting ('Scott Miller')
18. RE: RE: "Local Info" confusion... (Robert Bruninga)
----------------------------------------------------------------------
Message: 1
Date: Tue, 24 Apr 2007 12:18:39 -0500
From: "Richard N. Piper IV" <richard.piper_at_media4god.org>
Subject: [aprssig] Off Topic - KPG87DL
Yes I know this is off topic but I am in need of KPG87DL if anyone knows
where I can get it from. I work with a Search and Rescue group called
I-WARN and need the software to program a Kenwood TK-2202L.
In case you wanted to know that only 2 "Ture" Ham Units I have are a
IC-229H and Kenwood D700 Aprs Rig.
--
Richard N. Piper IV
+1 (573) 517-8601 voice
------------------------------
Message: 2
Date: Tue, 24 Apr 2007 12:32:16 -0500
From: "Tim Cunningham" <tim_cunningham_at_mindspring.com>
Subject: Re: [aprssig] RE: "Local Info" confusion...
In UI-View, you must enable Options->Highlight IGATES.
The UIDIGI digipeater transmitting the originating third party packet
format will be identified as an IGATE as soon as UI-View receives the first
originating third party packet from it. UI-View will then place a box
around that transmitting digipeater. The object with the antenna will
appear as normal, but the transmitting digipeater will be identified as an
IGATE as soon as it receives the first originating third party packet from
that digipeater. If you click on the details for the originating
digipeater, UI-View will identify it as an IGATE on the dialogue box.
When the originating third party packet format was removed from multiple
UIDIGI digipeaters, the problem disappeared from UI-View for all stations
transmitting an originating third party packet beacon! A third party packet
begins with the symbol "}" in the beacon text. Please make sure you are
talking about the same type of packet transmission.
Here are a couple of examples using the third party format that were
programmed remotely to update 7 of the UIDIGI digipeaters:
BT 3 }146.940->APOBJ:!3444.27N/08631.98WrPHG7730 PL 100.0 Net Th 730PM
BT 3 }146.900->APOBJ:!3443. N/08631. WrPHG7700 PL 123.0 Net Th 7PM
BT 3 }147.180+>APOBJ:!3429. N/08637. WrPHG7730 PL 100.0 Brindley Mtn
BT 3 }147.270+>APOBJ:!3431. N/08537. WrPHG7760 PL 100.0 Net Th 630PM
BT 3 }145.270->APOBJ:!3424. N/08723. WrPHG7630 PL 107.2 Net Tu 7PM
BT 3 }145.310->APOBJ:!3413. N/08651. WrPHG7700 PL 100.0 Net Su 830PM
BT 3 }145.150->APOBJ:!3448. N/08658. WrPHG7630 PL 100.0 Net Th 7PM
If your beacon text does not look like the above examples, then you are not
talking about the same thing (position ambiguity was utilized on all but
one).
What is the digipeater callsign and the object name it transmits that you
are referring? This should clarify any doubt.
Perhaps it only happens in Alabama because we are South of the Mason-Dixon
line ;>)
73's,
Tim - N8DEU
Huntsville, Alabama
----- Original Message -----
From: "Keith VE7GDH" <ve7gdh_at_rac.ca>
Sent: Tuesday, April 24, 2007 11:47 AM
Subject: Re: [aprssig] RE: "Local Info" confusion...
>Bob WB4APR wrote...
>
>>When Alabama implemented this in all their digis, it was soon
>>observed that all UI-View clients would mark the DIGIPEATERS
>>as IGATES that were the source of these 3rd party voice repeater
>>objects.
>
>That isn't my observation here. There's a stand-alone TNC-based digi at my
>elbow that is beaconing an object for the local repeater. I'm viewing it
>in
>UI-View and it just shows as an "antenna" symbol and isn't marked as being
>an IGate. I don't see a problem here, so nothing needs to be fixed, but
>I'm
>curious why that would happen in Alabama.
>
>Also, at www.ew.usna.edu/~bruninga/localinfo.html you say "Because of
>errors in UI-View which prevents the display of PHG range data and also
>prevents the use of the 3rd party format, we cannot use the very valuable
>PHG data for showing the ranges of these voice repeaters." UI-View "out of
>the box" doesn't display PHG but with the UI-PHG add-on that is freely
>available, it does. I just checked and it displays the PHG just fine for
>the
>local repeater that the digi is sending out as an object. What do you mean
>by "errors in UI-View"? Someone reading that without prior knowledge of
>UI-View might take it at face value.
>
>73 es cul - Keith VE7GDH
>--
>"I may be lost, but I know exactly where I am!"
------------------------------
Message: 3
Date: Tue, 24 Apr 2007 14:07:49 -0400
From: jack swift <jswift_at_up.net>
Subject: Re: [aprssig] Cheap laptops
i'm interested... but your spam blocker doesn't like my browsers...
At 03:16 PM 4/12/07 -0500, you wrote:
>For anyone interested... I have four used laptops of various vintages
>which I would be happy to part with. (Especially since Mona said "let's
>clear out some of the excess stuff we have!")
>
>Please contact me off list if interested for details.
>
>Jim Duncan, KU0G
vvvvvvvvvvvvvvvvvvvvvvvv
Jack Swift
I.E. Swift Co.
402 Shelden Ave.
Houghton, MI 49931
906-482-0530, 281-5300
Radio: N8WAV AAR5LD
^^^^^^^^^^^^^^^^^^^^^^^^
------------------------------
Message: 4
Date: Tue, 24 Apr 2007 11:24:55 -0700
From: "Keith VE7GDH" <ve7gdh_at_rac.ca>
Subject: Re: [aprssig] RE: "Local Info" confusion...
Tim N8DEU wrote...
>In UI-View, you must enable Options->Highlight IGATES.
It's enabled. I like to be able to glance at the map and see the other
IGates.
>The UIDIGI digipeater transmitting the originating third party packet
>format will be identified as an IGATE as soon as UI-View receives the
>first originating third party packet from it....
Perhaps I missed that in the original thread. The "digi at my elbow" that
is sending an object for the local repeater is a KPC-3+ not a UIDIGI. The
originating digi shows as a digi, not an IGate.
>When the originating third party packet format was removed from multiple
>UIDIGI digipeaters, the problem disappeared from UI-View for all stations
>transmitting an originating third party packet beacon! A third party
>packet begins with the symbol "}" in the beacon text. Please make sure you
>are talking about the same type of packet transmission.
>
>Here are a couple of examples using the third party format that were
>programmed remotely to update 7 of the UIDIGI digipeaters:
>
>BT 3 }146.940->APOBJ:!3444.27N/08631.98WrPHG7730 PL 100.0 Net Th 730PM
Here's the beacon that I'm sending from the KPC-3+ digi. It isn't using an
ambiguous position. It is going out with no path.
BT }147.320+>APOBJ:!4846.05N/12330.38WrPHG5730 Salt Spring Island, BC
Thanks for the info. I can't see any difference between the object that I'm
sending out and the examples you gave except for the "3" after the BT in
your examples and the fact that I'm not using an ambiguous position. What is
the significance of the "3"? Is the UIDIGI capable of sending out multiple
BTs? Does the problem you are describing only happen when the originating
digi is a UIDIGI?
73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"
------------------------------
Message: 5
Date: Tue, 24 Apr 2007 15:43:15 -0700 (PDT)
From: Matthew Stennett <wa4tkg_at_yahoo.com>
Subject: [aprssig] PCSATs, 1 & 2 Frequencies
I am hearing activity on 145.825MHz right now, I
venture to say that PCSAT; STILL LIVES.
My question though, is, what about PCSAT-2?
I have 440MHz capability, and would like to give it a
shot, but I only have a magmount antenna, on a metal
roof vent, to make the trip.
Think it'll work ?
------------------------------
Message: 6
Date: Tue, 24 Apr 2007 19:01:32 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] PCSATs, 1 & 2 Frequencies
>I am hearing activity on 145.825MHz right now, I
>venture to say that PCSAT; STILL LIVES.
Yes, PCSAT-1 (W3ADO-1) works every day during daylight passes sort of. It
works best for passes near local noon. But only for a few packets. We can
logon and restor it for just about any single pass, but then it dies on the
next eclipse 20 to 40 minutes later.
>My question though, is, what about PCSAT-2?
Was returned to earth in August 2006.
But ANDE and RAFT both come over 6 times a day on 145.825 and will digipeat
just like any APRS digipeater.. Except:
1) RAFT you can hear, but it is very difficult to get in during the day
2) ANDE sleeps unless it hears packets. But it only tests the channnel for
1 second out of every 16.
Oh, and they will both SPEAK an APRS message sent to TALK if they are set
up right.
Good luck!
GOOGLE for ANDE OPS or for RAFT OPS (it's the same web page).
Bob, WB4APR
------------------------------
Read previous mail | Read next mail
| |
