| |
ZL3AI > APRDIG 05.05.07 07:54l 260 Lines 8634 Bytes #999 (0) @ WW
BID : 10108-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 34 #25, 2/3
Path: DB0FHN<DB0FOR<DB0SIF<HB9EAS<DB0FSG<DB0PV<OE5XBL<OE6XPE<IW2OHX<I0TVL<
DK0WUE<7M3TJZ<ZL2BAU
Sent: 070505/0543Z @:ZL2BAU.#79.NZL.OC #:46293 [Waimate] $:10108-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 7
Date: Tue, 24 Apr 2007 18:27:25 -0500
From: "Tim Cunningham" <tim_cunningham_at_mindspring.com>
Subject: Re: [aprssig] RE: "Local Info" confusion...
>>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.
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 therafter, 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. Whne I seen the square box around
7 digipeaters, it was obvious something was not working correctly and the
third party format was changed to avoid this problem in UI-View.
>>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?
The "BT 3" command is a UIDIGI remote command to program the Beacon3Text as
UIDIGI supports 3 separate beacons that can be transmitted at various times.
The ambiguous position does not change the end result as we had one
programmed with the full position and observed the same results..
These were the setup conditions:
Beacon1Text = !3438.07NS08630.74W#PHG5630/W2,ALn Huntsville Alabama
Beacon2Text = !3438.07NS08630.74W#PHG5630/W2,ALn Huntsville Alabama
Beacon3Text = }146.940->APOBJ:!3444.27N/08631.98WrPHG7730 PL 100.0 Net Th
730PM
Beacon1Path Beacon2Path = WIDE2-1
Beacon3Path = LOCAL
AuxPath = AL2-2
Beacon 1 goes out every 10 minutes via no Beacon1Path.
Beacon 2 goes out every 29 minutes via Beacon2Path.
Beacon 3 goes out every 10 minutes 1 second via Beacon3Path.
Weather data received from the serial port is sent via the AuxPath every 3
minutes in the format:
!!000000A902E302A927F002EA0211----0070058900000000
Once the third party packet format was dropped we never seen the problem in
UI-View again.
I hope that helps explain the conditions a little better.
73's,
Tim - N8DEU
Huntsville, Alabama
------------------------------
Message: 8
Date: Tue, 24 Apr 2007 19:57:43 -0400
From: Jeff Davis <ke9v_at_mac.com>
Subject: [aprssig] APRS Client for OS X
I'm looking suggestions for an APRS client for OS X. I see that Xastir is
supposed to run on OS X but a little thread diving on the Xastir mailing
list looks like it may not be fully functional on this OS.
Thanks in advance for any advice.
73, Jeff
------------------------------
Message: 9
Date: Tue, 24 Apr 2007 19:12:04 -0500
From: Jason Winningham <jdw_at_eng.uah.edu>
Subject: Re: [aprssig] APRS Client for OS X
On Apr 24, 2007, at 6:57 PM, Jeff Davis wrote:
>I'm looking suggestions for an APRS client for OS X. I see that
>Xastir is supposed to run on OS X but a little thread diving on the
>Xastir mailing list looks like it may not be fully functional on
>this OS.
I've been running it on Mac OS X for a few years now. Works just fine.
Speech synthesis and AX.25 kernel extensions are both linux-specific;
the myriad other features work great.
-Jason
kg4wsv
------------------------------
Message: 10
Date: Wed, 25 Apr 2007 10:30:16 +1000
From: "Andrew Rich" <vk4tec_at_people.net.au>
Subject: [aprssig] PIC and Modem experienting
Gudday
I have been playing with a PIC chip and a GPS and a 433 MHz pair of radio
modules.
The radio modules use ASK or OOK. I have had limited success and the link is
immune to corruption.
I am thinking of trying MX614 and the PIC for telemetry.
Anyone playing with PIC's for telem ?
Looking for a source of MX614 down under as well.
Andrew
Andrew Rich
Amateur radio callsign VK4TEC
email: vk4tec_at_people.net.au
Brisbane AUSTRALIA
------------------------------
Message: 11
Date: Tue, 24 Apr 2007 19:46:10 -0500
From: Jason Winningham <jdw_at_eng.uah.edu>
Subject: Re: [aprssig] PIC and Modem experienting
On Apr 24, 2007, at 7:30 PM, Andrew Rich wrote:
>Gudday
>
>I have been playing with a PIC chip and a GPS and a 433 MHz pair of
>radio modules.
>
>The radio modules use ASK or OOK. I have had limited success and
>the link is immune to corruption.
>
>I am thinking of trying MX614 and the PIC for telemetry.
The ISM modules I've seen have digital inputs and take care of the
modulation themselves - the MX614 doesn't have anything to do.
I have an audio transmitter (from Abacom, IIRC) that has a simple audio
input. I tied an opentracker to it and flew it on a balloon. SAW
oscillator drifted terribly in the cold, but it otherwise worked OK.
>Anyone playing with PIC's for telem ?
I tried an AVR one time and abandoned the PIC - the development support is
way better for the AVR, and free to boot.
>Looking for a source of MX614 down under as well.
Can't help you there.
The XR2206/XR2211 pair take quite a few more passive components to
implement, but are cheaper, may be easier to find, and can work on
different audio tones so you can use the same circuit with different
passives to implement other AFSK systems like 300 baud packet, NOAA SAME
transmissions, etc. Check out the T2 for an XR2211 receiver design. I
suspect I'd use PWM on the microcontroller rather than mess with the 2206
if I tried to implement the transmit side.
-Jason
kg4wsv
------------------------------
Message: 12
Date: Tue, 24 Apr 2007 22:07:52 -0400
From: "Nick Kotch" <nkotch_at_earthlink.net>
Subject: RE: [aprssig] Cheap laptops
Just seeing if you've gotten rid of these laptops yet or not. Just
catching up on some of these messages so I may be a little late. : )
Nick
KF4BYA
------------------------------
Message: 13
Date: Tue, 24 Apr 2007 21:16:55 -0700
From: "'Scott Miller'" <scott_at_opentrac.org>
Subject: RE: [aprssig] PIC and Modem experienting
Circuit Cellar often has articles on PICs and telemetry applications.
[commercial content deleted]
Scott
N1VG
------------------------------
Message: 14
Date: Tue, 24 Apr 2007 22:50:48 -0700
From: "Keith VE7GDH" <ve7gdh_at_rac.ca>
Subject: Re: [aprssig] RE: "Local Info" confusion...
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
--
"I may be lost, but I know exactly where I am!"
------------------------------
Read previous mail | Read next mail
| |
