| |
ZL3AI > APRDIG 28.01.07 14:17l 234 Lines 9014 Bytes #999 (0) @ WW
BID : 9637-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 31 #31, 2/4
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<F5GOV<F4BWT<IW2OAZ<ZL2BAU
Sent: 070128/0611Z @:ZL2BAU.#79.NZL.OC #:29607 [Waimate] $:9637-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 9
Date: Fri, 26 Jan 2007 00:23:21 -0500
From: "A.J. Farmer (AJ3U)" <farmer.aj_at_gmail.com>
Subject: Re: [aprssig] Digi's Still Using Relay When Should Be Using Bob's
New Format
On 1/25/07, Richard N. Piper IV <richard.piper_at_media4god.org> wrote:
>using RELAY when they should be using Bob's New Format for APRS. I noticed a
>station that for some reason has it's settings set to Wide/Relay/Trace as
>noted in it's becon comment (Station is LTRock) and in the becon coment it
>says that callsign is K5SCD.
I suggest that you drop K5SCD a message and let him know what's up. Let him
know you would like to help him update to the latest settings. Take a calm,
helpful approach and most people will welcome it. If he doesn't want to
play, don't fight it. Just let it go.
--
A.J. Farmer, AJ3U
http://www.aj3u.com
------------------------------
Message: 10
Date: Thu, 25 Jan 2007 21:42:25 -0800
From: "VE7GDH" <ve7gdh_at_rac.ca>
Subject: RE: [aprssig] Local Repeater Displays on Mobiles
Richard (callsign?) wrote...
>Ok question about how this would be set up using the UI-View Digi?
UI-View could put out such information as an object at the rate specified in
"object interval" which is in "miscellaneous setup". You could use the
frequency of the repeater for the name of the object. More info could be in
the object comment. Ask D7 / D700 users how well the comment would be
displayed.
73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"
------------------------------
Message: 11
Date: Fri, 26 Jan 2007 03:00:29 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Local Repeater Displays on Mobiles
>>Ok question about how this would be set up using the
>>UI-View Digi?
>
>UI-View could put out such information as an object at the
>rate specified in "object interval"...
Only if that Uiview was operating with a (0), none, hop path.
The problem with using a client program to generate these objects is that
the object will not have its own simplex, DIRECT PATH independent of the
normal path the client uses. SO the object will go out with the 1,2, or
more hop path that the client program is already using. This means the
Voice repeater object will go out to an area that is far larger (in most
cases) than the radio coverage area of the voice repeater itself.
This would make the object be SPAM and unwanted QRM to most surrounding
areas and the negative impact of this kind of SPAM into areas where the
information is not-valid would kill any benefit of having the object in the
first place.
I have seen some such repeater objects in the past while mobile, coming in
from the next state and over 100 miles away. Tuning in the repeater, it
was impossible to work, and so I was irritated at this false informaton
while trying to drive the car and tune the radio, only to find out it was
SPAM coming in from the next state due to a 2 hop path over the mountains.
Unless UIview can have a separate 0, no-hop path for these objects, then I
recommend against using a client program to send these objects.
The advantage of putting these objects into a KPC-3+ DIGIpeater's Btext, is
that the UNPROTO path (direct, 0 hops)for that beacon is independent of the
four LTPaths being used for the digipeater's own proportional-pathing
beacon.
If there is no other way to send these objects direct, then the best way is
to install a $25 APRS tracker at the voice repeater and let it generate
it's own object from its own location. Then you know for sure that the
coverage area of the repeater-object is the same as the RF coverage area of
the repeater.
Bob, WB4APR
------------------------------
Message: 12
Date: Fri, 26 Jan 2007 00:50:02 -0800
From: "VE7GDH" <ve7gdh_at_rac.ca>
Subject: RE: [aprssig] Local Repeater Displays on Mobiles
Bob WB4APR wrote...
>Only if that UI-View was operating with a (0), none, hop path.
Good point. The object would be going out with the path specified in the
station setup. Probably not very many stations that would want to change to
a no-hop path just to send out a local object.
>...then the best way is to install a $25 APRS tracker at the voice
>repeater and let it generate it's own object from its own location.
>Then you know for sure that the coverage area of the repeater-object
>is the same as the RF coverage area of the repeater.
That sounds like a reasonable solution, but it would be "extra' traffic if
the local digi is going to send it's own beacon minus the information about
the voice repeater in any case. However, that digi might not be at the same
location as the voice repeater. It definitely sounds like an option to be
considered though. Perhaps future hardware will be smart enough to listen to
the beacon about the repeater and automatically QSY your radio to the local
frequency if you want to allow it to. Alternatively, just use two repeater
pairs along major corridors and have adjacent repeaters alternate frequency
A, frequency B etc. That way you could just scan frequencies (A, B and of
course 652) and have everything covered. Just a thought.
73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"
------------------------------
Message: 13
Date: Fri, 26 Jan 2007 01:56:07 -0700
From: Earl Needham <needhame1_at_plateautel.net>
Subject: RE: [aprssig] Local Repeater Displays on Mobiles
At 01:50 AM 1/26/2007, VE7GDH wrote:
>Good point. The object would be going out with the path specified in
>the station setup. Probably not very many stations that would want
>to change to a no-hop path just to send out a local object.
You could run AGWPE and TWO instances of UI-View32 -- one for "regular"
use, and one simply to transmit the object(s).
7 3
Earl
KD5XB
Clovis, New Mexico DM84jk
http://groups.yahoo.com/group/cw_bugs
"Just say NO to DHL"
------------------------------
Message: 14
Date: Fri, 26 Jan 2007 11:35:44 -0000
From: "Dave Baxter" <dave_at_emv.co.uk>
Subject: RE: [aprssig] 220KISS
Thanks to Ian ZL1VFO. Also G8BPQ who stuck his head over the parapet, but
I seem to have mistakenly deleted his mail, so yes please BPQ, in case I
have a corrupted download from somewhere else Do you still have the
sources, if so, is it permitted to pass them on?
Ray.
Yes, according to a text file I found on the web somewhere, G8BPQ used
JKISS as the basis for 220KISS. I think he said that what I had, was
potentially the latest version, but as above, I seem to have removed his
mail by accident.
And yes, the 220 I built (board serial number 0011 I see) at first was
very unreliable, locking up and doing all sorts of odd things. However,
as the then importer of the kits was a personal friend, and he seemed to
have a good raport with Pac-Com, we were trying out different firmware
versions, and modifications. Not least, to prevent the backup battery
emptying premeturely, due to a design "Feature" built in by Pac-Com.
It eventualy became a wholy reliable workhorse, spending many years on
24/7 before I even had a dialup internet account, shoveling "email"
(such as it was) in and out in an automated way in conjunction with my
local packet BBS.
It recently (a year or so ago) found a new life as a portal to the
wwwconv system, again working well 24/7. Then I got ADSL installed, and
that is just far easier to use for that sort of thing, and leaves the
airwaves less conjested.
As a result of to say the least "variable" experience trying to use and
run APRS localy, what with all the conflicting path paradigms etc (don't
go there) and local digi's etc that are there one week, then vanish for
ever, I've decided to try and fill a hole in the digi coverage, and
perhaps provide a path out of this active area, to the next active
patch.
As I have three of these (one though I now find is very dead) I thought
at first I'll try to use them, hence scratching arround trying to get
KISS mode working. The hardware I trust, Ui-View I sort of trust and
know my way arround.
I also now have one or two single chip (PIC) designs with code for KISS
only TNC's but was trying the "quick" route to posible success, with at
the moment, a distinct lack of...
So perhaps time permitting (not a lot of that spare these days) I'll try
one of them. As well as a couple more attempts at KISSing a 220, just
in case..
73...
Dave 'wbx
>-----Original Message-----
>From: Ray Wells [mailto:vk2tv_at_exemail.com.au]
>Sent: Thursday, January 25, 2007 10:55 PM
>To: TAPR APRS Mailing List
>Subject: Re: [aprssig] 220KISS
>Hi Dave
>
>The binary used to ship with BPQ408. It's along time since I
>used BPQ but I vaguely recall a couple of versions of KISS
>for the TNC220 (was JKISS the other version?). What I do
>recall is that my TNC220 NEVER gave reliable results,
>regardless of the EPROM installed, and it's been gathering
>dust for near 15 years.
>
>The version of the binary I have is the same as yours.
>
>Ray vk2tv
------------------------------
Read previous mail | Read next mail
| |
