| |
ZL3AI > APRDIG 03.04.07 06:34l 97 Lines 3446 Bytes #999 (0) @ WW
BID : 9995-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 34 #1, 2/2
Path: DB0FHN<DB0MRW<DK0WUE<F4BWT<IW2OAZ<ZL2BAU
Sent: 070403/0404Z @:ZL2BAU.#79.NZL.OC #:40999 [Waimate] $:9995-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 10
Date: Sun, 1 Apr 2007 11:27:31 -0400 (EDT)
From: "Bob Bruninga " <bruninga_at_usna.edu>
Subject: Re: [aprssig] KC8UCH balloon over western PA right now, reaching
NE Maryland by 10am
>I promise, SDG-2 will carry APRS equipment (I just need to
>find a very light tracker and a GPS that doesn't eat
>batteries)!
You might try what we plan on for our ocean buoys. That is, only power up
the GPS once every now and then. Maybe for a balloon, once every 10
minutes for 2 minutes would assure you got a good fix. That would reduce
the battery load by a factor of 5..
Bob, Wb4APR
------------------------------
Message: 11
Date: Sun, 1 Apr 2007 11:53:52 -0400
From: "Wes Johnston, AI4PX" <wes_at_kd4rdb.com>
Subject: Re: [aprssig] KC8UCH balloon over western PA right now,
reaching NE Maryland by 10am
You'd probably want some sort of logic that kept the GPS power on during
the descent phase right? Of course after it hits ground and the tiny trak
or open track modem device has a known position, there would be no need to
run the GPS any more. W/o it running the radio beacon could last a lot
longer.
1)run GPS every 10 minutes for two minutes during ascent. Tracker
should only beacon when gps data is valid.
2)run GPS continuously during descent, tracker beacons every 60 seconds
simplex.
3)shut GPS off after landing. Tracker beacons every 10 minutes with a
normal mobile path.
Since most trackers only have two mode, maybe a way to shut off the GPS
would be via impact sensor of some sort. Modes 1 and 3 are very similar,
maybe there's room here for a compromise that would allow this idea to work
with only two modes?
Wes
------------------------------
Message: 12
Date: Sun, 1 Apr 2007 09:13:13 -0700
From: "Keith VE7GDH" <ve7gdh_at_rac.ca>
Subject: [aprssig] APRS DOS
To Bob WBTAPR...
Hi Bob - I just replied to a query over on the UI-View list about APRS DOS
apparently version 852. Here's a report of parsing errors from findu.com
www.findu.com/cgi-bin/errorlist.cgi?call=VA3VA&last=24
20070401000541
VA3VA>APR852,WIDE2-2,qAo,VE3CTP:=4220.4NN/08256.3WW-.../.../Ed
in Windsor monitoring 145.470MHZ
The APRS spec calls for 8 characters for the latitude and 9 characters for
the longtitude. VA3VA appears to be using one decimal place and two NNs and
two WWs for the position report. Will you please comment on the double
characters?
For a test, I took a known good log file and played it back in UI-View and
then truncated it down to one decimal place and changed the N to NN and the
W to WW and it wouldn't display the positions. The original comment over on
the UI-View list was that this station wouldn't display in UI-View. It also
doesn't show up at findu.com except for the on the parsing errors page.
UI-View doesn't "do" ambiguity, but with the log file using one decimal and
a space followed by a single N or a single W, it displays a (non ambiguous)
position. However with a single decimal and the double NN or double WW,
it wouldn't display.
Note... VA3VA was using UI-View about 12 hours ago. It's while it was using
APRS DOS that it wasn't being displayed in UI-View or findu.com.
73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"
------------------------------
aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
End of aprssig Digest, Vol 34, Issue 1
Read previous mail | Read next mail
| |
