| |
ZL3AI > APRDIG 15.03.07 02:04l 247 Lines 9942 Bytes #999 (0) @ WW
BID : 9837-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 33 #3, 2/2
Path: DB0FHN<DB0MRW<DK0WUE<I0TVL<HS1LMV<SV1CMG<ZL2BAU
Sent: 070315/0043Z @:ZL2BAU.#79.NZL.OC #:37502 [Waimate] $:9837-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To : APRDIG@WW
Message: 7
Date: Fri, 02 Mar 2007 14:07:35 -0800
From: "Stephen H. Smith" <wa8lmf2_at_aol.com>
Subject: Re: [aprssig] Re:All APRS Digipeaters In The World (Almost!) Mapped
On UIview
bruninga_at_usna.edu wrote:
>I recommend that CLIENT software that wants to resolve multi-use
>symbols, should use the originally intended color atributes. Or
>at least draw a different color circle around the symbol if
>multiple meanings are intended. Such as the WHITE (or green)
>circle that both APRSdos and Uiview use around any station
>symbol that sends out an Igate status packet.
Huh?? UIview draws a blue square outline (not a filled box) around an
Igate.
>I wish Uiview had used WHITE, so that it could use a GREEN circle around any
>symbol that digipeats.
Used white for what?
------------------------------
Message: 8
Date: Fri, 2 Mar 2007 20:04:33 -0600
From: "Andy AB9FX" <ab9fx_at_aprs.pl>
Subject: [aprssig] Telemetry definition messages
I tried to find how often should be sent telemetry definition packets. Is
there any specific time?
I do some tests with new project called APRS Deluxe by Radek SQ2FOA. This is
hardware unit working as tracker, wx station, digi, and more. Among many
functions, one of them is telemetry. So far, five analog inputs are
available. In the Deluxe could be specified name, units, and coefficients
for every analog value. Monitor window displays all defined telemetry
values. Moreover, name, units, and coefficients are sent as APRS telemetry
parameter messages. So, every other station can know these telemetry
definitions.
In current beta version, messages are sent every time, right before
telemetry packet. I know this is not a good idea for regular work. So, we
are looking for proper rules regarding telemetry definition messages. In my
opinion, the best way would be special query to get them at request. But,
there is no such query in the APRS specification.
My tests with Deluxe are under AB9FX-8 callsign (all tlm data without
special meaning, just testing, except A2 - internal voltage)
http://www.findu.com/cgi-bin/raw.cgi?call=AB9FX-8&start=24&length=24
AB9FX-8>APFOA0,WIDE1-1,WIDE2-2,qAO,AB9FX::AB9FX-8 :PARM.,,I,T,F,,,,,,,,
AB9FX-8>APFOA0,WIDE1-1,WIDE2-2,qAO,AB9FX::AB9FX-8
:UNIT.LUX,V,A,DEG,HZ,,,,,,,,
AB9FX-8>APFOA0,WIDE1-1,WIDE2-2,qAO,AB9FX::AB9FX-8
:EQNS.0,1.9255,0,0,0.1,0,0,1,0,0,1,0,0,1,0
AB9FX-8>APFOA0,WIDE1-1,WIDE2-2,qAO,AB9FX:T#013,048,047,049,051,053,00000000Test
Screenshots of Radek's project http://sq2foa.republika.pl/ (link - APRS
Deluxe)
There is also a link to download project simulator running under Windows
http://sq2foa.republika.pl/deluxe_win.zip
After opening this program all navigation is available with arrows, Enter
and Esc. Telemetry monitor window by Esc from main view. Example packets
could be changed in the 'wynik.txt' file.
73!
Andy AB9FX
------------------------------
Message: 9
Date: Sat, 3 Mar 2007 15:06:31 +1100
From: "Warren Brown" <vk3byd_at_amsat.org>
Subject: [aprssig] grid square above 128m
Hi,
What is the difference between a normal grid square and one above 128m.
That's symbols /G v's /q
Thanks
Warren
VK3BYD
------------------------------
Message: 10
Date: Sat, 03 Mar 2007 11:30:13 -0600
From: Mark Cheavens <mcheavens_at_usa.net>
Subject: [aprssig] APRS I-Gates Mapping Idea
Here is an idea for plotting I-Gate coverage by station using the qxx
construct.
If you looked at each station that GATED someone, you could then plot the
last location of each station that the I-Gate posted to the database.
You could further refine the search by going back in each stations history
by x number of position reports to see if that I-Gate ever posted a
position and then plotting all those location. This would expand the
I-Gates station list significantly but would nice to see.
Here are some examples using my I-Gate in SW Colorado and some stations
that my I-Gate routinely post. My I-Gate antenna at the house is @ 30 feet
(above ground Ground elevation 8990 ft), but near the end of a Valley that
overlooks the high desert. Dollar is to the NW by 25 Miles of VERY rough
mountains, Harris 57 miles to the South, and Deza is 128 miles to the S,SW.
HARRIS>APN382,qAo,KC5EVE-14:!3638.34NS10746.50W#PHG4740/W4,NMn/N5DIG-3
Digi www.urfmsi.org
HARRIS>APN382,WIDE3-3,qAo,KC5EVE-14:!3638.34NS10746.50W#PHG4740/W4,NMn/N5DIG-3
Digi www.urfmsi.org
HARRIS>APN382,DEZA*,WIDE2,qAo,KC5EVE-14:!3638.34NS10746.50W#PHG4740/W4,NMn/N5DI3
G-
Digi www.urfmsi.org
HARRIS>APN382,DEZA*,WIDE2,qAo,KC5EVE-14:!3638.34NS10746.50W#PHG4740/W4,NMn/N5DI3
G-
Digi www.urfmsi.org
HARRIS>APN382,qAo,KC5EVE-14:!3638.34NS10746.50W#PHG4740/W4,NMn/N5DIG-3
Digi www.urfmsi.org
HARRIS>APN382,WIDE3-3,qAo,KC5EVE-14:!3638.34NS10746.50W#PHG4740/W4,NMn/N5DIG-3
Digi www.urfmsi.org
HARRIS>APN382,EUREKA,ANGFIR,METHOD,WIDE3*,qAR,K0QED:!3638.34NS10746.50W#PHG47404
/W,NMn/N5DIG-3
Digi www.urfmsi.org
HARRIS>APN382,WIDE2-1,qAo,KC5EVE-14:!3638.34NS10746.50W#PHG4740/W4,NMn/N5DIG-3
Digi www.urfmsi.org
DOLLAR>DHFYYX,WIDE2-2,qAo,KC5EVE-14:'sUcl #/]KC0RIA
DOLLAR>DHFYYX,WIDE2-2,qAo,KC5EVE-14:'sUcl #/]KC0RIA
DOLLAR>ID,qAo,KC0RIA-14:DOLLAR/R
DOLLAR>DHFYYX,WIDE2-2,qAo,KC5EVE-14:'sUcl #/]KC0RIA
DOLLAR>ID,qAo,KC0RIA-14:DOLLAR/R
DOLLAR>DHFYYX,WIDE2-2,qAo,KC5EVE-14:'sUcl #/]KC0RIA
DOLLAR>DHFYYX,WIDE2-2,qAo,KC0RIA-14:'sUcl #/]KC0RIA
DOLLAR>ID,qAo,KC0RIA-14:DOLLAR/R
DOLLAR>DHFYYX,WIDE2-2,qAo,KC0RIA-14:'sUcl #/]KC0RIA
DEZA>APN382,EUREKA,ANGFIR,METHOD,WIDE3*,qAR,K0QED:!3554.31NS10846.26W#PHG7640/WN
4,Mn/N5DIG-1
Digi www.urfmsi.org
DEZA>APN382,qAo,KC5EVE-14:!3554.31NS10846.26W#PHG7640/W4,NMn/N5DIG-1
Digi www.urfmsi.org
DEZA>APN382,qAo,KC5EVE-14:!3554.31NS10846.26W#PHG7640/W4,NMn/N5DIG-1
Digi www.urfmsi.org
DEZA>APN382,WIDE2-2,qAo,KC5EVE-14:!3554.31NS10846.26W#PHG7640/W4,NMn/N5DIG-1
Digi www.urfmsi.org
DEZA>APN382,qAo,KC5EVE-14:!3554.31NS10846.26W#PHG7640/W4,NMn/N5DIG-1
Digi www.urfmsi.org
DEZA>APN382,PORTER,LEMMON*,WIDE3-1,qAR,KC7GNM:!3554.31NS10846.26W#PHG7640/W4,NMN
n/5DIG-1
Digi www.urfmsi.org
DEZA>APN382,qAo,KC5EVE-14:!3554.31NS10846.26W#PHG7640/W4,NMn/N5DIG-1
Digi www.urfmsi.org
DEZA>APN382,qAo,KC5EVE-14:!3554.31NS10846.26W#PHG7640/W4,NMn/N5DIG-1
Digi www.urfmsi.org
DEZA>APN382,WIDE2-2,qAo,KC5EVE-14:!3554.31NS10846.26W#PHG7640/W4,NMn/N5DIG-1
Digi www.urfmsi.org
Example search would yield with the following parameters: (imagine
the database only contains the stations that are contained above in
either the from or the qxx location of Harris, Dollar, Deza,
KC5EVE-14, KC7GNM, K0QED, KC0RIA-14)
I-Gate Search back in records x times Stations heard
KC5EVE-14 1 Deza, Harris
KC5EVE-14 2 Deza, Harris
KC5EVE-14 3 Deza, Harris
KC5EVE-14 4 Deza,
Harris, Dollar
KC7GNM 1 -
KC7GNM 2 -
KC7GNM 3 -
KC7GNM 4 Deza
KC0RIA-14 1 Dollar
K0QED 1 -
K0QED 2 (thru 8) Harris
K0QED 9 Harris, Deza
In real life there are many more stations to parse for each I-Gate, but it
would be nice for me to know for each of my I-Gates how many station am I
the primary I-Gate for and how many stations I also gate for occasionally.
You could therefore also add search back x records and the I-Gate must show
up more than y times.
With that additional parameter if you use the same data set above
with a go back 8 records and the I-gate must appear 4 times (1/2 the
time) then the results would be:
KC5EVE-14 Deza, Harris
KC0RIA-14 Dollar
If the parameters were changed to 9 and 4 then KC5EVE-14 would pick up
Dollar as well.
Now for a coder to apply this!
AND Map the results! This is different from the #Hops to an I-Gate map.
Mark
KC5EVE
------------------------------
Message: 11
Date: Sat, 3 Mar 2007 13:00:01 -0500
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Telemetry definition messages
>I tried to find how often should be sent telemetry definition packets.
APRS has 3 network time standards for normal Human Ops:
- REGIONAL: refreshed within 30 minutes
- LOCAL/EVENT/DIRECT: refreshed in 10 minutes
- Not-Active: >80 minutes is not active.
These are the standard user expectations for valid, meaningful changing
data. Telemetry is usually a more routine, permanent and long term type
of system, so maybe it needs some consideration. Some telemetry is for
long term, and others for short term.
If the Telemetry is watchign the battery of special tracker in a race car,
then once every 10 minutes of data seems appropriate, and refreshing the
equations once every 30 minutes makes sense to me.
If the telemetry is watching river levels, then a once every 30 minute data
rate and a once every 2 hours refresh of the equations might be appropriate
DURING WEATHER ALERTS. But if it is watching something changine over
longer periods, then I woiuld do the equations once a day...
>opinion, the best way would be special query to get them at
>request. But, there is no such query in the APRS specification.
No, but a standard STATION Query to such a telemetry station would rightly
not only respond with its position packet, but also its definition packets.
Because someone making a query, clearly is a new station on the air, and
needs both.
Bob, Wb4APR
------------------------------
aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
End of aprssig Digest, Vol 33, Issue 3
Read previous mail | Read next mail
| |
