| |
ZL3AI > APRDIG 05.05.07 07:54l 97 Lines 3386 Bytes #999 (0) @ WW
BID : 10109-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 34 #25, 3/3
Path: DB0FHN<DB0FOR<DB0SIF<HB9EAS<DB0FSG<DB0AAB<DB0PV<OE5XBL<OE6XPE<IW2OHX<
I0TVL<DK0WUE<7M3TJZ<ZL2BAU
Sent: 070505/0543Z @:ZL2BAU.#79.NZL.OC #:46294 [Waimate] $:10109-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 15
Date: Wed, 25 Apr 2007 16:37:32 +1000
From: "Andrew Rich" <vk4tec_at_people.net.au>
Subject: RE: [SPAM] RE: [aprssig] PIC and Modem experienting
Am I reading this right ? Each time you want to TX or RX with the MX614 you
have to change m0 and m1 because there is no such mode as 1200 RX / 1200 TX
Andrew Rich
Amateur radio callsign VK4TEC
email: vk4tec_at_people.net.au
Brisbane AUSTRALIA
------------------------------
Message: 16
Date: Wed, 25 Apr 2007 08:38:38 -0500
From: Richard Montgomery <kb4ytm_at_gmail.com>
Subject: Re: [aprssig] RE: "Local Info" confusion...
Keith VE7GDH wrote:
>Tim N8DEU wrote...
>
>>UI-View will display the digipeater on the map with a star and an S
>>overlay at all times. The sequence of events is the UIDIGI will beacon
>>its position using the digi star with an S overlay using the following
>>beacon text format:
>>Beacon1Text = !3438.07NS08630.74W#PHG5630/W2,ALn Huntsville Alabama
>>Shortly thereafter, the third party beacon as defined earlier will be
>>transmitted. As soon as UI-View receives that packet, the digipeater is
>>highlighted with the square box around it...
>
>Thanks for the explanation. I've never noticed this. Perhaps there aren't
>any UIDIGIs around me, or if there are, perhaps they aren't sending out any
>3rd party beacons. Any idea what there is about the beacon from a UIDIGI
>that would make UI-View think the digi sending the object was an IGate? I
>couldn't see any significant difference between the examples you gave and
>the beacon going out from the KPC-3+ TNC that I was looking at.
>
>73 es cul - Keith VE7GDH
The KPC-3 tnc's that we use here as digipeaters also showed up as Igates
using the third party beacon settings, so its not limited to just the
UIDIGI tnc's. We switched back to Tim's recommendations.
Richard
KB4YTM
------------------------------
Message: 17
Date: Wed, 25 Apr 2007 06:59:46 -0700
From: "'Scott Miller'" <scott_at_opentrac.org>
Subject: RE: [SPAM] RE: [aprssig] PIC and Modem experienting
That sounds right. When it's transmitting at 1200 baud, it's receiving at
150 baud with tones around 386 and 486 hz. The back-channel is only useful
for a wired connection really. Just use m0 and m1 to switch to TX mode when
you transmit.
Scott
N1VG
------------------------------
Message: 18
Date: Wed, 25 Apr 2007 12:54:48 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] RE: "Local Info" confusion...
Keith, Its not a UIDIGI ROM issue. Its Uiview that interprets any source
of a 3rd party packet as being an Igate. And since we initially suggested
using 3rd party packets for these objects, this began to cover the map in
Uiview with digipeaters that then were marked as Igates.
So that is why we are abandoning 3rd party format and now receommending the
original APRS object format instead. Hope that helps. Bob
>-----Original Message-----
>>UI-View will display the digipeater on the map with a
>>star and an S... As soon as UI-View receives a [3rd
>>party voice-reepeater-object packet from that digi, then
>>Uiview] highlighs [the digi] with the square box
>>around it... [indicating an Igate]
------------------------------
aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
End of aprssig Digest, Vol 34, Issue 25
Read previous mail | Read next mail
| |
