| |
ZL3AI > APRDIG 05.05.07 08:00l 249 Lines 9182 Bytes #999 (0) @ WW
BID : 10103-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 34 #24, 4/5
Path: DB0FHN<DB0FOR<DB0SIF<HB9EAS<DB0FSG<OE7XLR<OE2XUM<DB0WGS<OE6XPE<IW2OHX<
I0TVL<DK0WUE<F4BWT<F6KMO<7M3TJZ<ZL2BAU
Sent: 070505/0543Z @:ZL2BAU.#79.NZL.OC #:46304 [Waimate] $:10103-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 25
Date: Mon, 23 Apr 2007 20:56:49 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Voice repeater objects
Now that the format for Voice Repeater FREQUENCY objects has been nailed
down, we can see on FINDU that 75 of the 440 or so objects are in the new
FREQUENCY format. I have added a link to the bottom of the New-Initiative
web page so you can see the summary. Of course, these objects are LOCAL
and so may not be making it to an IGate:
http://www.ew.usna.edu/~bruninga/localinfo.html
If your local digi is not putting out this local info for visitors, please
see the above web page and contact your local DIGI sysop. It would be
nice to have most of these in place by the time of the great Dayton
Pilgrimage in 3 weeks.
This final format takes the input from many of you so that this final
format looks good on the D7, D700, HamHud, Uiview, etc. TO make it unique
for FINDU, requires that you chose 1 or two unique bytes on the end of your
frequency to make it globally unique. Letters from A-z and numbers can be
used yielding 3600 differrnt combos for 10 KHz repeaters and 62 combos for
5 KHz repeaters. I have chosen 147.105-D for our Local Davidsonville
repeater.
Use FINDU to see if yours is unique or is ping-ponging with some other
area. Here is ours: http://map.findu.com/147.105-D Bob,
WB4APR
>-----Original Message-----
>From: aprssig-bounces_at_lists.tapr.org
>[mailto:aprssig-bounces_at_lists.tapr.org] On Behalf Of Robert Bruninga
>Sent: Thursday, April 19, 2007 7:50 PM
>To: 'TAPR APRS Mailing List'
>Subject: [aprssig] Voice repeater objects
>
>Voice Repeater Objects:
>
>Now, as Alabama has begun adding Voice Repeater Objects to all
>of its 15 UIDIGI ROM digipeaters (thanks tim!), we have a lot of
>good feedback and have improved the text associated with the
>display formats. The "lines" refer to how the voice repeater
>object looks when received on a D7 or D700 10x10x8 display
>format. Here are some examples.
>
>1st line: is the FFF.FFF FREQUENCY (in place of callsign)
>
>2nd line: (actually beginning of Object text)
>
>T123 R45mi - Combines PL and Range on one line.
>D234 R45mi - Combines DCS code and Range on one line.
>N45, S15mi - No tone with different ranges N/S or E/W
>
>3rd Line: (begins w space if previous line uses 10
>
>Net 9pm W - if it has regular nets worthy of note
>Mtg 1st M - if it has regular meetings
>144.875in - optional for a non stndard input
>
>4th Line: (The first 8 bytes will show on the D700, more will
>show on PC clients...
>
>Also the DUPE issue on the APRS-IS has been resolved since we
>have these OBJECT NAME Formats:
>
>FFF.FFF-x - where x is one of 62 characters (A-z or 0-9)
>FFF.FF+xy - where xy is one of over 3600 combinations
>
>The +/- indicate offset.
>
>With all these options, surely all of the 146.94 repeaters can
>find a unique combination. And the way I see it, the first one
>that gets on the air, the better the choice. Though it would be
>nice to negotiate if there are conflicts. Now that these all
>appear on the APRS-IS, it is easy to see what is already in use.
>Just http://MAP.FINDU.COM/146.94* to see which ones are on the
>air!
>
>So all this is on the updated LOCAL-INFO-INITIATIVE web site:
>http://www.ew.usna.edu/~bruninga/localinfo.html
>
>If you are going to get your locally recommended best travelers
>voice repeater object on the APRS map, please do it before the
>big Dayton Pilgrimage!
>
>Thanks,
>Bob, WB4APR
------------------------------
Message: 26
Date: Mon, 23 Apr 2007 21:07:15 -0500
From: "Matt Werner" <kb0kqa_at_gmail.com>
Subject: Re: [aprssig] Tactical call signs
For digis I have seen and/or operate, the callsign IS in the packet. My
point is that it doesn't need to be in the 'from' field of the packet, just
somewhere IN the packet.
If retransmission of a message occurs without proper id of the station of
origin it isn't a violation - the first retransmitting station is liable
for any violations contained in the message though. The lack of ID isn't a
violation in itself unless the originating station never IDs. That isn't
the case here though as the callsign is in the packet.
In the end it's a dead issue as John was referring to the legality of
identifying the originating station by morse code ID.
------------------------------
Message: 27
Date: Mon, 23 Apr 2007 20:24:35 -0600
From: Joel Maslak <jmaslak-aprs_at_antelope.net>
Subject: Re: [aprssig] Tactical call signs
On Apr 23, 2007, at 8:07 PM, Matt Werner wrote:
>For digis I have seen and/or operate, the callsign IS in the packet.
>My point is that it doesn't need to be in the 'from' field of the
>packet, just somewhere IN the packet.
My reading of the regs in the US (they are different elsewhere) is that you
have to identify during a communication. You don't have to identify every
transmission - think about how you use a 2 meter repeater. It's not at the
packet level, it's at the "conversation" level. You don't say your call
sign every time you hit the release-to-listen button.
I look at this and feel that if someone is making an effort to make sure
that someone else knows who is transmitting, I am not going to be terribly
picky. Sure, I could yell at a repeater user who doesn't identify until 11
minutes into a repeater conversation, but I don't think that kind of
nit-picking does anyone any good.
As long as people would know who is transmitting, the intent of the law is
met. Yes, you should identify every 10 minutes, and, yes, you should think
of what is (and isn't) sent via IGates and digis.
>If retransmission of a message occurs without proper id of the station
>of origin it isn't a violation - the first retransmitting station is
>liable for any violations contained in the message though. The lack
>of ID isn't a violation in itself unless the originating station never
>IDs. That isn't the case here though as the callsign is in the
>packet.
Agreed.
------------------------------
Message: 28
Date: Tue, 24 Apr 2007 11:25:45 +0100
From: "Dave Baxter" <dave_at_emv.co.uk>
Subject: RE: [aprssig] Amateur spam
>IMHO the worst thing you can do is respond, as it proves to
>the spammer the address is valid!
>
>Jim
Not just your humble opinion, but the IT industry recommendation is just to
ignore it, and above all *NEVER* respond to it in any way!
Setup some filters in your mailer to divert it to a junk folder, or delete
it on receipt.
If you have the control, query your mail host for a header list *Before*
downloading any messages. Only download those you know or are expecting,
and delete the rest.
If you zap anything important by mistake, whoever that is will contact you
some other way.
Cheers.
Dave G0WBX.
------------------------------
Message: 29
Date: Tue, 24 Apr 2007 04:41:36 -0700
From: "Stan Horzepa, WA1LOU" <stanzapple_at_mac.com>
Subject: ADMIN: RE: [aprssig] Amateur spam
Please take this topic off the SIG. It is not related to APRS.
Thank you for your cooperation.
Stan Horzepa, WA1LOU
APRSSIG moderator
------------------------------
Message: 30
Date: Tue, 24 Apr 2007 09:23:05 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: [aprssig] FW: Garmin Rino protocol
Anyone want to continue with the RINO-to-APRS project?
-----Original Message-----
>From: spyke555_at_yahoo.ca
>Sent: Friday, April 20, 2007 3:16 PM
>Subject: Garmin Rino protocol
>
>.... I recently found your article on the Garmin Rino on-air
>protocol and found it most interesting. I was just wondering if
>you are still interested in persuling this at all?
>
>I've been looking at your recordings (both test and wav and
>found an algorithm that does a descent job at deciphering the
>peaks from the noise.
>
>My interest is somewhat different that yours though. You see I
>already have the GPS and the FRS radios, just looking to make a
>circuit that turns the two into a Rino of sorts. Yes I am aware
>there are trackers and anti-trackers that are currently
>available that will do essentially the same thing and then
>some... But I'm trying to do this as inexpensively as possible,
>and the simplicity of the Garmin on-air protocol does appeal to
>me as it would be very easy to implement in a PIC or similar
>device both for sending and receiving.
>
>At any rate, I've developed a little program that allows you to
>create your own wav files with control of every bit in the
>message. The thought here is that if one were to braudcast this
>out via an FRS radio, the Rino's listenning should decode and
>respond. Thinking this may be an interesting way to further dive
>into the protocol, assuming of course that the check-sum (if
>any) is not critical for accepting the message...
>
>My problem is that I don't have a Rino myself, so can't test
>this on my own... So I was wondering if you still had any
>interest in this and if you would be willing to try out the
>application?
>
>Do let me know, and I'll send it over!
>
>Sandy Pyke
>----------------------------------------------------------------
>
>Québec Secours - Commandant - District 10 (Montérégie)
------------------------------
Read previous mail | Read next mail
| |
