| |
ZL3AI > APRDIG 28.11.06 05:02l 155 Lines 5829 Bytes #999 (0) @ WW
BID : 9148-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 29 #24, 1/1
Path: DB0FHN<DB0MRW<DK0WUE<7M3TJZ<ZL2BAU
Sent: 061128/0357Z @:ZL2BAU.#79.NZL.OC #:17498 [Waimate] $:9148-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Today's Topics:
1. [ANN] Realease of Aprstracker v0.11 (Arno Verhoeven (PE1ICQ))
2. Creating maps with a GPS for APRS use (Bill Diaz)
3. Packet test (R. Simmons)
4. RE: Packet test (scott_at_opentrac.org)
----------------------------------------------------------------------
Message: 1
Date: Sun, 26 Nov 2006 20:47:03 +0100
From: "Arno Verhoeven (PE1ICQ)" <pe1icq_at_sharon.esrac.ele.tue.nl>
Subject: [aprssig] [ANN] Realease of Aprstracker v0.11
Aprstracker is an open source firmware for PIC based trackers like the
TinyTrak, KF161-Tracker, or KF163-Tracker.
The following new features have been added in aprstracker v0.11.
* Added support for RMC. Aprstracker can now operate, incl. SmartBeaconing,
when RMC is the only available NMEA sentence. GGA is only needed if
transmission of altitude information is enabled. As with previous versions,
aprstracker can also operate with just GGA sentences without
SmartBeaconing. Or with GGA and VTG sentences with SmartBeaconing.
* The GPS LED now doubles as a "GPS alive" and a "GPS lock" indicator. If
the GPS is not locked yet, then the LED is mostly off, and will flash on
every time $GPRMC or $GPGGA is received. If the GPS is locked, then the LED
is mostly on, and will flash off every time $GPRMC or $GPGGA is received.
* An output signal is available to control a PLL synthesizer of a
transceiver. This enables the usage of a transceiver for both voice and
APRS communications.
* Status type APRS frames can now have a user configurable text. This
feature is not available in the build for the pic16f628 because this
microcontroller does not have enough EEPROM storage.
The following is not really a new feature, but should be mentioned anyway.
The modem tone generation interrupt service routine and the EEPROM read
routines have been further optimized in v0.11.
Download links information can be found on the aprstracker project
web-page.
For those who would like to upgrade their tracker but cannot program
PIC-micros, see <http://ezkits.illumicon.nl/en/picprog4.html>
Enjoy!
--
73, PE1ICQ Arno Verhoeven
------------------------------
Message: 2
Date: Sun, 26 Nov 2006 17:00:56 -0600
From: "Bill Diaz" <william.diaz_at_comcast.net>
Subject: [aprssig] Creating maps with a GPS for APRS use
I have been working on a standalone application to create detailed street
maps. StreetCreator (SC) is intended for use in areas where detailed
street maps are not available or prohibitively expensive. Existing streets
are captured from a GPS while driving thru the area to be mapped. It will
be possible to combine multiple street maps captured in different areas to
one street file thereby allowing multiple users to contribute to the
effort.
SC can create fully zoomable detailed street files for use with Precision
Mapping Streets and Traveler 8.0 and can also create raster .bmp files for
use in other applications such as UiView.
See http://www.billdiaz.dynip.com/ for info.
http://www.billdiaz.dynip.com/StrCreatorBeta.htm for some beta examples
using USGS topo maps as Underlays and street data captured from a GPS.
I will soon be looking for Beta testers outside the US and Canada. I
already have a good US and Canadian beta team at this time. Very
interested in having someone in the UK capture some detailed streets for
beta testing purposes. Please contact me at kc9xg at comcast.net if you
are interested and have a suitable GPS and laptop.
Bill KC9XG
------------------------------
Message: 3
Date: Mon, 27 Nov 2006 07:19:31 -0800
From: "R. Simmons" <pelican2_at_silcom.com>
Subject: [aprssig] Packet test
To all :
I am developing PIC code to send an APRS DF message, ( for a DF beacon )
and I approaching completion... getting close to an "air test" of the
software but still a few "loose ends" to clear up...
Questions about a suitable destination address, the proper SSID values and
C-bit values. Also, the AX.25 spec says the CRC bytes should be sent MSB
first, but public code I have seen shows LSB is sent first, things like
that...
Any ( authoritative ) help would be appreciated, and a peer review of my
intended message would also be appreciated. I can be contacted "off-forum"
at this address : pelican2_at_silcom.com
Thanks...
DE WB6EYV / Bob S.
------------------------------
Message: 4
Date: Mon, 27 Nov 2006 08:41:39 -0800
From: <scott_at_opentrac.org>
Subject: RE: [aprssig] Packet test
Destination address should start with AP. You can get a product identifier
from Bob if you don't want to use the generic APRS tocall. SSID value
should be whatever the user selects - the use of SSIDs for station type is
deprecated. You can hard-code the control byte to 0x03 and the PID to
0xf0. I'd have to check on the address field C bits. I'm pretty sure I've
got the one on the tocall set to 1, and on the fromcall set to 0.
For the proper CRC-CCITT algorithm, check my page at
and has a link to the reference I used for the OpenTracker. The bitwise
algorithm doesn't require any lookup tables and can be done with shifts and
XORs - it may not be as fast, but it's very compact.
What are you using for the AFSK modulation? Are you doing it in hardware
or software?
Until I saw your email address, I didn't realize that you're in Santa
Barbara - I'm an hour up the road from you in Santa Maria. Do you know
Bruce Gordon, N6OLT? I've used his DF equipment for years.
If you want a lower traffic list for a peer review of your message, you
might try the APRSSPEC list. It's mostly just us developers over there,
and no one minds esoteric discussions of protocol details.
Scott
N1VG
------------------------------
aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
End of aprssig Digest, Vol 29, Issue 24
Read previous mail | Read next mail
| |
