[aprssig] APRS-WSPR APRS from anywhere!

[Robert Bruninga]

That's the question.  We mostly have to use standard messages.  So far, we
have all the ARRL radiograms, and 50 more we thought of.  Plus with the 5
bits remaining, we can have 32 more tables of 100 messages and 99 modifiers
each.  Literally tens of thousands of pre-canned messages to select from.

http://aprs.org/aprs-wspr.html

Bob

On Wed, Oct 12, 2016 at 3:58 PM, spam8mybrain <spam8mybrain at yahoo.com>
wrote:

> So is there any way to send anything else useful with this? You know, a
> free-text comment, an APRS symbol code, etc.
>
> I have to admit, I'm not much of a contester. If I contact someone, I want
> to be able to pass more information than just "contact made/confirmed". So
> how can WSPR or WSJT transport useful information for, say, an EmComm
> situation? Even APRS text messages can transport a reasonable amount of
> data over and above "contact made".
>
> Andrew, KA2DDO
>
>
> -------- Original message --------
> From: Robert Bruninga <bruninga at usna.edu>
> Date: 10/10/16 11:21 PM (GMT-05:00)
> To: Cory Vickruck <crvickru at lakeheadu.ca>
> Cc: TAPR APRS Mailing List <aprssig at tapr.org>, Earl Needham <
> earl.kd5xb at gmail.com>
> Subject: Re: [aprssig] APRS-WSPR APRS from anywhere!
>
>
> The total data is 55 bits. 7 for power, 15 for grid and 23 for callsign.
> bob
>
> On Mon, Oct 10, 2016 at 9:42 PM, Cory Vickruck <crvickru at lakeheadu.ca>
> wrote:
>
>> So from what I gathered you can send 22 characters total which includes
>> the callsign and grid square?
>>
>> On Mon, Oct 10, 2016 at 7:48 PM, Robert Bruninga <bruninga at usna.edu>
>> wrote:
>>
>>> Good point.  APRS WSPR would be like most APRS bulletins and status..
>>> Directed to ALL.
>>> But I think I will work on a simply possible QSO token.  A sender asking
>>> for a reply would include a QSO token in his message and then the resposner
>>> could use that token instead of a full call.
>>>
>>> Bob
>>>
>>>
>>> On Mon, Oct 10, 2016 at 1:52 PM, crvickru <crvickru at lakeheadu.ca> wrote:
>>>
>>>> I am currious about the messaging aspect of this technique. How would
>>>> yoy encode the destination of the message?
>>>>
>>>>
>>>>
>>>> Sent from my Samsung Galaxy smartphone.
>>>>
>>>> -------- Original message --------
>>>> From: Earl Needham <earl.kd5xb at gmail.com>
>>>> Date: 2016-10-10 10:42 AM (GMT-05:00)
>>>> To: Robert Bruninga <bruninga at usna.edu>
>>>> Cc: TAPR APRS Mailing List <aprssig at tapr.org>
>>>> Subject: Re: [aprssig] APRS-WSPR APRS from anywhere!
>>>>
>>>> For many years, I've suggested using high speed CW.  You could then use
>>>> just about any amateur radio frequency.  WSPR might have better decode, but
>>>> CW is the "old stand by".
>>>>
>>>> Vy 7 3
>>>> Earl
>>>> KD5XB
>>>>
>>>> On Sun, Oct 9, 2016 at 1:20 PM, Robert Bruninga <bruninga at usna.edu>
>>>> wrote:
>>>>
>>>>> The more I think about it the more I get excited about building up an
>>>>> APRS-WSPR Gateway system.  With the 27 dB signal processing gain of WSPR,
>>>>> then a 1W transmitter is the same as 1000 watts.  And for receive, since
>>>>> APRS can have HF receivers everywhere, then this can really expand the
>>>>> usefulness of APRS anywhere in the world including on the fringes of our
>>>>> existing network.
>>>>>
>>>>> QST in September showed the $29 TAPR WSPR daughter board that plugs
>>>>> onto a Rasberry pi and although it is only a 100 millliwatt transmitter,
>>>>> with enough WSPRgates, that should not be a problem.  But adding a 1W PA
>>>>> will always help!
>>>>>
>>>>> I already have come up with a compression technique that can improve
>>>>> on the existing gridsquare (60x120miles) down to (18x12miles) and down to 3
>>>>> miles or nearly a half mile for 5 and 4 letter calls.
>>>>>
>>>>> see http://aprs.org/aprs-wspr.html
>>>>>
>>>>> Lets get those WSPR boards on the air!
>>>>>
>>>>> Bob, WB4APR
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> aprssig mailing list
>>>>> aprssig at tapr.org
>>>>> http://www.tapr.org/mailman/listinfo/aprssig
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20161012/070d1f27/attachment.html>