| |
ZL3AI > APRDIG 28.01.07 14:16l 178 Lines 6370 Bytes #999 (0) @ WW
BID : 9632-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 31 #30, 3/3
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<F5GOV<F4BWT<IW2OAZ<ZL2BAU
Sent: 070128/0611Z @:ZL2BAU.#79.NZL.OC #:29604 [Waimate] $:9632-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 22
Date: Thu, 25 Jan 2007 17:53:23 -0600
From: "Bill Diaz" <william.diaz_at_comcast.net>
Subject: RE: [aprssig] Garmin IMG Fn ?
Clem,
There is no way to determine from the filename what area an IMG file
covers as the filenames are more or less sequentially numbered.
You can use Garmin MapSource to determine the geographic coverage area of
the Img file. These are often polygons and a single IMG file is usually
restricted to a single state. You also use Mapsource to upload and download
img files to your receiver. If the file in question is loaded into the
receiver, have mapsource download the file to your computer and you can view
it's geographic coverage.
Bill KC9XG
>-----Original Message-----
>Clem NR3U wrote...
>
>>Can anyone help me relate a Garmin.IMG file name to a city or state map
>>that I may want to use?
>
>I don't know what the Garmin.IMG file is, but I would assume that it's only
>usable in the Garmin program that you are using. However you could grab one
>or more screenshots of the map and make note of the lat/long in the
>corners, or two points near the corners and calibrate them as a static maps
>for UI-View.
>
>73 es cul - Keith VE7GDH
------------------------------
Message: 23
Date: Thu, 25 Jan 2007 18:01:50 -0600
From: "AE5PL Lists" <HamLists_at_ametx.com>
Subject: RE: [aprssig] Local Repeater Displays on Mobiles
>-----Original Message-----
>From: William McKeehan
>Posted At: Thursday, January 25, 2007 4:11 PM
>Subject: RE: [aprssig] Local Repeater Displays on Mobiles
>
>Where I am, there are a number of repeaters that would have the same callsign
>as they are controlled by the same owner; not necessarily in the same
>location, so you could easily have multiple objects with the same name as you
>drive across East TN.
>
>Would this not cause more (at least similar) problems than using the frequency
>for the name of the object?
A good question and a good reason why we have 2 characters available to use
as a qualifier for our six letter (or less) callsigns. These instances you
speak of (I would say very common) could use -R -R1, -R2, etc. because the
key piece is the -R portion of the object name.
73,
Pete Loveall AE5PL
pete at ae5pl.net
------------------------------
Message: 24
Date: Thu, 25 Jan 2007 18:04:12 -0800
From: "Scott Miller" <scott_at_opentrac.org>
Subject: [aprssig] Long messages
I've been reworking my old APRS IS parser, and I'm finding a lot of overly
long messages, like this one:
KD5YOV-14>APU25N,TCPIP*,qAC,AHUBSWE::KC4JGC :5.3 miles northeast of
Norfolk, VA --- Report received 15 minutes 59 seconds ago {21
The spec gives a maximum length of 67 characters for a message. That one is
81 characters, counting the trailing space. Was the spec revised at some
point, or do clients just ignore it? Makes it hard to know how big a
database field is required to store it...
Scott
N1VG
------------------------------
Message: 25
Date: Thu, 25 Jan 2007 20:19:31 -0600
From: Jason Winningham <jdw_at_eng.uah.edu>
Subject: Re: [aprssig] APRS telemetry and the PIC 16F877A
On Jan 25, 2007, at 4:57 PM, Dave Baxter wrote:
>There is nothing wrong with the Atmel chips, but the CPU
>architecure you could argue harks backwards in time,
Atmel has (at least) two architectures, the 8051 and the AVR. The AVR is a
fairly modern architecture, designed by some college students somewhere in
northwestern Europe, IIRC (Norway? maybe Sweden?). The 8051 is certainly
"mature". (:
>PIC's and RISC archetcture, looking forward by comparison?
Gotta watch the PICs because many, especially the low end devices, require
multiple clock cycles to execute a single instruction (in _spite_ of the
fact it's RISC). A 20MHz 16F628 is actually executing instructions at 5M
instructions/s, where the AVR family uses a single cycle per instruction,
so you're getting 16M instructions/s with a 16MHz device.
If there are free PIC compilers, it's happened since I gave up on them.
I'll stick with the AVR all the same.
To keep this on topic, a couple of years ago N4TXI built a tracker based on
the AVR called WhereAVR. It generated APRS packets ala TT/OT, but he also
implemented a zero crossing detector to _decode_ packets. He used it to
fire a cutdown mechanism on a high altitude balloon by sending a message
from his D7.
-Jason
kg4wsv
------------------------------
Message: 26
Date: Thu, 25 Jan 2007 18:39:16 -0800
From: "VE7GDH" <ve7gdh_at_rac.ca>
Subject: Re: [aprssig] Long messages
Scott N1VG wrote...
>I've been reworking my old APRS IS parser, and I'm finding a lot of
>overly long messages, like this one:
>
>KD5YOV-14>APU25N,TCPIP*,qAC,AHUBSWE::KC4JGC :5.3 miles northeast of
>Norfolk, VA --- Report received 15 minutes 59 seconds ago {21
>
>The spec gives a maximum length of 67 characters for a message. That one
>is 81 characters, counting the trailing space. Was the spec revised at
>some point, or do clients just ignore it? Makes it hard to know how big
>a database field is required to store it...
Looking at http://map.findu.com/KD5YOV-14 and
http://www.findu.com/cgi-bin/raw.cgi?call=KD5YOV-14&time=1
There's something odd going on. First, Bryan KD5YOV is asking over on the
UI-View list why he seen sometimes moving at fantastic speeds and showing up
off the coast of Africa. He is using a D700, sometimes with UI-View and
sometimes with the D700 "stand-alone" and apparently at other times using
"something else" as well that is beaconing to "GPS" with NMEA $GPRMC
sentences and also sometimes to "APK101"...
20070126015731,KD5YOV-14>APK101,WIDE1-1,KB4TOH-4,WIDE2*,qAo,KG7SB-3::KC4JGC
:SORRY I ONLY RESPOND WHEN UI-VIEW IS ON, AT THIS TIME IT IS OFF.
What sends to "APK101"? That might help track what down is sending the long
messages.
I hadn't noticed it before, but yes, that's a whole lot of characters. He
isn't having a UI-View problem in my opinion, so he might be better off
asking over on this list. I posted a reply to the UI-View list with my
observations a while back, but it hasn't been echoed back to me by the
list yet.
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 31, Issue 30
Read previous mail | Read next mail
| |
