| |
ZL3AI > APRDIG 11.09.06 01:01l 130 Lines 4933 Bytes #999 (0) @ WW
BID : 8744-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 27 #8, 1/1
Path: DB0FHN<DB0MRW<OK0PPL<DB0RES<ON0AR<VK6HGR<ZL2BAU
Sent: 060910/2253Z @:ZL2BAU.#87.NZL.OC #:3359 [Waimate] $:8744-ZL3AI
From: ZL3AI@ZL2BAU.#87.NZL.OC
To : APRDIG@WW
Today's Topics:
1. Re: Wi-Fi Positioning System (WPS) for APRS (Frank Olaf Sem-Jacobsen)
2. RE: Re: aprssig APRS Telemetry (Robert Bruninga)
3. RE: Wi-Fi Positioning System (WPS) for APRS (Ron Huisinga)
4. Re: aprssig APRS Telemetry (Andy AB9FX)
----------------------------------------------------------------------
Message: 1
Date: Thu, 07 Sep 2006 19:43:10 +0200
From: Frank Olaf Sem-Jacobsen <frankose_at_ifi.uio.no>
Subject: Re: [aprssig] Wi-Fi Positioning System (WPS) for APRS
Hi, I thought I'd toot my own horn a bit on this subject :)
There is an application for using google maps on cell phones, mobile Gmaps
(http://www.mgmaps.com/), which has the possibility to use a small
application from navizon (http://www.navizon.com/) for positioning, in
addition to internal GPS systems (jsr-179) and Bluetooth GPS receivers.
This works on a lot of cell phones, and also on the Windows mobile
platform. Navizon provides positioning either through GPS receivers,
through cell tower information, or WLAN access points, depending on the
capabilities of the mobile device. I'm not too into the navizon
application, but I assume it sends the information to a central database
and receives an approximate position.
Now, the interesting point is that I have become a co-developer of mgmaps,
responsible for implementing tracking features. I am almost done with the
process of porting my tracking code from my own application mAPRS to
mgmaps, which in addition to providing mapping services to display received
station also is a more stable platform for GPS communication.
This new version of mgmaps in combination with navizon will be able to
provide APRS tracking based on cellphone towers or WLAN accesspoint
information. It will hopefully be released by next week, so be sure to
check out the web page, www.mgmaps.com some time then. I will also
probably not be able to resist the temptation of sending another e-mail
when it is released ;)
p.s. I am not in any way affiliated with navizon.
--
Frank Olaf Sem-Jacobsen, LA3NMA
------------------------------
Message: 2
Date: Thu, 7 Sep 2006 17:41:09 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Re: aprssig APRS Telemetry
>>...I would like to build a table of all existing APRS
>>KPC-3+ telemetry 5-channel systems...
>
>It would need to have some user definable values to allow for what is
>dreamed up in the future
Let me clarify...We are only talking here about the existing APRS and
KPC-3+ telemetry format. Any user can use this format for any values he
wants now. All this effort is trying to do is to tabluate any existinc
comon uses, so that others can chose from among many existing parameter
selections used by others so as to not have to re-invent each new wheel for
each new application if someone already is using such a format.
>>Each of these would have a different APExxx version number,
>>so that decoding Systems can decode and display them
>>without any other knowledge...
>
>It might be easier to add something on the end of the
>Telemetry beacon to indicate which data set it is.
Ah, but that is why we are proposing this initiative. As it is, The KPC-3+
format is fixed and cannot be changed and nothing Can be added to the end
of it. Hence, the use of the "version Number" in the TOCALL format to
specify a specific common application (if any)...
>We use "Site Alert" on some of our digi's in VK3 the format is,
>Temp, Volts, Ptt Counts. The third and fourth values are time
>but this could be changed should I find a better use for them.
Can you send an example packet so we can see the format?
We will add that to the list...
Bob, WB4APR
------------------------------
[duplicate]
------------------------------
Message: 4
Date: Fri, 8 Sep 2006 00:41:21 -0500 (CDT)
From: "Andy AB9FX" <ab9fx_at_aprs.pl>
Subject: [aprssig] Re: aprssig APRS Telemetry
Bob,
I tried many times to change in KPC3+ TOCALL for telemetry at SR3DGT.
Whatever is put in the UNPROTO dest address, packets are sent with dest
address BEACON. Now, there is KPC3+ v9.1, before 8.3 and 9.0 with the same
results.
Some settings for our digi/wx/tlm with solar panel (only power source)
http://www.aprs.pl/gontyniec.htm
Analog telemetry: 1 - battery voltage, 2 - current from the solar panel, 4
- temperature inside of the KPC3+.
73!
Andy SP3LYR
----- Original Message -----
From: "Robert Bruninga" <bruninga_at_usna.edu>
>
>Ah, but that is why we are proposing this initiative. As it is,
>The KPC-3+ format is fixed and cannot be changed and nothing
>Can be added to the end of it. Hence, the use of the "version
>Number" in the TOCALL format to specify a specific common
>application (if any)...
------------------------------
aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
End of aprssig Digest, Vol 27, Issue 8
Read previous mail | Read next mail
| |
