| |
ZL3AI > APRDIG 01.04.04 20:43l 298 Lines 11530 Bytes #999 (0) @ WW
BID : 3072-ZL3AI
Read: GUEST
Subj: TAPR Digest, Mar 29, 1/7
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<ZL2BAU<ZL2BAU<ZL3VML
Sent: 040401/1150Z @:ZL3VML.#80.NZL.OC #:21749 [Chch-NZ] FBB7.00i $:3072-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Monday, March 29, 2004.
1. Re: low cost
2. UAIS Position decoder
3. Re: New tracker design suggestions
4. Balloon recovery help needed
5. Re: New tracker design suggestions
6. Re: older Trimble GPS receiver
7. Re: New tracker design suggestions
8. Re: older Trimble GPS receiver
9. Re: New tracker design suggestions
10. Re: New tracker design suggestions
11. Re: New tracker design suggestions
12. Re: New tracker design suggestions
13. Re: New tracker design suggestions
14. Re: New tracker design suggestions
15. Re: New tracker design suggestions
16. Re: New tracker design suggestions
17. Re: New tracker design suggestions
18. Re: New tracker design suggestions
19. Re: New tracker design suggestions
20. Re: New tracker design suggestions (fwd)
21. Re: New tracker design suggestions
22. Re: New tracker design suggestions
23. Re: New tracker design suggestions (fwd)
24. Re: New tracker design suggestions
25. Re: New tracker design suggestions
26. Re: New tracker design suggestions
27. Re: New tracker design suggestions (fwd)
28. Re: New tracker design suggestions
29. Re: New tracker design suggestions
30. Re: New tracker design suggestions
31. Re: New tracker design suggestions
32. Re: New tracker design suggestions
33. Re: New tracker design suggestions
34. Re: New tracker design suggestions
35. Re: New tracker design suggestions
36. Re: New tracker design suggestions
37. Re: New tracker design suggestions
38. Re: New tracker design suggestions
39. Re: New tracker design suggestions
40. Re: New tracker design suggestions
41. Re: New tracker design suggestions
42. RE: UAIS Position decoder
43. Re: New tracker design suggestions
44. Re: New tracker design suggestions
45. Re: New tracker design suggestions
46. Re: New tracker design suggestions
47. FIRE Watches, Warnings, etc
48. Re: New tracker design suggestions
49. Dual Band On The Glass Antennas
50. Re: Dual Band On The Glass Antennas
51. Re: Dual Band On The Glass Antennas
----------------------------------------------------------------------
Subject: Re: low cost
From: WA8LMF2@aol.com
Date: Mon, 29 Mar 2004 04:18:46 EST
X-Message-Number: 1
You are probably thinking of the Deluo units available at:
http://www.deluo.com
Note that the unit is available in both USB and serial versions. Be sure to
get the serial version if you plan to connect it to non-PC devices (i.e.
TinyTraks, Kenwood TH-D7/D700, etc).
The USB version may be more useful with a PC since:
A) It lets you save the only serial port on a laptop for a TNC
B) It powers itself via the USB connection from the PC it is attached to.
No separate power connection or batteries are required.
----------------------------------------------------------------------
Subject: UAIS Position decoder
From: "Sadowski, Allan" <allan.sadowski@ncshp.org>
Date: Mon, 29 Mar 2004 06:52:13 -0500
X-Message-Number: 2
I believe someone here on the SIG posted recently that they had
successfully decoded the UAIS/AIS/DSC position "packet" that is used on
marine VHF.
The below URL goes into some detail about the information encoded in the
UAIS packet, but the GMSK 9600bps signal is not my forte' so I'd
appreciate hearing about any success with a TNC in at least demodulation
of the packets.
http://www.iala-aism.org/web/pages/publications/docpdf/ais/AISGDLoi.PDF
TNX
ALOHA
AH6LS
----------------------------------------------------------------------
Subject: Re: New tracker design suggestions
From: "Curt, WE7U" <archer@eskimo.com>
Date: Mon, 29 Mar 2004 08:42:24 -0800 (PST)
X-Message-Number: 3
On Sat, 27 Mar 2004, Brian D Heaton wrote:
>How about a few GPIO pins and perhaps a multiplexed analog sensor
>input?
1) An extremely low-power digi, that we can throw into an ammo-can with a
low-current handheld and a gell-cell.
2) Something that implements what you talked about way back when, before
you started the OpenTrac project: The capability for the portable trackers
to keep a detailed log, then blast that log back to base whenever a path is
found, including the capability for any of the portable trackers between
you and base to function as relays.
3) Capability to plot positions of other units as waypoints on the Garmin
map screen (as the Kenwoods, the anti-tracker, and Xastir can do).
--
Curt, WE7U archer at eskimo dot com
Arlington, WA, USA http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
----------------------------------------------------------------------
Subject: Balloon recovery help needed
From: "Rochte, Robert" <rrochte@gpacademy.org>
Date: Mon, 29 Mar 2004 11:39:43 -0500
X-Message-Number: 4
Our most recent flight was on Friday - this was a test of a long-duration
helium tetroon. The long duration part didn't quite work as planned (total
flight time now appears to be 7h56m), but otherwise it was a success.
We're now trying to locate the balloon and would appreciate the help of any
stations located in New York state, roughly within a triangle whose corners
are Albany, Binghamton and New York City.
Since this was simply a proof-of-concept flight, the balloon wasn't carrying
an APRS tracker - only a CW beacon which provided pressure, temperature,
light and voltage data. The beacon frequency is 28.636Mhz and it should be
transmitting for a few more days. Telemetry is sent every two minutes,
followed by dits every four seconds.
If you can hear it, please let me know! Thanks!
(How's this APRS-related? Well, the envelope design will be used for an
upcoming long-duration APRS flight!)
73,
Robert
KC8UCH
--
Robert Rochte
Director of Technology
The Grosse Pointe Academy
171 Lake Shore Road
Grosse Pointe Farms, MI 48236
Tel. +1 313-886-1221 x155
FAX +1 313-886-1418
www.gpacademy.org
----------------------------------------------------------------------
Subject: Re: New tracker design suggestions
From: David VanHorn <dvanhorn@cedar.net>
Date: Mon, 29 Mar 2004 11:58:52 -0500
X-Message-Number: 5
At 08:42 AM 3/29/2004 -0800, Curt, WE7U wrote:
>On Sat, 27 Mar 2004, Brian D Heaton wrote:
>
>> How about a few GPIO pins and perhaps a multiplexed analog sensor
>>input?
>
>1) An extremely low-power digi, that we can throw into an ammo-can
>with a low-current handheld and a gell-cell.
A NIMH pack, and switching regulators would be a huge improvement in any
low-power project. A linear reg, taking 12V to 5W wastes more power in
heat than it delivers to the load. The long term consumption is far more
important than the short term transmit pulses.
A switcher is typically 90%+ efficient. Linears win again at extremely low
currents where the static drain of the switcher becomes significant.
In my printer project, my drain while printing is 3-10A from a small nimh
pack. But the largest part of the power budget, in it's four day lifetime
after charge, is the 3mA that the sleeping system draws.
>2) Something that implements what you talked about way back when,
>before you started the OpenTrac project: The capability for the
>portable trackers to keep a detailed log, then blast that log back
>to base whenever a path is found, including the capability for any
>of the portable trackers between you and base to function as relays.
Not a bad idea, as long as you max out the number of positions reasonably.
Also, timestamping could be a bit wierd.
You will be heard more often than you think you are, so you'll essentially
be saying "I'm back over there again". A timestamp IN the original packet
would have been a good idea, way back when the protocol was designed.
>3) Capability to plot positions of other units as waypoints on the
>Garmin map screen (as the Kenwoods, the anti-tracker, and Xastir can
>do).
Very good idea.
----------------------------------------------------------------------
Subject: Re: older Trimble GPS receiver
From: "Al Wolfe" <awolfe@prairieinet.net>
Date: Mon, 29 Mar 2004 10:39:14 -0600
X-Message-Number: 6
APRS Experts,
I was given some older Trimble Placer-400 receivers. These were once
used in a commercial vehicle tracking application. They fire up OK and put
out data from a real RS232 port.
In doing some research on them I found that they will not do NMEA
messages, only TAIP (Trimble ASCII Interface Protocol). This appears to be a
good, versatile protocol, with all the important stuff there in the
messages, just not compatible with APRS as I understand it.
Has anyone built a PIC or other gadget to convert TAIP to NMEA? Is it
worth the effort? It looks doable but I have had no experience yet with
PIC's.
73,
Al, K9SI
----------------------------------------------------------------------
Subject: Re: New tracker design suggestions
From: "Curt, WE7U" <archer@eskimo.com>
Date: Mon, 29 Mar 2004 09:12:46 -0800 (PST)
X-Message-Number: 7
On Mon, 29 Mar 2004, David VanHorn wrote:
>A NIMH pack, and switching regulators would be a huge improvement in any
>low-power project. A linear reg, taking 12V to 5W wastes more power in
>heat than it delivers to the load. The long term consumption is far more
>important than the short term transmit pulses.
>
>A switcher is typically 90%+ efficient. Linears win again at extremely low
>currents where the static drain of the switcher becomes significant.
Very much agreed! I have NiMH packs too, and actually would prefer to use
those. Definitely prefer switchers over linear, assuming the switching
noise doesn't get into the radios.
>>2) Something that implements what you talked about way back when,
>>before you started the OpenTrac project: The capability for the
>>portable trackers to keep a detailed log, then blast that log back
>>to base whenever a path is found, including the capability for any
>>of the portable trackers between you and base to function as relays.
>
>Not a bad idea, as long as you max out the number of positions reasonably.
>Also, timestamping could be a bit wierd.
>You will be heard more often than you think you are, so you'll essentially
>be saying "I'm back over there again". A timestamp IN the original packet
>would have been a good idea, way back when the protocol was designed.
The OpenTrac protocol fixes this. They have a sequence number with
each posit, and (would have to look at the spec again) a timestamp.
Just the sequence numbers would be adequate to resort them at the
receive end. That means you could have different pieces of the
track getting to base via different paths.
I'd switch to OpenTrac in a usec for SAR uses if they had this sort
of operation, and I could buy/build something ruggedized on the
cheap.
We're going to play with the pockettrackers to see what they can do
in the woods. A pockettracker combined with an OEM GPS or
integrated GPS in a ruggedized enclosure, doing OpenTrac protocol
would be my ideal, although the receive-side software would have to
catch up first. I'm not sure yet whether we need more power than
the pockettracker provides, but we'll find that out soon.
--
Curt, WE7U archer at eskimo dot com
Arlington, WA, USA http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
